Zero-Egress
Don’t trust us. Verify us.
Every other PDF site uploads your file and asks you to trust that they’ll delete it. On our password and redaction tools, your file never leaves the browser — under a security policy that blocks the upload channel entirely. You don’t have to take our word for it. Here’s how to check, in under a minute.
The 30-second test
- Open one of the sealed tools below and press F12 → Network tab.
- Run the tool on a real file. Type your filename into the Network filter box.
- Zero requests appear — your file was never sent anywhere.
- Now turn off your Wi-Fi and do it again. It still works — because nothing needed a server.
Or let your own browser prove it
This button tries to open an outbound connection to example.com. On a sealed page, your browser refuses — the policy won’t let this page talk to anyone but this site.
Which tools are sealed
These Zero-Egress tools carry the tightened policy and load no ads and no analytics — nothing tracks you here:
Our other tools also run on your device and never upload your file — but they’re ad-supported, so they load ads and analytics. We keep the sealed set above completely clean, and we say so plainly.
What the guarantee is — and isn’t
Can’t silently upload (browser-enforced). Each sealed page ships connect-src 'self', so the browser blocks the background upload channel — fetch, XHR, WebSocket, and beacons to any other server. Read it yourself: curl -I the page.
No trackers here (our choice, checkable). We load zero ads and zero analytics on these pages — including no same-origin page-view beacon. That’s a choice we made, verifiable in your Network tab, not something the browser forces.
Honest limits: this covers the four sealed tools. Our advanced editor uses a backend for a few heavy operations, and the AI/OCR features download models (never your file) — those pages are labeled accordingly. And a policy is delivered per visit: the real assurance is that you can re-check it every time, not that we’ve bound our own hands forever.