{{ summaryHeading }}
{{ summaryMetric }}
{{ summaryLine }}
Browser-local {{ engineBadge }} {{ sourceBadge }} {{ artifactBadge }}
PDF page manager inputs
{{ 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 }}
Customize
Advanced
:

Introduction

A PDF often looks like one sealed document, but most practical editing jobs happen one page at a time. A scanned contract may need its appendices moved behind the signature pages, a training packet may need one PDF per lesson, and a board pack may need duplicate cover sheets before each section. Those jobs depend on page position, not on the text printed in a footer or the file name shown on disk.

Page management has two separate meanings that are easy to confuse. The first is the visible document order: page 1, page 2, page 3, and so on as a PDF viewer steps through the file. The second is the page label or printed number, which may use Roman numerals for front matter, restart at a chapter, or include appendix prefixes. A page instruction such as "copy pages 3 to 8" should be checked against the viewer's actual page position when the printed labels do not start at 1.

Common PDF page management jobs and what they change
Page job What changes What still needs checking
Reorder The reading sequence in the new PDF. Section breaks, page labels, bookmarks, and references such as "see page 12".
Extract A selected subset becomes the output. Whether omitted pages contained definitions, signatures, exhibits, or required notices.
Split One source sequence becomes several smaller PDF packets. Packet boundaries, naming, and whether the final packet is intentionally shorter.
Rotate Copied pages are turned by a quarter-turn or half-turn in the new output. Whether the rotation target is a source page position or an output page position.

Readable page instructions need a stable counting base. When several PDFs are combined for planning, their pages form one continuous sequence in the order the sources are placed. If a first file has 8 pages and a second file has 6 pages, combined page 9 is the first page of the second file. Moving the second source above the first would change every combined page number that points into those files.

Source PDFs feeding a page plan that selects, reorders, repeats, rotates, and outputs a managed PDF or packet ZIP.

Shortcuts such as odd pages, even pages, reverse order, open-ended ranges, and repeated page numbers can describe real work cleanly. A repeated page can place the same disclosure before multiple sections, while a reverse range can fix scans stacked backward. The same shortcuts can also create silent mistakes, especially when a long file has front matter, blank separator pages, or appendices with their own numbering.

Page management is not the same as document assurance. A new page order can be correct while bookmarks still point to old sections, a visible page number no longer matches the viewer's page position, or a digital signature no longer reflects the original file. Treat page selection as a build recipe, then open the result and check the sections that matter.

How to Use This Tool:

Work from the source list toward the output mode, then use the result tabs to verify the page recipe before downloading the built artifact.

  1. Drop or browse up to 12 unencrypted PDF files in PDF files. The Source order table shows each file's order, page count, and size. Move files before planning if combined page numbers need to follow a different source order.
  2. Choose Arrange pages into one PDF when the selected pages should become one managed PDF. Choose Split pages into packet ZIP when the output should contain multiple PDF packets inside one ZIP.
  3. Enter Page order or Range packets. Arrange mode accepts all, reverse, odd, even, single pages, forward ranges such as 3-8, open ranges such as 7-, and reverse ranges such as 8-3. Custom split mode treats each comma-separated token as one packet.
  4. For split work, set Split method to Custom range packets, Every page as a PDF, or Fixed pages per PDF. The Pages per PDF control appears only for fixed intervals and accepts 1 to 100 pages per packet.
  5. Use Rotation only when copied pages need to be turned. In arrange mode, Rotation pages refer to output page positions. In split mode, they refer to combined source page positions before packets are built.
  6. Open Advanced when duplicates, large jobs, or output metadata matter. Typed order, allow duplicates keeps repeated pages and reverse ranges. Ascending unique pages sorts selected pages and removes repeated references. The output page guard can block plans above the selected limit.
  7. Build only when the summary says the plan is ready and the Checks tab has no review state. If a warning says a file was ignored, a token is unsupported, or the page guard is exceeded, fix the source list, page selector, or guard before using Build PDF or Build ZIP.

Interpreting Results:

The result tabs are a plan preview until a PDF or ZIP has been built. After building, the summary reports the artifact name and size, and the Manifest tab becomes the best quick record of what was created. The most important check is whether every row in Page Plan points to the intended source file and source page.

PDF page manager result areas and verification cues
Result area Trust it for Do not overread it as
Page Plan Output page order, packet membership, source file, source page, copy action, and rotation. Proof that the visible document content is the right legal or business version.
Source Ledger Pages selected, rotated, omitted, and counted from each source file. A guarantee that omitted pages were safe to leave out.
Page Flow A quick chart of copied, rotated, and omitted pages by source. A substitute for reviewing the page-level table when the job is important.
Checks Source status, plan validity, output guard status, rotation status, engine readiness, and built artifact status. Document conformance, accessibility, redaction, or signature validation.
Manifest A readable recipe for the operation, sources, page plan, rotation choice, output name, and split packet files. A replacement for opening the generated PDF or ZIP and spot-checking the pages.

A valid plan means the selectors resolved inside the combined source count and stayed within the configured output page guard. Before sending or filing the result, open the built artifact and check the first page, the last page, packet boundaries, rotated pages, and any section where the printed page number no longer matches the viewer's page position.

Technical Details:

PDF is a fixed-layout document format. A page can contain text, images, annotations, metadata, form fields, and links, while document navigation may also use page labels that differ from simple positions. Page-copy work usually preserves the visual page content being copied, but it does not automatically rebuild every higher-level navigation aid or business rule around the new order.

A page selection plan first creates a one-based combined page sequence from the accepted sources. Selectors then expand into page references, and each reference creates one copied output page in either a single managed PDF or a packet inside a ZIP. Rotation is applied to the copied page during output creation, so the source file is not changed in place.

Transformation Core:

