Merging PDF Files: Order, Quality and What Breaks

Merging looks trivial: drop the files in, combine, download. Whether the result matches what you expected depends on how you prepared the inputs — particularly around order, page size and form fields.

Updated:

What survives a merge and what does not

Merging copies the page objects of several documents into a single document tree. Visual page content, embedded fonts and vector drawings carry over exactly. What gets lost is information held at the document level.

FeatureAfter mergingWhy
Page contentPreservedText, images and vectors carry over
Embedded fontsPreservedFonts from each source are combined
BookmarksUsually lostStored at document level
Form fieldsRiskyFields with the same name can collide
Digital signaturesInvalidatedThe document is rewritten
Document metadataTaken from the first fileTitle and author collapse to one

Order: the mistake almost everyone makes

Most tools sort files alphabetically by name, not by the order you selected them. If your files are scan1.pdf, scan2.pdfscan10.pdf, alphabetical order puts scan10 before scan2. In a thirty-page contract that is hard to notice.

The fix is zero padding: scan01.pdf, scan02.pdf, scan10.pdf. That naming gives the same result under both alphabetical and numeric sorting, and stays consistent in whatever tool you move the files through.

Advertisement

When page sizes are mixed

Merging A4 and Letter pages is technically fine — PDF stores a size per page. The problem shows up at print time: a printer has to pick one paper size, so pages of a different size get scaled or cropped.

Why the result is larger than expected

Merge three files and the result is usually close to their combined size, sometimes a bit more. The reason: each source file carries its own font subset. If the same typeface is embedded in all three, the merged document can end up holding three separate subsets side by side.

The difference is usually a few hundred KB. If the result crosses an email limit, try compressing after merging; doing the two steps in sequence gives a more predictable result than trying to do both at once.

Form fields and signatures

Merge two PDFs that contain fillable form fields and any fields sharing a name may start behaving as one field: type into one and the value appears in the other. That is not a bug, it is how the PDF form model works. Flattening filled forms before merging — converting fields into static content — removes the behaviour entirely.

A digitally signed document loses its signature when merged, because a signature is precisely the claim "this byte sequence has not changed", and merging changes the bytes. If signed documents must be combined, sign after the merge, not before.

A practical sequence

  1. Rename the files with zero-padded numbers.
  2. Normalise page sizes if the result will be printed.
  3. Flatten any filled forms.
  4. Merge.
  5. Check the first page, the last page and each handover point.
  6. Compress last if needed, and sign last of all.

Frequently asked questions

Does merging reduce page quality?

No. Merging copies page objects as they are; images are not re-encoded and text is not redrawn. The visual result is identical to the source files.

How many files can I merge?

There is no technical ceiling; the practical limit is your device memory. Rather than merging many large files at once, merge them in groups and then merge the groups.

Why did my bookmarks disappear?

Bookmarks are stored at document level, not on the page. Because merging builds a new document tree, most tools do not carry them over. They have to be recreated afterwards.

Can I merge a signed PDF?

Technically yes, but the signature becomes invalid. A digital signature asserts that the bytes have not changed, and merging changes them. Sign after merging, not before.

More guides

Try Konta PDF

Merging, splitting, reordering, encrypting, OCR and image-to-PDF are free. Files are processed in your browser.

Open the tools