PDF tools that never upload your files

Why uploads are the weak point

A typical online PDF tool works like this: your file travels to a server, a queue processes it, and a copy is downloaded back. That round-trip is where privacy is lost — the document now exists on infrastructure you do not control, under retention policies you have not read, sometimes in a jurisdiction you did not choose. For a blank form that hardly matters. For a contract, a medical record, or a tax return, it is the difference between a convenience and a disclosure.

Every tool on this page takes the other approach. The PDF is parsed and rewritten by JavaScript running inside your own browser tab. There is no upload step because there is nothing to upload to — the network indicator on each tool page stays at zero uploads from start to finish. You can even load a tool, switch off Wi-Fi, and keep working.

A private workflow, end to end

A common sequence looks like this: merge the source documents into one file, split out the pages that should not travel, compress the result so it fits the attachment limit, then add a password before it leaves your machine. Each step happens locally, so at no point does the full document exist on a third-party server.

The same privacy guarantee covers the less obvious cases. Rotating a scan, deleting a blank page, or stamping DRAFT across a proposal are all operations on your file's contents — and on this site they are all performed by your device, not ours.

What 'private' means here, concretely

There is no processing queue, no temporary storage bucket, and no server-side copy to delete later. When you close the tab, the only copy of the result is the one you downloaded. The core tools need no account, so there is no profile tying your name to the documents you worked on. The single exception is the AI editor, which sends a file to a model only when you explicitly choose to run an edit — and it is labelled as such.