How to Check That a PDF Tool Doesn't Upload Your Files
Three tests anyone can run in two minutes: the offline test, the Network tab, and the Content-Security-Policy.
Every PDF website claims to be secure, and many now say "your files are never uploaded". A promise on a web page is just text, though. The good news is that you do not need to trust it: with the browser you already have, you can see for yourself what a page sends. Here are three tests, from the easiest to the most thorough. Each takes a minute or two.
Use a harmless test file for these checks, such as a one-page PDF you made yourself, not the confidential document you want to protect.
Test 1: the offline test
A tool that processes files on your device does not need the internet once the page has loaded.
- Open the tool you want to check, for example Merge PDF, and wait for the page to load completely.
- Disconnect from the internet: switch off Wi-Fi, unplug the network cable, or turn on flight mode.
- Add your test file and run the tool.
If you get a result, the processing happened on your device. If the tool hangs, shows a network error or asks you to try again later, it needed a server, which means your file was going to be sent to one.
TrustPDF passes this test and goes further: after your first visit it keeps a copy of its own pages and scripts in your browser, so the tools even open when you are offline. A few larger parts (the OCR engine, the password library and extra fonts) are stored the first time you use them online.
Test 2: watch the Network tab
Your browser's developer tools list every request a page makes. An upload is hard to hide there.
- Open the tool page. Press F12 (or Cmd+Option+I on a Mac) and choose the Network tab.
- Tick Preserve log so the list is not cleared, then click the clear button (🚫) to start with an empty list.
- Add your test file, run the tool and save the result.
- Look at what appeared. Sort by the Size column and look at the Method column: an upload is a
POSTorPUTrequest at least as big as your file.
On TrustPDF you will see files loaded from trustpdf.net (scripts, fonts, icons) and, if statistics are on,
a few tiny POST requests to /analytics/e/, a few hundred bytes each. Those are cookie-free page
statistics: the page address, the names of the buttons that were clicked, and how long the page was open.
They never contain file names, file contents or anything you typed. What you will not see is a request
the size of your PDF.
A blob: address in the list is not an upload either: it is the browser handing the finished file
to your downloads, inside your own computer.
Test 3: read the Content-Security-Policy
The first two tests show what a page did. The Content-Security-Policy shows what a page is allowed to do. It is a rule the website gives to your browser, and the browser enforces it: if the policy says the page may only talk to its own site, the browser blocks any attempt to send data anywhere else, even by a buggy or compromised script.
- In the Network tab, reload the page and click the first request (the page itself).
- Under Response Headers, find
content-security-policy. - Look at
connect-src, which lists where scripts may send data.
TrustPDF's policy says connect-src 'self': scripts may only talk to trustpdf.net, never to an
analytics company, an advertising network or another server. Many sites have no such policy at all, or
allow dozens of third-party domains.
Bonus: read the source code
The strongest guarantee is code you can read. TrustPDF is open source under the AGPL-3.0 license, and
the code is on GitHub. Each tool is a short
JavaScript file; search it for fetch or XMLHttpRequest and you will find no code that sends your file.
If you prefer, you can run your own copy.
Red flags
- An "uploading…" progress bar, or a queue position.
- A result that you download from a different domain, or a link that "expires in 1 hour".
- A request to create an account or give an email address before you can download.
- A privacy policy that talks about how long files are kept: files that are never received do not need to be deleted.
For more on why this matters, read Are online PDF tools safe?
Frequently asked questions
Can a website say it doesn't upload files and still do it?
Yes. A privacy promise is only text. The tests in this guide check what the page actually does, so you do not have to trust the claim.
Does the offline test prove nothing is ever sent?
It proves the tool does not need a server to process your file. A badly behaved page could still store data and send it later, which is why the Network tab and the Content-Security-Policy checks are worth doing too.
What are the small requests I see on TrustPDF?
Requests to /analytics/e/ on trustpdf.net are cookie-free page statistics: the page address, the names of buttons that were clicked and how long the page was open. They never contain file names, file contents or anything you typed, and the code that sends them is public on GitHub.