How to Tell Whether a File Tool Actually Uploads Your Files
· 6 min read
Open your browser's developer tools, switch to the Network tab, and process a file. If the tool uploads, you will see a request the size of your file leaving the page. If it does not, you will see nothing of the kind. This takes about thirty seconds and settles the question outright.
Every tool in this category says it respects your privacy. The claim costs nothing to make, so it carries no information. Here is how to stop guessing.
On this page
Why the words on the page are worthless
Read the homepage of any online file tool and you will find the same sentences: secure, private, encrypted, files deleted after an hour. They appear on sites that upload everything you give them and on sites that upload nothing, in the same words, because nothing stops anyone writing them.
"Deleted after one hour" is the tell that most people miss. It is offered as reassurance, and it is an admission: a file can only be deleted by someone who has it. The sentence concedes the upload while sounding like a privacy feature.
None of this makes those services dishonest. Server-side processing is a legitimate design with real advantages — it works on any device, however old and slow. But it is a different thing from what it is often made to sound like, and you should be able to tell which one you are using.
The thirty-second check
Every modern browser ships with a panel that lists every request a page makes. It is the same tool the site's own developers use, it cannot be disabled by the page, and it does not care what the marketing copy says.
- Open the tool's page, but do not add your file yet.
- Press F12, or Ctrl+Shift+I (Cmd+Option+I on a Mac), and choose the Network tab.
- Tick "Preserve log" if it is offered, so nothing disappears on a page change.
- Now add your file and run whatever the tool does.
- Watch the list. Sort by size if the column is available.
Reading what you see
You are looking for one thing: a request whose size is roughly the size of your file, going out to the site's own domain. That is your file being uploaded. It is usually a POST, and the size column gives it away — nothing else a page loads is 4 MB.
A tool that processes in your browser produces a very different list. You will see the page, its scripts and styles, and on the first run a codec — a WebAssembly file, typically a few hundred kilobytes, which is the compression engine itself being fetched. That download happens once and is then cached. Crucially, it is the same size every time, whatever file you gave it.
That difference is the whole test. Upload traffic scales with your file. A codec download does not.
| What you see | Uploads your file | Works in your browser |
|---|---|---|
| A request the size of your file | Yes | No |
| Traffic changes with a bigger file | Yes | No |
| A one-off .wasm download | Rarely | Yes, on first use |
| Anything at all while processing | Yes | No |
Three stronger checks, if it matters
The Network tab settles most questions. If the document is sensitive enough that you want more than a glance, these take a little longer and prove more.
- Process a file, then turn off your connection entirely and process another. A tool running in your browser keeps working once its codec has loaded. A server-based one stops immediately.
- Compare a small file with a large one. If the outgoing traffic grows with the file, it is being uploaded. If it is identical, it is not.
- Look at how long it takes on a slow connection. Uploading 50 MB takes minutes on domestic broadband. Local processing starts the moment you drop the file.
What the answer actually means for you
If a tool uploads, your file exists on a machine you do not control, for as long as that company's policy says and no shorter. That is fine for a holiday photo. It is a different decision for a signed contract, a bank statement, a passport scan or a medical letter — which, being large scans, are exactly the files people most often need to compress.
It also decides what the service can offer. Bandwidth and CPU cost the operator money per file, which is why free tiers come with daily caps, file-size ceilings and watermarks. Those limits are not stinginess; they are the shape of the business model showing through.
Why we can afford to tell you this
Publishing a guide that teaches people to audit file tools is only comfortable if your own tool passes. Ours does: run anything on this site with the Network tab open and you will not see your file leave, because the compression runs in your browser using WebAssembly.
Every tool here also prints what it measured underneath the result — how many requests were made while it ran, and how many of those went anywhere other than this site. The second number is zero. That is a measurement taken during your run, not a promise written in advance.
We are not claiming this makes us better at everything. Browser-based processing is limited by your device's memory, and our PDF compression on text-only documents is weaker than tools built on server-side engines we are not licensed to use. Those trade-offs are stated on the tool pages. The upload question, though, is not a trade-off — it is simply checkable, and now you know how.
Common questions
How do I open the Network tab?
Press F12 on Windows or Linux, or Cmd+Option+I on a Mac, then choose Network. On mobile it is not available directly — do this check on a computer, and the answer applies to the same site on your phone.
What exactly am I looking for?
A request whose size is close to the size of your file, going to the site's domain. That is an upload. Everything else — scripts, styles, fonts — is far smaller and the same on every visit regardless of what file you chose.
I see a .wasm file being downloaded. Is that my file leaving?
No, that is traffic in the other direction. A .wasm file is the compression engine being fetched so it can run on your machine. It is the same size whatever file you process, and it is cached after the first run.
Does HTTPS mean my file is private?
It means nobody can read it in transit. It says nothing about what happens at the other end, which is where the file is decrypted, processed and stored under whatever policy that company keeps. Encryption in transit and never transmitting are different guarantees.
Is uploading always a bad thing?
No. Server-side processing works on any device however old, and can use engines that are impractical in a browser. It is a legitimate design. The point is to know which one you are using so the choice is yours to make.
Why do free online tools cap file sizes and daily use?
Because every file costs the operator bandwidth and processing time. Caps, watermarks and sign-up walls are how that cost is recovered. A tool that processes on your device has no such cost, which is why it can leave those limits off.
Can a site fake this check?
Not meaningfully. The Network panel is part of the browser, not the page, and it records requests the page cannot hide from it. A site could delay an upload until later, which is why the offline test is a useful second step.
Does FileCrisp pass its own test?
Yes, and it is the reason we can publish this. Run any tool here with the Network tab open and no request carries your file. Each result also reports the requests measured during that run, and how many left this site — zero.