Understanding Page Ranges: How to Specify Exactly What You Want

Page range syntax looks simple — a few numbers and dashes — but getting it exactly right matters, since a small mistake in how a range is written extracts the wrong pages without necessarily producing an obvious error. Understanding the common conventions makes it much easier to get the intended result on the first attempt.

Common range formats

• A single page: "5" extracts just page 5.
• A continuous range: "5-10" extracts pages 5 through 10 inclusive, meaning both page 5 and page 10 are included.
• Multiple separate pages or ranges: "1,5,10-12" combines individual pages and ranges into one request, extracting page 1, page 5, and pages 10 through 12.

Most tools, including the one on this site, follow this same general comma-and-dash convention, though it's always worth checking a specific tool's exact expected format before assuming, since small variations do exist between different tools.

Inclusive vs exclusive ranges

A genuinely important detail: does "5-10" mean pages 5 through 10 (6 total pages, inclusive of both endpoints), or pages 5 through 9 (5 pages, excluding the final number, as some programming contexts define ranges)? Nearly all PDF tools built for general, non-technical use treat ranges as inclusive of both endpoints, matching how people naturally read "pages 5 through 10" in everyday language, but this is worth confirming with an unfamiliar tool rather than assuming, particularly if the tool's documentation doesn't explicitly say.

Common mistakes when writing a range

• Reversing the order of a range ("10-5" instead of "5-10"), which most tools won't interpret correctly and will either reject or silently produce an empty result.
• Adding spaces inconsistently ("5 - 10" versus "5-10"), which some stricter tools may not parse correctly even though it looks equivalent to a human reader.
• Requesting a page number beyond the document's actual page count, which typically gets silently ignored or clamped rather than causing an error, so it's worth double-checking the total page count first.

Why checking the total page count first matters

Before typing any range, confirming the source document's total page count — usually shown by the tool right after a file is loaded, as it is with the tool on this page — avoids the common mistake of requesting a range that partially or entirely falls outside the actual document, which produces a smaller or empty result without necessarily explaining why.

A quick way to double-check a range before running it

Reading a written range back in plain language — "1 through 5, plus 7, plus 10 through 12" — and comparing that against what you actually intend to extract is a fast, reliable sanity check that catches most range-writing mistakes before they run, since misread syntax is much easier to catch out loud or on a second read than in the compact comma-and-dash notation itself. When trying an unfamiliar tool for the first time, a quick test with a small, low-stakes range confirms its exact expected format before relying on it for something that actually matters.