About Split PDF
Split PDF makes several PDFs from one source, either from comma-separated page ranges or in equal-sized chunks. A preview groups the thumbnails into the parts that will be saved. The range parser accepts page numbers such as 1-3,5,7-9; it does not accept words such as ‘end’. Each part is downloaded as its own PDF, with no ZIP bundle.
Split PDF specs
| Price | Free ($0) — no paid tier |
|---|---|
| Account | Not required |
| Watermark | None |
| Where it runs | In your browser, on your device |
| File upload | No file is uploaded |
| Input | PDF (1 file) |
| Output | PDF (one file per range) |
| File size limit | Limited only by your device's memory |
| Offline use | May work after all required code and assets have loaded; browser caching is not guaranteed |
How to use Split PDF
Load one PDF
Drop the document and wait for its page thumbnails and page count.
Choose a mode
Use By ranges for entries such as 1-3,5,7-9, or Every N pages for fixed-size chunks.
Review the parts
The preview shows one group per output PDF and reports invalid or out-of-bounds page numbers before export.
Split and download
Press Split & download. The browser saves each part separately in sequence.
Frequently asked questions about Split PDF
What range syntax works?
Use positive, 1-based page numbers, optionally joined by a hyphen, and separate outputs with commas: 1-4,6,9-12. Spaces are allowed. The literal word ‘end’, open-ended ranges and reversed ranges are rejected.
Can I make one PDF per page?
Yes. Choose Every N pages and set Pages per part to 1. There is no separate Every page mode.
Are bookmarks and forms preserved?
Each output is a new document made from copied pages. Page appearance is retained, but document-level outlines and form structures are not rebuilt for the smaller files. Flatten completed forms first when their displayed values are important.
Why in-browser processing matters
Every PDFChamp tool runs inside this page: the file you choose is read by JavaScript in your own browser and is never sent to a server, so nothing is uploaded, queued, or stored anywhere. That removes the upload wait, the processing queue, and the question of what happens to your file afterwards — the PDFChamp overview compares this architecture with server-side PDF tools.
Last updated