Skip to content
Dexta Studio
PrivacyNovember 15, 2026 · 6 min read

How to check if a website uploads your files (a two-minute test)

Lots of sites say your file never leaves your device. You don't have to take their word for it. Here's how to check with the developer tools already in your browser.

"Your files never leave your device" is an easy sentence to put on a homepage. We put it on ours. But it's a claim, and you can test a claim. Every desktop browser ships with a tool that shows each request a page makes, including how big it is, and an upload is just a big request. If you can open a menu, you can do this.

Use a file that doesn't matter for the test: a holiday photo, a blank PDF, a short clip from your camera roll. Find out how a site behaves before you give it the bank statement.

Test 1: watch the Network tab

Step 1

Open the tool's page

Load the converter or editor you want to check, but don't add a file yet.

Step 2

Open developer tools

In Chrome or Edge press F12, or Cmd+Option+I on a Mac. In Firefox, Cmd+Option+E (Ctrl+Shift+E on Windows) opens the Network tab directly. In Safari you first need to turn on the developer menu in Settings > Advanced, then press Cmd+Option+I.

Step 3

Switch to the Network tab and clear it

Click Network. Tick "Preserve log" so nothing disappears if the page navigates, then press the clear button (a circle with a line through it) so you start from an empty list.

Step 4

Now use the tool normally

Add your test file, run the conversion and download the result, exactly as you would for real.

Step 5

Sort by size

Click the Size column header (Firefox calls it Transferred). Look for a request that is roughly as large as your file, and check its method in the Method column. POST or PUT with a few megabytes attached means the file went somewhere.

Some things in that list are normal and harmless. The page downloading its own code, fonts, images and, on a site like ours, a WebAssembly build of FFmpeg that can be 30 MB or more: those are downloads coming in, not your file going out. The direction is what matters. In Chrome you can click any request and look at the Payload tab. If you see your file name, or a "multipart/form-data" body, that's an upload.

Test 2: pull the plug

The Network tab can get noisy. The blunt version of the test is cleaner: if the work happens on a server, the tool can't work offline.

Step 1

Do one run while online

Run the tool once with a tiny file. A lot of browser-based tools only download their processing code the first time you use them. We do this too, with the PDF library. Without a warm-up run, an honest tool can fail offline just because it never got the chance to load.

Step 2

Go offline

Turn off Wi-Fi, or in Chrome's Network tab change "No throttling" to "Offline".

Step 3

Run it again

Add a different file and convert it. If you get a working download while disconnected, the processing happened on your machine. If it spins forever or shows a network error, it needed a server.

What these tests don't prove

  • They tell you what happened on this visit, in this browser. A site can change its code tomorrow.
  • A page could in theory hold on to the file and send it after you reconnect. Leave the Network tab open with Preserve log on, go back online, and watch for a large request for a minute or so. It's paranoid, and it's also free.
  • Browser extensions can read files you open in a page. A clean test of the website says nothing about the extensions you have installed.
  • Local processing isn't the same as no tracking. A page that processes files locally can still load ads and analytics. Those scripts don't get your file, but they do see that you visited.

What you'll see if you test us

Run the test on Merge PDF and you'll see the page load its scripts, then pdf-lib the first time you merge, then nothing large going out. You'll also see two tiny requests to /api/event, one when the page opens and one after each run. They record which tool was used, whether it worked and how long it took, so we know which tools break. They carry no file data, no cookie and no identifier, and they're a few hundred bytes. Check the Size column.

If you find something that doesn't match what we say, we'd genuinely like to know. The contact page reaches a person. The longer explanation of how our tools work is on How file processing works.

Merge PDFCombine multiple PDFs into one document, in the order you choose.