Merge PDF Files

Combine two or more PDFs into a single document. The whole merge happens inside your browser tab — your files are never uploaded to a server.

0 uploads

Most online PDF mergers upload your document to a remote server, process it there, and keep a copy for hours. If you are merging contracts, invoices, medical records or ID scans, that is a real problem. PDFLocal does the opposite: it loads pdf-lib into your browser, reads your files locally, and writes the merged result in memory. Open your browser devtools Network panel while you click Merge — you will see zero upload requests.

The result is unlimited. There is no daily quota, no two-file limit, no file size cap imposed by a server, and no watermark stamped across your pages. The only limit is the memory of your own device.

The list order is the page order

A merge cannot know which document should come first, so the order shown in the file list is literally the order of the output. Two habits make that reliable. Name the files so they sort the way you think about them — 01-cover.pdf, 02-terms.pdf, 03-appendix.pdf — and compare the list against the printed pages once before running the merge rather than after. Adding forty files and only then noticing the order is wrong means reordering forty files.

Mixing page sizes is allowed, and usually a mistake

Merging A4 invoices with Letter-size statements produces a document where every page is a different shape. Nothing breaks: each page keeps its own dimensions and viewers show them one after another without complaint. What breaks is everything downstream. Print dialogs scale one set to fit the other, two-pages-per-sheet imposition becomes impossible, and the file stops looking like one document. If the merged result will be printed or filed, normalise the page size afterwards with Resize Pages, which rescales each page without re-rendering it.

What carries over, and what does not

Merging a document that has already been signed

Worth a moment of thought, because it is easy to undo somebody else's work by accident. A drawn or stamped signature is page content, so it travels into the merged file unchanged — usually exactly what you want when assembling a signed set. A certificate-based signature keeps its visible mark but loses its validity, and the recipient gets a warning instead of a confirmation. Assemble first and sign last whenever you have the choice.

What merging does not give you

Merging turns many files into one. It does not make that file searchable, and it does not make it smaller — the merged document is roughly the sum of its parts. If the goal is a stack of scans that behaves like a real document, merging is step one and tidying is step two: number the pages, crop the scanner edges, normalise the page size. The guide on combining scanned documents into one PDF walks through that sequence in order.

How to merge PDF files

  1. Add your PDFsDrop the files you want to combine, or click to browse. Add as many as you like.
  2. Set the orderUse the arrow buttons to move a file up or down. The merge uses the order shown in the list.
  3. Click Merge PDFEverything is processed locally. No progress bar waiting on a server round trip.
  4. Save the resultA single merged PDF downloads to your device. Nothing is left behind on any server.

Frequently asked questions

Are my files uploaded anywhere?
No. The entire operation runs in your browser using JavaScript. You can verify this yourself by opening the Network panel in your browser developer tools — no request carries your file.
Is there a file size or page limit?
No artificial limit. You are bounded only by your device memory. Merging a few hundred pages works comfortably on a laptop or phone.
Will my PDFs have a watermark?
Never. There are no watermarks on outputs, and no feature is locked behind an account.
Can I merge password-protected PDFs?
Encrypted PDFs must be decrypted before editing. Browser-side libraries cannot open them, so remove the password first, then merge.
Do bookmarks and links survive the merge?
Page content, images and form fields are preserved. Document outlines and cross-document internal links are not rebuilt, because they point to page indexes that change after merging.

Related tools

Related guides

Every tool on this site runs locally. Read the no upload policy to see how to verify it yourself.