Are Online PDF Tools Safe?
What actually happens when you drag a contract into a web converter — and how to tell the risky ones from the boring, private ones.
The real question: where does your file go?
Most "online PDF tools" follow the same architecture: your browser uploads the document to their server, the server processes it, and a download link comes back. That means three real risks, in order of practical importance:
- Copies you can't un-send. Uploaded files live on someone else's disk for at least as long as processing takes. Retention policies vary from "minutes" to "until we're hacked"; you have no way to verify any of them.
- Their terms apply. Many free services grant themselves broad licences to processed content while it's on their infrastructure.
- Confidentiality obligations. If the document falls under NDA, GDPR, HIPAA or internal policy, uploading it to a random converter may already be a reportable incident.
How to check a tool before trusting it
| Signal | Server-based (file leaves your device) | Client-side (file stays) |
|---|---|---|
| Network tab during use | Upload of the whole file | Only page assets loaded; no file traffic |
| Works with network off? | No | Yes, after loading |
| Size limits | Free-tier caps (10–100 MB) | Your RAM, effectively none |
| Processing speed | Upload-time bound | Instant to seconds |
| Privacy claim | "We delete after N hours" | "We never receive it" — verifiable |
The fastest check: open your browser's developer tools, watch the Network tab while adding a file. If the file itself never appears in the request list, it never left your machine.
Where PDFeather sits
Every tool on this site — merge, split, compress, convert and the TOC generator — is client-side JavaScript. Your documents are read into browser memory, processed there, and written back out by the same browser. There is no upload endpoint, no temporary server copy, nothing to breach. You can verify it with the Network-tab test above in under a minute — and you should; "trust but verify" is the right posture for every tool, including this one.
Rules of thumb
- Public, non-sensitive documents: any reputable tool is fine, including server-based ones.
- Contracts, IDs, payslips, medical or legal papers: client-side or offline only.
- When a policy (NDA/GDPR/HIPAA) applies: client-side, or ask before uploading anything anywhere.
- Desktop alternatives exist for everything — the private merge guide covers the offline landscape for one common task.