It's a reasonable question that comes up often: will merging several PDFs into one produce a file roughly the size of all of them added together, or something different? The honest answer is "usually close to the sum, with some nuance," and understanding that nuance helps decide whether a compression step is actually needed afterward.
Why merged size is close to, but not always exactly, the sum
Merging copies each source file's page content into a new document, so the resulting file size is typically very close to adding up each source file's individual size. It's not always an exact match, since PDF files can share certain internal resources (like an embedded font used across multiple source files) more efficiently once combined, occasionally producing a merged file slightly smaller than the simple sum — though this effect is usually modest, not dramatic.
When a large merged file becomes a problem
The most common practical issue is hitting an email attachment size limit, or a specific upload limit on a website or application portal, after combining several already-sizable files. A handful of scanned documents, each a few megabytes, can add up past a 20–25MB email limit surprisingly quickly once merged into one file, even though no individual source file seemed large on its own.
Deciding whether to compress the merged result
If the merged file comfortably fits its intended use — under an email limit, within an upload portal's allowance — there's no need to compress it further, since compression always involves some trade-off, however small, and isn't worth applying without a genuine reason. If the merged file is too large for where it needs to go, compressing it afterward, covered in more detail in the compression guides on this site, is the appropriate next step rather than trying to avoid the size problem by merging fewer files at once.
Compressing before or after merging: which is better
Compressing each source file individually before merging, versus compressing the already-merged result, generally produces a similar final outcome, since compression operates on the same underlying image and text data either way. Compressing after merging is usually more convenient in practice, since it's one step applied once to the finished file, rather than several separate compression steps applied to each source file beforehand.
A rough way to estimate final size before merging
Adding up the file sizes shown in your file browser for each source PDF gives a reasonably accurate preview of the merged file's likely size before you even run the merge, which is useful for checking against a known limit (like an email attachment cap) in advance rather than discovering a problem only after the merge is already complete. This estimate is rarely off by more than a small percentage, making it a quick, practical gut-check worth doing for any merge involving several already-sizable files, particularly scanned documents, which tend to run larger than text-based exports for the same number of pages.
Try the Merge Pdfs tool yourself — free, instant, nothing uploaded.
Open the toolFrequently asked questions
Will a merged PDF always be exactly the sum of its source file sizes?
Very close, though not always exact — shared internal resources like embedded fonts can make a merged file marginally smaller than the simple sum of its parts, though the effect is usually modest.
Should I compress files before or after merging them?
Either order generally produces a similar result, but compressing once after merging is usually more convenient than compressing each source file separately beforehand.
What's a common email attachment size limit to watch for?
Most major email providers cap total message size somewhere around 20–25MB, though the exact limit varies by provider, and some corporate or institutional systems apply stricter limits than that.
Does merging PDFs from cloud storage work the same way as local files?
Yes, functionally the same, though you'll typically need to download each file locally first (or the tool needs to fetch them) before the actual merge can run, since the underlying page-copying process works on the file data directly. Cloud-based tools sometimes handle this fetching step automatically in the background, while purely local, browser-based tools generally need the files already downloaded to your device first. This small check takes only a moment but avoids an unpleasant surprise later.
