Many tools claim your files never leave your device. Here are three simple checks, using only your browser, that let you verify it yourself.
“Your files never leave your device” is a promise nearly every online tool wants to make. It is also a promise you do not have to take on trust. Because a browser tool runs on your computer or phone, you can watch what it does. This guide shows three checks, from the easiest to the most thorough. None of them needs any technical background beyond following the steps.
Documents such as identity cards, bank statements, contracts and medical letters are personal. When a tool uploads a file to a server, that file passes through a computer you cannot see. It may be stored for a while, logged, or backed up. A tool that processes the file inside your browser avoids that whole problem, since the data never travels. The difference is invisible on the surface, so it is worth knowing how to check. If you want the background, read Are online PDF tools safe?
Start with the privacy policy. A trustworthy tool describes where files are processed and what the site does collect, such as standard technical data, cookies and advertising. A vague line like “we care about your privacy” tells you nothing. Look for concrete statements, for example that processing happens in the browser, which libraries are loaded from public networks, and how ads work. Be wary of sites that say “files deleted after one hour”, because that sentence means the files were uploaded.
If the tool still converts, edits or generates the file, it did not need a server to do the work. This is strong evidence of in-browser processing. Be aware of two caveats. A tool may need to download an extra component the first time you use a feature (OCR language data is a common example), so a first-time failure offline is not proof of an upload. And it does not prove the site would not send something once you reconnect. Use it as a quick filter, then confirm with check 3.
Every modern desktop browser has built-in developer tools that list every request the page makes. On Chrome, Edge or Firefox for desktop:
An upload shows up as a POST or PUT request with a size roughly the size of your file, often to a path containing words like upload, convert or process. Click the request and open the Payload or Request section to see what was sent. If you process a 5 MB file and never see a request that large leaving the page, the file stayed on your device.
Do not be alarmed by every line in the list. A normal page makes many small requests: fonts, style sheets, scripts from content delivery networks, visitor statistics and advertising. Ads in particular add a stream of small requests to ad servers. These are not your file. They are small, usually a few kilobytes, and they do not change in size when you pick a bigger document. The pattern to look for is one request whose size matches your file.
Try this with a tool like PDF to Text. Open the Network tab, drop in a PDF of a few megabytes and watch the list. You should see the page’s code libraries load when the page opens (or the first time a feature is used), and little or nothing when the file is processed. With OCR, the first run downloads a language data file, which is a download to your browser, not an upload from it. You can confirm the direction by looking at whether data is being received or sent.
Developer tools are harder to reach on a phone. The offline test works well, though: load the page, switch to airplane mode and try the tool. You can also open the same page on a computer and use the Network tab there.
Read the policy, run the offline test, and check the Network tab if the document matters. It takes a few minutes and tells you far more than any claim on a landing page. Docsworker processes files in your browser and encourages you to check this for yourself.
No. The padlock only means the connection between you and the site is encrypted. It says nothing about what the site does with a file once it has it.
Yes, and that is normal. The page itself, its fonts, its code libraries, analytics and ads all use the network. What matters is whether anything large leaves your browser when you process a file.
It is a good quick test, but some tools load extra code only when you first use a feature. If a tool fails offline, the Network tab check is more reliable.
Yes. Even if a tool is private, treat the most sensitive documents carefully: use a device you trust, keep your browser updated, and delete downloaded copies you no longer need.