Organising pages
How to merge PDFs — and keep them in the right order
Upload the files, put them in the order you want before merging, and download the combined PDF — the common trap is alphabetical sorting, which puts page10 before page2.
Merging PDFs is the most-used PDF operation after opening one, and it is usually simple. The problems that do come up are almost all about order and about what quietly gets lost.
The ordering trap
Say you have scanned a twelve-page document as individual files:
page1.pdf page2.pdf page3.pdf ... page10.pdf page11.pdf page12.pdf
Sort those alphabetically and you get:
page1, page10, page11, page12, page2, page3, ...
This is not a bug. Alphabetical comparison looks at characters, and the character 1 sorts before 2, so page10 comes before page2. Every system that sorts by name does this unless it has been specifically taught not to.
The fix that always works is zero-padding: name files page01, page02, ... page12. Then alphabetical and numerical order are the same thing, and every tool everywhere handles it correctly. If you scan documents regularly, setting your scanner's naming pattern to include padded numbers eliminates this problem permanently.
The other fix is a tool that sorts numerically — comparing the numbers inside the names rather than the characters. ZIP to PDF does this when converting an archive, precisely because zipped scan sets hit this constantly.
Whichever route, check the order before merging, not after. Reordering afterwards means starting again.
What happens to your files
The mechanics are worth understanding because they explain what survives.
Merging copies the pages of each document into a new one, in sequence. Page content — text, fonts, images, vectors — comes across intact. Text stays selectable. Nothing is re-rendered or re-compressed, so there is no quality loss.
What is less predictable is everything that lives *outside* the page content:
Bookmarks. The outline tree belongs to the document, not the pages. Good tools rebuild it; simpler ones drop it. On a long merged document this is worth checking.
Links. Internal links pointing to a page within the same file usually survive. Links pointing outside — to a page that was in a different source file — may not, because their target moved.
Form fields. The most fragile. AcroForm fields belong to the document, and two merged documents may have fields with identical names, which collide. If you are merging fillable forms, test the result before relying on it.
Metadata. The merged file gets new document properties. Author and title from the sources do not automatically carry across.
File size
A merged PDF is roughly the sum of its parts, sometimes a little less.
Where it can be noticeably less is when the same font or image appears in several source documents. A good merge stores one copy of a shared resource rather than one per source. Where it can be a little more is bookkeeping overhead.
If the result is too large to email, that is a separate job — Compress PDF reduces the size afterwards. Merging first and compressing once gives a better result than compressing each piece and then merging.
Merging things that are not PDFs
Often the real task is not "combine these PDFs" but "combine these files": a Word document, two spreadsheets, some photographs and an existing PDF, into one deliverable.
Two routes. Convert everything to PDF individually and then merge, which gives you control over each conversion's page setup. Or put everything in a .zip and convert the lot in one go with ZIP to PDF, which converts each supported file and merges the results in order.
The second is much faster for a large batch, and it reports which files it could not convert rather than silently leaving them out.
After merging
Two things are usually worth doing to a freshly merged document.
Add page numbers. A 60-page merged bundle with no numbers is painful to discuss. Page Numbers stamps them on — and this must be done *after* merging, since the numbers are drawn permanently and reordering later would leave them wrong.
Check the joins. Look at the first page of each section. Mixed page sizes and orientations are the usual surprise — an A4 report with a landscape A3 drawing in the middle is legitimate but often unintended.
A practical order of operations
For assembling a document from many pieces, this sequence causes the fewest problems:
- Get every piece into PDF form.
- Put them in order — rename with padded numbers if sorting is doing the ordering.
- Merge.
- Check the page order and the joins.
- Add page numbers.
- Compress if it needs to be emailed.
- Protect it if it needs a password.
Each step assumes the one before it is settled. Doing them out of order is what creates the rework.
Checking the result without reading all of it
A merged document of 200 pages does not need proofreading. It needs three specific checks, which take about a minute.
The page count. Add up what you expected. A number that does not match means a file was missed or added twice — the single most common merge error, and invisible unless you count.
The seams. Jump to the first page of each source document. That is where a wrong order shows, and it is the only place it shows.
The last page. A document ending mid-sentence means a file was truncated or the wrong one was last.
Bookmarks, links and what happens to them
Two things behave differently, and both catch people out.
Internal links break. A contents entry in document A pointing to its own page 12 now points to page 12 of the merged file, which belongs to a different document. Nothing looks wrong; the link just goes somewhere unexpected.
Bookmarks may or may not survive. Depending on the tool, each source document's outline is either carried across under its own heading, merged into one flat list, or dropped. If your documents rely on bookmarks for navigation, check the merged file before assuming.
Neither is a reason not to merge. They are a reason to look, once, at anything with a table of contents in it.
Merging things that are not PDFs yet
If half your material is Word documents and images, converting each one and then merging is the long way round.
Convert the odd ones out first — Word to PDF for documents, Image to PDF for photos — then merge everything in one pass. Or, if it is a whole folder of mixed types, ZIP to PDF does the conversion and the joining together, ordered by filename.
Common questions
Why are my merged pages in the wrong order?
Almost always alphabetical sorting: page10 sorts before page2 because it compares characters. Rename with padded numbers (page01, page02) or use a tool that sorts numerically.
Do bookmarks and form fields survive a merge?
Page content always does. Bookmarks depend on the tool. Form fields are the most fragile, because fields with identical names in different sources collide — test a merged form before relying on it.
Does merging reduce quality?
No. Pages are copied, not re-rendered or re-compressed, so text stays selectable and images keep their original quality.
Can I merge files that are not PDFs?
Convert them first, or put everything in a .zip and use ZIP to PDF, which converts each supported file and merges the results in order.