'Runs locally in your browser' means the tool's JavaScript/WebAssembly executes on your device's CPU, your files are read from local memory, and none of your content is sent to a server. It's a claim you can and should verify — with DevTools Network in less than a minute.
The 30-second verification
- Open the tool's page (e.g. Compress PDF).
- Open DevTools → Network tab. Click Clear.
- Drop your file and start the operation.
- Look at outbound requests: only HTML, JS, WASM, and CSS should download; no POST/PUT should carry your file bytes.
- Bonus: toggle airplane mode after the page loads; the tool should still work.
What 'local' rules out
- Upload to a converter server.
- Cloud AI API calls.
- Analytics that ship file names, sizes, or content.
- Silent 'diagnostic' uploads.
What 'local' still allows
- Downloading the tool's own code + WASM (JS bundle, model weights).
- Loading web fonts / icons from a CDN.
- Optional lookups you explicitly trigger (e.g. DNS-over-HTTPS to Cloudflare for a DNS tool).
Local vs Cloud (side by side)
- Local (Zro7): file bytes never leave the tab. Airplane-mode capable.
- Cloud (Smallpdf / iLovePDF / CloudConvert): file bytes uploaded to their server, processed, and returned.
- Local requires: a modern browser, enough RAM for your file. Cloud requires: trust in a third party.
Steps to try it yourself
- Open Zro7.
- Pick any tool.
- Open DevTools → Network before dropping your file.
- Confirm no request carries the file payload.
Updated December 22, 2026 · Zro7 editorial team.
Zro7