{{ summaryHeading }}
{{ summaryMetric }}
{{ summaryLine }}
Disabled {{ engineBadge }} {{ packetBadge }} {{ sourceSizeLabel }}
{{ message }}
Browse or drop one PDF. Extra files are ignored so the split plan has one clear source.
{{ dropzoneTitle }}
{{ dropzoneHint }}
Ignored {{ ignoredCount }} extra file(s). This splitter handles one PDF at a time.
Choose how the source pages become separate output PDFs.
Examples: 1-3, 4-6, 7- or 1, 3, 5-8.
Quick ranges
{{ quickRangeHint }}
Use a whole number between 1 and 100 pages per split file.
pages
Each generated PDF uses this prefix plus a packet number and page span.
{{ actionStatusLabel }}
{{ actionHint }}
{{ progressPercent }}%
Choose how document info fields are written into split PDFs.
Accepted range: 1-300 output PDFs per run.
PDFs
Accepted range: 10-300 MB of source PDF bytes.
MB
Field Value Copy
{{ row.field }} {{ row.value }}
Packet Range token Source pages Page count Filename Size Copy
Load a PDF and choose a split mode to preview the packet manifest.
{{ row.packet }} {{ row.token }} {{ row.sourcePages }} {{ row.pageCount }} {{ row.filename }} {{ row.size }}
Check Status Detail Copy
{{ row.check }} {{ row.status }} {{ row.detail }}
Tags: File Tools, Productivity
Export to PDF Fullscreen
Customize
Advanced
:

PDF splitting divides one page-oriented document into several new PDF documents. It is useful when a scanned packet needs one file per form, a binder needs chapter packets, or a long report needs smaller review attachments. The split plan matters because each output packet gets its own page sequence, filename, and size.

The safest split starts with source page positions, not printed page labels. Covers, Roman-numeral front matter, and inserted divider pages can shift visible numbering, so source page 7 may not be the page printed as 7. Check the source page count and planned ranges before treating the new files as ready.

PDF split packets A source PDF is divided into custom page packets, then packaged for handoff as split PDF files. Source PDF 1 2 3 4 5 6 Packet 1 pages 1-2 Packet 2 pages 3-4 Packet 3 pages 5-6 ZIP handoff

Splitting copies pages into new PDFs, but it is not a document-certification step. Bookmarks, page labels, signatures, form behavior, attachments, and accessibility structure may need separate review. For regulated handoffs, inspect each output PDF in a reader after download.

Technical Details:

A PDF is a structured, page-oriented format. A split creates a plan from the loaded page count, then copies selected source pages into one new PDF per packet. The packet can contain one page, a contiguous range, an open-ended range, every odd or even source page, or all pages, depending on the selected splitting rule.

Custom range packets are intentionally packet-based. Each comma-separated token becomes one output PDF, so 1-3, 4-6, 7- creates three PDFs rather than one seven-page subset. A source page may appear in more than one packet. That is allowed, and the repeated placement is reported because it duplicates the page into separate outputs.

Split rule Packet behavior Best fit
Custom range packets Each comma-separated token creates one output PDF from the pages selected by that token. Chapter packets, exhibits, scan batches, odd/even sets, and named review sections.
Every page as a PDF Every source page becomes its own one-page output PDF. Single-page forms, receipts, signed sheets, or per-page routing work.
Fixed pages per PDF The source is divided into equal page-count packets, with the final packet shorter when needed. Large scans or reports that need predictable chunk sizes.

Range validation is tied to the loaded source page count. Source page positions start at 1, closed ranges must not run backward, and open-ended ranges use the final source page as the missing end. The parity selectors use source page positions, not printed numbers inside the document.

Token form Example Expansion Validation rule
Single page 5 Creates a packet containing source page 5. The page must be within 1 through the source page count.
Closed range 8-12 Creates a packet containing pages 8 through 12. The start must be positive and cannot be after the end.
Open range 20- Creates a packet from page 20 through the final source page. The loaded page count supplies the missing end page.
Whole document all Creates one packet containing every source page. The source must have at least one readable page.
Parity selection odd or even Creates a packet containing odd or even source page positions. Printed page labels do not change the parity calculation.

