Merging PDFs is usually straightforward: upload the files, arrange them in order, and download one combined document. The process assumes all the source files have compatible page sizes and orientations. When they do not, when an A4 portrait report is merged with a legal landscape spreadsheet and a letter-size presentation, the result is a document where pages flip between sizes and orientations with no visual consistency. Recipients scrolling through the merged file feel like they are switching between unrelated documents.
Merging PDFs with conflicting formats requires an extra step: normalizing the source files to a consistent page size and orientation before merging. This step takes a few extra minutes and transforms the merged output from a jarring patchwork into a cohesive document.
The Merge PDF operation itself is simple. The complexity lies entirely in the preparation. Once the source files are normalized, the merge produces a consistent document regardless of how different the original files were.
Identifying the Format Conflicts Before Merging
Open each source file and check the page size and orientation. Page size is typically listed in the document properties as A4 (210 x 297 mm), Letter (8.5 x 11 inches), or Legal (8.5 x 14 inches). Orientation is either portrait (taller than wide) or landscape (wider than tall). Note the size and orientation of each file. The file with the most pages or the most important content should usually set the standard that the other files are normalized to match.
If all files use standard paper sizes but differ between A4 and Letter, the difference is small enough that most recipients will not notice. If the files mix portrait and landscape, the orientation difference is immediately obvious and should be resolved before merging. The PDF Pages normalization decision should prioritize the reading experience of the recipient over the convenience of the sender.
Normalizing Page Sizes Before Merging
Use a PDF tool that supports page resizing to convert all source files to the same dimensions. Resize the minority files to match the majority format. When resizing, choose how the content should fit the new page size. Scale to fit shrinks or enlarges the content to fill the new dimensions. Center and keep original size places the original content in the center of the new page size with white margins, preserving the original scale but potentially making content look small or lost on a larger page.
Scale to fit is usually the better choice for merging because it uses the full page area consistently. The exception is when scaling would make text too small to read comfortably. In that case, keep the original size and accept the margins. WukongPDF's PDF Tools for page resizing and merging handle both approaches.
Handling Mixed Orientations
If the merged document needs a single orientation, rotate the landscape pages to portrait or vice versa. Rotation changes the reading direction: a landscape spreadsheet rotated to portrait will display sideways on a portrait-oriented screen. This is acceptable for occasional pages where preserving the content is more important than perfect orientation. For documents where mixed orientation is unavoidable, such as reports with wide data tables alongside portrait text, keeping the mixed orientations may be better than forcing everything into a single orientation.
After merging, scroll through the entire document and check that all pages display correctly. Pay attention to the transitions between source files. These are where orientation changes and size mismatches are most visible. A quick scroll catches the page that accidentally rotated the wrong direction.
When Merging Is Not the Right Solution
Some documents are better kept separate. If the source files serve different audiences, have different security requirements, or would create a confusing combined document, keep them as individual files and share them in a folder or ZIP archive. The recipient sees related but distinct documents rather than a merged file that blurs the boundaries between them. Merging is a tool, not a requirement.