How to tell whether an online tool uploads your file, in about 20 seconds
How to tell whether an online tool uploads your file, in about 20 seconds Every web tool says it is private. Almost none of them let you check. The good news is you do not need permission — you need the Network tab. I paste customer data, private keys and production JSON into browser tools fairly often, so I stopped taking the claim on trust and started testing it. Here is the check, and what the…
Determining if an online tool uploads your file can be done quickly in about 20 seconds. Most tools claim to be private, but they rarely let you verify this. The good news is, you don't need permission - you need the Network tab in your browser's Developer Tools. Here's how to do the test:
1. Open the tool and wait for the page to finish loading.
2. Open DevTools (press F12) and navigate to the Network tab.
3. Set the throttling dropdown to Offline mode.
4. Use the tool as you normally would.
If the tool runs locally, it should continue working. However, if it uploads your data, you'll see the action immediately, usually in the form of a failed fetch or a spinner that never resolves. This test is a fast way to check if your data is being uploaded.
For more sensitive information, a slower method involves using DevTools → Network → filtering to Fetch/XHR, clearing the current entries, then pasting your input and running the tool again. Look at the results - local processing will produce a short list of things unrelated to your input, while an upload will show a POST request with a request body roughly the size of what you pasted. Check the request headers and payload to confirm if your data was sent.
Be aware that WebAssembly and Web Workers can perform work without making requests, so the absence of network traffic doesn't necessarily mean local processing. However, if there are a few requests, it's unlikely to be an upload. It's important to look at what's in the request itself, not just the number of requests.
There are three things that legitimately leave the tab: page weight (HTML, CSS, fonts, analytics pings), deliberate API calls (like using a translation service), and browser-provided features like text-to-speech. The first one is the only one you can verify by yourself.
Only the first claim - "Nothing is uploaded" - can be checked directly by you. The other two claims are up to the tool's provider. When someone offers a tool claiming to not store your data or delete it after a certain period, ask why they need to keep your data around.
The biggest issue is often subtle - it might just be a small inconvenience like checking a syntax error in a .env file, or dropping a customer CSV into a converter. Files under a megabyte might feel harmless, but the real concern is whether your data left your machine. The size of the file isn't the issue - it's whether it left your device.
Two examples of this test applied to real tools are a JSON formatter and a Base64 decoder. Both work fine when the Network tab is set to Offline, confirming they make no uploads.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
