Some free online PDF tools are safe for sensitive files and some are not, and from the outside they look almost the same. The safe ones process your file in your browser and never upload it. The risky ones upload it, keep it for a time you can't control, and are paid for in ways they don't explain.

You can tell them apart with a few checks that take five minutes the first time and seconds after that. Here is the checklist, grouped by what each check tells you, followed by how to weigh the answers for different kinds of documents.

Checks 1 to 4: where is your file processed?

This matters most, because a file that never leaves your device can't be leaked, kept or passed on by the site.

  • Check 1, the claim on the tool page. "Runs in your browser" or "your file never leaves your device" is a specific, testable claim. "Secure", "encrypted" or "we respect your privacy" says nothing about where the work happens.
  • Check 2, an upload step. A progress bar that climbs before anything else happens, even for a one-page file, is usually the file travelling to a server.
  • Check 3, the offline test. Load the tool page, turn off Wi-Fi, then run a harmless test PDF through it. If it still works, the processing is local.
  • Check 4, the network tab, if you're comfortable with it. The next section shows how.

How to read the network tab without being a developer

Every desktop browser can show you what a page sends. In Chrome, Edge or Firefox, press F12 (or right-click the page and choose Inspect), then open the Network tab. Keep it open while you drop in a test file and run the tool.

  • Ignore the small stuff. Ads, analytics, fonts and images all make requests of a few kilobytes. Almost every website has them.
  • Look at the size column. If your test PDF is 2 MB and a request of about 2 MB goes out when you drop it in, that's your file being uploaded.
  • Look at the method. An upload is normally a POST or PUT request, often to an address with words like upload, task or process in it.
  • Repeat with the download. Some sites process locally but send the result back to a server to "store" it. The download should create a file without a large request going out.

On a phone there's no easy network tab, so use the offline test instead. Load the tool, switch on airplane mode, then try a test file. Remember to switch it off again afterwards.

Checks 5 to 8: what does the privacy policy say?

If a tool does upload, the privacy policy tells you how much it matters. Search the page for "files", "documents", "delete" and "retain".

  • Check 5, retention. "Files are deleted after one hour" means they had your file for an hour. Note whether that applies to free users too, and to backups.
  • Check 6, use of your content. See whether documents can be used to improve services or train systems. If it's vague, assume yes.
  • Check 7, who else touches it. Look for the list of processors and hosting providers, and which country the servers are in.
  • Check 8, a real contact. A named company, an address and a way to ask for deletion are a minimum. No policy at all is an answer too.

Checks 9 to 12: how is it paid for, and what does it ask of you?

  • Check 9, funding you can see. Ads or a paid plan are normal ways to pay for a free tool. When you can't tell how a site makes money at all, be more careful with what you give it.
  • Check 10, an account wall. Being asked to sign in after you've done the work, just to download, is a sign the site wants your email more than your custom.
  • Check 11, installers and extensions. A PDF site that pushes a download, a browser extension or notification permission to finish a simple job is asking for far more access than the job needs.
  • Check 12, the download itself. The result should be a PDF. A file ending in .exe, an unexpected .zip, or a chain of redirects before the file is a reason to stop.
The most common mistake is trusting the word "secure". A padlock and HTTPS mean the file is encrypted on its way to the server. They say nothing about what happens to it once it arrives.

How much each check matters depends on the document

You don't need the same care for every file. A rough guide:

  • Low stakes, such as a café menu, a public brochure or a school event flyer. Any reputable tool is fine. Checks 11 and 12 still apply.
  • Personal, such as a payslip, a bank statement or a tenancy agreement. Prefer a tool that passes checks 1 to 4. If it uploads, it should pass 5 to 8 clearly.
  • Identity documents, such as a passport, IC or driving licence scan. Use a tool that processes in your browser and nothing else. A leaked ID scan is hard to undo.
  • Other people's data, such as customer records, patient files or HR documents. Your organisation's rules come first. Data protection laws such as Malaysia's PDPA and the EU's GDPR place duties on organisations to keep personal data secure.

When a tool fails a check

Failing check 3 doesn't make a tool dishonest. Some jobs, such as large-scale text recognition on scans, are often done on servers, and a clear policy can make that acceptable for ordinary files. Failing it while claiming to run in your browser is a different matter: that claim isn't true, so don't trust the rest.

If you already uploaded something sensitive to a site you now doubt, look for its deletion request process and use it. If it was an ID document or bank details, keep an eye out for phishing that quotes those details back to you.

Run the checks again now and then for the tools you use often. Sites get sold, change how they're funded or move a feature to a server, and the tool you checked last year may work differently today. A bookmarked tool that suddenly shows an upload bar is worth a second look.

How Kopitiam does on the same checklist

It's only fair to run our own tool through it. Kopitiam's PDF tools process your file in the browser and never upload it, and they keep working if the connection drops after the page has loaded. There's no account, no download wall and no installer.

What the site does send: Kopitiam is paid for by ads, so your browser asks our ad partner for an ad to show. If you accept analytics on the cookie banner, anonymous events record things like which tool was opened, never the file or its name. If you choose Essential only, analytics doesn't load. Fonts come from Google Fonts. The privacy page lists all of it, and you can confirm it in the network tab yourself.