Splitting a Scanned Book or Long Report Into One File Per Chapter

A 200-page scanned textbook, or a long report bound into a single PDF, is awkward to work with as one file: hard to navigate on a course site, slow to scroll through to find one section, unwieldy to link a specific chapter directly. Splitting it into one file per chapter fixes all three, and if the chapters are roughly the same length, Split PDF's every-N-pages mode does it in one pass.

Working out the math first

Every-N-pages divides the document into consecutive chunks of N pages each: a 200-page document split at N=20 produces 10 files, 20 pages apiece. If the total doesn't divide evenly, a 205-page document at N=20 still produces 11 files, with the last one holding only 5 pages, nothing is dropped or padded, the remainder just becomes a shorter final file. Working this out before you start, a quick glance at the thumbnail grid's page count, lets you pick a chunk size that produces a sensible number of files rather than guessing and re-running it once you see the result.

Doing it

Drop the document, up to 80MB, and let the thumbnail grid finish rendering, on a 200-page file a progress line shows while it works since that genuinely takes a moment. Switch to Every N pages, set N to your chapter length, and click Split. With more than one output, which every-N-pages almost always produces, the result downloads as a zip, each file named by the page range it holds, so "pages 1-20", "pages 21-40" and so on sort and identify themselves without any manual renaming afterward.

When every-N-pages is the wrong mode

This mode assumes equal-length chunks. If the real chapters are genuinely different lengths, chapter one is 15 pages and chapter two is 40, every-N-pages will cut straight through a chapter boundary rather than respecting it, landing part of one chapter at the end of one file and the rest at the start of the next. Custom ranges is the right tool for that case instead: look up where each chapter actually starts and ends in the thumbnail grid, then type the exact ranges (1-15, 16-55, 56-80) so each output matches a real chapter rather than an arbitrary page count. It takes a minute longer to look up the boundaries, but the result respects the document's actual structure instead of an assumption about it.

Naming the results after they download

Each output file in the zip is named by the page range it covers, "pages-1-20.pdf" and so on, which is accurate but not especially meaningful once you're looking at a folder of ten similarly-named files. A quick rename pass after extracting the zip, "chapter-1.pdf" instead of "pages-1-20.pdf", makes the set easier to navigate later, especially once it's been sitting in a folder for a few weeks and the original page-range logic isn't front of mind anymore.

A size note worth planning for on a long document

Splitting a resource-heavy scanned PDF, one with the same embedded font or a repeated header image on every page, into many small files means each output carries its own copy of those shared resources rather than sharing one copy the way the original document did. On a 200-page document split into 10 files this is usually a modest, tolerable increase; the tool shows a plain notice whenever a split will produce four or more files, since that is when the total can grow past the original, so it's visible rather than a silent surprise after the download finishes.

A real ceiling worth knowing up front

The 80MB limit applies to the source document being split, not the combined output. A 200-page scan that's mostly text usually sits well under that, but a 200-page document scanned at high resolution with a lot of photographed illustrations can genuinely approach or exceed it. If a scan is that heavy, checking the file size before starting saves the trouble of waiting through thumbnail rendering only to hit the limit at the end.

Checking the result before relying on it

After the zip downloads, open a file or two before deleting the original, especially the first and last chapter files, where a boundary miscalculation would show up most obviously. Confirming the split landed where expected takes a few seconds and is worth doing once before treating the original as safe to discard.

If the source started as photographed pages, not a PDF

If what you're actually working from is a stack of photographed book pages rather than an existing PDF, build the PDF first with JPG to PDF, then split it into chapters here. That guide covers ordering and page setup for the photo-to-PDF step.

Putting it back together later

If chapter files ever need to be recombined, into a different order, or merged with a different edition's cover page, that's the reverse job: merge PDF takes several separate files and produces one ordered document again, the opposite job to this one.

Try it on a real long document, work out the chapter length once, and let every-N-pages do the rest.