PDF

Organize PDF Pages: Multiple Files, Page Order, Duplicates and Resets

·

Organize PDF creates one new document from the planned pages of one or more supported local PDFs. Choose each file’s physical page ranges, then move, duplicate, rotate or remove planned page occurrences. Inspect the output sequence and download organized.pdf after checking it in your intended reader.

Source files, their selected ranges and the manually edited page plan are separate parts of this workflow. Marking a checkbox targets bulk edits rather than export membership. The twelve-card window is a display view, and changing a source file or range rebuilds the manual arrangement.

Organize PDF

Choose supported PDFs and save one planned document

Use Choose PDF files or drop supported local PDFs into the workspace. One file is enough; up to 20 can be combined under the input budget. Wait for their page counts, enter any desired per-file ranges, then inspect the page cards. The thumbnail editor starts shown, even before a source is added.

Press Save organized PDF to create one output from the current plan. This workspace does not produce one file per source, split groups or a ZIP. Original device files are not overwritten by adding files, arranging pages or downloading the generated document.

  • Keep original files and decide which physical page positions you need.
  • Set source ranges and file order before making manual card edits.
  • Review the final plan and generated document before using it in another workflow.

MDN: local files and the File APIMDN: Web Worker messaging and lifecycle

Source ranges create page occurrences in file order

Each file’s Pages field accepts ASCII decimal numbers, commas and ascending hyphen ranges. Blank or whitespace-only text means all pages of that source. 3,1,3 creates three occurrences in that entered order, including the repeated third page. These are physical one-based positions, not printed labels, Roman front matter or PDF page labels.

The initial plan concatenates the selected occurrences of the first file, then the second, and so on in the visible source-file order. Repeated ranges are allowed here. Page 0, descending ranges, missing comma items, non-ASCII numeral syntax or out-of-range positions can block processing. Every occurrence counts toward the combined selection budget.

W3C PDF17: labels and physical page positionspdf-lib: PDFDocument.copyPages

File ordering and manual page ordering are different operations

The source list provides file up/down and remove buttons. With more than one file, Sort by filename and Reverse order change the source queue. Each file keeps its own range text when the queue is reordered. These operations rebuild the page plan from current files and ranges, discarding manual page edits, marks, window position and prior results.

Sort by filename uses the page language with numeric comparison and base sensitivity. Names such as source-2.pdf and source-10.pdf sort by their digit sequences in that tested example; letters and accents can behave differently across languages and environments. This is not a universal ASCII order or page-content sort. Reverse pages instead reverses the whole current card plan with each card’s added rotation retained.

File ordering and manual page ordering are different operations
OperationWhat changes
File up/down or Reverse orderSource queue changes; ranges travel with files; manual plan resets
Sort by filenameSource queue follows locale-aware numeric name comparison; manual plan resets
Move or drag one page cardCurrent output plan changes, including across source boundaries
Reverse pagesEntire current page plan reverses; per-card additions stay with their occurrences
Restore pages from file rangesManual edits are discarded; current ranges rebuild in current file order

MDN: locale-aware string comparisonMDN: numeric and sensitivity options for collation

All planned cards export; marks target bulk edits

Checking a card marks it for bulk rotation or removal. Unmarked cards still export if they remain in the plan. Use source ranges or remove unwanted cards when you want fewer output pages. A checked box is not a separate include-in-export switch.

Mark all addresses the whole plan, including offscreen cards. Unmark all clears marks without editing the page sequence. Rotate marked 90° and Remove marked act on marked entries; Reverse pages acts on the entire plan. Marking or changing the display window does not by itself regenerate the saved result.

All planned cards export; marks target bulk edits
Control or stateMeaning
Source ranges / current planDefine exported page occurrences
Mark or unmarkChoose bulk-edit targets, not output membership
Mark allIncludes planned entries outside the visible window
Rotate marked 90° / Remove markedModify marked planned entries
Reverse pagesReverse every current planned entry

Move, duplicate and remove individual page occurrences

