Is it safe to upload PDFs to free online tools?
Short answer: for anything confidential, you shouldn't have to ask — because uploading is unnecessary. Here's what actually happens, and the alternative.
What “free online PDF tool” usually means
Nearly every well-known PDF site works the same way: your file is uploaded to their servers, processed there, and handed back as a download link. The site's privacy promise — however sincere — is a policy, not a property of the system. Policies change, companies get acquired, servers get breached, and retention rules are invisible to you. If the document is a lease, that's probably fine. If it's a client contract, a medical record, or an HR file, the upload itself may already breach your obligations.
The alternative: tools with nowhere to upload to
Browsers can now run real document engines locally via WebAssembly. Every tool on this site — merge, compress, redact, sign, unlock — runs entirely in your browser tab. Our server serves the app and can't do anything else: there is no endpoint that accepts files, and the site's security policy blocks it from contacting any other server. You don't have to trust that claim — here's how to verify it in 30 seconds.
Frequently asked questions
What happens to my file when I upload it to a free PDF site?
It is transmitted to the company's servers, processed there, stored at least temporarily, and covered by whatever their privacy policy and retention rules say today. Most reputable sites delete files after a period — but you are trusting a policy you can't observe, applied by a company you can't audit, in a jurisdiction you may not know.
Is that actually a problem for normal people?
For holiday photos, no. For anything covered by confidentiality — client contracts, medical records, immigration files, payroll, unreleased financials — the upload itself can be the violation, regardless of what happens to the file afterwards. Many professional obligations (attorney-client privilege, HIPAA, NDAs) don't have a 'but the website said it deletes files' exception.
How can a website process PDFs without uploading them?
Modern browsers can run real software — the same kind of engines desktop apps use — via JavaScript and WebAssembly. The page you load IS the program; your file goes from your disk into your browser's memory, gets processed there, and comes back out as a download. No server is involved in the processing at all.
How do I verify a tool really works this way?
Two checks anyone can do: open your browser's developer tools, watch the Network tab while processing a file — there should be zero requests. Or load the page, turn on airplane mode, and use the tool: if it still works, there is provably no server involved.