PDF page management transformation rules
Stage Rule Boundary to verify
Source map Accepted PDFs are counted in visible source order and assigned one continuous page sequence. Moving a source changes combined page numbers for all later sources.
Selector expansion all, reverse, odd, even, single pages, closed ranges, open ranges, and reverse ranges expand to page lists. Any selector outside the combined page count becomes a plan error.
Sequence handling Typed order keeps repeats and reverse ranges. Ascending unique removes repeats and sorts selected pages. Repeated pages are output pages only when typed order is active.
Packet formation Arrange mode creates one PDF. Split mode creates custom packets, every-page packets, or fixed-interval packets. The last fixed-interval packet may contain fewer pages than the selected interval.
Rotation target Arrange rotation targets output page positions. Split rotation targets combined source page positions. The same number can point to a different page when the operation mode changes.

Formula Core:

Every expanded selector reference becomes one copied output page. Duplicates therefore increase the copied-page count when typed order is used.

Pcombined = i=1nPi Pcopies = k=1mlength(Sk)

Pcombined is the total page count after all accepted sources are placed in order. Sk is one expanded selector or packet range after sequence handling. For example, 1-3, 3, 2 in typed order produces five copied pages: pages 1, 2, 3, another copy of page 3, and then page 2.

PDF page manager limits and processing behavior
Limit or behavior Value or rule Practical effect
Source files Up to 12 PDFs per run. Extra files are ignored and reported as unsupported or excess selections.
File size guard 10 MB to 250 MB per selected PDF, default 150 MB. Large or image-heavy files can be kept out of a browser job before memory becomes a problem.
Output page guard 1 to 1,000 planned page-copy operations, default 500. Plans above the current guard enter a review state before building.
Fixed split interval 1 to 100 pages per packet. Packets are generated from the combined source sequence until all pages are assigned.
Unreadable PDFs Encrypted, damaged, or non-PDF selections are ignored with a warning. Those files need repair, decryption, or conversion before page copying can continue.

Privacy and Accuracy Notes:

Selected PDF bytes are read and rewritten in the browser for the page-management action. The page may need network access to load browser capabilities, but the selected document bytes are not uploaded by the PDF or ZIP build step. Use a local policy-approved workflow for highly confidential, signed, regulated, or litigation-sensitive files, and do not treat page rearrangement as redaction, accessibility remediation, or conformance validation.

Worked Examples:

Board packet reorder: A 14-page set contains an 8-page agenda PDF followed by a 6-page appendix PDF. With Arrange pages into one PDF and 1-4, 9-12, 5-8, Page Plan should show 12 copied pages, Source Ledger should show two omitted source pages, and the built artifact should be one PDF.

Section ZIP: A training binder needs separate lesson files. In Split pages into packet ZIP with Custom range packets, the range packets 1-3, 4-6, 7- create three packet PDFs inside one ZIP. After building, Manifest should list the packet file names and page counts.

Guard recovery: A 620-page source with all selected and an output page guard of 500 makes Checks report the plan as too large. Narrow the page order, split the job, or deliberately raise the guard before building. A valid guard status only means the page-copy count is allowed, not that the resulting document is complete.

Rotation mode check: In arrange mode, rotation pages 3, 6 turn output pages 3 and 6. In split mode, the same selector turns combined source pages 3 and 6 before packets are formed. Check Page Plan after switching modes so the rotated rows are the intended pages.

Advanced Tips:

  • Use Typed order, allow duplicates when page repetition is intentional, such as adding the same cover page before several sections. Use Ascending unique pages when the output should contain each selected source page only once.
  • Check whether Rotation pages refer to output positions or combined source positions before building. Arrange mode uses output page numbers, while split mode uses combined source page numbers.
  • Set the Output page guard low enough to catch accidental repeats, then raise it only when the Page Plan and Checks tabs show the large job is deliberate.
  • Use Fixed pages per PDF for equal packet sizes and Custom range packets when section boundaries matter more than equal lengths.
  • Review Source Ledger after deleting or extracting pages. It shows which source pages were copied, rotated, or omitted, but it cannot prove an omitted page was safe to remove.
  • Choose Source title metadata only when the first source filename should identify the output. Neutral metadata is safer for renamed, combined, or client-facing artifacts.

FAQ:

Does this change my original PDFs?

No. The build step creates a new PDF or ZIP from copied pages. Omitted pages are left out of the new artifact, but the source files on your device are not edited in place.

Why do the page numbers not match the numbers printed on the document?

Page selectors use the viewer's page position in the combined source sequence. Printed page numbers or PDF page labels may use Roman numerals, prefixes, or restarted numbering, so check the source in a PDF viewer before typing ranges.

Why did one of my files get ignored?

The tool ignores unsupported, excess, oversized, encrypted, damaged, or non-PDF selections and reports a warning. Reduce the file size guard only when needed, or repair and decrypt the PDF before trying again.

Why are duplicate pages appearing?

Typed order, allow duplicates keeps repeated page references because they may be intentional. Switch to Ascending unique pages when you want duplicates removed and selected pages sorted by source order.

Why does split mode download a ZIP?

Split mode can create more than one PDF. The ZIP keeps all packet PDFs together so they arrive as one downloadable artifact with packet file names listed in the manifest.

Glossary:

Combined source page
A one-based page position after accepted source PDFs are placed in visible source order.
Page label
A PDF navigation label that may differ from the simple page position, such as Roman numerals or appendix prefixes.
Packet
One output PDF inside a split ZIP.
Typed order
A sequence mode that keeps selector order exactly as expanded, including repeated pages and reverse ranges.
Output page guard
The maximum planned copied-page count allowed before the build action enters a review state.
Manifest
A readable text record of the sources, page recipe, rotation choice, output name, and built packet files.

References: