Where your PDFs go when you drop them on a website
Dropping a contract on a free website means sending it to someone else's machine. That is not always true, and you can check the difference yourself in thirty seconds.
Published
The question nobody asks
An online PDF tool asks for a file and gives back a file. Something happens in between, and almost nobody asks what. That is understandable: the gesture is ordinary, free, and the result arrives in three seconds.
But that file is sometimes a contract, a payslip, a medical report, a document from a client's case. The question is worth thirty seconds.
Two architectures, two realities
There are only two ways to process a PDF on the web, and they have nothing in common.
In the first, your file leaves. It is uploaded to a server, processed there, and the result is sent back. That is the historical way, and it is necessary for some operations — converting a Word document needs a full office suite, recognising text needs an engine that will not fit in a browser.
In the second, nothing leaves. Processing runs in your browser, on your machine, with your processor. The site sent you code, not the other way round. This has become possible for most PDF manipulation, and it is what twenty of our twenty-nine tools do.
The difference is not a matter of trust or of contractual promise. It is a difference of architecture: in the second case there is nothing to promise, because there is nothing leaving.
How to check for yourself
Do not take our word for it — nobody should be taken at their word on this. Two checks, neither requiring technical skill.
The first: cut your connection. Open the tool page, wait for it to load, then turn off wifi or unplug the cable. Drop your file in. If the tool works offline, it is sending nothing, because it cannot send anything. Our browser tools pass this test; no uploading tool can.
The second: open the "Network" tab of your browser's developer tools (F12 on most), then run the job. You see everything that goes out. A file upload is immediately recognisable by its size.
Both checks work on any site, not only ours. They are the only honest way to settle it.
What does leave, here, and why
Seven of our tools do send your file, and we would rather say so plainly than maintain a convenient vagueness: conversion from Word, Excel and PowerPoint, text recognition, PDF/A conversion, file repair, and conversion from a web page.
None of these fit in a browser. They need an office suite, a recognition engine, libraries weighing hundreds of megabytes. Claiming otherwise would be a lie.
Those files are processed on machines in Europe, then deleted automatically. Every tool page carries a badge at the top saying which of the two families it belongs to. It is not fine print at the bottom: it is the first thing shown.
Why this matters beyond principle
For an individual it is a matter of preference. For a professional it is a matter of liability.
A lawyer filing a case document, an HR team handling a payslip, a medical practice moving a report, a public body preparing a named document: in each case, sending the file to a third party is a transfer of personal data. It has to be documented, justified, and depending on where the server sits, it gets complicated.
Processing that sends nothing makes the question disappear rather than answering it. There is no processor to enter in the register, no transfer outside the European Union to frame, no retention period to negotiate — because no data was transmitted.
This is not legal advice, and your data protection officer remains the only judge of your situation. But the technical distinction is sharp, and it survives the disconnected-network test.