Search for “merge PDF” and almost every result does the same thing: you pick a file, a progress bar appears, the file travels to a server, the server does the work and sends a result back. It is fast, it is free, and it usually says something reassuring about deleting your file within an hour.
For a holiday photo, none of this matters. For the documents people actually merge and convert, it matters more than the page admits.
What you are handing over
Think about what goes through a PDF merger on a normal weekday: a signed rental contract, a payslip, a medical report, a tax assessment, an invoice with full bank details, a passport scan for a visa application. Each one contains data you would not email to a stranger.
When the file goes to a server, three things become true at once. A company you have never heard of holds a copy. That copy sits on infrastructure whose location and jurisdiction you do not know. And the promise to delete it is a sentence on a web page, not something you can verify.
None of this requires bad intent to go wrong. Backups outlive deletion policies. Servers get breached. Companies change owners, and the new owner is not bound by the old privacy page in the way you might assume.
When it genuinely does not matter
Being proportionate is more useful than being paranoid. Upload tools are fine for content that is already public or has no personal data: a product photo you are about to publish, a public PDF brochure, a screenshot of a landscape, a meme.
The line worth drawing is simple. If the file contains a name, an address, a bank detail, a signature, health information or anything a court would call personal data, it should not leave your device for a convenience task that a browser can do locally.
For businesses in the EU there is a second reason. Sending personal data to a third-party processor is a data transfer under the GDPR. A proper setup needs a data processing agreement with that provider. Almost nobody signs one with a free PDF site before dragging a client contract into it.
How to tell the difference in ten seconds
A page that processes files locally will say so, but so will pages that do not, so trust the network instead of the copy.
- Open the page and press F12 to open developer tools.
- Go to the Network tab.
- Use the tool with a small test file.
A local tool produces nothing in that list beyond the page’s own assets. An upload tool shows a request carrying your file, usually a POST with a size close to the file’s own.
A second signal is behaviour. If a tool works after you switch off your internet connection, it is local. If it shows a spinner and then an error, it was never local.
What local tools cannot do
Being honest about the trade-off matters. Browser-based tools cannot do everything.
Some formats need decoders browsers do not have. Apple’s HEIC photos are the common example, which is why almost no browser tool converts them. Very large files are limited by your device’s memory rather than a server’s. And anything that needs to reach another service, like fetching a web page or sending an email, needs a server by definition.
Heavy operations also run at the speed of your own hardware. Merging forty scanned PDFs on a five-year-old phone will be slower than on a server farm. The trade is that nothing leaves the phone.
The practical rule
Use a local tool when the file is yours and private, which covers most contracts, invoices, applications and anything with a name on it. Use whatever is convenient for files that are already public.
And if a tool cannot tell you where your file goes, treat that as the answer.