Split PDF Strategies: Page Count vs File Size Optimization

Splitting PDFs seems simple until you realize there are two completely different approaches—and picking the wrong one can make your life harder. I've seen people split a 300-page manual into 10 equal parts only to find the file with all the diagrams is still too big for email. Others split by size and end up with a chapter that starts on page 47 of Part 2 and finishes on page 12 of Part 3.

So which method should you use? Let me walk you through both strategies and when each one actually makes sense.

The Two Splitting Philosophies

Page count splitting is straightforward: you divide a 200-page PDF into four 50-page files. Page 1-50, 51-100, 101-150, 151-200. Done. This approach treats every page as equal—which is great for predictability but ignores the fact that page 47 (a full-color infographic) might be 10x larger than page 48 (plain text).

File size splitting is smarter about reality. You set a target—say, 15MB per file—and the tool figures out how many pages fit before hitting that limit. Sometimes that's 80 pages, sometimes it's 20. It depends on what's actually on those pages.

Here's the thing: neither method is universally better. They solve different problems.

When to Split by File Size

Use file size splitting when you're dealing with hard limits that don't care about your document structure:

• Email attachments: Gmail caps at 25MB. Outlook at 20MB (or sometimes 10MB for older Exchange servers). If your PDF is 60MB, splitting into three 20MB files guarantees each one sends.
• Cloud storage quotas: If you're trying to stay under a certain storage tier or share files with size-restricted links, file size matters more than page count.
• Upload limits on web forms: Many document portals have strict file size caps (often 10-50MB). Page count is irrelevant here.
• Mobile device optimization: Opening a 100MB PDF on a phone can crash the app. Splitting into 15-20MB chunks makes files actually usable on mobile.

The downside? You might split mid-chapter, mid-section, or even mid-sentence if there's a page break. A 200-page technical manual split by 20MB might produce files with 43 pages, 67 pages, 28 pages, and 62 pages. It works, but it's ugly for readers.

When to Split by Page Count

Page count splitting shines when structure matters and file size is flexible:

• Logical document sections: Splitting a 300-page book into three 100-page files keeps chapters intact and readers sane.
• Consistent reading experiences: If you're sharing a report series, having each part be roughly the same length feels more professional than "Part 1: 20 pages, Part 2: 87 pages."
• Print preparation: Splitting for physical printing often requires exact page counts (e.g., signatures of 16 or 32 pages).
• Archival purposes: When organizing documents in a library or archive, consistent page ranges make cataloging easier.

The risk here is that you might still exceed file size limits. A 200-page PDF split into four 50-page chunks could produce files of 8MB, 12MB, 35MB, and 9MB if pages 101-150 are full of high-res images. You'll need to check file sizes afterward and re-split the heavy sections.

The Hybrid Approach (What I Actually Do)

In practice, I usually combine both methods:

1. Start by identifying natural break points in the document—chapter endings, section dividers, major topic shifts. Open the PDF in a reader, check the bookmarks (if they exist), and note where logical splits would occur.

2. Check the file size of each potential section. If Chapter 3 (pages 45-89) is 32MB and your email limit is 25MB, you know you need to split it further—even if it breaks the chapter.

3. Use a tool like KokoConvert's split PDF to preview pages before splitting. This lets you eyeball where images and heavy content are, so you can make informed decisions about where to cut.

4. Name files descriptively. Instead of "document-part1.pdf," use "annual-report-2026-executive-summary.pdf" and "annual-report-2026-financials.pdf." This way, when someone opens the file weeks later, they know what they're looking at.

Common Scenarios and Best Practices

Scenario 1: Sending a large proposal via email

Your 150-page proposal is 45MB. Gmail won't take it.

Solution: Split by file size (20MB max) but try to align splits with major sections. If the proposal has an intro, technical specs, and pricing, aim for those as natural boundaries. You'll probably end up with 3 files: 20MB intro/specs, 19MB more specs, and 6MB pricing. Better than random page breaks.

Scenario 2: Archiving a scanned book

You've scanned a 400-page textbook. Each page is roughly the same size (all scans at 300dpi).

Solution: Split by page count at chapter boundaries. Since scanned pages are uniform in size, you don't need to worry about file size variance. Four 100-page files or eight 50-page files both work—just pick boundaries that match the table of contents.

Scenario 3: Uploading to a document portal with a 10MB limit

Your engineering drawings are 280 pages and 95MB total. The portal won't accept files over 10MB.

Solution: File size splitting with 9MB targets (leaving headroom). You'll get 10-11 files. It's annoying for users, but there's no alternative. Name them clearly ("drawings-sheet-001-029.pdf") so people can navigate.

Why Some Pages Are Huge and Others Aren't

If you've ever split a PDF by page count and been shocked that the files aren't the same size, here's why:

• Images: A single high-res photo can be 2-5MB. Text-only pages are usually 50-200KB.
• Embedded fonts: If a document uses custom fonts, those get embedded in the PDF. The first occurrence of a font adds ~500KB-2MB; subsequent pages reuse it.
• Vector graphics: Complex diagrams with lots of paths can balloon file sizes, especially if they're not optimized.
• Compression settings: Some PDFs are heavily compressed (images at 150dpi), others are bloated (images at 600dpi with no compression).

This is why splitting a 200-page PDF into four 50-page chunks can give you files of wildly different sizes. The section with all the photos is going to be massive compared to the appendix full of tables.

Tools That Actually Help

Most PDF tools let you split by page count (every X pages, or page ranges like 1-50, 51-100). Fewer tools let you split by file size, and even fewer give you a preview so you can see what you're doing before committing.

KokoConvert's split tool handles both methods. You can set a page range manually, or let it auto-split by target file size. The preview shows you exactly where the splits will happen, so you're not guessing.

If you need to merge files later (maybe you split too aggressively), you can use merge PDF to recombine them. And if your files are still too big after splitting, compress PDF can reduce sizes without re-splitting.

Final Thoughts

Splitting PDFs isn't rocket science, but doing it well requires thinking about both the technical constraints (file size limits) and the user experience (logical section breaks). Start with your constraints—email limits, upload caps, storage quotas—and then figure out how to respect document structure within those boundaries.

And look, if you're just trying to email a file and don't care about elegance, split by file size and call it a day. But if you're preparing documents for clients, archiving important records, or sharing professional reports, taking the extra five minutes to split intelligently makes a real difference.

You don't need to overthink it. Just know which approach solves your problem, preview before you split, and name your files so you remember what's in them. That's honestly 90% of the battle.