{{ summaryHeading }}
{{ summaryMetric }}
{{ summaryLine }}
Browser-local {{ engineBadge }} {{ sourceBadge }} {{ artifactBadge }}
{{ message }}
Drop or browse PDFs, then arrange, extract, delete, rotate, merge, or split pages from the combined page sequence.
{{ dropzoneTitle }}
{{ dropzoneHint }}
Ignored {{ ignoredFileCount }} unsupported or excess file(s).
Source order:
Order PDF file Pages Size Controls
{{ index + 1 }} {{ source.name }} {{ source.pageCount }} {{ formatBytes(source.size) }}
Choose whether the current page plan becomes one managed PDF or multiple split packets.
Select how the combined source pages should be packeted.
{{ pagePlanHelp }}
Quick plan
{{ quickPlanHint }}
Use a whole number from 1 to 100 pages per split packet.
pages
Rotate selected planned pages while copying them into the new PDF artifact.
{{ rotationPagesHelp }}
Name the generated artifact before downloading it.
{{ actionStatusLabel }}
{{ actionHint }}
Leave typed order on for page reorder, duplicate, and reverse workflows.
Accepted range: 1-1000 planned output pages.
pages
Accepted range: 10-250 MB per selected PDF.
MB
Choose the lightweight title metadata written into generated PDFs.
Packet Output page Source file Source page Action Rotation Copy
{{ row.packetLabel }} {{ row.outputPageLabel }} {{ row.sourceName }} {{ row.sourcePage }} {{ row.action }} {{ row.rotationLabel }}
Source file Pages Selected output pages Rotated Omitted Size Copy
{{ row.name }} {{ row.pages }} {{ row.selected }} {{ row.rotated }} {{ row.omitted }} {{ row.sizeLabel }}
Check Status Detail Copy
{{ row.check }} {{ row.status }} {{ row.detail }} 
{{ manifestText }}
{{ jsonPretty }}
Tags: File Tools, Productivity
Customize
Advanced
:

PDF page management is the practical work of turning page-level decisions into a clean document packet. A reviewer may need the contract before the appendix, a scanned binder may need every odd page removed, or a training handout may need sections split into smaller files. The PDF format stores pages as ordered objects, so a page plan has to say which source page is copied, where it lands, and whether that copied page needs rotation.

The important distinction is between document content and page order. Moving, extracting, duplicating, or rotating pages changes the reading sequence of the new output, but it does not prove that the resulting packet is legally complete, accessible, signed, bookmarked, tagged, or free of hidden document features. A page manager is therefore most useful when the page job itself is clear: copy these pages, in this order, into one PDF or into several smaller PDFs.

PDF source pages copied into a managed output plan Two source PDFs feed a page plan that selects, reorders, duplicates, and rotates pages before creating one managed PDF or split packets. Source PDFs Page plan Output A1 A2 A3 B1 B2 B3 1-3, 6, 4 typed order duplicates allowed selected pages rotate P1 P2 P3 PDF or ZIP

Page ranges can be more expressive than a simple start and end. all, odd, even, reverse ranges, repeated pages, and open-ended ranges describe common document jobs without making the user click every thumbnail. A repeated page might be intentional when a cover sheet must appear before several sections; a reversed range might be useful when a scan was stacked backward. Those same shortcuts can also create mistakes, so the page plan should be inspected before the output is built.

Browser-side PDF work is convenient because source files can stay on the device, but it still depends on available memory and readable source documents. Encrypted, damaged, very large, or image-heavy PDFs may fail even when the file name looks right. A clean page plan should be treated as a build recipe first, then the downloaded PDF or ZIP should be opened and spot-checked like any other edited document.

How to Use This Tool:

Start by loading source PDFs or the sample set, then decide whether the output should be one arranged PDF or a ZIP containing split PDF packets.

  1. Choose or drop up to 12 unencrypted PDF files. The source ledger shows file order, page count, and size. Move rows up or down before building because combined page numbers follow that order.
  2. Set Operation to Arrange pages into one PDF for one managed document, or Split pages into packet ZIP for multiple output PDFs packaged together.
  3. Enter a page plan. Arrange mode supports all, reverse, odd, even, single pages, ranges such as 3-8, open ranges such as 7-, and reverse ranges such as 8-3. Split mode can use custom range packets, every page as a PDF, or a fixed pages-per-file interval.
  4. Choose a rotation only when selected copied pages need it. In arrange mode, rotation page selectors refer to output page numbers. In split ZIP mode, they refer to combined source page numbers before packets are created.
  5. Use Advanced for sequence handling, output page guard, file-size guard, and output metadata. Typed order preserves duplicate pages and reverse ranges; Ascending unique pages sorts selected pages and removes repeats.
  6. Build the PDF or ZIP only after the Page Plan, Source Ledger, Page Flow, and Checks tabs agree with the document job. The manifest and JSON tabs are useful handoff records for someone reviewing the same page recipe.

Interpreting Results:

The output is ready only after the browser has written a PDF or ZIP and the summary reports an artifact name and size. Before that, the result tabs are a plan preview. The most important check is whether each output row points back to the intended source file and source page.

