Split a PDF Into Separate Files

How the tool decides where one file ends and the next begins

Splitting works on physical page positions, counted from the first sheet in the file. Position one is whatever appears when the document opens, whether that is a cover, a contents page or the first page of the text. The numbers printed inside the document are ink on a page and carry no meaning to the tool.

A range names a start and an end, and both are included — 11-60 produces a fifty-page file, not forty-nine. That off-by-one is the second most common way a split lands short, and it compounds: four consecutive ranges each entered one page narrow leaves four pages unaccounted for across the set.

Anything you do not name is simply absent from the output. That is the behaviour to watch, because it fails silently. Splitting a 96-page document into 1-30 and 41-96 produces two perfectly valid PDFs and no warning whatsoever that pages 31 to 40 have gone nowhere. Add your range lengths up and compare the total to the page count before you download.

What each output inherits, and what gets left behind

Every part is written as a complete, independent PDF. It receives its own catalogue, its own page tree, and copies of the fonts and images its pages actually use, so it opens anywhere without reference to the original or to its siblings.

Document-level properties are copied wholesale to each part, which is worth knowing because it means the title metadata of the source now describes several files. If those parts are going to different recipients, that metadata travels with them.

Anything that pointed across a boundary cannot survive the cut. A bookmark to a chapter that ended up in a different file has nothing left to point at. An internal cross-reference — a table of contents entry, a "see page 74" link — is a reference to a page object that is no longer in the same document. Interactive form fields keep working within a part but any calculation that read a value from a page in another part will not.

A signed document loses its signature, for the same reason merging does: the byte range it covered no longer exists.

A worked example: a scanned tender document

A 96-page tender, scanned rather than exported, arriving at around 60 MB — under the 100 MB ceiling, so it uploads in one piece. It divides into four sections that four different people need: instructions to bidders, the specification, the pricing schedule, and the terms.

Find the boundaries in a reader by scrolling to each section start and reading the position from the page counter, not from the printed folio. Enter the four ranges, split, and the result downloads as a single ZIP archive containing four PDFs. Extract it and each opens normally.

Expect the four parts to add up to slightly more than 60 MB. Nothing has been re-encoded, and a typeface or a logo that appeared throughout the tender now has to be embedded in each part that uses it. Page counts, on the other hand, add up exactly — four sections of 12, 41, 8 and 35 pages come to 96, and if yours do not, a range is wrong.

Each part is as sharp as the source, because splitting copies rather than re-renders.

When keeping the document whole is the better decision

Splitting is easy and reversing it is tedious, so it is worth asking whether the division needs to exist as files at all. A document sent whole to someone who only needs part of it costs them a scroll. A document split into six parts costs everyone the job of keeping six files together for the rest of its life, and the first time one is emailed on without the others, the context is gone.

Version control is the sharper version of the same problem. Once one part is revised, there is no longer a single authoritative document — there is a set, and somebody has to know which member of it is current.

If the parts do need to come back together later, Merge PDF will rebuild the sequence, and Organize PDF will let you interleave revised pages back into their proper places rather than only appending them.

Split when the parts are genuinely going to separate destinations. Keep it whole when they are going to the same one.