Don't trust us. Prove it yourself.
We say your files never get uploaded — they're processed entirely in your browser. Instead of asking you to take our word for it, this page hands you the tools to verify the no-upload claim with your own eyes.
Uploads of your file
0
Bytes of your file sent
0 B
Verified — your file never left this device.
Process a file and watch these stay at zero.
Below is a live monitor of real outbound network requests made by this site. Run a PDF tool in another tab and watch: your file's bytes never appear here.
Two ways to prove nothing leaves your device
1. Watch the Network tab while you work
Your browser already ships with a tool that records every single request a page makes. Open it, run any PDF tool, and you'll see that no request ever carries your file out.
- 1Open DevTools: press F12, or right-click the page and choose Inspect (Chrome, Edge, Firefox all work).
- 2Click the Network tab, then make sure recording is on and the filter is set to show all requests (you can filter by Fetch/XHR or Doc to keep it tidy).
- 3Process a real PDF with any tool on this site — merge it, redact it, compress it, whatever you like.
- 4Watch the request list: you'll see static app assets load, but zero requests that POST or upload your file's contents. Click any request and check its payload — your document is never in there.
2. Cut your internet — then keep going
This is the test you can't argue with. Load this site once, then turn off Wi-Fi or unplug your network cable. Now keep using the PDF tools. They still work — merging, splitting, redacting, signing, all of it — because everything runs locally on your machine. Uploading is physically impossible with no connection, so the fact that the tools still work proves your files are staying put.
One honest exception: most tools work fully offline after the first page load, but OCR (scanned PDF to Word / searchable text) needs to download its recognition engine once from a CDN the first time you use it. After that one-time download, OCR also runs completely offline. Everything else needs no connection at all once the page has loaded.
Try it right now — run any of these with the Network tab open
Why is this even possible without a server?
For years, editing a PDF online meant uploading it to someone's server and trusting them with your data. That's no longer necessary. Modern browsers can run full PDF and image engines locally using WebAssembly and JavaScript — the same kind of code that used to live on a server now runs inside your tab, on your own CPU. There's no server round-trip because there's nothing to round-trip to: the engine, your file, and the result all live on your device. We literally never built an upload endpoint to send files to.
Read the full security explainerFrequently asked questions
Couldn't you just upload my file secretly in the background?+
No. The browser's Network tab logs every request a page makes — there's no way to hide one from it. If we were sneaking your file out, you'd see it there. And the offline test settles it completely: with your internet disconnected, a background upload is physically impossible, yet the tools keep working.
How can a website do all this without a server?+
The processing engines run inside your browser using WebAssembly and JavaScript. Your CPU does the work locally, in your tab. The server's only job is to deliver the static app the first time you visit — after that, the actual PDF work happens entirely on your device.
Does the live counter actually prove anything?+
Yes. It watches your browser's real outbound network requests as they happen. It isn't a number we typed in — it reflects what your browser is genuinely sending. Run a tool while you watch it and you'll see your file never goes out.
What about OCR — doesn't that need a server?+
OCR runs locally too, but it has one quirk: the first time you use it, it downloads its recognition engine once from a CDN (this fetches the engine, not your file). After that one-time download it works offline like everything else. Your scanned document's contents are never sent anywhere.
Is my file ever sent anywhere for any feature?+
No. The bytes of your file never leave your device for any tool. The only things ever fetched over the network are static app code and, for OCR, its engine — generic assets that are identical for every user and contain none of your data.