Split a PDF into individual pages or custom page ranges and extract the sections you need. All processing runs in your browser — no uploads required.
Drop a PDF into the box above and the tool reads its page count. Then choose one of two modes: split into individual pages, which produces one single–page file per page, or split by page ranges, where you type exactly which pages you want and get one file per range. Each result appears in a list with its size and its own download button.
The split runs entirely inside the browser tab. The file is read with the browser's file API, cut apart by a JavaScript PDF library that loads with the page, and the pieces are handed back as local downloads. There is no upload anywhere in the code — no request carries your document off the machine, so there is no server copy to be stored, indexed, or deleted afterwards. After the page loads you can disconnect from the network and it still works. When the thing you are cutting up is a client contract, a patient record, an ID document, or a payroll run, that is usually the deciding factor.
Most of the value here is in the range box, so it is worth being exact about what it accepts. Enter a comma–separated list. Each item is either a single page number or two numbers joined by a hyphen. Every item produces its own output file.
| You type | You get |
|---|---|
1-3, 4-6, 7-10 | Three files: pages 1–3, pages 4–6, pages 7–10 |
5 | One file containing page 5 only |
1, 7, 12 | Three separate single–page files |
1-2, 9 | Two files: a two–page file, then a one–page file |
3-3 | One file with page 3 — same as typing 3 |
1 - 4 | Spaces around the hyphen are fine; one file, pages 1–4 |
Numbering is 1–based and matches what you see in your PDF viewer's page box — the first page is 1, not 0. Ranges are inclusive at both ends, so 4-6 is three pages.
9-3 is rejected. To reverse page order, list the pages individually — and note you would get separate files, not one reordered document.1-25 for a 24–page file.10-12, 1-2 produces the 10–12 file first. The list is not sorted for you.1-5, 3-8 is accepted, and page 3 through 5 appear in both outputs. Useful when two recipients each need an overlapping slice.2, 17 is a perfectly good instruction that ignores everything else.5-, -5, last, odd, even, and all are not understood. To reach the end of the document, type the actual final page number — the tool shows it, and the placeholder in the box is pre–filled with your file's real page count.The two modes solve different problems and the wrong choice is mostly a nuisance rather than a mistake.
Individual mode ignores the range box entirely and cuts every page into its own file, labelled Page 1, Page 2, and so on. It is the right answer when a downstream system wants one page per document — a records system that files each sheet separately, a batch of scanned forms that need to be routed to different people, or a stack of certificates where each recipient gets their own page.
The thing to know before you press it: a 200–page document produces 200 files, each with its own download button, and there is no ZIP and no download–all. That is a lot of clicking, and browsers frequently prompt or throttle when a page tries to save many files in quick succession. For anything beyond a couple of dozen pages, either use range mode to produce a handful of files, or accept that you will be working through the list.
Range mode is the better default for almost every human–driven task, because real tasks are about a specific slice, not about atomising the document.
The most common request of all: the counterparty wants proof of execution, not the twenty–page agreement. Open the file, find the signature page in your viewer — say it is page 18 — select range mode, type 18, split, download. You get a one–page PDF containing exactly that page, and the twenty–page original is untouched on disk. If the execution block runs onto a second sheet with the notary stamp, type 18-19 and you get both in one file rather than two.
Two details matter here. First, check whether the page you want carries a needed exhibit reference on the sheet before or after it; a signature page in isolation sometimes loses the context that makes it meaningful. Second, if you want the page removed from the document rather than extracted, express it as the ranges you want to keep: to drop page 18 of a 24–page file, type 1-17, 19-24. That gives you two files, which you then combine — there is no delete–page operation here.
A flatbed or sheet feeder run produces one PDF containing several unrelated documents — three invoices, or a stack of signed consent forms, or a month of receipts. Scroll through once and note where each document starts, then type the boundaries in one go: 1-4, 5-9, 10-11, 12-18. Four files come back, in that order, each ready to file under its own name.
Scanned pages behave identically to text pages here — the split copies page content as it stands. If the scan carried an OCR text layer, the pieces keep it and remain searchable; if it did not, they do not, because nothing in this tool performs OCR. Pages also keep their original size and rotation, so a sheet that fed in sideways comes out sideways in its extracted file. Fix rotation in the source before splitting if it matters.
Each output is a newly built PDF containing copies of the pages you selected. Page content transfers faithfully; document–level structure does not, because it belonged to the original document as a whole.
| Element | In the extracted file |
|---|---|
| Text, vector graphics, images | Preserved exactly — nothing is re–rendered or re–compressed |
| Embedded fonts | Preserved, so the page renders correctly elsewhere |
| Page size and rotation | Preserved per page |
| OCR text layer on scans | Preserved if it was there |
| Bookmarks / outline | Not carried over |
| Interactive form fields | Do not survive as working fields — flatten the form first if the values matter |
| Document metadata | Not carried over |
| Links pointing to pages outside the extracted range | Broken, necessarily — the target is not in the file |
Page numbers printed on the page do not change. If you extract pages 18–19, the resulting two–page file shows "18" and "19" in the footer, because that text is part of the page content. This is usually what you want for a legal or audit context — the extract is evidently a slice of a larger document — but it surprises people who expected renumbering. Nothing here renumbers pages.
application/pdf is refused with a message.Not within one file. Each range produces its own document with its pages in ascending order. Reordering means extracting the pieces here and then combining them in the order you want, which is a separate operation.
Quality, no — content streams are copied verbatim. Size is less predictable than people expect: a single extracted page is usually far smaller than the original, but it is not the original divided by the page count. Resources the page depends on, most notably embedded fonts, must be carried into every file that needs them, so a one–page extract from a font–heavy report can be larger than a simple arithmetic share suggests. Extracted scan pages track the size of their own bitmap closely.
Almost always one of four things: a number larger than the document has pages, a descending range like 12-4, a stray character in the list, or a hyphen that is actually an en dash pasted from a document — type the hyphen rather than pasting the range from formatted text. The error message includes your file's page count, which resolves the first case immediately.