Combining two PDFs takes ten seconds. The problems show up afterwards — in the ordering, the bookmarks, and the form fields nobody checked.
Why do merged pages end up in the wrong order?
Almost every ordering problem traces back to the same cause: filenames sort as text, not as numbers. A file manager or a merge tool sorting alphabetically produces this:
Chapter 1, Chapter 10, Chapter 11, Chapter 2, Chapter 3…
That is not a bug, it is how string comparison works — "1" sorts before "2", so "10" sorts before "2". It bites hardest when you select thirty scanned pages at once and trust the default.
- Pad your numbers. Name files
01,02…10rather than1,2…10. Sorting then matches reading order for free. - Check the thumbnails before exporting. Any merge tool worth using shows you the sequence. Ten seconds of looking saves redoing it.
- Add files in batches when order matters and names are inconsistent — add the first document, confirm, then the second.
The Merge PDF tool lists files in the order you add them and lets you drag to reorder, so alphabetical sorting never silently overrides your intent.
What gets lost when you merge?
Merging is not a neutral operation. Page content always survives; several other things frequently do not, and no tool warns you.
| Element | Survives a merge? | What to do |
|---|---|---|
| Page content, text, images | Always | Nothing |
| Interactive form fields | Usually flattened | Fill in after merging, not before |
| Bookmarks and outline | Often dropped | Rebuild in a PDF editor if needed |
| Internal hyperlinks | Often break | Check any cross-references |
| Digital signatures | Always invalidated | Merge first, sign last |
| Page rotation | Preserved | Nothing |
| Attachments and embedded files | Usually dropped | Re-attach afterwards |
The form field one causes the most real damage, because it is silent. Someone fills in a twelve-page application, merges it with their supporting documents, and sends a file where every field is now flat text that cannot be edited — or worse, blank. If your document has fields, merge first and fill second.
How do you merge only some pages from each file?
Frequently what you want is not "all of A then all of B" but pages 3–7 of one document and page 12 of another. Two approaches work.
The direct route is to split first, then merge. Use Split PDF to extract the ranges you want as separate files, then feed those into the merge tool in order. It is two steps but completely predictable, and you can verify each extraction before combining.
The other is to merge everything and delete pages from the result. Faster for one or two unwanted pages, worse for anything more complex — it is easy to lose count in a 200-page document.
If you find yourself doing this monthly for the same report, standardise on split-then-merge: the intermediate files are reusable and self-documenting.
Does merging change the file size?
A merged PDF is roughly the sum of its parts, and often slightly more than the sum. That surprises people who expect merging to deduplicate.
The overhead comes from repeated resources. If five documents each embed the same corporate logo and the same font subset, a simple merge carries five copies of both. Some tools deduplicate identical objects; many do not.
If the result is uncomfortably large, compress after merging rather than before — one compression pass over the combined file avoids compounding lossy re-encoding across each part. How to compress a PDF without losing quality covers what to expect.
Is it safe to merge confidential PDFs online?
Merging is the operation people most often perform on exactly the documents they least want to upload: bank statements for a mortgage application, medical records, contracts, passport scans and payslips bundled for a visa.
A conventional online merge tool uploads all of those to a server. Even under a good retention policy, they exist somewhere outside your control for a period.
Browser-based merging avoids the question entirely. The PDF structure is rewritten locally through WebAssembly and the output is generated as a download from memory — there is no upload request to make. That also removes the practical limits: no total size cap, no file count cap, no queue at busy times.
You can verify this on any tool: open the Network tab in developer tools before you merge. An upload-based service shows a multi-megabyte outgoing request. A local one shows nothing.
Frequently asked questions
How many PDFs can I merge at once?
On this site there is no fixed limit — the constraint is your device’s memory. Merging a few dozen ordinary documents is unremarkable. If you are combining hundreds of large scans, do it in batches of about twenty and then merge the batches, which keeps memory use predictable.
Can I merge a PDF with a Word document or an image?
Not directly — everything has to be a PDF first. Images are easy: convert them with JPG to PDF, then merge. For Word documents, export to PDF from Word itself (File → Save as PDF), which preserves the layout better than any converter will.
Will merging reduce the quality of my pages?
No. Merging copies page content objects across unchanged; it does not re-encode images or rasterise text. Quality is identical to the source files. Only compression is lossy, and that is a separate operation.
Why is my merged PDF larger than the files I combined?
Because repeated resources are carried multiple times. Five documents sharing one logo and one embedded font produce a merged file with five copies of each, plus structural overhead. Compress the merged result if size matters.
Can I reorder pages after merging?
Yes, but it is easier to get the order right during the merge, where you can drag whole files. To reorder individual pages afterwards, split the file into single pages and merge them back in the order you want.
Does merging remove passwords or encryption?
An encrypted PDF cannot be merged until it is decrypted, because the tool cannot read its contents. The merged output is unencrypted — if the combined document needs protection, apply it to the result as a final step.