PDFMay 1, 2026· 8 min read

Splitting Large PDFs: Page Count vs File Size — What Works Better?

You've got a 200-page PDF that's too big to email. Should you split it into 4 chunks of 50 pages each, or aim for 10MB files regardless of page count? Here's why the answer isn't obvious.

Let's start with the annoying reality: not all PDF pages are created equal. A 200-page document could be 5MB (if it's mostly text) or 500MB (if it's scanned architectural drawings). So when someone says "split my PDF into smaller files," the method you choose actually matters.

Most people assume you split by page count because that's the most obvious option. But here's the thing — if your goal is to email those files or upload them to a platform with size limits, splitting by pages is like cutting a cake blindfolded. You might end up with wildly different file sizes.

When Page Count Makes Sense

There are absolutely situations where splitting by page count is the right move. If you're working with a consistent document — say, a novel manuscript where every page is roughly the same (text, standard formatting, minimal images) — then page count works beautifully.

For example:

  • Splitting a 300-page report into three 100-page sections for easier reading
  • Breaking a book manuscript into chapters for reviewers
  • Dividing meeting minutes by month (where each month is roughly the same length)
  • Splitting standardized forms or templates into batches

The advantage here is predictability. If you know pages 1-100 are Chapter 1, pages 101-200 are Chapter 2, and so on, splitting by page count creates clean, logical files. No one gets confused about which file contains what.

But this only works when page content is consistent. The moment you introduce high-resolution images, scanned pages, or embedded graphics, all bets are off.

When File Size Wins (Spoiler: Most of the Time)

If your goal is to actually get the file delivered — via email, upload portal, or mobile data — you need to split by file size. Period.

Here's why. Email providers have wildly different attachment limits:

  • Gmail: 25MB per email (including all attachments)
  • Outlook: 20MB for most accounts
  • Yahoo: 25MB
  • Corporate email servers: often 10MB or less

If you split a 100MB PDF into 10 files by page count, you might end up with files that are 5MB, 15MB, 22MB, and 8MB depending on what's on those pages. Three of those files won't send via email. You'll have to split again, manually, which defeats the entire purpose.

Splitting by size means you say "give me files under 10MB each" and the tool figures out where to cut. Maybe File 1 is pages 1-47, File 2 is pages 48-95, and File 3 is pages 96-120. Who cares? They'll all send, and that's what matters.

The Scanned Document Problem

This is where people get burned.

You scan a 200-page physical document at 300 DPI (which is standard for good quality). Each page becomes a high-resolution image inside the PDF. Suddenly, your "200-page document" is 180MB because you're storing 200 full-color images, not text.

If you split this by page count (say, 50 pages per file), each file is still 45MB. Still can't email it. Still too big for most upload forms. You've accomplished nothing.

But if you split by file size — say, 15MB per file — you'll get 12 files with varying page counts. File 1 might be pages 1-8, File 2 might be pages 9-17, depending on how image-heavy each page is. And all 12 files will actually send via email.

Before you even think about splitting, though, consider compressing your PDF first. A 180MB scanned document can often compress down to 30-40MB without noticeable quality loss. Then you might only need to split it into 2-3 files instead of 12.

Mobile Users Care About Size, Not Pages

If you're sending PDFs to people who'll read them on phones (which is increasingly common), file size is king. Mobile data isn't unlimited for everyone. A 60MB PDF over a cellular connection is annoying. A 300MB PDF is a dealbreaker.

Splitting by size means you can optimize for mobile: "keep each file under 10MB so people can download on 4G without destroying their data plan." That's user-friendly design.

The Hybrid Approach (If You Want to Be Fancy)

Look, sometimes you want the best of both worlds. You want files that are logically organized and sized for distribution.

Here's how you do it:

  1. Identify natural breakpoints in your document (chapters, sections, topics)
  2. Split at those breakpoints first
  3. Check the file size of each resulting file
  4. If any file is still too large, split that section again by size

So if you have a 500-page report with 5 chapters, you split it into 5 files by chapter. Then you check: Chapter 1 is 8MB (fine), Chapter 2 is 35MB (too big), Chapter 3 is 12MB (fine). You split Chapter 2 into 3 files by size, and now you have 7 total files that are both logically organized and small enough to send.

This takes more work, but for professional documents where both usability and deliverability matter, it's worth it.

What About Merging PDFs Later?

One underrated benefit of splitting by consistent file size: it's easier to merge PDFs back together later. If someone receives 5 files that are each 15MB, they can quickly combine them into the original 75MB document if needed.

But if you send 12 files with random sizes (because you split by page count), the recipient has no idea if they have all the pieces or if something got lost in transit. Consistent file sizes act as a sanity check.

Real-World Example: Legal Discovery Documents

Legal teams deal with this constantly. Discovery documents can be thousands of pages with mixed content: typed depositions, scanned evidence photos, email threads, handwritten notes. File sizes are all over the place.

Courts often have strict filing limits (e.g., "no single file over 25MB"). Law firms can't just split by page count and hope for the best. They split by size, then create an index document that maps which pages are in which file. Problem solved.

Tools That Handle This Well

Most modern PDF tools let you choose your splitting strategy. Some even let you preview the resulting file sizes before you commit. If you're splitting frequently, look for tools that remember your preferences (e.g., "always split to 10MB files").

And honestly, browser-based tools have gotten good enough that you don't need to install anything. Upload your PDF, choose "split by size," set your target size, and download the results. Done.

The Verdict

For most people, most of the time, splitting by file size is the safer bet. It guarantees your files will actually send, upload, or download where they need to go. You're optimizing for the constraint that matters (delivery), not the constraint that's easy to think about (page count).

But if you're working with predictable content and don't have size restrictions, splitting by page count is simpler and easier to navigate. And if you're being thorough, the hybrid approach gives you logical organization plus guaranteed deliverability.

Just don't blindly split a 300-page scanned document into 6 chunks of 50 pages and wonder why none of them fit in an email. Now you know better.

Frequently Asked Questions

What is the best way to split a 500-page PDF for email?
For email, always split by file size (staying under 10-15MB per file) rather than page count. A 500-page PDF with mostly text might fit in 2-3 files, but one with high-res images could need 10+ files. Check your recipient's email provider limits first.
Can I split a PDF by file size instead of page count?
Yes, many PDF tools allow splitting by target file size. This is especially useful for ensuring files stay under email attachment limits or mobile data constraints, regardless of page count variation.
Why is my 100-page PDF 80MB?
PDFs with high-resolution scans, embedded images, or unoptimized graphics can balloon in size. A 100-page PDF of scanned documents at 300 DPI can easily reach 80-100MB. Consider compressing the PDF before splitting.
Should I split PDFs by chapter or by size?
For books or reports, splitting by logical chapters improves usability, even if files vary in size. For technical distribution (email, uploads), split by consistent file size. Ideally, combine both: split at chapter breaks while staying under size limits.