Merging is the document task people assume is a one-click operation — and it mostly is, until the first time the output has pages in the wrong order, a scan that's rotated sideways, or a file so large it can't be emailed. Merging is not just gluing pages together; it's assembling them in the right sequence with consistent orientation and a sensible file size. Those three concerns are what separate a usable merged document from a mess.
What merging actually preserves
A PDF merge concatenates the page streams of the source files into one document. Text stays selectable, images keep their resolution, and internal links and bookmarks are usually carried across. What you can't assume survives: interactive form fields can behave unpredictably when multiple forms are combined, and fonts embedded in one file may not render identically in another if the merge tool is careless. A good merge tool preserves the pages exactly as they were — if the output looks different, the tool did something to the content, which is a red flag.
The real workflow
- Add the files in the order you want them to appear — most tools let you drag to reorder before merging, which is far easier than fixing the order afterward.
- Rotate any scans that arrived sideways. A portrait document scanned as landscape should be fixed in the source, not in the final file.
- Check for duplicate pages and blank pages (common when someone scanned a stack with a stray empty sheet in the middle).
- Merge, then open the result and skim it end to end — verify the page count is the sum of the sources and the first and last pages are right.
- If the merged file is bloated, compress it before sending; merging never shrinks files, it only adds pages.
Merge first, compress second
Compressing before merging wastes effort — any new pages added afterward miss the treatment. Merge everything, then run one compression pass on the finished document. You'll get a smaller file than compressing the parts separately.
The most common merge mistake is assuming the input order will survive. Many tools append files in the order they were selected, not the order they appear on screen — so a 30-page contract can silently gain a misplaced appendix. Always confirm the final page order before you send the document anywhere.
Merge with full control
ForgePlug's Merge PDF lets you drag files into the exact order you want, preview every page, rotate scans, and merge — all in your browser, no uploads.
Open Merge PDFWhy a merged file can be bigger than the sum of its parts, font-wise
Merging concatenates whatever each source file embeds, and if five source documents each use a different typeface, the merged file carries all five font sets even though any given page only displays one of them. A single document reusing the same font throughout doesn't have this problem, but stitching together files from different authors, templates, or software — a contract drafted in one word processor, an appendix exported from another — routinely does. It's one of the less obvious reasons a merged file can weigh noticeably more than a simple sum of the source file sizes would suggest, and it's exactly the kind of bloat a compression pass after merging cleans up.
Merging a file that's already password-protected
A source PDF that's itself locked with a document password generally can't be merged directly — the merge tool has to read the actual page content to combine it, and encrypted content isn't readable without the password. If one of your source files is protected, unlock it first (with a password you're authorized to use) before adding it to the merge, then re-protect the finished, combined document afterward if it still needs to be locked. Trying to merge an encrypted file without unlocking it first is the most common reason a merge silently fails or drops a file from the output.