Why Is My Merged PDF Bigger (or Smaller) Than the Originals?

Combine three 2 MB PDFs and you'd expect a 6 MB result. Instead you get 4 MB, or 9 MB, and neither number feels like it should be possible if merging is "just" sticking pages together. It is just sticking pages together — the surprising part is everything a PDF quietly carries around per file that has nothing to do with the pages themselves.

"Bigger" also means something else to a lot of people asking this: not the file size, but one page that looks far bigger or smaller than the rest when you scroll through the merged document. That's a different problem with a different cause, and it's covered in the next section before getting to file size.

When one page looks much bigger or smaller than the others

You merge a few documents, scroll through the result, and one page fills the screen while the next is a small rectangle floating in white space — or the page you added is enormous and the originals look like postage stamps beside it. Nothing is broken. Every page in a PDF carries its own physical size, in inches or millimetres, and merging keeps each page at exactly the size it had in its source file. Your viewer is showing them to scale relative to each other, and they were never the same size to begin with.

The usual culprit is a page that was made from an image. An image has pixels, not inches, so whatever converted it to PDF had to decide how big each pixel is. Many converters ignore the resolution saved in the image and assume 72 pixels per inch, which is the PDF's own unit. A scan or photo saved at 300 pixels per inch then comes out 300 ÷ 72 ≈ 4.17 times larger in each direction than intended. That exact ratio turns up in real reports: a batch of images meant to be 29 × 26 cm that became 120.83 × 108.34 cm pages after conversion — both dimensions scaled by 4.17. A phone photo, with no meaningful print size at all, can easily become a page three or four feet wide.

Smaller mismatches have duller causes. A4 (8.27 × 11.69 in) and US Letter (8.5 × 11 in) differ by about a quarter inch in width and two-thirds of an inch in height, which is barely noticeable on its own but obvious when the two alternate in continuous scroll. A slide exported at a widescreen aspect ratio sits beside portrait pages as a short, wide band. A scanner set to a custom crop produces receipt-sized pages. And an application's own export can surprise you — a spreadsheet laid out for A4 but exported through a print driver set to a different scale comes out at two or three times the size.

To confirm which page is off, check the actual page dimensions rather than trusting how it looks. In Acrobat or Reader, hovering over the bottom-left corner of the page shows its size, and there's a preference to display it permanently. Document Properties shows it too. Once you see that one page is 42 inches wide and the rest are 8.5, the mystery is gone.

To fix it, the reliable approach is to correct the odd page at its source and merge again: re-export the image at a set page size, or reconvert it with a tool that honours the image's resolution. If the sources aren't available, printing the merged file to a PDF printer with a fixed paper size and a "fit" or "shrink oversized pages" option redraws every page onto the same sheet — at the cost of turning it into a new file, and in some tools flattening form fields and links. Adjusting the zoom only hides the problem on your own screen; the next person to open the file sees the same mismatch.

Worth knowing before you choose a merge tool: essentially all of them, including FreeToolDev's, copy each page at its original size, because silently rescaling someone's pages is its own kind of bug. If the pages need to match, make them match before merging.

Why merging can make the file smaller

A PDF isn't just page content — it also embeds the fonts used on those pages, and font data is often the single biggest thing in a small, text-heavy file. If three source PDFs all use the same typeface, each one embeds its own full copy of that font. A merge tool that's smart about it (Adobe Acrobat's "Combine Files" does this) recognizes the duplicate font across source documents and keeps only one copy in the output — three embedded copies become one, and the total drops accordingly. The same logic applies to any other resource repeated across files: a shared color profile, a shared image used as a letterhead on every page, and so on.

This is a genuine, lossless size reduction — nothing about how the pages look or behave changes. It just doesn't happen automatically with every merge tool. Whether you see it depends entirely on whether the specific library or app doing the merging bothers to detect and deduplicate shared resources across the files you're combining, which brings up the other direction.

Why merging can make the file bigger instead

Plenty of merge tools — including the popular open-source library pdf-lib, which FreeToolDev's own merge tool uses — don't deduplicate anything across source files by default. Each source PDF's fonts, images, and internal objects get copied into the output as-is, one set per source file. If three input PDFs each embed their own copy of the same font, the merged file ends up with three copies too, and the total size lands close to (or slightly above) the simple sum of the originals, once you add the overhead of the new document's own internal structure (a fresh cross-reference table, object streams, and so on).

Neither behavior means a tool is broken. "Smaller than the sum" means the tool deduplicated shared resources; "roughly the sum, or a bit more" means it didn't. Both are normal outcomes of the same operation — merging — done two different ways.

Merging and compressing are two different problems

It's tempting to assume a merge tool should also shrink the result, but combining pages and reducing file size are separate operations that happen to often get bundled into one workflow because people need both at the same time. Deduplicating repeated fonts across files, at best, recovers what was already redundant — it doesn't touch the biggest actual cost in most PDFs, which is embedded images. A merge tool that only deduplicates fonts will still hand back a large file if the source PDFs are full of high-resolution scans or photos; getting that down meaningfully requires re-encoding those images at a lower quality or resolution, which is a fundamentally different, lossy operation.

What real compression actually costs you

There are two honest ways to shrink a PDF, and they trade off differently:

Structural cleanup — stripping unused metadata, optimizing the internal object structure — is lossless. Nothing about the document's appearance or text changes. The catch is the ceiling: for a text-heavy document, this might recover single-digit percentages, because there wasn't much redundant structure to begin with.

Re-rendering pages as images is the only way to get dramatic size reduction on an image-heavy PDF, but it comes at a real cost: every page becomes a flattened picture. Text stops being selectable, searchable, or copyable, and small text or thin lines can look softer depending on the resolution you re-render at. This is the right tradeoff for a stack of scanned receipts or a photo-heavy brochure where a smaller file matters more than a searchable one — and the wrong one for a contract or report someone still needs to search or copy text from afterward.

FAQ

Is there a way to get real compression without losing text selectability?

Not a reliable one for image-heavy PDFs specifically — the size is coming from the images, and shrinking an image without touching it as an image isn't possible. For text-heavy PDFs, structural cleanup (stripping metadata, deduplicating fonts) gets you a modest, fully lossless reduction without this tradeoff, since there's comparatively little image data to begin with.

Does Adobe Acrobat handle this differently from free/open-source tools?

Acrobat's "Combine Files" does deduplicate shared fonts and some resources across source documents by default, which is why people are sometimes surprised to see a smaller-than-expected result from it specifically. Many free and open-source merge tools (including browser-based, no-upload ones) prioritize simplicity and correctness over this kind of cross-document optimization, so seeing a larger result from a different tool doesn't mean anything went wrong.

If I only need to merge one small set of files once, does any of this matter?

Only if the resulting file size is actually a problem for you — an email attachment limit, a slow upload to a portal, a storage quota. If the merged file's size is fine as-is, there's no need to reach for a compression step at all.

Try it

FreeToolDev's Bulk PDF Merge & Compress tool combines multiple PDFs in the order you choose, with an optional "Safe" (lossless) or "Aggressive" (image re-render) compression pass — entirely in your browser, nothing uploaded.