Split PDF

From ToolzPedia, the free tools encyclopedia
This is one of several pdf tools. For the full list of utilities, see All tools.

Splitting a PDF means taking one document and producing several smaller ones, either by extracting a specific range of pages or by exploding the file into one PDF per page. It is the natural counterpart to merging, and it shows up just as often in real workflows: extracting a single chapter from a long ebook, pulling one signed contract page out of a scan bundle, or breaking a 200-page report into individual sections to send to different stakeholders.

The ToolzPedia Split PDF tool handles both modes. You can specify custom ranges using a familiar comma-and-dash syntax (1-3, 5, 7-9 creates three output files containing pages 1 to 3, page 5, and pages 7 to 9 respectively), or you can choose "every page" mode to split a 50-page document into 50 single-page PDFs at once. Like every PDF tool on ToolzPedia, the split happens entirely inside your browser using pdf-lib, so the file you upload never leaves your device.

On a modern laptop the split is essentially instantaneous, the slowest part is the download of the resulting files, which the tool packages into a single ZIP if you produce more than one output PDF.

Use the tool edit

✂️
Drop a PDF here or click to upload

Single PDF file · Max 100MB

How to use Split PDF edit

Follow these steps to use the tool:

  1. Upload your PDF

    Click the upload zone and select a single PDF file. The tool reads the file metadata and shows you the total page count so you know what range numbers are valid before you start typing.

  2. Choose split mode

    Pick "Custom ranges" if you want specific page groupings (typing something like <code>1-5, 8, 11-13</code>), or "Split every page" to produce one separate PDF per source page. Custom is the right choice for almost all real workflows; split-every-page is mainly useful for OCR pipelines or single-page archive-per-page workflows.

  3. Click Split

    Hit the Split PDF button. The tool processes each requested range, builds the output PDFs, and packages them into a ZIP archive (or a single download if you only requested one output).

  4. Download the results

    A download link appears for the ZIP file. Inside, each output PDF is named by its page range, for example <code>pages-1-5.pdf</code>, <code>pages-8.pdf</code>, <code>pages-11-13.pdf</code>, so you don't have to rename them afterwards.

Frequently asked questions edit

Use the page-range field with comma-separated ranges. Examples: <code>1-3</code> for the first three pages as one file, <code>1, 5, 9</code> for three separate single-page files, <code>1-5, 10-15</code> for two separate range files. Whitespace is ignored, so <code>1 - 5 , 10 - 15</code> works the same way.
No. The split happens entirely in your browser using pdf-lib. Your file is read into memory, processed locally, and written back as new PDFs, none of it touches the ToolzPedia server. You can verify this by opening DevTools and watching the Network tab during a split.
There is no hard limit, but the practical ceiling is around 100 MB on a typical laptop and 30 MB on a phone, because the entire PDF has to be held in browser memory while the tool works on it.
Not directly, pdf-lib refuses encrypted input. Open the PDF in any reader, enter the password, save an unlocked copy, then split that.
Yes, exactly. Pages are copied at the object level, so fonts, images, and vector graphics are preserved byte-for-byte. The split is lossless.
Not directly through the UI today, but you can do it manually. For a 100-page PDF into 4 equal parts, type <code>1-25, 26-50, 51-75, 76-100</code>.
The tool catches this and shows a clear error before doing any work, for example, "Range 95-110 exceeds the document's 100 pages." Just adjust the range and try again.
Most metadata (title, author, creation date) is preserved, but bookmarks pointing to pages outside a given output range are dropped from that output, since they would point to nothing.

Use cases edit

Extracting a chapter from an ebook or report

Pull pages 47 to 82 out of a 300-page corporate report so you can email just the section a colleague asked about, without forwarding the whole document.

Separating signed pages from a contract bundle

A counter-signed contract often comes back as a 30-page PDF where only pages 28 to 30 are the actual signature pages. Split those out for your records.

Splitting scanned receipts for expense reports

Phone scans frequently bundle a week of receipts into one PDF. Splitting them into individual files matches what most expense-reporting tools (Expensify, Concur, etc.) require.

Breaking a textbook into per-chapter PDFs

For students, separating a digital textbook into chapters makes per-section study and annotation much easier than scrolling through a 600-page file.

Distributing a multi-section report to different teams

Split an annual report so the finance team gets only the financials, marketing only the campaign summary, and so on, with each section as its own properly named file.

How it works edit

Splitting a PDF is, structurally, the inverse of merging. The tool parses the input PDF using pdf-lib, builds a list of page indices for each requested output, then for each output it creates a new empty PDF document and copies the requested pages into it via copyPages(). Each new document is then serialised and added to a ZIP archive (using the JSZip library, also loaded from a CDN) for one-click download.

The custom-range parser accepts a flexible syntax: numbers separated by commas split into separate output files, and dashes specify continuous ranges within a single file. So 1, 5-8, 12 produces three output PDFs: page 1 alone, pages 5 to 8, and page 12 alone. Whitespace around the separators is ignored, and out-of-range pages produce a clear error rather than a silent failure.

Because everything runs in the browser, the split is private by default. There is no need to trust ToolzPedia with your input, you can verify network activity in DevTools and confirm that no data leaves your machine after the initial page load.

Tips and best practices edit

  • For very large PDFs (500+ pages), prefer custom ranges over split-every-page mode. Producing 500 individual files puts pressure on the ZIP packaging step and your filesystem when you extract the archive.
  • The page numbers you type refer to the visible page sequence in the PDF, not any internal page labels (like Roman numerals in front matter). If your PDF's first 10 pages are i, ii, iii … x and the body starts at "page 1," you should still type 11 to extract the first body page.
  • If you need to remove pages rather than extract them, use a complementary range. For example, to drop pages 50 to 60 from a 100-page document, split with <code>1-49, 61-100</code> and re-merge those two outputs.
  • Splitting preserves bookmarks, links, and form fields where possible, but isolated split sections may have orphan internal links pointing to pages that no longer exist in the same file.

Common mistakes edit

Forgetting that page numbers are 1-indexed

The first page of a PDF is page 1, not page 0. This trips up developers familiar with array indexing.

Specifying overlapping ranges

Writing <code>1-5, 4-8</code> is allowed but the resulting outputs will have pages 4 and 5 in both files. This is rarely what you want.

Splitting then losing track of which file contains what

The auto-named output files (<code>pages-1-5.pdf</code> etc.) make this almost impossible, but if you rename the outputs immediately, do so consistently.

Your files stay private. This tool processes files entirely in your browser using JavaScript. No file is uploaded to any server.

Other free pdf tools available on ToolzPedia:

See also edit