PDF Forge LiB
PDF Forge LiB
TutorialJuly 2, 20264 min read

How to Split a PDF: Range, Count, Bookmark

Splitting a PDF isn't just one operation - here's the difference between range, count, and bookmark splitting, and which one actually fits your task.

Try it yourself: Split PDF tool →

"Split the PDF" can mean a few genuinely different things depending on what you're trying to produce, and picking the wrong approach usually means more manual cleanup afterward. Here's the difference between the three common ways to do it.

Split by page range

This is the most direct method: you specify exactly which pages go into each output file - pages 1-5 into one file, 6-12 into another, and so on. Use this when you already know precisely which pages belong together, such as separating a report from its appendix, or pulling out a specific chapter you already know the page numbers for.

Split by page count

Rather than specifying exact ranges, this splits a document into equal chunks of a fixed size - every 10 pages becomes its own file, for example. This is useful when the content doesn't have meaningful natural boundaries and you just need manageable pieces: breaking a 200-page scanned archive into 20-page files for easier handling, without caring exactly where each piece starts and ends content-wise.

Split by bookmark

If the source PDF already has bookmarks (common in ebooks, manuals, and reports exported from word processors with a table of contents), splitting by bookmark uses those existing markers as the cut points - each chapter or section becomes its own file automatically, without you having to look up page numbers at all. This only works if the PDF actually has bookmarks to begin with; a plain scanned document won't have any to split by.

How to choose

  • You know the exact pages you need → page range
  • You just need smaller, roughly equal pieces → page count
  • The document already has a table of contents / bookmarks matching how you want to divide it → split by bookmark
  • You're extracting just a handful of specific, possibly non-consecutive pages → see our guide on extracting specific pages instead, which is built for that exact case

After splitting

Whichever method you use, it's worth a quick check of the first and last page of each resulting file - off-by-one page-number mistakes are the most common error with range-based splitting, and it's much faster to catch a misaligned boundary immediately than after you've already distributed the files.

Common mistakes with each split method

  • Using page-count splitting on a document with meaningful chapter breaks, resulting in chapters being cut in half at arbitrary points.
  • Using range-based splitting on a very long document, which requires manually working out and typing every page boundary rather than letting the document's own structure do it automatically.
  • Assuming a scanned document has usable bookmarks when it doesn't - bookmark-based splitting only works if bookmarks were actually added at some point, either by the original creator or manually beforehand.
  • Splitting by a fixed count without checking whether the last resulting file ends up oddly short (a five-page leftover file when the split count was set to twenty, for example).

Combining split methods for complex documents

For a genuinely complex document - say, a 300-page compiled report with several distinct sections of very different lengths - it's sometimes worth combining approaches rather than picking just one: use bookmark or range-based splitting first to separate the document into its natural sections, and then apply page-count splitting within any individual section that's still too long to handle comfortably on its own. This two-step approach respects the document's real structure while still keeping every resulting file to a manageable size.

Renaming files automatically after splitting

Most split tools generate generic filenames for the resulting files (like document_1.pdf, document_2.pdf) by default. If the split files are based on a document's own chapters or sections, it's worth spending a moment renaming each one to reflect its actual content rather than leaving the generic names, especially if you'll need to find a specific piece again later without reopening every file to check.

None of these three split methods is universally "correct" - the right one depends entirely on what the resulting files need to be used for next. A quick gut check that usually points to the right method: if you know exactly which pages you need, use range; if you just need manageable chunks regardless of content, use count; if the document already has real chapter structure, use bookmarks.

Finally, whichever method you choose, do a quick spot-check on at least the first and last resulting file after splitting - these are the two most likely to have an off-by-one boundary issue, since the very start and very end of a page range are exactly where small counting mistakes tend to show up first.

Splitting a PDF that mixes portrait and landscape pages

Documents that mix page orientations - a mostly-portrait report with one landscape-oriented chart or spreadsheet page in the middle - split without any special handling, since each output file simply preserves whatever orientation its pages originally had. The one thing worth checking afterward is that a landscape page split into its own single-page file still displays correctly when opened, since some viewers default to a portrait-oriented preview window regardless of the actual page's orientation until you rotate the view manually.

Frequently asked questions

Which split method should I use if I'm not sure?

If you know exactly which pages you need, use page range. If you just need equal-sized chunks and don't care about content boundaries, use page count. If the document already has bookmarks matching how you want it divided, bookmark splitting saves you from figuring out page numbers at all.

Can I split a PDF into more than two files at once?

Yes - splitting isn't limited to a single cut point; you can define multiple ranges or a repeating page count to produce several output files from one split operation.

Does splitting reduce file size?

Each resulting file is naturally smaller since it contains fewer pages, but splitting itself doesn't compress anything - if the pages contain large images, each split file still carries the same per-page weight as the original.

Related guides