Are online PDF tools safe? What actually happens to your file

People upload remarkable things to free PDF sites: signed contracts, tax returns, passport scans, medical letters, entire employment files. Usually nothing bad happens. But “usually nothing bad happens” is a weak position to hold with documents like those, and most people have never been told what the alternatives are.

This is an honest look at the risk, including where we think it is overstated.

The two architectures

Every online file tool works one of two ways, and the difference decides everything else.

Server-side. Your file is uploaded to the company’s servers, processed there, and the result is sent back. This is how most of the well-known PDF sites work. Your document exists, however briefly, on a computer you do not control.

Client-side. The tool sends your browser a program, and your browser does the work locally. The file never leaves your device. This is possible today because browsers became genuinely capable — WebAssembly means a browser can run the same PDF and image libraries a server would.

Both can be run responsibly. But only one of them can make a promise that does not depend on trust.

What actually happens server-side

Let us be fair rather than alarming. A reputable server-side service typically:

• transfers your file over an encrypted connection;
• processes it and deletes it within a fixed window, often an hour;
• does not read it, and has no commercial interest in doing so.

The realistic risks are not usually a company reading your divorce papers for entertainment. They are structural:

The file exists somewhere else, on someone else’s disk, for a while. During that window it is covered by their security, not yours. Breaches happen to careful companies.

“Deleted within an hour” is a policy, not a mechanism. You cannot verify it. It may be true, it may be aspirational, and it may not survive a backup system nobody thought about.

Policies change, companies get acquired. The terms you agreed to are not the terms that will apply forever, and nobody emails you when they change.

Some services are not reputable at all. A free tool with no company behind it, running ads from networks you have never heard of, has no reputation to protect.

And for some documents, the risk is not really about the company: if you handle client, patient, or employee data, uploading it may breach your own obligations under GDPR, HIPAA, or your employment contract — regardless of how well-behaved the service is. Many people doing this at work do not realise they are making a data-transfer decision on their employer’s behalf.

What client-side changes

If the file never leaves your device, most of that list stops applying. There is no upload to intercept, no copy to breach, no retention policy to trust, and no cross-border transfer to justify.

This is worth being precise about, because it is easy to overclaim. Client-side processing does not make you safe from everything. The page still comes from a server, so you are trusting that the code sent to your browser does what it says. A malicious site could ship JavaScript that uploads your file anyway.

The difference is that this is checkable, and it is checkable by you. A retention policy is a promise; network traffic is a fact.

How to check for yourself

This takes about thirty seconds and works on any site, including ours.

1. Open the tool’s page.
2. Press F12 to open developer tools, and choose the Network tab.
3. Use the tool normally — pick your file and run it.
4. Watch the list of requests.

If your file is being uploaded, you will see a request with a size comparable to your file, usually a POST. If the tool is genuinely client-side, you will see the page’s own assets load and then nothing of any size while the work happens.

You can also just disconnect from the internet after the page loads. A client-side tool carries on working. A server-side one cannot.

We would rather you did this to us than took our word for it.

Practical advice

For genuinely sensitive documents — anything with financial details, health information, government identifiers, or other people’s personal data — use a client-side tool, or desktop software, or your operating system’s built-in features. Do not upload.

For routine documents, a reputable server-side service is a reasonable risk, and it is the only option for some tasks. Converting a complex Word document to PDF properly still needs a server, and any site claiming otherwise is either doing it badly or not doing what you think.

At work, check before uploading anything belonging to your employer or their customers. “I did not know” is not a defence that has ever gone well.

Regardless of tool, be wary of anything demanding an account, an email address, or a payment method to perform a basic file operation, and be more wary of anything that installs software to do it.

Where we stand

Every tool on PDFCasa today runs entirely in your browser, for the reasons above. For exactly what that means in practice, and how to check it yourself in under a minute, see how PDFCasa works.

You can start with merge PDF, split PDF, or compress PDF.