The browser session has practical guardrails because the source bytes, copied pages, generated PDFs, and ZIP package all use local memory during a run. The source file must look like a PDF by name or media type, start with the PDF header marker, parse successfully, and contain at least one page.

Boundary Limit or rule Result when it fails
Source file size 150 MB maximum when the PDF is loaded. The file is rejected before the split plan is built.
Browser work limit 10 MB to 300 MB, with 150 MB as the default setting. Work limit exceeded blocks the split until the source or limit changes.
Packet guard 1 to 300 output PDFs, with 200 as the default setting. Packet guard exceeded blocks the split until the plan is smaller or the guard is raised.
Fixed interval 1 to 100 pages per output PDF. The value is clamped to the accepted range before packets are planned.
Output naming The prefix is cleaned to letters, numbers, dots, underscores, and hyphens before filenames are written. Unsafe filename characters are replaced rather than copied into PDF or ZIP names.

Everyday Use & Decision Guide:

Start with Custom range packets when the document has human-meaningful sections. A request such as 1-2, 3-10, 11- is easier to audit than a file-size guess because each packet maps to a clear part of the source PDF. Use Every page as a PDF only when one-page outputs are actually needed, because a 90-page source creates 90 separate PDFs.

Fixed pages per PDF is strongest for mechanical chunking. Set Pages per PDF to the packet size you want, then check the final packet in Split Manifest; it can contain fewer pages when the source does not divide evenly.

Use Halves, Thirds, and Odd/even after the source is loaded. Those helpers read the current page count, so they are useful for a fast first pass. They are not a substitute for reviewing the manifest when covers, appendices, or inserted dividers change the expected page positions.

  • Set Output prefix before splitting if the ZIP and PDFs need a case number, packet name, or date.
  • Keep Output metadata on neutral split PDF metadata unless the output title should include the source filename.
  • Leave Packet guard near the default for ordinary work; raising it means the browser must create more PDFs in one run.
  • Use Browser work limit as a memory-safety check, not as proof that a large desktop browser will process every heavy scan comfortably.
  • Open Split Checks when the action row reports Plan needs review, Packet guard exceeded, or Work limit exceeded.

The selected source, generated PDFs, and ZIP bytes stay inside the browser session when the required PDF and ZIP components are available. A successful local run is still a production review point, not a guarantee that document-level bookmarks, signatures, or form behavior satisfy a records workflow.

Step-by-Step Guide:

Use the manifest and checks tabs as the control point before relying on the generated ZIP.

  1. Choose one source in PDF file with Browse PDF, drag it into the dropzone, or use Load sample. The summary should move from Choose a PDF to a planned-packet count after the page count is read.
  2. Choose Split mode. Use Custom range packets for section-based outputs, Every page as a PDF for one-page files, or Fixed pages per PDF for equal-size chunks.
  3. For custom splitting, enter Range packets such as 1-3, 4-6, 7-, or use the quick range buttons after the file is loaded. For fixed splitting, set Pages per PDF from 1 to 100.
  4. Set Output prefix. Open Advanced if you need a different Output metadata mode, Packet guard, or Browser work limit.
  5. Review warnings and the action row. If it shows Plan needs review, fix the first range error. If it shows Packet guard exceeded or Work limit exceeded, reduce the job or intentionally adjust the matching guard.
  6. Click Split PDF. The progress bar should advance while pages are copied, and the summary should change to Split ZIP Ready when the package has been created.
  7. Open Split Manifest to compare packet numbers, range tokens, source pages, page counts, filenames, and sizes. Use Download ZIP only after those rows match the split plan.
  8. Open a few generated PDFs from the ZIP, especially the first packet, every range boundary, and the final packet. Keep Split Checks or JSON when another reviewer needs the run evidence.

A clean run leaves a ZIP whose filenames, packet count, manifest rows, and downloaded pages match the source sections you meant to separate.

Interpreting Results:

