Are online PDF tools private? How to tell where your file actually goes

The difference between browser-based and server-based PDF tools, how to check in under a minute, and a safe workflow for passports, contracts and other sensitive documents.

By SathiTools editorial team · published 2026-09-22 · updated 2026-10-26 · 9 minute read

Most "free online PDF" sites look identical: a drop zone, a button, a download link. What differs is where the work happens. Some tools read the file in your browser; others upload it to a server, process it there and send back a result. For a shopping list the difference hardly matters. For a passport scan, a signed contract or a medical report, it is the whole question.

This guide explains the two architectures, how to check which one you are using, and where the limits of browser-based processing are — including one redaction mistake that has exposed documents that people thought were blacked out.

Two very different architectures

In a server-based tool, your file leaves your device. It travels to the operator's server, is written to disk or memory, is processed, and is then served back. The operator may delete it immediately, after an hour, or after a retention period. You are relying on their promise and their security.

In a browser-based tool, the file is opened by JavaScript running in your own tab. The processing uses your device's memory and CPU, and the result is produced locally. The file can still be sensitive, but it does not cross the network, and there is no server-side copy to delete.

How to check a tool in under a minute

Open the browser developer tools, go to the Network tab, and clear it. Then add your file and start the operation. If you see a request with your file in the body — usually a POST to an upload endpoint — the file is leaving your device. If the operation completes with no such request, the work is local.

A second signal is behaviour with the network disconnected. A truly local tool keeps working after the page has loaded; a server-based tool fails or hangs. A third signal is the privacy policy: it should say plainly whether files are uploaded and how long they are kept. Vague claims like "secure processing" are not an answer.

  • Watch the Network tab for a POST while the file is processed.
  • Disconnect the network after the page loads and try again.
  • Read the privacy page for a clear statement about uploads and retention.
  • Be suspicious of a tool that needs an account for a simple local operation.

What local processing can and cannot do

Modern browsers are capable of serious document work: merging, splitting, rotating, compressing, adding page numbers, watermarking, extracting text and rasterising pages. Libraries such as pdf-lib and PDF.js make that possible without a server.

The limits are practical rather than conceptual. Very large files can exhaust the memory of a phone or an older laptop. Some operations are slow in JavaScript compared with native code. And nothing local can recover a password you do not know or repair a file that is already corrupt. If a tool promises either, be careful.

Redaction: covering text is not deleting it

A black rectangle drawn over text is a drawing on top of the text. The characters are still in the file and can be selected, copied or extracted unless the page is actually flattened or the text is removed. This is how redacted court filings and company reports have leaked information for years.

If you need to remove information, use a tool that deletes the text or rasterises the page, then verify the result by selecting the area and trying to copy it, and by searching the document for the removed words. If you are not sure, export the page as an image and assemble a new PDF from the images — crude, but it genuinely removes the text layer.

A safe workflow for sensitive documents

For a passport, citizenship certificate, contract or medical report, prefer a local tool and check the Network tab the first time you use it. Work on a copy, not the only version of the file. Save the output with a clear name, and delete temporary files from your downloads folder when you are done.

If the document must go to a third party anyway — a bank portal, a government system, an employer — the upload is part of the process and the recipient's policy applies. The question is whether an unrelated tool site also needs a copy. Often it does not.

  • Use a copy and keep the original untouched.
  • Verify that the operation is local before adding a sensitive file.
  • Check the output, especially page order, signatures and form fields.
  • Delete temporary downloads when finished.

When uploading is the right choice

Local processing is not automatically better. A server with more memory can handle a 500-page scan that would crash a phone. A service with a proper retention policy and encryption may be a better home for a file than a shared computer. Some workflows genuinely require a server, such as converting with a format the browser cannot handle.

The point is to know which one you are using. A site that says "your file never leaves your device" and then uploads it is worse than a site that says "we upload, process and delete within an hour" and does exactly that.

Useful next steps

Frequently asked questions

Do SathiTools PDF tools upload my files?

The PDF, image and document tools run in your browser using JavaScript. They read the file locally and produce the result on your device. You can verify this yourself in the Network tab: no request carries the file.

Is browser-based processing safe for a passport scan?

It removes the network copy, which is a real improvement. The file still exists in your browser memory and in your downloads folder, so use a trusted device, work on a copy and delete temporary files afterwards.

Why is a black box on a PDF not enough to redact it?

Because the text underneath is still present unless the page is flattened or the characters are removed. Select the area or search for the hidden words to check; if they can still be copied, they are still in the file.

Why does a large PDF fail to process in the browser?

Browser tools are limited by the memory available to the tab. Very large or image-heavy files can exceed that limit. Splitting the file into smaller parts, or using a desktop application, is usually the practical answer.

Related guides

This article follows our editorial standards. Corrections are welcome at info@sathitools.com.