Is it safe to use free online PDF tools?
It's a fair question to ask before dragging a tax form, a signed contract, or a scan of your ID into a random website. Most "free online" file tools work by uploading your document to a server somewhere, and it's worth understanding exactly what that means before deciding whether it matters for a particular file.
What "online tool" usually means
For most PDF and image tools, "online" means your file is uploaded to the provider's server, processed there, and the result is sent back for you to download. That means the file physically leaves your device and transits the network, and it sits, even briefly, on infrastructure you don't control. You're trusting that provider's retention policy, its security practices, and often its business model: a "free" service still costs something to run, and it's worth asking how it actually makes money.
When it actually matters
Not every file needs this level of caution, a public flyer or a screenshot for a forum post isn't sensitive, and using any reasonably reputable online tool for it is fine. The calculus changes for anything that identifies you or exposes financial, medical, or legal information: tax documents, signed contracts, ID scans, medical records, anything with a signature or an account number on it. For those, the question isn't really "is this particular provider trustworthy", it's "why take on any upload risk at all when a client-side tool removes the question entirely."
What "runs in your browser" actually means
Client-side processing is a different architecture. JavaScript running in the browser tab you're already looking at reads the file using your device's own CPU and memory, and never sends the file's contents anywhere over the network. This isn't a euphemism, it's a verifiable technical claim, which is the important part.
How to verify a tool's claims yourself
Don't just take a privacy claim on faith, most modern browsers make it easy to check:
- Open developer tools (F12 in most browsers) and switch to the Network tab.
- Use the tool on a file and watch the Network tab while it processes. If a request goes out that's roughly the size of your file, it's being uploaded somewhere, whatever the marketing copy says.
- Alternatively, load the tool's page fully, then disconnect from Wi-Fi or mobile data and try using it. If it still works with no connection, nothing is being sent to a server, it can't be, there's no connection to send it over.
Where this site stands
Every tool here runs entirely client-side, using the open-source pdf-lib and pdf.js libraries, which are hosted on this site rather than fetched from a third party at runtime. There's no server for these tools to upload to in the first place. What data is (and isn't) collected beyond that is laid out plainly in the Privacy Policy, as of this writing, that's nothing: no analytics, no accounts, no cookies.
See it for yourself
Browse the toolsFrequently asked questions
Can I trust a tool just because it says it doesn't store my files?
Be a little skeptical of that phrase specifically. "We don't store your files" can still mean the file was uploaded, processed on a server, and then deleted, which still involved a transmission over the network. Client-side processing, where the file never leaves your device, is a stronger and more verifiable guarantee.
Does this mean cloud-based PDF tools are always unsafe?
No. Reputable services with clear security practices, and enterprise contracts with real accountability, can be perfectly reasonable for everyday documents. The calculus changes for genuinely sensitive material, where avoiding the upload entirely removes a whole category of risk.
How can I tell if a tool is really processing files client-side?
Open your browser's developer tools (F12), go to the Network tab, and use the tool while watching for any request that sends your file's data out. Or simpler: load the page, then disconnect from the internet and try using the tool, if it still works, nothing is being uploaded.