The hidden privacy risk of online PDF tools

Online PDF tools ask you to upload contracts, payslips, IDs and medical records to servers you know nothing about. This article explains what happens to those files and why browser-side tools eliminate the risk by design.

What uploading actually means

When you use a typical online converter, your file travels over the internet to their infrastructure, gets processed there, and is stored at least temporarily. Even with honest operators, that means copies exist on disks and backups you do not control. With dishonest ones, your documents may train datasets or leak in a breach.

The client-side alternative

Modern browsers can do the heavy lifting themselves. Libraries like pdf-lib and pdf.js read and rewrite PDFs using JavaScript and WebAssembly entirely on your device. No upload step exists, so there is nothing to leak, nothing to delete, and nothing to subpoena.

How to tell which kind of tool you are using

Watch the network: a client-side tool shows no large upload after the page loads. You can even disconnect from the internet and it keeps working. Also check the privacy policy for phrases like 'files are processed in your browser' versus 'files are stored on our servers for X days'.

A simple rule of thumb

If a document would embarrass you on the internet, do not upload it to a random tool with a .com and a green padlock. Process it locally, with PDFerret or any tool that can work offline.