Researchers: work with papers and data without uploading them
Unpublished manuscripts, peer reviews under embargo, datasets with personal data. Researchers handle sensitive PDFs daily. reader.me processes them in your browser, never on a server.
A researcher’s day is full of PDFs that aren’t supposed to be public yet. A manuscript under review. A grant proposal before submission. A paper you’re peer-reviewing under embargo. A dataset appendix with participant information that an ethics board signed off on under strict conditions. These aren’t just files; many of them come with formal obligations about who can see them and where they can go.
Then you need to do something ordinary with one. Merge the figures into the main text. Compress a heavy PDF so it fits a journal’s upload limit. Make a scanned reference searchable. The quick move is to find a free online tool and drop the file in. And that’s the moment the obligation quietly breaks, because that file just went to a server you’ve never vetted.
The problem with “just this once”
Confidentiality in research isn’t a vibe, it’s often a written condition. Double-blind peer review depends on the manuscript not leaking. Ethics approval for human-subjects data usually specifies how and where data is stored and forbids transfer to third parties. A pre-publication embargo is a contract with a journal.
A typical online PDF tool asks you to upload the document to its server, where it’s processed and, you’re told, deleted later. For a holiday photo, fine. For a manuscript you’re reviewing blind, or a dataset covered by an ethics protocol, “uploaded to an unknown third party and deleted on a timer you can’t see” is exactly the thing your agreements were written to prevent. You can’t promise a journal or an ethics board that the file stayed where it should if you’ve handed it to a server you don’t control.
How reader.me is different
reader.me runs the tools in your browser. There’s no upload step because there’s no server doing the work. The processing engine is loaded into the browser tab itself and runs on your own machine.
So when you compress a heavy PDF, the sequence is: your browser reads the file into memory on your laptop, does the compression right there, and hands you the result. The file is never transmitted. It’s the difference between using a workshop you’ve brought home and dropping your document through a stranger’s mail slot.
You don’t have to take that on faith. Open any reader.me tool, open your browser’s developer tools (F12), and watch the Network tab while you process a file. You’ll see no upload. Want to be completely sure? Turn off your Wi-Fi and do it offline. It still works, which is only possible because the file was never going anywhere.
The everyday jobs, done privately
The tasks researchers reach for most, all running locally:
- Compress for submission. Journal portals love to cap upload sizes. Compress a PDF down to the limit without shipping your unpublished manuscript to a compression service first.
- Make a scan searchable. An old reference or a scanned figure is just an image until you run OCR, which adds a real text layer so you can search and cite it. The scan never leaves your machine.
- Pull quotes and data out. Need the exact wording or the numbers from a source? Extract the text instead of retyping, locally.
- Assemble the final document. Merge the manuscript, figures, and supplementary material into one file for submission.
- Lock a draft before sharing. Sending a sensitive draft to a co-author? Protect it with a password and send the key separately.
A note on metadata
One thing worth a researcher’s attention: PDFs carry hidden metadata, including author names, software details, and sometimes revision history. For double-blind review that matters, because a manuscript that names you in its properties isn’t really blind. It’s a reason to be careful about what’s baked into a file before you submit it, and a reason to prefer tools that don’t add their own traces on top.
Why this fits how research already works
Researchers are trained to document provenance, follow protocols, and not cut corners with data. A tool that quietly uploads your files cuts against all of that. One that does the work on your own machine fits it. You keep custody of the document from start to finish, which is exactly what your agreements, your ethics approvals, and your own standards already ask of you.
Next time you need to compress a manuscript or OCR a reference, you don’t have to choose between getting it done and keeping your word. Open the PDF tools, do the job in your browser, and the file stays exactly where it’s supposed to: with you.