Split a PDF Into Separate Files
Break one PDF into several, either a file per page, fixed-size groups, or ranges you define. Before anything is written the tool lists exactly which output files it will create and warns you about any pages that would be left out entirely. Output filenames are zero-padded so they sort correctly, and everything runs in one pass on the server.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeWhat it does
- Split every page, by group size, or by custom ranges
- Preview of the exact output files before splitting
- Warns about pages no output file covers
- Zero-padded filenames that sort correctly
- Download individually or as one ZIP
How to use Split PDF
- 1
Open your PDF
Drop the file in. Its page count is read straight away, so you know what you are working with before choosing a mode.
- 2
Choose how to split
Every page separately, fixed-size groups of N pages, or specific ranges where each comma-separated range becomes one file.
- 3
Check the preview
The panel lists the files that will be created. If any pages are not covered by a range, it says so before you commit.
- 4
Split and download
Save the files individually, or take the whole set as a single ZIP archive.
How it works
For each output file a new empty PDF is created, the chosen pages are copied into it from the source, and it is saved. Copying carries each page's full object graph — content streams, fonts, embedded images, annotations — and renumbers the internal references so they resolve inside the new document.
That is why nothing is re-rendered and nothing loses quality. It is also why an extracted page can be large: a font shared across the whole original has to be duplicated into every output file that uses it.
The three modes differ only in how pages are grouped.
Every page separately produces one file per page, named with a zero-padded index. The padding width is derived from the total page count, so a 9-page document gets single digits and a 250-page document gets three.
Fixed-size groups walks the document in blocks of N. The last group is whatever is left over, which is usually smaller — a 10-page document in groups of 3 gives 3, 3, 3, 1 rather than an error.
Specific ranges treats each comma-separated range as one output file. This is the only mode that can leave pages out, which is why it is also the only one that checks and warns.
When you'd use each mode
Every page separately suits scanned batches — a stack of receipts, invoices, or forms fed through a scanner in one pass and needing to become individual documents.
Fixed-size groups suits anything with a regular structure: double-sided forms where every two pages are one record, or splitting a long document into manageable chunks for an upload limit.
Specific ranges suits documents with meaningful sections — chapters, appendices, the parts of a contract that go to different people. It is the mode where you know what you want and the page numbers to prove it.
A note on what the preview is for
The panel listing output files before you press Split is not decoration. Two mistakes are common enough to be worth designing against.
The first is a typo in a range that silently drops a chunk of the document. If you type "1-12, 25-30" when you meant "1-12, 13-30", nothing is technically wrong, and the omission warning is the only thing that will tell you.
The second is a group size that covers the whole document, producing one output file identical to the input. That is reported explicitly rather than leaving you to wonder why splitting appeared to do nothing.
Both take a second to notice in the preview and considerably longer to notice after the fact.
Examples
Separating a scanned batch of invoices
The page numbers are zero-padded to two digits because the document has twelve pages. Without that padding a file manager sorts page-1, page-10, page-11, page-12, page-2 — which looks like a cosmetic annoyance right up until someone reassembles them in the order shown.
Pulling two chapters out as separate files
Two files, and an explicit warning that thirty of the forty-eight pages have been left out. That warning is the point of this mode — leaving pages behind is entirely legitimate when you want two chapters, and a silent disaster when you meant to cover the whole document.
Frequently asked questions
What is the difference between splitting and extracting pages?
Splitting produces several files from one document. Extracting produces a single file containing only the pages you chose. If you want one PDF with pages 5 to 10 in it, use the page extractor. If you want each chapter as its own file, or every page separately, use this. The ranges mode here sits between the two, producing one file per range.
Do the split files lose quality?
No. Pages are copied from the source document into the new ones without being rendered or re-compressed, so text stays as text and images keep their original data. Each output file is visually identical to the corresponding pages of the original at any zoom level.
Why is a single split page sometimes almost as big as the whole document?
Because a page carries its dependencies with it. If page 3 uses a font that is embedded once in the original and shared by all fifty pages, the extracted page 3 must contain a copy of that font. For text-heavy documents with several embedded fonts, a one-page extract can be surprisingly large. Scanned documents, where each page is its own image, split almost exactly in proportion.
Can I split a password-protected PDF?
No. An encrypted document cannot be read without its password, and attempting the operation anyway would produce corrupted output that looks like it worked. The file is refused with an explanation instead. Open it in a PDF reader with the password, save an unprotected copy, and split that.
Is there a limit on the number of output files?
No fixed limit — a 500-page document split per page produces 500 files. The constraint is memory, since each output is held in the browser until you save it. For very large splits, downloading as a ZIP is more practical than saving hundreds of files one at a time.
Further reading
- Three PDFs Merged Into Less Than Half Their Combined SizePeople expect a merged PDF to weigh what its inputs weighed, and are surprised when it does not. Joining three copies of an eight-page document produced a file well under half the combined size, and the reason explains something useful about what is actually inside a PDF.
- One Page Out of Eight Was a Quarter of the FileSplitting a document feels like slicing a loaf: take an eighth, get an eighth. PDFs do not divide that way. A single page pulled out of an eight-page file was a quarter of it, and the gap between what you expect and what you get is the most useful thing a PDF will teach you about its own structure.
- Zipping 500 Tiny Files Made the Archive Bigger Than the FilesA zip is supposed to make things smaller, and on a folder of many small files it can do the opposite. Each entry carries its own header, its own directory record and its own compression stream, and below a certain file size that bookkeeping is bigger than the file.