What Happens to a PDF You Upload to an Online Converter

“Deleted after one hour” describes a policy, not a mechanism. Here is how to tell the difference.

In short

  • Most online PDF tools process your file on their servers, not in your browser.
  • "Deleted after one hour" describes a policy, not a technical guarantee.
  • You can test whether a tool is genuinely local in about ten seconds.

The question is not whether these services are run by bad actors — the large ones are legitimate businesses with real security teams. The question is whether handing them a copy of a specific document is a decision you would make deliberately, if anyone had asked you.

What "online PDF tool" usually means

In the common design, your file is uploaded to a server, placed in a processing queue, converted by software running there, and offered back as a download link. Between those steps the document exists as a file on someone else's disk, and typically also in temporary storage, in a CDN cache, and in operational backups.

Providers describe this honestly enough in their privacy policies — files removed after an hour, or a day, or on demand. Those statements are commitments rather than mechanisms. They depend on the retention job running correctly, on backups being purged on schedule, on sub-processors honouring the same terms, and on the company not being acquired or breached in the meantime. None of that is paranoid; it is just the ordinary set of things that can go wrong with data you no longer control.

Documents where this actually matters

Nobody needs to agonise over a restaurant menu. The calculation changes for:

The ten-second test

You do not have to take anyone's word for it, including ours.

  1. Load the page

    Open the tool normally and let it finish loading, including any libraries it fetches.

  2. Disconnect from the internet

    Turn off Wi-Fi, or use your browser's developer tools to switch the network to offline mode.

  3. Use the tool

    Add a file and run it. If it completes and gives you a download, the processing happened on your machine — there was no network available to send anything over. If it hangs or errors, the file was going somewhere.

A second check for the curious: open the Network tab in developer tools before running the tool. A local tool shows no request carrying your file. An uploading tool shows a large POST at the moment you press the button.

Why local processing is possible now

This is not a moral achievement, it is a technical shift. Modern browsers can read files from disk into memory, decode and re-encode images through the canvas API, run PDF parsers compiled to WebAssembly, and hand a generated file back as a download. Mature open-source libraries — pdf-lib for constructing and rewriting documents, Mozilla's PDF.js for rendering them — do the heavy lifting. Ten years ago the server was necessary. For merging, compressing, and re-rendering, it no longer is.

The honest limits are worth stating too. Browsers cannot faithfully convert Word, Excel, or PowerPoint files, because that requires a full office rendering engine; any site offering it is doing the work remotely. Very large documents are constrained by your device's memory. And OCR, while possible in a browser, is slow enough that most sites do it server-side.

A short checklist before you upload anything

Test us with the same method

Load any tool on this site, go offline, and keep working. Nothing here needs a connection once the page has loaded.

Open the tools →