Drag a displayed card to another displayed card, or use its earlier/later buttons, to change the output sequence. Buttons can move a page across a display-window boundary. The drag operation targets one card; marked checkboxes do not create a multi-card drag, cut/paste selection or an automatic cross-window drag workflow.

Duplicate inserts a new occurrence immediately after the chosen card, copies its current additional rotation and gives it a separate identity. The new occurrence starts unmarked, and later edits can affect it independently. Duplication is disabled at 300 planned occurrences. Removing cards changes the output plan, while removing every card disables Save until a valid plan is restored or selected again.

Twelve thumbnail cards are a display window

The editor shows up to 12 planned cards at once. Previous pages and Next pages move through the current plan; they do not truncate the output to the visible cards. A card’s output position differs from its original source page number and filename, especially after cross-file moves or duplication.

Mark all and marked bulk operations can reach entries beyond the visible window. Review the full plan before saving. Hiding the editor changes visibility but keeps the plan, marks and existing result. Clear files also retains the shown/hidden editor preference, so a new input can initially have its thumbnails hidden.

PDF.js: viewport and canvas rendering examples

Card rotation is added to the original source orientation

A card rotation click adds 90° to that occurrence’s additional angle, cycling through 0°, 90°, 180° and 270°. Bulk marked rotation uses the same 90° increment on each marked entry. The saved angle is the original source rotation plus the card’s addition, normalized within a full turn.

For an original page at 90°, an added 90° exports at 180°; an added 270° exports at 0°. Duplicating a card copies its addition, while later changes to the two occurrences are independent. An added zero preserves the source orientation rather than automatically making its content upright. There is no arbitrary-angle deskew, reflection or page-crop control here.

pdf-lib: setting page rotation

Worked plans show file order, repetitions and individual angles

Suppose A.pdf has three pages and B.pdf has two. The first page of A already has 90° rotation; the second page of B has 270°. A range of 3,1 followed by B’s 2 creates the initial occurrence sequence A3,A1,B2. Each output occurrence keeps its source identity even after moving between file groups.

The examples below describe explicit plan operations, not an automatic alternating-page or duplex-scan interleave mode. Cross-file page placement is manual through cards. Source positions, output positions and additional rotation are distinct, so check the actual sequence and orientation before using the generated file.

Worked plans show file order, repetitions and individual angles
OperationResulting planRotation effect
Ranges A 3,1; B 2A3,A1,B2Original source rotations remain
Move B2 earlier than A1A3,B2,A1Movement alone adds no rotation
Duplicate A1 after adding 90°A3,B2,A1,A1Both A1 occurrences initially export at 180°
Reverse the complete planA1,A1,B2,A3Each occurrence keeps its own additional angle
Restore the current source rangesA3,A1,B2Manual moves/duplicates/additions are discarded

Changing files or ranges rebuilds manual arrangement

Adding, removing, moving, sorting or reversing source files rebuilds the plan and clears manual page order, duplicates, removals, added rotations, marks, window position and old results. Source preview closes on file operations. Editing a file’s range also rebuilds the plan and clears those edits/results, while keeping an existing preview of the unchanged source.

Restore pages from file ranges discards manual edits and reconstructs current ranges in current file order. It keeps the range text and editor visibility preference. It is not an undo stack or necessarily a return to every original page. Hiding thumbnails alone preserves edits and result; save again after an actual plan or range change.

Source limits and output-occurrence limits are separate

Choose 1–20 nonempty PDFs totaling at most 50 MB. Every complete source must have 1–300 pages before selecting a subset. The combined parsed range selection and the edited output plan each must remain within 300 occurrences, including repetitions and duplicated cards. A manually shortened plan does not bypass an invalid or oversized original range selection.

Saving creates one new PDF capped at 100 MB. Adding files is not permission to exceed the combined selection budget, and removing cards does not create an unlimited-source reader. The tool has no byte-target compression or automatic file-size guarantee. Compare the actual generated size for an upload limit.

