The short answer

Merging is one of the few PDF operations that is genuinely cheap. A PDF is a container of numbered objects; joining two of them means copying the page objects from the second file into the first, renumbering the references, and writing a new cross-reference table at the end. No page is re-rendered, no image is re-encoded, and no text is re-laid-out. A browser can do that with a few hundred kilobytes of JavaScript.

That is why a merge can happen with the network disconnected. If a site asks you to wait while it "processes" your files, it is not merging — it is uploading, merging on a machine it controls, and downloading the result.

A "your files never leave your device" badge is a claim, not a mechanism. The Network panel of the developer tools shows the truth in one glance: if nothing is sent while you pick files, nothing is sent.

Why so many mergers upload anyway

Server-side merging is easier to build once and sell to everyone: the library is mature, the phone does not need memory for a 200 MB document, and the same code path works for a batch of fifty files. It also creates a place to store the result, which is how a free service pays for itself — with retention, an expiring download link, and occasionally a subscription wall in front of the download button.

None of that is necessarily dishonest, but it changes what you have to trust. You are no longer judging a conversion; you are judging a company, its retention policy, its jurisdiction, and whether the delete button actually deletes.

What to check before you drop a file

These four checks take about ten seconds and settle the question for any merger, including this one:

  • Does it work offline? Load the page, disconnect the network, then merge. A browser-side merger keeps working.
  • Does the file size limit look like a memory limit or a business limit? A tab runs out of memory at a few hundred megabytes; a business limit is usually a round number like 10 MB.
  • Is there a sign-up between you and the download? If the result is already produced, an account prompt is a marketing step, not a technical one.
  • Does the page tell you what happens to the file afterwards? "Deleted after one hour" is a retention policy; "never uploaded" is a different architecture.

When the browser is the wrong tool

Local merging has real limits, and they are worth knowing before you start. A tab has less memory than a desktop application, so a stack of very large files can fail where a native tool would not. Password-protected PDFs must be unlocked first, because the pages cannot be copied without decrypting them. And a phone will hit its memory ceiling sooner than a laptop.

For ordinary documents — contracts, scans, tickets, a term paper split into chapters — none of that matters. The merge is over before a server could have finished the upload.