PDF Merge

How to use this PDF merge tool

1. Select two or more PDF files.
2. Files merge in the order they appear in the list.
3. Click "Merge & Download" to get one combined PDF.

How does this work?

Your PDF files are loaded directly into your browser's memory and combined using a client-side PDF library — nothing is uploaded to any server. Files are merged in the order you select them.

Is there a file size limit?

Only the limits of your device's memory. Very large PDFs (hundreds of MB) may be slow in the browser, but there's no artificial cap like paid tools often impose.

What actually happens when PDFs are merged

Merging PDFs isn't like merging images — a PDF page is a structured object (text, vector graphics, embedded images, fonts, all referenced by position) rather than a flat picture, so combining PDF files means copying each source document's page objects directly into a new file's internal structure, preserving them exactly as they were. This is why merging doesn't degrade quality the way combining compressed images might: text stays selectable and searchable, vector graphics stay sharp at any zoom level, and embedded images keep their original resolution, since nothing is rasterized or re-encoded in the process — the merge tool is essentially reorganizing object references, not redrawing content.

Why bookmarks and form fields don't always survive

Interactive PDF features — fillable form fields, internal bookmarks, cross-document links — rely on internal identifiers and references that are specific to the document they were created in. When two source PDFs are combined, their internal reference structures don't automatically reconcile with each other: a form field with a given internal name in one file might collide with, or simply fail to connect properly to, structures from another file merged alongside it. Straightforward page-content merging (which is what most merge tools, including this one, focus on) reliably preserves what's visually on the page, but doesn't attempt the more complex work of rebuilding a unified, functioning set of interactive elements across originally separate documents.

Why merged files sometimes end up larger than expected

Each source PDF typically embeds its own copy of whatever fonts it uses, even if two files you're merging happen to use the exact same font. A straightforward merge operation copies each file's embedded font data along with its pages rather than detecting and deduplicating identical fonts across the merged set, so combining several PDFs that all use, say, the same corporate font can result in that font's data being embedded multiple times in the final file. This is a real but usually minor size overhead — fonts are typically a small fraction of a PDF's total size compared to images — and it's the tradeoff for a merge process that doesn't risk breaking anything by trying to be clever about shared resources across documents it has no way of confirming are truly identical.

Order matters, but mistakes are easy to undo

Since this tool never modifies your original files — it only reads them into browser memory to build a new, separate merged document — there's no risk in experimenting with the file order before merging. If the resulting order isn't right, your source PDFs are completely untouched, so reordering the list and running the merge again costs nothing but a few seconds. This is a meaningful difference from editing a PDF directly in desktop software, where reordering pages happens on the file itself and a mistake can be more disruptive to undo.

Limitations of this tool

This tool merges complete PDF files in the order you arrange them — it doesn't support extracting or reordering individual pages from within a source file before merging (for that, this site's PDF split tool can pull out specific pages first), and it doesn't support merging password-protected or encrypted PDFs without first removing that protection in other software. Everything happens in your browser's memory, so extremely large combined files (many hundreds of megabytes total) may be slow to process, limited by your device's available memory rather than any artificial cap this tool imposes.