Is it safe to upload PDFs to online tools?

Short answer: Uploading hands a copy of the file to the service: it is stored and processed on their servers, under their retention rules. That is fine for public or harmless files, not for ID documents, contracts, medical or client files. Tools that work in your browser need no upload; the Network panel of your browser's developer tools shows what such a page actually sends.

Last updated:

Steps

  1. Open the tool and the developer toolsOpen the tool page. Press F12 (or Cmd+Option+I on a Mac) and choose the Network tab. Tick "Preserve log" so nothing is cleared.
  2. Clear the list, then use the toolClear the list. Choose a test file, run the tool and save the result — the whole job.
  3. Read every requestLook at every row that appeared after you chose the file: the domain, the full address including anything after "?", and the request body (Payload). Data can leave in a POST or PUT body, but also inside the address of a GET request, in small pieces, or over other channels such as WebSocket (filter "WS").
  4. Try it offline, and know what that showsRun the tool once, then switch the network off (or choose Offline in the Network tab) and run it again with another file. If it still works, the processing itself does not need a server. It does not prove that nothing is sent later, once the connection is back.

What happens when you upload

An online PDF tool that uploads works like this: your browser sends a copy of the file to the provider’s server, the server processes it, and you download the result. The copy then exists on infrastructure you do not control, for as long as the provider keeps it, possibly with sub-processors and backups. Even honest providers can be breached, misconfigured or compelled to hand data over.

None of that matters for a restaurant menu. It matters a lot for the documents people most often need to fix.

A rule of thumb

Usually fine to uploadThink twiceDo not upload
Public documents, brochures, published papersInternal documents, drafts, price listsID documents, passports, bank account details
Your own files with nothing personal in themDocuments with colleagues’ names and contact detailsContracts, HR files, medical records
Files your employer has rules aboutClient files you are bound to keep confidential
Anything containing passwords or access codes

When in doubt, use a tool that processes the file on your computer: a desktop program or a browser tool that does not upload. Also check what the file carries besides the visible pages — see what PDF metadata reveals.

How to check that a tool does not upload

Any tool can say “no upload”. Your browser shows what a page actually sends while you watch; the steps are above. What to look for:

  • Every request after you choose the file, not only large ones. Loading program files (.js, .wasm, language data) is normal. Look at the full address and the body of each request: file content or extracted text can travel in a request body, inside an address, or split into many small requests.
  • Other domains. Requests to the tool’s own site are expected; requests to other domains while you work deserve a closer look.
  • The offline test shows that the processing works without a server. An uploading tool fails it; a tool that works offline could still send something once you are back online, so it complements the request check rather than replacing it.

A check covers the version of the page and the steps you watched. Repeat it when a tool changes or when you use a function you have not checked.

What we see on our own tools

We recorded every request two of our tool pages made, from opening the page to the finished result (Chromium, 12 November 2026):

Tool pageRequests after choosing the filePOST/PUTOther domains
Redaction check with a 1-page test form3 × GET: the PDF reader’s program files00
PDF OCR with a 1-page scan7 × GET: program files of the PDF reader and the OCR engine, English language data00

None of these requests had a request body or anything after ”?” in its address. The tool pages also carry a content security policy that lets them connect only to this site. The details per request type are on network behavior. Please repeat the check yourself rather than taking our word for it.

If you have already uploaded something sensitive

  • Look up the provider’s retention and deletion policy; some offer a “delete now” button.
  • If the file contained passwords or access codes, change them.
  • For personal data of others, check whether your organisation must report it.

FAQ

The site says files are deleted after an hour. Is that enough?

It depends on the file. Deletion promises are hard to check from outside, and during that hour the file sits on someone else's server. For files you would not email to a stranger, use a tool that does not upload, or a desktop program.

Does "runs in your browser" mean nothing at all is sent?

No. Running in your browser does not by itself prove that the file stays local: a page can process a file in the tab and still send the file or its text somewhere. Only watching what the page sends (see the steps above) shows what happens, and even that covers only the time you watched. On this site the files are processed in the tab and not sent; the page still loads its program files from the site and may send usage statistics. The tool pages may only connect to this site, and the optional anonymous counts contain the page, its language, the tool and a result category — never file names, contents or search words.

Can a browser tool upload my file secretly?

Technically a web page can send anything it reads. That is why the check in the steps above matters: it shows what was actually sent, whatever the page claims.

Desktop app for Windows

The Windows installer has not been published yet. There is no download link on this site until it is.