Is it safe to use free online PDF tools?
"We delete your files after an hour" is a policy someone chose to follow. Whether a tool needs that policy at all is an architecture someone chose to build — and only one of those two things you can actually verify.
The question most sites never quite answer
Search for almost any PDF tool and the results are dominated by sites that upload your file to a server, process it, and hand back a download link. Most of them post a privacy policy promising the file is deleted afterward — after an hour, after 24 hours, "immediately."
That promise might be entirely true. It also might not be, and there's no way to check from the outside — you're trusting a policy, not observing a fact. For a tax return, a signed contract, a medical form or anything with someone else's personal information on it, that's a real question worth actually answering rather than trusting a footer link.
The distinction that actually matters
There are two entirely different classes of tool here, and the difference isn't in what they promise — it's in what's technically possible.
A server-based tool receives your file over the network, no matter what it does afterward. The upload itself is the exposure: it happened, it's logged somewhere at the network level even if the application never stores the file, and it's a step that a client-side tool skips entirely.
A genuinely client-side tool runs the whole operation — parsing, editing, re-encoding — inside your browser using JavaScript and WebAssembly, the same technology that lets a browser display a PDF at all without a plugin. Your file is read from disk into memory, processed there, and handed back as a download. It's not that the file is deleted quickly; it's that there was never a request carrying it to delete data from in the first place.
How to check which kind of tool you're looking at
This doesn't require reading source code, and it takes under a minute:
- Open your browser's developer tools (F12 or right-click → Inspect) and switch to the Network tab before using the tool.
- Use the tool normally — upload or drop a file, run the conversion.
- Watch what appears in the Network tab. If you see a request carrying your file's data leaving the page, it's server-based, whatever the site's copy claims. If you only see the page's own initial scripts load and then nothing while you work, it's genuinely local.
- For a stronger version of the same test: load the tool, then disconnect from the internet entirely (turn off Wi-Fi), and try using it. A client-side tool keeps working with no network at all. A server-based one breaks immediately.
Why this is worth checking even for "unimportant" files
It's tempting to reserve this kind of scrutiny for obviously sensitive documents and not bother for a school assignment or a résumé. But a surprising amount of everyday paperwork carries something worth protecting once you look closely — a résumé has a home address and phone number, a filled-in form has a signature, a scanned receipt has a card's last four digits. The habit of checking costs a minute; the alternative is trusting a policy you have no way to verify, for files where you often can't tell in advance which detail turns out to matter.
Frequently asked questions
If a site says it deletes files after an hour, isn't that safe enough?
It might be true, but it's a policy you're trusting, not something you can verify. The upload itself already happened regardless of what's promised afterward — a tool that never uploads at all skips that exposure entirely.
How can I tell if a PDF tool actually uploads my file?
Open your browser's developer tools, go to the Network tab, and use the tool. If your file's data leaves the page as a request, it's uploaded. A genuinely local tool shows no such request at all.
Does 'client-side' just mean the button is on a webpage?
No — it specifically means the processing happens inside your browser using JavaScript and WebAssembly, with no server involved at any point. Confirm it with the network-tab check above rather than taking the label on faith.
Is a client-side tool slower than a server-based one?
Sometimes marginally, depending on your device — but it also means no upload time, no queue, and it keeps working with no internet connection at all.
What's the strongest way to test if a tool is really local?
Load the page, then disconnect from the internet entirely and try using it. A genuinely client-side tool keeps working; anything server-based fails immediately.