Offline PDF tools — how we protect your privacy
Introduction to local-first PDF processing.
Why your files never leave your device
Many PDF sites send your file to their servers. Here, core operations run in your browser: your PDF is processed locally and is not uploaded to our servers for merge, split, compress, protect, unlock, rotate, extract, watermark, page numbers, and similar tools.
How we protect your privacy
- No upload for core tools — When you use merge, split, compress, protect, unlock, and other built-in tools, the file is read and processed entirely in your browser. We do not receive or store your PDF.
- You stay in control — No account required for basic use. No need to trust a third-party server with sensitive documents.
- Offline-capable — Once the page and scripts are loaded, you can process PDFs without an internet connection; the logic runs locally via WebAssembly.
How it works (execution principle)
Our PDF tools use WebAssembly (WASM): the same kind of code that runs in games and high-performance web apps. The PDF processing engine is compiled to WASM and runs inside your browser tab. When you add a file, it stays in browser memory (and optional local storage if you choose); it is not sent to our backend for these operations.
So the flow is: your device → browser → WASM engine → result PDF. No round-trip to our servers for the core toolset.
How to verify that your file isn't uploaded
You can check this yourself with your browser’s Developer Tools:
- Open the tool (e.g. Merge PDF), then open DevTools (F12 or right‑click → Inspect) and go to the Network tab.
- Select your PDF and run the operation (e.g. merge, compress). Watch the Network list.
- You will not see any request that sends your PDF to our servers. The only requests are for loading the page and scripts (HTML, JS, WASM); your file data stays in the tab.
As an extra check: after the page has loaded, you can turn off your network (e.g. enable “Offline” in DevTools or disconnect Wi‑Fi) and run the tool again — it will still work, because processing happens entirely in the browser.