Source limits and output-occurrence limits are separate
BoundaryCurrent rule
Input files1–20 nonempty PDFs
Combined input sizeUp to 50 MB: 50000000 bytes
Every complete source1–300 physical pages before subset selection
Combined range selectionAt most 300 occurrences, including repeated ranges
Edited output planAt most 300 occurrences, including duplicated cards
One encoded output PDFUp to 100 MB: 100000000 bytes

Every attached source must be supported

The source reader checks a PDF-header hint and parses each document under its source limits. Encrypted or damaged sources and detected signature fields or markers can be refused, including recognized unused signature fields. These checks are editing policy rather than cryptographic signature validation or a full PDF-conformance audit.

Every attached file is read for saving, even if no remaining output card uses its pages. Deleting all cards from an unsupported source cannot bypass its validation; remove the unsupported file from the source list and rebuild the plan. There is no password/unlock control. A smaller range cannot admit a source with more than 300 pages.

Organization creates a new copied document without rasterizing

The saved document copies the planned page occurrences into a new PDF root. Supported page resources, bounds, existing rotation and physical-unit information are retained through the copy path, with each occurrence’s additional rotation applied. The operation does not resample pages into screenshots, add OCR or turn a scan into selectable text.

Document-level bookmarks, interactive forms, accessibility tags, attachments and cross-page links are not guaranteed to survive page copying. Removal or reordering is not a redaction, hidden-object sanitization or original-byte/property preservation guarantee. Inspect important features, metadata and appearances in the reader or workflow where you will use the output.

pdf-lib: PDFDocument.copyPagespdf-lib 1.17.1: pinned PDF object copierpdf-lib 1.17.1: page attributes and inheritance

Source previews and planned/result positions are independent

A file row’s Preview control browses that complete source independently of its range and the edited plan. The result’s Show PDF preview browses the newly assembled output in its own order and numbering. Result page 1 can therefore come from a later physical page or a different source. Arrangement thumbnails display current planned entries and their additions.

Document preview detail offers 800, 1600 and 2400 pixel longest-side limits; card thumbnails use up to 260 pixels. These are display settings rather than output-quality or physical-page-size controls. Source inspection and page-copy work run in the tool worker, while previews use PDF.js parsing support and main-thread canvas rendering.

PDF.js: viewport and canvas rendering examplesMDN: Web Worker messaging and lifecycle

A preview guard can leave supported saving available

Embedded images above 24 megapixels or 12000 pixels on either side can block previews, and the renderer separately guards 12-megapixel/8192-side page displays. A valid, otherwise supported source can remain copyable even when its thumbnails or source/result preview are unavailable. These are app limits rather than universal PDF.js restrictions.

Preview reading is limited to 50 MB, including generated files, while the output cap is 100 MB. A successfully downloaded large output can be unavailable in this preview. Parsing, source-page-count, encryption or detected-signature-field refusal is different and can block saving itself. Check which kind of error the interface reports.

PDF.js: viewport and canvas rendering examples

Download organized.pdf and choose the next workflow deliberately

Successful saving produces one file named organized.pdf with the planned occurrences in output order. Download saves that new file; the original inputs remain unchanged. Download all as ZIP is not offered for this one-result workspace. Use Split PDF when you need separate part files, or other dedicated tools for their supported operations.

Compress this PDF, Review text for Word and Export page images transfer the generated file through one-time same-tab memory to separate destinations under their limits. Organization itself is not PDF compression, OCR, text editing or page-image export. It does not insert blank or designed pages, import a cloud URL or create a persistent saved project.

Cancel retains inputs; Clear discards the plan

The copy job has a 60-second timeout. Cancel terminates active processing while retaining inputs and the current plan; no partial completed result is exposed. It does not delete already downloaded files. Plan and source edits invalidate earlier results and require another Save organized PDF action.

Clear files removes sources, ranges, manual plan, marks, window position, results and source preview, but retains the editor’s shown/hidden preference. Device originals are not deleted. Refreshing or leaving discards this transient workspace. Keep originals and downloads separately, and finish source/range changes before rebuilding detailed manual arrangements.

