Why in‑browser tools are the new gold standard for privacy

For most of the last twenty years, "convert this PDF online" meant uploading your private document to someone else's server and trusting they'd delete it. That trade‑off is no longer necessary.

WebAssembly changed the rules

WebAssembly (Wasm) lets browsers run near‑native compiled code at sandboxed speed. That means the same C++ or Rust libraries that powered desktop file tools can now run inside the tab, on your CPU, with zero round‑trip to a server.

What that means for your files

• Your document never leaves your device.
• No retention policy to read — there's literally nothing stored.
• Latency drops from seconds to milliseconds because the network isn't involved.

The catch

Some workloads still need a real server: AI models that don't fit in browser memory, scanning at very high resolutions, or anything that demands a private GPU. For everything else — compression, conversion, splitting, watermarking — in‑browser processing is now both faster and safer than the old cloud workflow.

If a tool says it processes your file "in the cloud" but doesn't have to, ask why.