Merge PDF files — order, bookmarks, form fields, and the file-size math

The short version

1. Drop two or more PDFs on the merger. We show a thumbnail strip with every file in the order you dropped them.
2. Drag to reorder — top-to-bottom becomes page 1 to the end of the output.
3. Optional: click a file to pick a page range (e.g. 1-3, 5, 7-9) instead of the whole document.
4. Click Merge. Download one combined PDF. Bookmarks preserved, form fields renamed to avoid clashes, original page order intact.

If that covers it, go. The rest of this post is for when the order matters, when bookmarks or form fields are involved, when the output is bigger than expected, or when you're choosing between this and Acrobat / Smallpdf / iLovePDF / PDFsam.

Order is a decision, not a default

PDF page order is fixed at merge time. You can't reorder a merged PDF after the fact without re-merging or running a page reorder tool. That means the order you set in the thumbnail strip is the order you'll live with.

Three patterns we see:

• Alphabetical by filename — the default if you just drop a folder. Works when your files are named chapter-01.pdf, chapter-02.pdf and the numbers already sort right.
• Drag to a specific sequence — for assembling a report from a cover page, a contents page, three chapters, and an appendix that don't sort alphabetically. Thumbnails make this five seconds of work.
• Reverse order — more common than you'd think. If you scanned a stack of paper face-down, page 1 is the last file. Click the reverse button.

Sort order matters most for scanned documents where the filenames are meaningless (scan-2026-04-25-173021.pdf) and the only way to know the right order is to look at thumbnails. This is where the previewed merge UI earns its keep over a command-line tool.

Page-range selection — pull parts, not whole files

You often don't want the whole PDF. You want pages 1-3 from one doc, page 5 from another, and pages 7-9 from a third. Most free mergers force you to either take the whole file or split first — two tools, two operations, twice the work.

We accept a range expression per file. Drop the PDF, click "Range", type something like:

• 1-3 — pages 1, 2, 3
• 5 — just page 5
• 1-3, 5, 7-9 — pages 1, 2, 3, 5, 7, 8, 9 in that order
• -3 — shorthand for "first 3 pages"
• 10- — shorthand for "page 10 to the end"

