Every few months a new online tool goes viral, and every few months someone discovers that the "privacy-friendly" PDF editor they just used shipped their tax documents to a server farm. I got tired of wondering, so I started applying one simple test to every tool I use: open DevTools, go to the Network tab, and watch what happens when I feed it a file.
For most tools, the answer is sobering. The file leaves the tab before the first preview renders.
A browser in 2026 is an absurdly capable runtime. WebAssembly runs real ML models. Canvas and WebCrypto handle images and encryption natively. Which means a whole class of tools — the kind that used to demand an upload — can now run entirely on your machine, and the only reason many still don't is that uploading your file is a better business model than respecting it.
The two-minute privacy test
Try this on any tool site:
- Open DevTools → Network tab.
- Drop your file in.
- Watch for a request with a body.
If the list stays quiet while the tool works, everything happened locally. If a POST flies off to an API the moment you click — you were the product, or at least your file was.
This test is why I ended up building my daily toolkit around Ajiez, a collection of 101 free browser tools. The background remover is the flagship demo: a real segmentation model (U2Net, ~5 MB) downloads once into the browser cache and every cutout after that runs on-device. Cut out a photo of your kid, your ID, a client's product shot — nothing uploads, because there is no upload path in the code at all. Disconnect your Wi-Fi and it still works. That's not a privacy policy; that's an architecture.
The calculators nobody thinks about
Here's the part that surprised me: the tools that leak the most sensitive data are the boring ones. People paste salary numbers into "paycheck calculators" hosted by lead-gen farms, feed their mortgage details into refinancing funnels, and paste invoice totals into sites that exist to sell their data to lenders.
That's why I point anyone doing money math at a calculator cluster that runs the same way as the cutout tool: entirely in the tab. The finance calculators hub covers the whole "money questions" stack — take-home pay under 2024 federal rules, the self-employment tax freelancers always underestimate, credit card payoff timelines that show why minimum payments take 56 years, retirement projections with the 4% rule spelled out. The math is plain JavaScript running against your inputs; the numbers have no way to leave.
There's an extra benefit beyond privacy: the tool works when the site doesn't care anymore. No rate limits, no signup walls, no "you've used your 3 free operations today." A browser-local tool can't meter you, because there's no server to do the metering.
What browser-only can't do
To be fair about the trade-offs: a 5 MB WASM model is not a 5 GB datacenter model, so the background remover is good, not magical — complex hair edges lose to server-side monsters. And anything that genuinely needs fresh data (live currency rates, say) still needs a network call somewhere. The honest framing: for a huge slice of everyday tasks — cutouts, OCR, PDF surgery, every calculator under the sun — local execution is not a compromise anymore. It's just better defaults.
Try the test yourself
The next time a tool asks for a file or a number, spend the two minutes. Open the Network tab first. Tools that pass it quietly deserve your bookmarks; tools that don't deserve a second thought.
(I keep the whole toolbox at ajiez.top — no account, no uploads, and the DevTools test above will confirm both claims.)
Top comments (0)