PRACTICAL GUIDE
Is It Safe to Upload a PDF to an Online Tool?
What happens to a document after you drop it on a website, which questions are worth asking, and how to tell a local tool from an uploading one.
Last updated
The honest answer is: it depends entirely on the tool
The phrase 'online PDF tool' covers two completely different architectures. In the traditional one, your document is transmitted to a server, processed there, stored for some period, and offered back to you as a download. In the other, the page sends your browser some code and the whole operation happens on your own machine; the document never travels anywhere.
Both look identical from the outside. Both have a drop zone, a progress indicator and a download button. The difference matters enormously and is almost never stated on the page.
What a PDF can be carrying
This question is not paranoia, because the documents people merge and split are precisely the sensitive ones: contracts, payslips, medical letters, bank statements, passports and identity documents, tax returns, signed agreements. A PDF also often contains more than what is printed — the author name and software from whoever created it, revision timestamps, and in many cases the full text layer of a scanned page, searchable and extractable.
The questions worth asking about a server-based service
Where is the file processed, and under which jurisdiction. How long is it retained — 'deleted after one hour' is a policy, not a mechanism. Who at the company can access it while it is there. Whether the content is used to train anything. Whether the service is itself a reseller of someone else's API, which quietly adds a second company to every one of those answers.
None of these are unreasonable for a business to answer, and reputable services do. The problem is that most of the free tools at the top of the search results answer none of them.
How to check whether a tool is really local
You can verify this yourself in about thirty seconds. Open your browser developer tools, switch to the Network tab, then run the operation. If the document is being uploaded, you will see a request carrying a payload roughly the size of your file. If nothing of the sort appears, nothing was sent.
A second, blunter test: disconnect from the internet after the page has loaded and try the operation again. A tool that runs locally will carry on working. A tool that uploads will stall.
How our PDF tools work
Merging, splitting and image-to-PDF conversion here are performed by code running in your browser, using the pdf-lib library. There is no upload endpoint to send documents to. The library is bundled into the page rather than loaded from a third-party CDN, so opening the tool does not announce your visit to another company either. Both claims are visible in the Network tab, which is the point of making them.
Local is not a licence to be careless
Browser-based processing removes the network from the equation; it does not make a document safe in every other respect. The output still lands in your downloads folder on a machine that may be shared, backed up to a cloud service, or managed by an employer. And if your organisation has rules about where regulated documents may be handled, those rules apply to your browser too.
Frequently asked questions
Does a privacy policy saying files are deleted after an hour make it safe?
It is better than nothing, but it is a promise about behaviour you cannot observe. A tool that never receives the file has nothing to delete, nothing to leak in a breach, and nothing to hand over on request, which is a structurally stronger position than a retention policy.
Is HTTPS enough protection?
HTTPS protects the file in transit between you and the server. It does nothing about what the server does with the document once it arrives, which is the part people are actually worried about.
Can a browser-based tool handle large PDFs?
Within reason. Everything happens in your device memory, so very large files are limited by the machine rather than by a server. Our merge tool accepts up to 20 files and 100 MB in total, which covers the overwhelming majority of everyday documents.
Why do so many free tools upload files if it is not necessary?
Partly history — server-side processing was the only option for years — and partly business model. A server-side pipeline supports accounts, quotas and paid tiers. It is also simply easier to build once and reuse across every tool on the site.