MDN: Web Worker messaging and lifecycleMDN: stopping a worker

Use Add this tool to your website on the localized tool page to copy or download the supplied HTML snippet. Keep its iframe, sizing behavior and visible ToolMellow backlink with the existing link attributes. Choose the intended language and enough frame space for multiple sources, page cards, controls and result previews.

Visitors choose their own supported local files under the same combined byte, source-page and output-plan limits. This snippet is not a hosted-file PDF organization API. Ordinary hosting, asset and analytics requests are separate from local PDF-byte processing, without an anonymity or zero-logging guarantee. Test the intended layout and keep the attribution link visible.

MDN: local files and the File APIMDN: Web Worker messaging and lifecycle

Common questions

How do I combine and reorder pages from multiple PDFs?

Choose supported local sources, set each file’s unique or repeated physical page ranges, establish file order, then move, duplicate, rotate or remove page cards. Save organized PDF creates one new organized.pdf containing every remaining planned occurrence.

Do marked checkboxes choose which pages are exported?

No. Marks target bulk rotation or removal. Unmarked planned cards still export. Define output membership with ranges and card removal rather than checking only the desired cards.

Does the 12-thumbnail window limit the output?

No. Twelve cards are a display window. The complete valid plan exports up to 300 occurrences, and Mark all includes offscreen planned entries.

Why do file or range changes discard manual arrangement?

Those operations rebuild the plan from current files and ranges, clearing manual page edits, marks, window position and old results. File ranges remain attached to their files during queue reordering; range edits keep an existing source preview.

How do duplication and repeated ranges affect the 300-page budget?

Each repeated range entry and duplicated card counts as an occurrence. Both the original combined range selection and edited plan must fit 300 occurrences. Card duplication is disabled when the plan reaches 300.

How is added card rotation combined with existing page orientation?

The saved angle is source rotation plus the occurrence’s additional angle, normalized within a full turn. Original 90° plus added 90° becomes 180°; plus added 270° becomes 0°. Duplication copies the addition, then occurrences can be edited independently.

What is the difference between Reverse order and Reverse pages?

Reverse order reverses source files and rebuilds the plan from their current ranges, discarding manual page edits. Reverse pages reverses the entire current card plan while keeping each occurrence’s additional rotation.

Does hiding thumbnails skip or reset the page plan?

No. Hiding the editor preserves the current plan, marks and result. Its shown/hidden preference also survives Clear files, although Clear discards the actual sources and page edits.

Can I remove all cards from an unsupported PDF and still save?

No. Every attached source is inspected/read under its own restrictions, even if no surviving card uses it. Remove the unsupported FILE from the list, then rebuild the plan; removing its cards is not a validation bypass.

Does reordering remove hidden objects or preserve every document feature?

No such guarantee is made. New-root page copying can lose document-level features, and changing visible page order or removing cards does not certify hidden-object removal, redaction or preservation of all source properties.

Can saving an organized PDF work when preview fails?

Yes, supported copying can remain available when preview image/render guards trigger. A generated PDF can also fit the 100 MB output cap but exceed the preview reader’s 50 MB limit. Source-validation refusal can instead block saving.

Can I embed Organize PDF with a visible credit link?

Yes. Copy or download the supplied HTML snippet from Add this tool to your website, keeping its visible ToolMellow backlink and sizing behavior. Visitors choose supported local files; the snippet is not a hosted PDF API.

Is Restore pages from file ranges an undo stack?

No. Restore discards manual page edits and reconstructs the current file ranges in current source order. It keeps range text and the editor visibility preference; there is no history of individual undo steps.

Can selecting a few pages admit a PDF with more than 300 pages?

No. Every complete source must satisfy the 1–300-page reader limit before selecting a subset. Combining more files does not bypass the 50 MB total input or 300-occurrence combined selection and edited-plan limits.

Sources and further reading

Put it into practice.

Related guides