Skip to content

Is it safe to use online PDF tools? Why in-browser processing is private

By the PDFSherpa team ·

Short answer: most online PDF tools upload your file to their servers to process it, so its safety depends on trusting a company you can’t audit. Tools that process files in your browser, like PDFSherpa, never send the document anywhere. That removes the main risk entirely, and you can verify it yourself.

What happens when you upload a PDF

On a typical upload-based PDF site, your document:

  1. travels over the internet to the provider’s server (usually encrypted with HTTPS, which is good);
  2. is stored on their disk while it’s processed, sometimes on third-party cloud infrastructure in another country;
  3. is kept for a retention period, often an hour to a day, sometimes longer for “recent files” features;
  4. may appear in logs, backups or analytics, depending on how the service is built.

None of this is necessarily malicious. But each step is a place where a misconfiguration, a breach or an over-curious employee could expose your bank statement, passport scan or medical report. You’re relying on their promises, and you have no way to check them.

What in-browser processing means

Modern browsers can run serious software through JavaScript and WebAssembly. PDFSherpa uses this to run real PDF engines, pdf-lib, Mozilla’s pdf.js and Ghostscript, directly on your device. When you compress or merge a file, the bytes are read from your disk into the page’s memory, processed there, and handed back to you as a download. There’s no server step, because there’s no server that could receive the file.

How to check any tool yourself

  • The airplane-mode test: load the tool page, switch off your internet, then process a file. If it works, it’s local. PDFSherpa passes this test once its engines are cached.
  • The network test: on a computer, open developer tools → Network, clear the list, then process a file. Look for large outgoing requests (POST or PUT) around your file’s size.
  • Read the privacy policy: look for “retention”, “delete after” or “upload”. Those words mean files go to a server.

Remaining risks, honestly

  • Your own device: local processing can’t protect a device that already has malware. Keep your browser and system updated.
  • Downloads: processed files go to your Downloads folder like any other file. Delete them when you no longer need them.
  • Ads and analytics: PDFSherpa may show ads that set cookies. They never see your files, but they’re part of the page. See our privacy policy.
  • Password strength: Protect PDF uses standard 128-bit PDF encryption, which is good against casual access but not a substitute for a strong password.

A simple rule

If a document would hurt you if it leaked, such as IDs, contracts, financial or medical records, use tools that process it locally, or desktop software. For everything else, upload-based tools from reputable companies are a reasonable trade-off. With PDFSherpa you don’t have to make that trade-off.

Try it now: free and private

These tools run in your browser. Your files never leave your device.

Frequently Asked Questions

How can I verify that PDFSherpa doesn’t upload my files?
Open your browser’s developer tools (F12), go to the Network tab, then use a tool. You’ll see the page’s own code and libraries load, but no request carrying your file. You can also turn on airplane mode after the page loads and the tools still work.
Does PDFSherpa collect anything at all?
The site may show ads from Google AdSense, which uses cookies as described in our privacy policy. Your files and their contents are never collected.
Are upload-based PDF sites dangerous?
Not necessarily. Many reputable services delete files after a few hours. But you have to trust their security, retention and staff, and you can’t verify any of it. Local processing removes that trust requirement.

More guides