Split Manifest is the main evidence table. It connects each packet number to the range token, source pages, page count, output filename, and generated size. A ready ZIP matters only after that mapping matches the expected page plan.

Result cue How to read it Follow-up check
Planned packets Shows how many PDFs the current split plan will create and how many page placements it will copy. Compare the count with the number of files you expect in the ZIP.
Overlapping pages Reports repeated source page placements across packets. Keep overlaps only when the same page should appear in more than one output PDF.
Split Packet Map Shows page count by packet as a bar chart. Use it to spot a packet that is much larger or smaller than intended, then confirm the row in Split Manifest.
ZIP filename Shows the cleaned output prefix plus a timestamp token. Confirm the name is suitable before attaching, filing, or handing off the ZIP.
Privacy path Reports that source, split PDF, and ZIP bytes stay in the browser session. Reset the page or close the tab when the local review is complete.

Split ZIP Ready means the browser created the package. It does not prove printed page labels, bookmarks, signatures, forms, or accessibility structure match a formal document-control requirement. Open the generated PDFs and inspect the pages that define the split boundaries.

Worked Examples:

Board packet split into sections

An 18-page board packet needs a cover packet, the main paper, and appendices. Enter 1-2, 3-10, 11- with Custom range packets. Planned packets should read 3 PDFs, Overlapping pages should read none, and Split Manifest should show packets for pages 1-2, 3-10, and 11-18.

One-page forms from a scan

A 12-page scanned intake packet contains one form per page. Choose Every page as a PDF. The manifest should list 12 rows, each with a single source page and a filename based on the output prefix. If Packet guard is lower than 12, the split remains blocked until the guard or mode changes.

Fixed chunks for review upload

A 23-page report needs chunks of five pages. Choose Fixed pages per PDF and set Pages per PDF to 5. Split Manifest should show five packets: pages 1-5, 6-10, 11-15, 16-20, and 21-23. The shorter final packet is expected.

Intentional overlap for a shared cover

A cover page must appear with both the executive summary and the appendix packet. Enter 1-4, 1, 5-12. Overlapping pages should report one repeated page placement. That warning is acceptable only if page 1 is meant to be copied into more than one output PDF.

Rejected range before splitting

A 24-page source receives 8-5 or 40 in Range packets. The action row should report Plan needs review, and Split Checks should point to the range error. Correct the range before using Split PDF; no ZIP should be generated from an invalid plan.

FAQ:

Does the selected PDF leave my browser?

The source PDF is read in the browser session, pages are copied there, and the split PDFs are packaged into a ZIP there. No backend helper path is used by this splitter.

Why is the Split PDF button unavailable?

The action needs the PDF and ZIP components loaded, one readable source PDF, a valid split plan, packet count within Packet guard, source size within Browser work limit, and no active splitting run.

Which range tokens can I use?

Use single pages such as 4, closed ranges such as 4-9, open ranges such as 10-, all, odd, or even. Separate tokens with commas when each token should become its own output PDF.

Can the same source page appear in more than one output PDF?

Yes. Overlaps are allowed for custom packets, and Overlapping pages reports repeated placements. Treat that warning as a stop-and-check cue unless the duplicate page is intentional.

Why do I get a ZIP instead of one PDF?

A split can create many output PDFs. The ZIP groups those PDFs into one download while Split Manifest lists the individual filenames, page counts, and source-page spans.

Will bookmarks, signatures, and forms stay valid?

Pages are copied into new PDFs, but document-level navigation, signatures, form behavior, attachments, and accessibility structure can require separate checking in a PDF reader or editor.

Glossary:

Split packet
One planned output PDF created from a range token, one source page, or one fixed-size group.
Range token
A text selector such as 1-3, 7-, odd, or all that expands to source pages.
Source page position
The numeric position of a page inside the loaded PDF, which can differ from printed page labels.
Packet guard
The maximum number of output PDFs allowed in one browser split run.
Browser work limit
The source-size cap used to avoid processing a PDF that is too large for the current browser session.
Output prefix
The cleaned filename stem used before packet numbers, page spans, PDF names, and the ZIP name.

References: