Client-side processing

A PDF toolkit that runs in the browser

An editor plus single-purpose tools for merging, splitting, compressing, converting, signing and securing PDFs. Files are processed on your device.

Drop a PDF to open it in the editor

or tap to begin

Opens in the editor · no upload

Tools

Each tool reads the file, shows its pages and returns a finished document. The result can be passed straight into the next tool.

A document stays open as you move between tools, so you can merge, then compress, then sign the same file without uploading it again.

Processing

Files are opened and written in the browser. The site has no upload endpoint.

Limits

No account, no file size cap, no watermark. Available memory is the limit.

Output

Page objects are parsed and rewritten, so text stays selectable.

Chaining

A result can be passed to another tool or the editor without reloading it.

What “runs in the browser” actually means

There is no upload endpoint. When you open a document, a PDF engine already loaded in the page reads the file from your disk, and every change is written by that engine into a new file on your device.

The practical consequences: nothing is queued on a server waiting to be deleted, there is no account or file-size quota to work around, and once the page has loaded the tools keep working with the network switched off. The limit is your own device's memory rather than someone else's plan.

Editor or a single-purpose tool?

Use a single-purpose tool when you know exactly what one change you need: rotate the pages, drop page four, shrink the file, add a password. Each one shows the document, does that job and hands back a finished file.

Use the editor when you are working through a document — annotating, signing, rearranging pages and checking the result as you go. Either way the open document follows you, so a file you merged can go straight into compressing or signing without starting over.