Choosing between page ranges, fixed intervals, and single pages
Different document workflows call for different cut points: invoices need fixed intervals, packets need custom ranges, and scanned stacks need one file per sheet. Selecting the right How to split mode saves manual cleanup after export.
| Split mode | Input setting | Example on a 10-page PDF |
Output files created | Best suited for |
|---|---|---|---|---|
| By page ranges | Comma-separated spans | 1-3, 4-8, 9-10 |
3 custom PDFs |
Pulling exhibits, covers, or appendices |
| Every few pages | Pages in each part (>= 1) |
2 pages per part |
5 equal PDFs |
Fixed-length forms or duplex packets |
| One file per page | None needed | 1 page per part |
10 single-page PDFs |
Separating individual receipts or certificates |
| Bookmark alternative | Outline depth level | Chapter 1, Chapter 2 | 1 PDF per chapter |
Manuals and ebooks with sidebar outlines |
| Size-cap alternative | Max megabytes (>= 50 KB) |
Under 10 MB |
Variable page counts | Email attachments and portal upload caps |
Under the ISO 32000-1 PDF 1.7 Specification, copying page objects via copyPages() preserves vector fonts, embedded images, and internal page geometry losslessly. If your document already includes a sidebar outline tree, you can divide chapters using outline bookmarks instead of typing page numbers by hand.
How does page-range syntax work when dividing a PDF?
Comma-separated ranges tell the splitter exactly which pages belong in each output PDF, with hyphens defining continuous spans and standalone numbers creating single-page files. When you first load a multi-page PDF, the Page ranges field pre-fills a midpoint split so you can adjust or replace the pattern right away.
Comma-separated ranges vs. single-page picks
Each comma-separated token generates 1 independent PDF file in the output bundle. Entering 1-3, 4-8, 9 creates 3 separate PDFs, whereas entering 1-5 alone produces a single 5-page PDF.
Tip: If you want to pull several non-adjacent pages (such as pages 2, 5, and 9) into one combined document rather than three separate files, use a single-file page extractor instead.
How output PDFs are named automatically
Every generated file inherits the original document stem followed by its exact 1-based page span. A single-page output from report.pdf is named report-page-9.pdf, while a multi-page range is named report-pages-1-3.pdf.
This predictable naming makes it easy to sort extracted sections alphabetically in Finder or File Explorer without opening each file to check what is inside.
When you switch to Every few pages, the Pages in each part field divides the document into consecutive equal chunks down to any remainder on the last file. Choosing One file per page skips manual range entry altogether and outputs every single sheet as its own standalone PDF.
Why do multi-part splits download inside a ZIP archive?
Multi-part splits bundle into a ZIP archive because browsers block or prompt repeatedly when a web page attempts to trigger 10 or 50 separate file downloads at once. Packaging multiple PDFs into one archive guarantees every file arrives cleanly in a single click.
Single PDF download vs. bundled ZIP output
When the planner evaluates to exactly 1 group, the result panel offers a direct .pdf download. Whenever 2 or more PDFs are created, they are packed into a standard container defined by the PKWARE ZIP File Format Specification.
On macOS, double-clicking the ZIP expands all PDFs into a folder; on Windows, select Extract All before opening individual parts.
Using a single ZIP container also guarantees that every split file arrives together without partial downloads or browser pop-up blockers interrupting a 20-part batch. Each PDF inside the archive remains a valid standalone file with its own page tree and cross-reference table.
When to split by megabyte limits instead of page counts
Fixed page intervals work well when every page has similar weight, but scanned PDFs often vary wildly between text pages and full-color photos. If a portal rejects files over 10 MB or 25 MB, you can keep attachments under email size limits by letting the splitter pack as many pages as fit under your byte ceiling.
Local memory processing and recombining split files
Legal exhibits, payroll statements, and medical charts often need to be broken apart before sharing only relevant pages with an outside recipient. Keeping the split step inside your browser avoids uploading the full, unredacted source file just to extract a few pages.
Keeping confidential documents inside your browser
As documented in the MDN File API Documentation, the browser reads your selected PDF into local memory without transmitting bytes over the network. A background Web Worker constructs each new PDF locally, keeping network usage at 0 bytes throughout the entire operation.
Because processing happens on your own CPU rather than a queued remote server, even 500-page binders split quickly without hourly task caps, watermarks, or account registration walls.
Reassembling or rotating extracted sections
Splitting is frequently paired with orientation fixes or re-assembly when preparing final packets for clients or courts. From the result screen, you can send extracted parts straight to Rotate PDF to turn sideways scans upright or recombine selected chapters with Merge PDF in any new order.
Running these steps in sequence inside your browser avoids saving intermediate copies to cloud drives or email drafts before your final packet is ready. Every split file retains its original bookmarks, page dimensions, and vector text selectability without extra conversion passes or re-encoding delays.