The syntax matches qpdf and pdftk for compatibility, so if you already know one you know ours. Invalid ranges (a page that doesn't exist, or a range that reverses) show a warning in the thumbnail strip before you merge — we'd rather tell you than produce a silently wrong PDF.

Bookmarks and the outline tree

PDFs carry an outline — the clickable tree in the left sidebar of Acrobat or Preview that jumps to chapter 3 section 2. Most free merge tools destroy this. The merged PDF opens with no sidebar, you scroll through 400 pages looking for "Appendix A", and you're furious.

The reason most tools drop outlines: preserving them is real work. Each source PDF's outline references page numbers that are no longer accurate in the merged doc. To keep them, the merger has to remap every outline entry's page reference to its new offset. That's the step Acrobat does, PDFsam does, qpdf does if you ask it to, and that cheap online tools skip.

Our tool preserves outlines by default. If both source PDFs have outlines, you get a merged outline with the source filename as the top-level entry and the original outline nested underneath. You can customize the top-level labels in advanced settings (default is the filename minus the .pdf).

If a source PDF has no outline (most scans don't), we leave it flat — there's nothing to preserve. If you want to add bookmarks manually, that's a separate editor step; the merger doesn't invent outline entries.

Form fields — the quiet collision

Fillable PDFs carry AcroForm fields with names like name,date, signature_1. When you merge two fillable forms that both use the name name, PDF readers treat them as the same field — filling one auto-fills the other. For a boilerplate field like a date or a shared header, that's sometimes what you want. For a per-page signature, it's a disaster.

Three ways a merger can handle this:

• Leave fields as-is (the default in most free tools) — collisions happen silently. Filling one "name" field fills every other "name" field across the merged doc.
• Rename colliding fields with a prefix — name from file A becomes A_name, from file B becomes B_name. Each page has its own field. This is what our tool does by default when it detects duplicates.
• Flatten fields on merge — fields become uneditable text baked into the page. Useful when you're merging signed copies and don't want anyone to edit them further.

Our default is option 2 — prefix-rename on collision, keep fillable. Option 3 (flatten) is a one-click toggle in advanced settings; use it when merging already-filled forms for archival. Acrobat exposes all three; Smallpdf and iLovePDF free tiers typically do option 1 silently, which is the worst pick for anything legally binding.

Output file size — the arithmetic

A merged PDF is usually not the exact sum of the input sizes. Three effects:

• Shared resources deduplicate. If five input PDFs all embed the same font (common — Helvetica, Times), the merged doc can embed it once and reference it five times. Savings typically 2-8% on text-heavy merges.
• Structural overhead adds up. Each source PDF contributes its own xref table, metadata dictionary, and object indirection. The merged doc rebuilds these once, slightly smaller than the sum.
• Image-heavy PDFs don't dedupe. Each embedded JPEG or scan is unique. The merger can't find savings there.

The honest rule of thumb: expect the merged output to land within 5% of the sum of inputs — slightly smaller for text-heavy docs sharing fonts, roughly equal for image-heavy scans. If your merged output is significantly larger than the sum, something is wrong (usually a free tool re-encoding every embedded image at a higher quality than the source).

If the merged PDF is too big to email, don't re-merge with different settings — chain into our PDF compressor after merging. That downsamples embedded images and often cuts the output to 30-50% of the merged size with no visible quality loss. See PDF too large to email for the full workflow.

How our tool compares (honestly)

PDF merging is commodity functionality — every PDF tool does it. What differs is what survives the merge (bookmarks, form fields), whether your file gets uploaded, and how much control you have over page ranges. Honest scoresheet:

Honest summary: for a single merge on a machine with Acrobat already installed, use Acrobat — best output fidelity. For repeated server-side merges on huge batches, PDFsam or qpdf from the CLI. For everything else — no-sign-up, no upload, real page ranges, outline preservation, form-field safety, and a chain into PDF compression afterward — our PDF merge tool is the short path.

When the merger isn't the right tool

• Scanned PDFs you want searchable. Merging scans produces a merged scan — still an image of text, not text. For a searchable merged document, OCR the pages first. See how to OCR a PDF.
• Password-protected PDFs. If a source PDF has an owner or user password, we can't read it to merge it. Remove the password first (legal reasons only — you own the doc).
• Digital signatures. A PDF's digital signature is invalidated by modification — merging counts as modification. If a source doc is legally signed, merging breaks that signature. You can still produce the merged file; just know the signature block on that source page is no longer verifiable.
• Different page sizes in one merged doc. The merger preserves each source page's size exactly — an A4 page followed by a Letter page stays two different sizes in the output. If you need a single consistent page size across the whole merged doc, that's a resize-and-merge workflow (Acrobat's "make all pages A4" step), not a plain merge.

Tips for a clean merge

• Rename source files before the merge if you plan to use the default alphabetical order. 01-cover.pdf, 02-intro.pdf, 03-chapter-one.pdf sorts correctly; cover.pdf, intro.pdf, chapter-one.pdf sorts alphabetically ("chapter" before "cover") and surprises you.
• Use page ranges instead of splitting first. If you only need pages 5-10 of a 100-page doc, type 5-10 in the range picker instead of running PDF split first and then merging. One step instead of two.
• Chain into compression for email-bound docs. Merge first (lossless, fast), then run the output through our PDF compressor. Splitting that into two steps gives you a cleaner, smaller final file than trying to compress each input separately before merging.
• Check the outline before you share. Open the merged PDF in your viewer and expand the sidebar. If the outline is empty or wrong, one of the source PDFs had no outline — add top-level bookmarks manually in a PDF editor afterward if needed.
• Flatten fields if the merged doc will be signed as a whole. Advanced settings → "flatten form fields on merge" locks every field, then you or your signer can sign the whole doc as a single document rather than re-filling the internal fields.

Common questions

Can I merge PDFs without uploading them?

Yes — our tool runs entirely in your browser using pdf-lib. The files never leave your machine. You can verify this in DevTools: open the Network tab, merge a PDF, see zero outbound requests besides the page itself loading. See why in-browser conversion matters for the privacy angle.

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

The free tier handles up to 20 PDFs and a total combined size around 100 MB before browser memory becomes the bottleneck. Paid tiers raise those limits, and the API has no practical limit for server-side jobs. For very large merges (thousands of PDFs), use the API or qpdf CLI — browser-side isn't the right tool at that scale.

Will the merged PDF preserve bookmarks and the table of contents?

Yes, by default. Each source PDF's outline is nested under a top-level entry named after the filename. If you want flat outlines or no outlines at all, toggle in advanced settings. Note: if a source PDF has no outline (most scans don't), there's nothing to preserve for that file.

What happens when two PDFs have form fields with the same name?

Our default is to rename on collision — the field name from the first file becomes A_name, from the second becomes B_name, so filling one doesn't auto-fill the other. If you actually want fields to share values (e.g. a shared "date" field across merged boilerplate), disable rename in advanced settings. If you want fields frozen to their current values, enable flatten-on-merge.

Can I reorder pages within a file before merging?

Not within the merge tool itself — it treats each input as a unit and merges in the range you specify. To reorder pages inside a single PDF, run it through PDF split first (extract each page), then merge them in your target order.

Why is my merged PDF bigger than the sum of the inputs?

Almost never — if it is, the tool you used re-encoded every embedded image at a higher quality than the source. Our merger copies image streams byte-for-byte without re-encoding, so your output is at most a few percent larger than the sum (structural overhead) and usually 2-8% smaller (shared-font dedup).

Can I merge encrypted/password-protected PDFs?

Only if you remove the password first — encrypted content can't be read without the key, and merging requires reading. If you own the doc and have the password, unlock it in a PDF editor, merge, then re-apply encryption to the output.

Does merging invalidate digital signatures?

Yes — any modification to a signed PDF invalidates the signature. If a source doc is legally signed and the signature must remain valid, don't merge it; attach it alongside instead. Merged output is still useful (a "packet" of signed docs), but verifiers will see the original signatures as no longer authoritative over the combined file.

Ready?

Merge PDF →. Drop the files, drag to reorder, optionally pick page ranges, download one combined PDF. Free, in your browser, no sign-up, no watermark. If the result is too big to email, chain into our PDF compressor — that's the standard path to an emailable document. If you need to pull parts out instead, see split PDF by pages.