Skip to main content

PDF Merger

Merge multiple PDF files into a single document with drag-and-drop reordering.

Reviewed by · Last reviewed

📄

Drop PDF files here or click to upload

Select multiple files at once

How to Merge PDF Files

  1. Drop several PDFs onto the upload zone or click the dashed box to pick multiple files at once through your OS file picker. Each accepted file shows as a row with its size and a drag handle.
  2. Order the queue using the up and down arrow buttons on each row. The top file becomes page one of the output; files below continue the page sequence in order.
  3. Prune and extend. Click the X on any row to drop it, or re-open the picker to append more files without losing your existing order.
  4. Click "Merge & Download" to assemble and save a single combined PDF. The file downloads as merged.pdf and your source files on disk are untouched.

What the Merger Does to Your PDFs

Behind the dropzone, the page calls pdf-lib's PDFDocument.load on each uploaded file to parse its cross-reference table (XRef), catalog, and page tree. It then creates a fresh, empty PDFDocument and uses copyPages to pull every page object, font dictionary, and image XObject into the new document's object pool. Each copied page is appended with addPage, so the final output has one continuous page tree rather than a collection of nested documents. When you click Merge & Download, save serializes the new object pool into a single byte stream, regenerates the XRef, and hands it to a Blob so the browser can trigger a download. No fetch call fires anywhere in the pipeline; the only network request is the initial page load.

Document Workflows Where Merging Actually Matters

  • Assembling a loan application packet (W-2, 1099, bank statements, tax returns) into a single file the underwriter can flip through without switching tabs.
  • Combining a signed MSA, a statement of work, and an order form into one artifact for a SOC 2 evidence binder.
  • Merging scanned receipts into a monthly expense report where the accounting team wants a single PDF per employee.
  • Packaging a main contract with exhibits A through G before sending to DocuSign so the signer does not have to accept multiple files.
  • Stitching a front cover and a back cover onto a technical datasheet that marketing needs to publish.
  • Combining board meeting minutes from Q1 through Q4 into one annual archive for governance review.

Common Pitfalls When Merging PDFs

The tool preserves raw page content perfectly, but higher-level structure can fray. Bookmarks (the outline tree) are rebuilt from scratch per document in pdf-lib and may not carry over; if the inputs had a table of contents, it will likely need to be reinserted. Cross-document hyperlinks that referenced a page inside another source file will dangle because those targets no longer share the same object graph. AcroForm fields with identical names across inputs will collide and only the first occurrence wins. Password-protected files cannot be loaded at all, so they must be unlocked first. Very large merges (dozens of files totaling more than a few hundred megabytes) can exhaust the tab's heap in Safari and Firefox before Chromium, so consider splitting the job into two passes. Finally, scanned PDFs with embedded JPEG 2000 images take longer to copy because pdf-lib decodes and re-encodes their object streams.

The PDF File Format in One Minute

A PDF is not a flat document; it is a database of numbered objects plus a cross-reference table at the end that says where each one lives. The root object points at a catalog, which points at a page tree, where each page is a dictionary referencing a content stream and a resources dictionary. Merging is essentially a graph-copy operation: take the subgraph rooted at each source document's page tree and splice it under a new parent. ISO 32000-2 (PDF 2.0, 2020) formalizes this structure and superseded ISO 32000-1 (PDF 1.7, 2008); both documents are open standards published by ISO and maintained in sync with Adobe's historical reference. For long-term archival, ISO 19005 defines the PDF/A subset, which forbids features that would break twenty years from now (JavaScript, external fonts, encryption) and is what you want when merging files that will be filed with a regulator.

How This Compares to CLI and Desktop Alternatives

For one-off merges, a browser tool is faster than installing anything. For a hundred-file batch or anything that needs bookmarks preserved, a CLI wins. pdftk input1.pdf input2.pdf cat output merged.pdf remains the simplest invocation if you already have pdftk installed. qpdf --empty --pages one.pdf two.pdf -- merged.pdf gives the same result with better AES-256 compatibility if any inputs are encrypted (supply --password per file). mutool merge -o merged.pdf one.pdf two.pdf from MuPDF is the fastest of the three on large pages because it writes a compressed object stream by default. macOS Preview can drag-and-drop thumbnails between two open documents with no install at all. Adobe Acrobat Pro is the only option that reliably rebuilds a combined table of contents from source bookmarks, which matters if your output is a compliance submission.

Frequently Asked Questions

Is there a maximum file size or count?

There is no hard cap built into the tool, but the practical ceiling is browser memory. Chromium comfortably handles a hundred files totaling a few hundred megabytes; Safari is more conservative and may throw RangeError on heap growth past roughly 500 MB. If you are bumping against a limit, split the job into two or three smaller merges and combine those results at the end.

Does merging preserve form fields and digital signatures?

Form fields with unique names carry over intact and remain fillable. Fields sharing the same name across source documents collide on merge and only the first occurrence is kept, which is why standardized internal form templates usually need renaming before they are combined. Digital signatures survive the copy as visual annotations but always report as broken because their byte-range digest does not cover the merged object pool.

How is the merge order determined?

Strictly top-to-bottom in the file list on the left side of the tool. Drag with the up and down arrows until the list matches the page order you want in the output. The first file contributes page 1 through its own last page, then the second file continues the numbering, and so on.

Why can I not merge a password-protected PDF?

pdf-lib refuses to load encrypted documents because the content streams are opaque without a decryption key, and no password prompt is provided in this UI. Run the PDF through the Unlocker with its correct password first, or use qpdf --decrypt on the command line, then drop the plaintext copy into the merger. This is a deliberate separation of concerns: we never want to auto-prompt for passwords mid-merge.

Does my PDF get sent to any server during merging?

No. The merger runs entirely inside the page using pdf-lib compiled to JavaScript. There is no upload endpoint defined, no telemetry that exfiltrates file contents, and no service worker that intercepts reads. You can verify by disconnecting your network after the page finishes loading; the merge still works. The only outbound traffic from this page is the usual analytics ping and it does not carry file data.

Will the merged PDF be smaller than the sum of its parts?

Usually slightly smaller, because pdf-lib deduplicates identical font and image resources as it copies pages. If the sources share an embedded font (Helvetica, Calibri), the combined document carries one copy instead of N. Scanned PDFs with unique images page-by-page see no such savings. If tight file size matters, run the output through the PDF Compressor afterward.

Can I append the same PDF twice, for example to duplicate a cover sheet?

Yes. The file list treats each drop as a separate entry even if two entries point at the same source bytes, so dropping the same cover sheet twice produces a merge where that content appears twice at the positions you chose. Useful for templates that need a title page and a copy at the end.

What happens to table-of-contents bookmarks after a merge?

pdf-lib does not currently copy the outline tree across documents, so the merged output typically has no bookmarks even if the sources did. The page content itself is untouched. If you rely on a functional TOC for a compliance submission, use a desktop tool like Acrobat or PDF Studio that explicitly rebuilds the outline, or add bookmarks back manually in the final file.

How does this differ from a PDF portfolio?

A PDF portfolio is a container that embeds its children as attached files rather than flattening them into one continuous page stream. This merger produces a flat, linear document where every page is a real page in the page tree, which is what most downstream tools and print services expect. If you genuinely need a portfolio, Acrobat Pro remains the right tool for that specific construct.

Can the merger reorder pages within a single document?

Not here. The merger works at file granularity; for page-level reordering use the PDF Page Reorder tool, which exposes each page as an item you can move up or down.

More PDF Tools