✂️ Split PDF by Page Range
Extract a range of pages (e.g. 5–12) from any PDF into a new file. Runs entirely in your browser — nothing is uploaded.
How to Split a PDF by Page Range — Extract Exactly the Pages You Need
You have a 200-page report, a scanned textbook, or a multi-chapter manual — and you need just pages 47 through 62. Emailing the full PDF is wasteful. Printing all 200 pages to then scan 16 of them is painful. What you actually need is a clean, standalone PDF containing only those exact pages.
This guide walks you through how page range splitting works, why doing it entirely in your browser matters for privacy, and what to watch out for when working with complex PDFs.
What Happens When You Split a PDF by Page Range?
A PDF file is not a linear document like a Word file. It is a collection of numbered objects — page dictionaries, content streams, image data, fonts, and annotations — all stitched together through a cross-reference table that acts like an index. Every page is its own object, pointing to its own content stream and its own resource dictionary (which lists fonts, images, and color spaces).
When you extract a page range, you are not simply "cutting out" a block of bytes. A proper extraction must:
- Walk the page tree to find the exact objects representing pages 5 through 12 (or whatever range you chose)
- Identify every resource those pages depend on — content streams, embedded fonts, image XObjects, color profiles
- Rebuild a new, self-contained PDF with only those objects, renumbered cleanly from scratch
- Update the cross-reference table with correct byte offsets for every new object
- Write a valid trailer that points to the new catalog and pages tree
The tool above does all of this locally in your browser using a pure JavaScript PDF engine — no server, no upload, no waiting.
Step-by-Step: Using the Split PDF Tool
Step 1 — Load your PDF. Click the upload area or drag your PDF file directly onto it. The file is read into memory using the browser's FileReader API. At this point, nothing leaves your device.
Step 2 — Confirm the page count. As soon as the file loads, the tool scans the PDF's internal page tree and tells you exactly how many pages it found. This number matters — if you type page 95 as your end point but the PDF only has 80 pages, the tool will clamp the range and warn you.
Step 3 — Enter your start and end pages. Use 1-based page numbers, the same way you would count pages in a printed book. Page 1 is the first page. If you want the third through seventh pages, enter 3 and 7.
Step 4 — Click Extract Pages. The tool parses the full object structure, collects the chosen pages and their dependencies, renumbers everything, rebuilds the cross-reference table, and produces a new binary-valid PDF entirely in memory.
Step 5 — Download the result. A download link appears immediately. The output filename automatically includes the page range (for example, report_pages_5-12.pdf) so you always know what is in the file.
Why Browser-Based Matters for Privacy
Many PDF tools on the web silently upload your file to a server in a distant data center. This is a real problem when your PDF contains contracts, medical records, financial statements, confidential slides, or identification documents. You have no control over what happens to that data after it reaches the server — whether it is stored, indexed, or shared.
This tool processes everything inside your own browser tab. The PDF never touches any network. Your operating system's firewall would block any such attempt, and you can verify this yourself by opening your browser's developer tools and watching the Network tab — you will see zero outbound requests during processing.
When Page Splitting Is Most Useful
There are a handful of scenarios where splitting by page range becomes genuinely necessary rather than just convenient.
Sharing a specific chapter. Academic papers, legal filings, and technical manuals are often delivered as one enormous PDF. Extracting chapter 4 (pages 88–121) and sending only that saves your recipient from opening the full document just to read one section.
Reducing file size before email. Many email providers cap attachments at 10–25 MB. If you only need a subset of the document, extracting those pages can bring a 40 MB PDF down to 3 MB without any quality loss.
Printing specific sections. Sending a 300-page PDF to a printer is slow and expensive. Splitting out the 8 pages that actually need printing makes the process faster and cheaper.
Archiving subsections separately. Large corporate documents are often archived as unified PDFs, but teams sometimes need individual sections stored separately for faster retrieval and access control.
Understanding the "Total Pages Detected" Number
After you load a PDF, the tool shows a "Total pages detected" count. This number comes from walking the PDF's internal page tree — the /Pages node hierarchy that every PDF contains. Unlike counting visual page breaks, this reads the actual structure the PDF author intended.
Occasionally, a PDF created by an unusual tool might count slightly differently from what your PDF viewer shows on-screen. This can happen with form PDFs that have hidden template pages, or with some scanned PDFs where blank separators were embedded without full page metadata. In practice, the count matches almost universally for standard-generated PDFs.
Limitations to Know About
This browser-based tool handles the vast majority of real-world PDFs correctly, but there are some cases where results may differ from professional desktop software:
Encrypted or password-protected PDFs. If a PDF has owner restrictions or is locked with a password, the tool cannot parse its object structure. You would need to remove the protection first using a tool you trust.
Linearized (web-optimized) PDFs. Some PDFs are structured specifically for fast web streaming, with object ordering that differs from the standard. The tool handles these in most cases, but edge cases exist.
Cross-reference streams (PDF 1.5+). Newer PDFs sometimes use compressed cross-reference streams instead of plain text xref tables. The tool reads the traditional xref format; PDFs using newer compressed xref formats fall back to a linear object scan that works for most files.
For everyday use — splitting presentation decks, extracting report sections, pulling specific pages from scanned books — this tool handles the job completely and correctly without any data leaving your browser.