Skip to main content
BrowserStay

Command Palette

Search for a command to run...

PDF

Merging PDFs without uploading them

Merging is the most common PDF job on the internet, and the one most likely to hand a stranger your documents. It does not have to work that way.

Merge PDFs in the browser

A merged PDF is not a complicated object. It is a container: page one of the first file, then page two, and so on, with a table of contents stitched together at the end. The work is mostly copying bytes around. That is exactly the kind of job a browser can do.

Servers do it because servers are what most web apps have. Upload a file, run a library on the server, send the result back. It is easy to build, easy to bill, and it puts your document — contracts, medical letters, bank statements, the scan of a passport someone asked you for — on a machine that is not yours.

What changes when it runs locally

The browser reads each file into memory, writes the pages into a new document, and hands you a download. The tab needs enough memory to hold the files while it works. On a laptop that is nothing. On an older phone, a stack of 200 MB scans can run out of room — and when it does, the honest answer is that the local approach failed, not that it lied to you.

Doing it on this site

  1. Open Merge PDF.
  2. Drop the files in, in any order. They are read from your disk into the tab.
  3. Drag the pages into the order you want.
  4. Press merge, then download the result.

There is no upload step, no waiting bar labelled "uploading", and no file list waiting for you when you come back tomorrow. If you close the tab, the work is gone — which is the point.

The trade-offs, honestly

  • Memory is the limit. A handful of ordinary PDFs is fine. A 500 MB archive of scans is not, on a phone.
  • Speed depends on your device. A server farm is faster than your phone. It is also someone else's computer.
  • Repairing badly broken files is a different job, and a local tool will simply refuse where a server-side service might try harder.

When uploading is the reasonable choice

If the file is enormous, the device is ancient, or the document is genuinely public — a published report, a form template — then a server is convenient and the risk is close to zero. The mistake is doing it by default, with the one document that would hurt you most, because the site had a nicer logo.

You can check any of them, including this page's tool, in two minutes: open the Network tab and watch.