How to split a PDF — ranges, chunks, or page by page

Splitting is the mirror image of merging, and nearly as common: a client paid for one chapter, not the whole 200-page manual; a colleague needs pages 12 through 18; a scanned batch has to become one file per page for an archive. Most online splitters handle all of that — after your document has traveled to their server. This guide walks through the split that keeps the file on your machine, then covers what most guides skip: which cutting mode fits which job, what happens to page quality, and how splitting chains with the rest of a document workflow.

Split a PDF in your browser, step by step

The fastest path is the Split PDF tool on this site. It runs entirely in your browser — the document you add is never uploaded.

1. Open the split tool and drop your PDF anywhere on the page, click to browse, or paste it from the clipboard. The tool reads it locally and reports how many pages it found.
2. Choose the cutting mode: custom ranges, every N pages, or one file per page.
3. With ranges, type what you want — “1-3, 5, 8-10”. A live summary confirms how many files will be created and flags typos or pages that don’t exist, before anything runs.
4. Click Split PDF. The document is divided on your device, page by page, with a progress bar tracking each part.
5. Download the ZIP. All parts arrive in a single archive named after your document — “report-pages-1-3.pdf”, “report-page-5.pdf” — so the order survives the unzip.

Ranges, chunks, or one file per page

Three modes, three different jobs.

Custom ranges are for curated selections. The input is forgiving: open-ended forms like “5-” (from page 5 to the end) and “-4” (up to page 4), plain page numbers, any order, and overlaps are all legal — “1-3, 3-5” puts page 3 in both parts, which is exactly what you want when a page belongs to two sections. Use ranges when you know which pages go where: the signature page for a client, the appendix for finance.

Every N pages cuts the document into equal chunks. A 20-page report split every 5 pages yields four files of five pages each, named by their ranges. This is the mode for repetitive structures — weekly handouts from a course pack, quarterly packets from an annual report — where the boundaries are arithmetic, not editorial.

One file per page bursts the document completely. For a scanned batch, one file per page plus a quick rename pass is the fastest way to build a page archive; for a short document it is usually overkill.

A useful heuristic: once you find yourself typing a fourth or fifth range, switch to every N pages or one file per page, then merge the parts you want to keep.

Copied, not rebuilt — quality survives the split

Each part is assembled by copying pages, not re-rendering them. Fonts, images and vectors are untouched: text stays selectable, scans keep their original resolution, and vector graphics remain vector. A part containing page 7 is pixel-identical to page 7 of the original — which matters when the parts will be archived, printed, or merged back later. Nothing degrades by passing through the split.

One prerequisite: password-protected files must be unlocked first. The browser cannot copy pages it cannot read, so remove the password before splitting.

Splitting inside a larger workflow

Splitting rarely happens alone; it is usually one step in a chain.

Split or extract? For a single range, extracting pages is the quicker trip — one selection, one file. When you need many parts at once, splitting does the whole job in one run.

Sending parts by email: remove the pages nobody needs first with delete pages, then split — smaller parts travel better and clear attachment limits. If a part is still heavy, compress it before attaching.

And the way back: a part can be split again — the tool recognizes its own part names and doesn’t stack them — and any selection of parts can be merged into a new document. Split to distribute, merge to reassemble; the two tools cover the whole lifecycle.

When a desktop tool still wins

Browser splitting handles a few hundred pages comfortably — it runs on a background worker thread, and you can watch it work with the network disconnected. Two cases justify installing something. Books and manuals with a clean bookmark table: desktop tools can cut at every outline entry automatically, which no hand-typed range list matches on a 400-page volume. And scripted repetition: if the same document must be divided the same way every week, a command-line tool in a script beats retyping ranges.

For the one document in front of you, the browser wins on everything that matters: nothing to install, and no contract, medical record or legal filing that leaves your device.