Merge PDF Files: Common Errors and Fixes
Quick answer
Five problems account for almost every failed merge. Wrong order comes from the picker, not the tool; fix it by selecting again. A refusal is either a protected file or the 200-page limit. Mixed page sizes are usually correct behaviour, not a bug. A missing text layer means that source was a scan. And a merge that "lost" a file usually means the file was not a PDF at all. Each has a specific check.
What this article covers
The symptoms in the order they appear in practice, the cause behind each, and the fix. It also covers the two cases where the right answer is a different tool. Read the beginner's guide first if you have not run a merge yet.
What it actually does
Because pages are copied rather than redrawn, the failure modes are structural rather than visual. There is no quality loss to diagnose; the questions are which pages went in, in what order, and whether each source was readable. That makes debugging a merge much more mechanical than debugging a compression.
The tool refuses rather than guesses in two places — an encrypted file, and a file that is not a PDF — because a silent skip would produce a document that looks complete and is not. The page count limit is the third refusal.
Step by step
- Count the pages in each source and add them up.
- Compare the total with the merged file's page count.
- If they differ, identify which source is missing by finding the seam where it should be.
- If the run was refused, read the message: it names the file or the limit.
- Re-select in the correct order and run again from the sources.
What to check after download
- Page count against the sum of the sources, and the source list against the picker, because a picker that dropped a click is the most common surprise.
- The first page of each source at its expected position.
- The seams for blank pages or duplicated pages.
- Text selection per source.
- Page size where the sources differed.
- The file name — a revision needs a revision number.
- Form values in fillable sources.
Fixes by symptom
The pages are in the wrong order. The picker's selection order was not the intended order. Fix: select again, clicking in the order you want. There is no reorder control, by design.
A file was refused. Either it is password-protected or it is not really a PDF. Fix: open it alone; if it asks for a password, remove that in the owning application. If it opens as a web page, it is an HTML download with a PDF name.
The merge was refused for page count. The total exceeds 200 pages. Fix: split the sources into two documents, or merge only the parts this recipient needs.
A source is missing from the result. Check the picker selection; a multi-select that looked complete may have dropped the last click. The page count check catches it.
A page looks resized. It probably is not: each page keeps its own dimensions, so a Letter page beside A4 pages looks different by design. Fix: resize the odd source in its own editor before merging, if uniformity matters.
The text cannot be selected. That source is an image-only scan. Fix: nothing — the merge preserved what was there. OCR is a different operation and this tool does not do it.
A link points somewhere unexpected. Links are copied with their targets. A relative link may resolve differently once the file lives in a new place. Fix: check links in the merged file before sending it on screen.
Links or bookmarks are not what you expected. The documented guarantees are page-level: size, text, links, form fields. Document-level navigation should be checked after download, not assumed.
The document is much larger than expected. Nothing is compressed by a merge, and the sources included a scan with large images. The merge does not compress anything, so the result is roughly the sum of the inputs. That is correct behaviour, and the fix is a different tool, not a different merge.
Common beginner mistakes
Debugging the merge when the source is the problem. Open the source alone first; if the page is wrong there, the merge copied it correctly.
Re-running with the same selection after a refusal. If the refusal named a file, that file has to change before a re-run can succeed.
Assuming a 200-page source can be merged with another. The limit is the total, not per file.
Assuming the merge reordered the files alphabetically. It did not; the picker's selection order is the only order the tool knows. If the result looks sorted by name, that is how the files were selected.
When this tool is the right choice
When the pages are final and the destination wants one document. If the problem is order inside a single file, or removing pages, this is the wrong operation — those are page-organisation tools, and forcing them through a merge produces a document with the wrong contents.
Related tools
If the merged file is too large for its destination, Compress a PDF makes a smaller delivery copy at the cost of the text layer. If a recipient wants page images, PDF Converter renders them.
Use this tool
Re-select in the intended order on Merge PDF Files and verify the page count against the sum of the sources before you send anything.
Next step
For recurring packs, read business use cases and write the order and the naming convention down once, so the next merge is a checklist rather than a decision.
Continue Exploring
Browse more release notes and the tools they reference.