How PDFCasa works

Most online PDF tools upload your file to their server, process it there, and send the result back. Here's what happens on PDFCasa instead:

Check it yourself in thirty seconds

This isn't a policy we're asking you to trust — it's how the tools are built, and it's checkable by you, not just claimed by us.

1. Open any tool page and press F12 to open developer tools, then choose the Network tab.
2. Add your file and run the tool normally.
3. Watch the request list. You'll see the page's own assets load, then nothing of any size while the work happens — no request carrying your file's data anywhere.

Or simpler still: disconnect from the internet after the page loads, then try the tool with a file. Most tools work immediately. A few PDF tools fetch a small font file the first time they need it on a page you haven't used before — reload once while online if you're testing that specific case — but nothing about your file ever leaves your device either way. A server-side tool couldn't work offline at all.

Where we stand

Every tool on PDFCasa today runs entirely in your browser. We don't receive your files, which means we can't lose them, sell them, or be compelled to hand them over — not because of a retention policy, but because there is nothing on our end to retain in the first place.

Some future features genuinely can't work this way — AI background removal, for instance, needs a model too large to run on a phone, and will use a Cloudflare service to do that one specific job. When a tool like that ships, its page will say so plainly, before you choose a file, not in a policy you'd have to go looking for.

For the fuller picture on why any of this matters — what server-side tools actually risk, and how to check any site, not just this one, read "Are online PDF tools safe?"