Result area What it confirms Common problem to catch
Page Plan Every planned page copy, output page or packet, source file, source page, and rotation. A duplicate, reversed range, or omitted page that was typed unintentionally.
Source Ledger How many pages each source contributes, how many rotate, and how many source pages are omitted. Assuming a source was fully used when only a few pages were selected.
Page Flow A charted view of selected, omitted, and rotated page counts by source file. Missing a source that contributes no pages to the final output.
Checks Source status, plan validity, output guard, rotation status, and PDF engine state. Building from a plan that exceeds the page guard or still has range errors.
Manifest A text recipe for the operation, sources, page plan, rotation choice, output name, and built split files. Sending the output without a traceable page-selection record.

A valid plan means the page selectors resolved cleanly and stayed inside the configured guard. It does not prove that page content is correct, accessible, redacted, or signed. Open the built file, check the first page, section boundaries, rotated pages, and final page, then compare the result with the manifest when the document is important.

Technical Details:

A page-management plan starts by flattening the accepted source PDFs into one combined, one-based page map. If the first source has 8 pages and the second has 6, combined page 9 means page 1 of the second source. The copied output never edits the original source file in place; it creates new PDF pages from selected source pages and writes a new artifact.

Arrange mode builds one packet named Managed PDF. Split mode builds several packets. Custom split packets use each comma-separated token as one output file, while every-page and fixed-interval modes generate packet boundaries automatically. Rotation is applied while copying the page into the output document, so it belongs to the copied page operation rather than to the source file itself.

Transformation Core:

Stage Rule Boundary
Source map Accepted PDFs are concatenated into combined page numbers in visible source order. Moving a source row changes combined page references.
Selector expansion all, reverse, odd, even, exact pages, open ranges, and closed ranges expand to page arrays. Selectors outside the combined page count become plan errors.
Sequence mode Typed order keeps repeats and reverse ranges; ascending unique removes duplicates and sorts pages. Duplicate output pages are intentional only in typed order.
Packet creation Arrange mode creates one output; split mode creates custom, every-page, or fixed-interval packets. The final fixed-interval packet may contain fewer pages.
Output guard The planned copy count must stay at or below the configured page limit. The visible guard ranges from 1 to 1,000 planned output page copies.

Formula Core:

The core page count relationship is simple: every selected page copy becomes one output page inside its packet. Repeated selectors therefore increase the output count.

Pcombined = ∑i=1nPi Poutput = ∑k=1mlen(Sk)

Here, Pi is the page count for one accepted source PDF, Sk is one expanded selector or packet page list, and len counts page references after the selected sequence mode is applied. A plan such as 1-3, 3, 2 in typed order produces five copied output pages because page 3 is repeated and page 2 appears after it.

Limit or behavior Value or rule Reason
Source file count Up to 12 source PDFs per run. Keeps the source ledger and browser workload bounded.
Source file size guard Configurable from 10 MB to 250 MB, default 150 MB per PDF. Large image-heavy PDFs can exceed memory in one tab.
Split ZIP creation Each packet is written as a PDF and then compressed into one ZIP download. Multiple browser-built PDFs need one downloadable artifact.
Metadata mode Neutral output title or first source title. Document information should be intentional after page copying.

Privacy and Accuracy Notes:

The source PDFs are read and rewritten in the browser for this workflow. The page may still need network access before the browser can build PDF or ZIP outputs, but the selected document bytes are not sent to a server by the page-management action. Check organizational policy before processing confidential PDFs, and avoid relying on the output as a redaction, accessibility, signature, or compliance pass.

Worked Examples:

Reordered packet: Two PDFs have 14 combined pages. The plan 1-4, 9-12, 5-8 moves the appendix between the cover section and the middle section. The page plan should show 12 copied pages and two omitted source pages.

One PDF per section: Split mode with custom packets 1-3, 4-6, 7- creates three packet PDFs in a ZIP. Each token becomes its own output file, so the manifest should list three packet names after building.

Rotated scan pages: Arrange mode with rotation set to 90 degrees and rotation pages 3, 6 rotates output pages 3 and 6 only. In split ZIP mode, the same selector would refer to combined source pages 3 and 6 before packet output is formed.

FAQ:

Can this delete pages from the original PDF?

No. It creates a new output from selected page copies. Omitted pages are left out of the new artifact, but the original source files are not modified in place.

Why do duplicate pages appear in the output?

Typed order preserves repeated page references. Switch to ascending unique mode when repeated pages should be removed and the output should follow source order.

Why does split mode download a ZIP?

Split mode creates more than one PDF. The ZIP keeps those packet PDFs together in one browser download.

Does rotation affect every copied page?

Only when rotation is enabled and the page selector includes that copied page. Leave the rotation pages field blank to rotate every page in the current operation.

Glossary:

Combined source page
A one-based page number after all accepted source PDFs are placed in visible source order.
Packet
One output PDF inside a split ZIP.
Typed order
A sequence mode that keeps the page selectors exactly as expanded, including repeats and reverse ranges.
Output guard
The maximum planned page-copy count allowed before the build action is blocked.
Manifest
A text summary of the sources, page recipe, rotation choice, and output artifacts.

References: