How to split a PDF into separate pages

Split, extract, or burst: pick the right operation

"Split a PDF" is an umbrella phrase that covers three different operations. Picking the right one before you start saves rework.

Split usually means cutting a document into multiple files by page ranges: pages 1–10 into one file, 11–20 into another. Extract means pulling a specific page or range out into its own file and leaving the rest behind. Burst means producing one file per page, so a 50-page document becomes 50 single-page PDFs. Most tools support split and extract; burst is split with a one-page range applied to every page.

Step-by-step: split a PDF in your browser

A local browser split tool reads the file in the current tab, copies the requested page objects into new documents, and offers them as downloads. The source is not uploaded for the split step.

• Open the Split PDF tool and drop the file.
• Choose the mode: by page ranges, by fixed size (every N pages), or one page per file.
• Enter the ranges, for example 1-5, 8, 11-20. Use the page count the tool reports as your reference.
• Run the split. The browser builds the new PDFs in memory and prepares downloads.
• Save the results to a folder you control, and open each one to confirm it has the pages you expect.
• Keep the source file until you have verified every output.

How to specify page ranges correctly

Page ranges are the most common source of split mistakes. Most tools accept a comma-separated list where a hyphen denotes an inclusive range and a lone number denotes a single page. "1-5, 8, 11-20" produces three files: pages 1–5, page 8, and pages 11–20.

Watch for off-by-one errors around the document's boundaries. If the source has 20 pages, a range of 15-30 silently produces a file with pages 15–20 in some tools and errors in others. Confirm the source page count before you specify ranges, and open the largest output file to verify it ends where you expect.

One page per file: when burst is right

Burst — one file per page — is the right choice when each page is a self-contained record: scanned receipts, individual invoices pulled from a monthly bundle, or pages that need to be routed to different people. It is the wrong choice for a 200-page report, where you will end up with 200 files nobody wants to manage.

If you burst a large document by accident, merge the outputs back in order rather than starting over. The merge runs locally too, so the round-trip stays on your device.

Quality checks after splitting

A faithful split copies page objects without re-encoding, just like a faithful merge. After downloading, run these checks.

• Page count: each output file should have exactly the pages you asked for, no more, no less.
• Vector quality: zoom to 300% on a page with a logo. Edges should stay crisp.
• Searchable text: if the source was searchable, each output should be searchable on its own pages.
• File size: outputs should sum to roughly the source size. A much larger total suggests re-rasterization.

Forms, signatures, and bookmarks after a split

Splitting a PDF changes the file, which affects a few features the same way merging does. Form fields anchored to page coordinates travel with their page, so a field on page 5 ends up in the file that contains page 5. Digital signatures do not carry over: a signature is bound to the exact bytes of the original, and a split produces new bytes, so the signature will not validate on the extracted file.

Bookmarks and the table of contents usually do not survive a split in a useful way, because they reference page numbers that no longer match. If you need bookmarks in the output, rebuild them from the new page numbers after the split. For most extraction use cases — pulling a receipt or a single page — bookmarks are irrelevant.

How to confirm the file was not uploaded

Open the browser's developer tools and switch to the Network tab. Clear the list, then run the split with a non-sensitive test file. Look for a request whose body contains the PDF — a multipart/form-data POST with a PDF part, or a request with Content-Type application/pdf.

If you see only requests for the application's own code and analytics, the split is local. The same test works on any online PDF tool, and it is the only objective way to confirm a "no upload" claim.

Splitting very large PDFs

Browser memory is the limit for a local split, the same as for a merge. A 500-page PDF can be split into ranges in one pass on most laptops; a 2000-page PDF may need to be split in two passes, or have its largest ranges produced first while memory is fresh.

Closing other tabs helps. If the tool runs out of memory on a very large file, a desktop utility (PDFsam Basic is free and open source) or a server-based batch tool is the practical fallback. For everyday documents — contracts, reports, statement bundles — the browser path handles it without trouble.

After splitting: common follow-ups

Once the file is split, the rest of the toolkit applies. Compress each output if it is going to email. Run OCR on a scanned output if you need searchable text. Rename the files so they sort in a useful order. Each of those steps runs locally too, so the document never has to leave your device just because you needed it in pieces.

If you split a document to share only part of it, that is a form of data minimization — the recipient gets only what they need. Combine it with a metadata-removal pass on the output so author names and comments from the source do not travel with the extracted page.

Naming, ordering, and the output folder

A split produces several files, and their names decide whether the result is usable or a mess. Name outputs so they sort in the order you want: a leading page number is the simplest convention, for example 01-cover.pdf, 02-introduction.pdf, 03-methods.pdf. Without a leading number, the operating system sorts alphabetically and a file called methods.pdf lands before cover.pdf because m comes before c — not what you want.

Pick a dedicated output folder before you split, not the Downloads folder where the outputs mix with everything else. A clean folder makes verification faster: you see exactly the files the split produced, you can open them in order, and you can delete or archive the set as a unit when you are done. For sensitive content, keep that folder local and not synced to a shared cloud.

If you split a document that you will later merge back in a different arrangement, keep a note of the original page numbers on each output (in the filename or in a small index file). Reconstructing the original order from unnamed single-page PDFs is tedious; a leading page number in the filename makes it a one-minute job instead of a half-hour one.

• Name outputs with a leading page number so they sort in the right order.
• Use a dedicated output folder, not Downloads, so the set stays together.
• Keep the original page number in the filename if you may merge back later.
• For sensitive content, keep the output folder local and not cloud-synced.

A quick reference for splitting PDFs

Before you split a PDF:

• Pick the right mode: ranges, fixed size, or one page per file.
• Confirm the source page count so your ranges land correctly.
• Save outputs to a local folder, not a synced or shared location for sensitive content.
• Open each output and verify the page count and the first and last page.
• Keep the source until every output is verified.