Merge PDF Files

A PDF isn't a flat stack of pages — it's a tree. Every file has its own page tree, its own font and image objects, and its own cross-reference table mapping object IDs to byte offsets. When you 'merge' two PDFs, a tool has to walk each file's object graph, copy every referenced object (fonts, images, content streams) into a new file, renumber every object ID so nothing collides, and rebuild a single page tree that points to the right pages in the right order.

That's why merging isn't just concatenation. Two PDFs can both use an object numbered 12 internally — if a merger just glued the bytes together, the second file's object 12 would silently overwrite or corrupt the first. A correct merger, like the pdf-lib library this tool runs on, treats each source file as an isolated document, copies pages (and their dependencies) into a new document object by object, and only then writes a fresh cross-reference table.

| Element | Survives merge | Why |

| --- | --- | --- |

| Page content (text, images, vectors) | Yes | Copied directly as content streams |

| Fonts and embedded images | Yes | Copied as dependent objects |

| Page order between files | Yes | Controlled by your arrangement before merging |

| Internal bookmarks / outline tree | Often lost | Each source file has its own outline; there's no universal rule for merging two separate trees |

| Internal links (jump to page X) | Often broken | Page-number references point to the old document's page index, not the new one |

| Form fields (AcroForms) | Partially | Field values usually survive; field names can collide across files and get renamed |

| Metadata (title, author) | From first file only | Only one document can own the metadata slot |

Click the drop zone or drag your PDF files onto it — add at least two.

Reorder the files using the up and down arrows so they appear in the order you want the final document to read.

Click Merge PDFs — the combined file is generated locally and downloads instantly.

Open the result and verify the page order before deleting your originals.

The order you set in step 2 is final for that merge — this tool combines whole files in sequence, it doesn't interleave individual pages from different files.

Don't just check the file opens — check the seams. Scroll to the exact page where one source file ends and the next begins; this is where page-numbering, orientation, and font-rendering mismatches show up first. If your source files came from different origins (one scanned, one exported from a word processor), watch for a jump in page size (Letter vs A4) at that boundary — merging preserves each page's original dimensions, it doesn't normalize them.

If you're privacy-conscious, open DevTools → Network before merging: since this runs entirely client-side, you should see zero upload requests while the files combine.

Merging before reordering: it's easier to arrange files first, then merge once, than to merge and re-merge.

Assuming bookmarks carry over: if you need a navigable outline in the final PDF, plan to rebuild it in a PDF editor afterward — merging tools generally can't reconcile two different outline trees automatically.

Merging password-protected files without a plan: the tool can read many encrypted PDFs, but the output is unencrypted unless you re-protect it afterward.

Trusting internal links after merging: a 'jump to page 4' link created in the original file may now point to the wrong page in the combined document, since page numbers shift.

There's no hard cap on how many PDFs or pages you can merge — the tool has no arbitrary limit — but everything happens in your browser's memory, so very large merges (hundreds of high-resolution scanned pages) are bounded by your device's RAM rather than any server-side quota. If a merge of dozens of large scanned files stalls, try merging in smaller batches and then merging the batches together.

Combining a signed cover letter with a resume before emailing an application.

Assembling monthly bank or utility statements into a single yearly PDF for tax records.

Joining scanned chapters from Images to PDF into one book-length document.

Stitching together contract amendments into the original agreement for a single source of truth.

Merging exported reports from different tools into one packet for a client or reviewer.

Q: Is merging PDFs really free and unlimited?

A: Yes. There's no account, no watermark, and no daily cap — merge as many files as you need.

Q: Are my PDFs uploaded to a server?

A: No. Merging runs entirely in your browser using the pdf-lib library; you can confirm this yourself in DevTools → Network by watching for the absence of upload requests during the merge.

Q: What's the maximum number of PDFs I can merge?

A: There's no limit set by the tool itself — it's bounded only by your device's available memory, and most browsers handle hundreds of pages without trouble.

Q: Can I reorder individual pages, not just whole files?

A: This tool merges whole files in the order you arrange them. To build a custom page-by-page order across documents, first pull the pages you want with Extract PDF Pages, then merge the resulting files here.

Q: Does it work on encrypted or password-protected PDFs?

A: It can load many password-protected PDFs, but only merge files you're actually authorized to access — the merged output itself is not re-encrypted automatically.

Q: Will the merged PDF keep its bookmarks and links?

A: Page content transfers fully, but interactive elements like the bookmark outline and internal jump-links are a known limitation of client-side merging and may not carry over cleanly.

Q: My merged file looks fine but is much larger than the sum of the originals — why?

A: This usually happens when the source files embed the same font or image separately; a merge tool that copies objects file-by-file won't always deduplicate identical fonts across documents, so some size overhead is normal.

Merge your files with the Merge PDF tool, then clean up the result with Rotate PDF for any sideways pages, Delete PDF Pages to drop blank scans, or Add PDF Watermark before sharing the final document.