What "online PDF editor" normally means
The standard architecture is simple: your browser posts the file to an API, a worker on a server opens it, applies the change, writes a new file and hands back a download link. The file sits on that infrastructure for as long as the provider's retention policy says — commonly a few hours, sometimes longer, and always subject to their backups, their logs and their jurisdiction.
For most documents this is unremarkable. For a signed contract, a bank statement, a medical letter, an ID scan, an unpublished manuscript or anything covered by an NDA, it means handing a copy to a third party in order to delete one page.
How to verify a tool for yourself
Open your browser's developer tools and switch to the Network tab before you load a document. Filter by Fetch/XHR, then do the edit. If the tool uploads, you will see a POST or PUT carrying megabytes; the request size gives it away even when the endpoint name does not.
A stronger test: load the page, then switch off your network connection entirely and edit a document. A browser-side tool keeps working. An upload-based one fails at the first operation. This site passes both tests, and it is worth running them on any tool that claims to be private.
What this costs and what it buys
The trade-off is real: your device does the work, so a 500-page scan depends on your own memory and CPU rather than a server farm. In exchange there is no upload wait, no queue, no daily task limit, no account, and no copy of your document anywhere but your disk.
It also means the service cannot be breached into leaking your files, cannot be compelled to hand them over, and cannot quietly change its retention policy — because it never receives them in the first place.
Frequently asked questions
How can I be sure nothing is uploaded?
Open the Network tab in developer tools while you edit, or disconnect from the internet and keep working. Both prove it directly.
Do you log or store anything?
The web server logs a page request like any site. Your documents never reach it, so there is nothing about them to log.
Is browser-side editing less capable?
For page-level work — delete, reorder, rotate, merge, add images — no. It uses the same PDF engines desktop software does.
Does it work behind a corporate firewall?
Yes, and it is often the only kind that does, since no outbound file transfer is involved.
Related tools
- Editing confidential PDFs without sending them anywhereContracts, patient records, payslips, case files: documents whose whole point is that they do not get copied onto somebody else's infrastructure.
- How it worksA short technical account of what happens between dropping a file on the page and downloading the result.
- How this compares with Smallpdf, iLovePDF and PDF24They are good products with far more features. The difference that matters is where your document is when the work happens.
- Organize PDF pagesDelete, reorder, rotate and duplicate pages in one view, then save the document — without sending it to anyone.