Split PDF by page range into a new file

Provide the source PDF, the first page, and the last page using familiar one-based numbering. The result is a separate PDF containing that inclusive range in its original order. The source remains unchanged, and an invalid range is rejected clearly instead of creating a partial or misleading file.

Choose an inclusive range with predictable page numbers

This tool treats the first page shown by a normal PDF viewer as page 1. Enter a start page and an end page, and both boundaries are included in the new file. Asking for pages 4 through 7 therefore produces four pages: 4, 5, 6, and 7. That simple rule avoids the zero-based indexing surprises common in programming libraries and makes an automated request match what a person sees on screen. Before splitting, check whether the document has a printed cover or unnumbered introductory pages, because printed folio numbers can differ from viewer page positions. The capability uses physical PDF page positions, not numbers printed inside the artwork. The start must be less than or equal to the end, and both values must be positive integers. If either boundary exceeds the source document page count, the request returns an input error. It never silently clamps a range, substitutes the last page, or produces an incomplete file that could be mistaken for the requested section.

Understand what the splitter returns

A successful request creates a new PDF containing only the pages inside the selected continuous range. The original input is not edited, so it can be used again for another range or kept as the authoritative document. Alongside the new PDF, the response reports the source page count, the number of extracted pages, and the accepted start and end values. Those fields make automated checks straightforward: a workflow can confirm that pages 12 through 18 yielded seven pages before attaching the result to a case, customer record, or email. The operation is deterministic, with no network request, random choice, model inference, or current-time dependency in the splitting logic. The browser version runs the same core algorithm as the API handler. This capability is intentionally for one continuous interval. If a task needs scattered pages, reordered pages, or several output files, use a page extraction, reordering, or general splitting workflow designed for that different selection model.

Build safe document workflows around range validation

Range validation matters most when page numbers come from another system. An index may say that an invoice occupies pages 31 through 34, while a later scan has only 30 pages because an upload was truncated. Generating pages 31 through 34 as an empty or shortened result would hide the upstream problem. This splitter instead compares both boundaries with the parsed page count and fails the request when the range is outside the document. Treat that error as a signal to quarantine the file, refresh the index, or ask for a complete upload. For interactive use, verify the viewer page count and retry with valid boundaries. For API use, log the requested range and returned page count without logging the document itself, especially when PDFs contain personal or financial material. Billing is simple: each API request costs $0.002, while the browser execution is available locally. Because the result is a separate file, give it a descriptive filename that records the source identifier and range for later auditing.