Almost every online PDF tool works the same way: you pick a file, it uploads to a server, the server does the work, and you download the result. It is convenient, and for a holiday itinerary it is fine. For a contract, a payslip, a medical form or a bank statement, it means handing your document to someone else's computer and trusting what happens next.
We did not want to ask for that trust, so we built the tools differently. Here is how, in plain terms.
The usual model: move the file to the code
A normal web app keeps its code on a server. To use it, your file has to travel to where the code lives. That single design choice is the reason your document gets uploaded, and it is also why those services need large amounts of compute and storage, and why a breach of their servers can expose user files.
Our model: move the code to the file
Browsers have become surprisingly powerful. They can read files you choose, crunch data, and even run near-native code. So instead of sending your file to our code, we send our code to your file. The PDF engine is downloaded to your browser once, then every operation runs locally on your device.
There is no upload step because there is nowhere to upload to. The part of the service that would normally receive your file simply does not exist.
What actually runs, and where
A few browser technologies make this possible:
- Your file stays in memory. When you choose a PDF, the browser hands the app the file's bytes directly. They live in the tab's memory, not on a server.
- Web Workers do the heavy lifting on a background thread, so the page never freezes, even on a large document.
- WebAssembly runs the parts that need to be fast, like encryption, at close to native speed.
- Temporary working data is kept in the browser's own storage and cleared automatically. Nothing is meant to outlive your session.
When you download the result, the finished PDF is built right there on your device and saved straight to your downloads.
What this means for you
- Privacy by architecture, not by promise. A privacy policy can change. The absence of an upload endpoint cannot be quietly walked back.
- It is fast. There is no upload to wait for, so processing starts the moment you drop a file.
- It works offline. After the first visit, the tools keep working with no internet connection at all. You can merge PDFs on a plane.
The honest tradeoffs
This approach is not magic. Because the work happens on your device, very large files depend on your device's memory, and a phone will not be as quick as a desktop. We think that is a good trade for never having your documents leave your hands, and we design around it with techniques like processing one page at a time.
Try it
Every tool on the site works this way. A good place to start is Merge PDF or Compress PDF. If you are comparing options, see why people pick us as a privacy-friendly set of PDF tools.