Editing PDFs without uploading them

Every "free PDF tool" works one of two ways. Upload tools send your file to a server, process it there, and send it back — you're trusting the operator with contracts, payslips, medical paperwork. Browser-side tools load JavaScript into your page, and the file is read and rewritten on your own machine. The output is identical; the trust model is not.

Verify it yourself in thirty seconds

Open any tool page, press F12 (or right-click → Inspect), switch to the Network panel, and use the tool with a real file. A browser-side tool shows zero file transfers — maybe one tiny counter request. An upload tool shows the file leaving, sized in megabytes. This test works on every tool, ours and competitors'; run it before deciding whom to trust with a contract.

What browser-side tools do well

• Merge: pages are copied as objects, so text stays selectable and barcodes stay sharp — no flattening, no recompression.
• Extract: pull page ranges (with reverse order for scan cleanups) into a new file.
• Rotate: a flag change per page — no quality loss, tiny size delta.
• Images to PDF: embeds JPG/PNG natively, no re-encode.

What they can't do: anything that needs heavy server computation — OCR on large scans, aggressive compression of huge files, editing password-protected documents. Those remain server tools or desktop software.

A cleanup workflow that keeps files local

1. Rotate the sideways strays (target just those page numbers).
2. Extract the pages worth keeping — reversed ranges reorder on the way.
3. Merge the results with other documents into the final package.

Three passes, all in browser memory, no final_v2_REAL.pdf sprawl on your desktop — and nothing for a breach to leak, because there's nothing on a server.

The honest limits

• Browser memory sets the ceiling: hundreds of pages merge fine; gigabyte scans may not.
• Encrypted PDFs fail by design — remove the password with the password first.
• Document-level extras (bookmarks, some form fields) don't always survive merging; page content does.

Try it

Run the Network-panel test on the merge tool with any file you'd rather not upload. Then keep using whichever tool passes it.

Try it: Merge PDF (browser-side) →

The trade-offs, stated plainly

• Scale: browser memory caps job size. A 900-page scanned archive is desktop-software territory.
• Features: no OCR, no redaction, no compression of existing PDFs here — those need either heavy local computation or a server, and pretending otherwise would be the sales pitch this site refuses to make.
• Convenience: there's no account to sync from, so the "same tool on every device" comfort of upload services is absent. What you get instead is the same tool on every device anyway — it's a URL — with nothing stored between visits.

Why upload tools have this business model

Server processing costs money per file, which is why the free tiers are small, watermarks appear, and the useful features sit behind subscriptions. None of that is villainy — it's the economics of doing the work on someone else's computer. Browser-side processing simply has different economics: your CPU does the work, so the per-file cost to the operator is zero and limits come from your device, not a billing plan. When your task fits in a browser, that's the better deal on both axes at once — privacy and price.

A quick decision rule

• Sensitive content (contracts, IDs, medical, financial)? Browser-side, always.
• Huge or scanned-heavy files? Desktop software, or split the job.
• Everyday merge/split/rotate on ordinary documents? Browser-side is faster than finding the upload button.

Two details worth knowing

• Offline after load: once the page is open, the libraries are cached in the tab — kill your Wi-Fi and the merge still works. That's the cleanest possible proof of where processing happens.
• Output location: results download through your browser like any file, straight to your downloads folder. No account, no cloud copy, no link that expires.

Where the open-source part comes in

The PDF engine here is pdf-lib, an MIT-licensed library — the same license family as everything else this site serves, listed with versions on the Licenses page. Open source is what makes the browser-side approach auditable: you can read the code that handles your file, not just trust a privacy policy that describes it.

And a reframe worth keeping: "online PDF tool" describes the delivery, not the location of work. Ask where the file goes while you wait. If the answer is nowhere, the privacy question answers itself — and the answer is the same whether the tool costs nothing or a monthly fee.

Last reviewed October 28, 2026.