Handling Sensitive PDFs: Local Processing vs Uploading

Tax returns, payslips, medical letters, contracts, passport scans – the PDFs people most often need to merge, split or shrink are also the ones they least want to hand to a stranger. This guide explains what actually happens to your file with different kinds of online tools, how to check a tool's claims yourself, and what else to look at before a document leaves your hands.

What happens when you upload a PDF

Many online PDF services work by uploading your document to their servers. The file travels over an encrypted connection, is stored at least long enough to be processed, and the result is stored again until you download it. That model is not wrong in itself, and reputable services describe it in their privacy policies. But it means that:

What local, in-browser processing means

A browser-based tool does the work on your own device. The website delivers program code – JavaScript – and your browser runs it. When you choose a file, it is read from your disk into the memory of that browser tab, processed there, and the result is handed back to you as a download. The server never receives the document.

PDF Hut works this way. Merging, splitting, compressing, watermarking and building PDFs use the open-source pdf-lib library; reading text and rendering pages to images use Mozilla's PDF.js. Both libraries are downloaded from public content-delivery networks when you open a tool page. Nothing is stored after you close the tab.

How to verify a tool really works locally

Don't take any website's word for it – including ours. Two simple checks work on any computer:

  1. Watch the network. Open your browser's developer tools (F12, or Cmd+Option+I on a Mac), switch to the Network tab and then run the tool. An upload shows up as a request – typically a POST – whose size is similar to your file. With a local tool you will see no such request; you may see ads or library files load, but nothing that carries your document.
  2. Go offline. Open the tool page, wait for it to load completely, then switch off Wi-Fi or unplug the network. Run the tool. PDF Hut's pdf-lib-based tools – such as Merge PDF, Split PDF or Add Watermark – keep working, because everything they need is already in the page. (The PDF.js-based tools fetch an extra worker file the first time they run, so test those with the network check instead.)

A tool that stops working offline is not necessarily uploading your file, but a tool that keeps working offline cannot be sending it anywhere during that run.

Local doesn't mean risk-free

Processing on your own device removes the biggest risk, but a few others remain, and they apply to every website:

Before you share: what a PDF can reveal

The visible pages are only part of a PDF. Before sending a sensitive document, check these:

Mark the copies you hand out

When you have to send a copy of a passport, driving licence or bank statement – to a landlord, an employer or a service provider – it is commonly recommended to label the copy with who it is for, what it is for and the date, for example "For XYZ Lettings, rental application only, Sep 2026". A copy marked like this is much less useful to anyone who later tries to misuse it. Add Watermark stamps such a line across every page in a few seconds; converting the result to images and back afterwards makes it considerably harder to remove.

A short checklist

  1. Prefer tools that process files locally, and verify it with the network or offline test.
  2. For highly regulated documents, use approved offline software.
  3. Close other tabs and use a window without extensions for very sensitive files.
  4. Check document properties, comments and form data before sharing.
  5. Test redactions with a text extractor.
  6. Watermark copies of identity documents with recipient, purpose and date.
  7. Clear downloads on shared computers.