Modern browsers are capable application platforms. They can run compiled code at near-native speed, draw graphics, and work with files you select, all without sending anything to a server. Online PDF Editor uses those capabilities to do PDF work on your device.
What happens when you use a tool
- The page loads code, not your file. Your browser downloads the JavaScript and WebAssembly that implement the tool, just like any web page.
- You choose a file. The browser gives the page read access to that one file. It is loaded into memory on your device.
- The tool processes it locally. Libraries running in the page parse the PDF, change it, and write a new PDF in memory.
- You download the result. The new file is handed to your browser’s download manager. Nothing is transmitted.
When you close the tab, the memory is released and the document is gone from the tool.
The building blocks
- PDF parsing and writing: a PDF library reads the document structure, copies pages, rotates them, adds text or images, and saves a new file.
- Rendering: a PDF renderer draws pages onto a canvas to show previews, export images (PDF to JPG), or rebuild pages for compression.
- Image encoding: the browser’s own encoders turn rendered pages into JPEG or PNG at the quality you choose.
- WebAssembly: heavy work, such as decoding iPhone HEIC photos, uses compiled code that runs much faster than ordinary scripts.
What this means for you
- Privacy: your document is not stored on a server, because it never reaches one.
- Speed: no waiting for uploads and downloads of large files.
- Compliance: fewer questions about data processors and where data is stored.
- Limits: your device does the work, so huge files are limited by its memory.
Verify it yourself
Open your browser’s developer tools, choose the Network tab, and run any tool. You will see the page’s own code, images, and analytics, but no request that carries your document. See Is it safe to edit PDFs online? for more on checking any PDF service.