- Page order, rotation and deletion act on positions in the grid, not on original page numbers - measured, not assumed
- The export builds a new PDF and copies pages in, so bookmarks, page labels and form fields do not survive; page content and annotations do
- Nothing is re-encoded: a 12-page scan left with byte-identical image streams, +72 bytes
- But a file that shares one image across 12 pages grew 11.7x, because sharing is not preserved
- Ready-to-paste interleave strings for duplex scans, and saddle-stitch sequences for 8 to 24 pages
- Every range behaviour documented from 19 test runs, including the ones that fail silently
- Device limits, the 20-step undo stack, and the toast strings you will actually see
Three Moves: Load, Arrange, Export
Everything in this tool is one of three actions. Nothing else changes your file.
Load the PDF
Drop the file on the zone, press Browse Files, paste with Ctrl+V, or pull it from Google Drive / Dropbox. The tool reads the page tree and starts rendering thumbnails one at a time as you scroll, so a 400-page file is usable before every thumbnail exists.
Change the order
Drag a card, or use one of the five buttons above the grid: Reverse, Shuffle, Odd First, Even First, Undo. Each card also carries rotate, duplicate and delete controls. There is no "apply" step - the grid is the document from that moment on, and every change pushes onto a 20-step undo stack.
Organize, then download
Organize builds a fresh PDF, copies each page in the order you set, and hands you yourfile_organized.pdf. The progress line stays honest about what it is doing - "Organizing page 7/12" - because that copy loop is literally what is running.
Two things surprise people on the first run. First, the buttons act on positions in the grid, so after a shuffle "delete page 3" means the third card you can see, not the page that used to be number 3. Second, the export does not edit your file - it copies pages into a new document, which is fast and lossless but drops anything that lives at document level rather than page level. That second point gets its own section, because it is the thing that catches people out.
If you only need to fix one page's orientation, the Rotate PDF tool handles it in one pass without the grid. This tool earns the extra step when the order itself is wrong.
What the Export Keeps and What It Drops
Organize does not edit your file in place. It builds a new PDF and copies pages into it, which is why some things survive untouched and others disappear completely.
This is the part most guides leave out. I built a six-page file with a deliberately awkward structure: document title, author, subject and keywords all filled in, a two-entry bookmark outline, one fillable form field, one link annotation, and a single page that already carried a 90 degree rotation. Then I ran it through Organize with the order left alone and read the output back field by field.
| Property | Before | After one Organize run |
|---|---|---|
| Page count and order | 6 pages | 6 pages, in the order shown in the grid |
| Per-page rotation | page 3 at 90° | still 90°, and it travels with that page when you move it |
| Page content (text, images, vectors) | original streams | same streams, no re-encoding |
| Link annotations | 1 link on page 2 | kept, and it follows the page it belongs to |
| Title, author, subject, keywords | all four set | all four empty |
| Bookmarks (outline) | 2 entries | none |
| Form fields | 1 fillable field | 0 fields: the widget is left behind as a dead annotation |
| Open action, page mode, page labels | not set | not set, because nothing writes them back |
The pattern is simple once you see it: everything that lives on a page is copied with the page, and everything that lives on the document is not. Your text, your images, a stamp you added earlier, a hyperlink someone embedded: all fine. The title that shows in a browser tab, the sidebar bookmarks, the fillable client-name field: gone the moment you press Organize.
Bytes: usually identical, sometimes 11x bigger
Copying pages sounds like it must re-encode something. It does not. A 12-page scan where every page carried its own JPEG came back 72 bytes larger than the input (1,498,520 to 1,498,592 bytes), with all twelve content streams and all twelve image streams byte-for-byte identical to the originals. The 72 bytes are the new file's cross-reference table and a short page index. Nothing was re-compressed, so the export cannot make your scan blurrier.
There is one case where the output grows a lot. A second 12-page file pointed all twelve pages at a single shared 125,791-byte image (129,726 bytes total on disk, because the image was stored once and referenced twelve times). Output: 1,515,500 bytes, about 11.7 times the input, because the copy loop writes that image into the new document once per page. This is not a bug you can work around with settings; it is what "copy each page into a fresh document" means. If you hit it, compress afterwards and the duplicate copies merge back down.
If a form field still needs filling, fill it first. If the bookmarks matter, note the chapter pages before you start, because you will be rebuilding them. If the file is a signed contract, keep the original: the signature panel and document metadata are the first things a rebuild drops.
Watch a Full Run, Start to Finish
About twenty seconds, the real sequence: load, drag one page to the front, shuffle, delete, then organize and download.
Removing Pages, At One Page or Two Hundred
Deleting pages is the job people open a page organizer for. There are two ways to do it here, and one of them refuses to work when it should.
The slow way is the small X on a page card: one click, one page gone, and Undo brings it back. That is fine for a cover sheet or a stray blank. It stops being fine somewhere around page forty of a 200-page scan, which is where the Delete Pages box earns its place. Type the positions you want gone and it removes them in one action.
| You type (6-page file) | What actually happens | Toast |
|---|---|---|
3 | Page 3 removed, five pages left | Deleted 1 page(s). |
3,7-9 | Only page 3 removed; 7, 8 and 9 do not exist and are ignored | Deleted 1 page(s). |
2,4 | Both removed, four pages left, original order kept | Deleted 2 page(s). |
1-6 | Refused. The grid is untouched | Cannot delete all pages. |
9-3 | Reversed to 3-6 and removed, so four pages remain | Deleted 4 page(s). |
| empty | Nothing happens | Enter pages to delete. |
0,-2,abc | Nothing happens | No valid pages found. |
Two behaviours there are worth knowing before you rely on them. A range typed backwards (9-3) is silently swapped to 3-9 rather than rejected, so a fat-fingered range deletes more than you meant. And a file cannot be emptied: deleting every page is blocked, which is a guard rail rather than a limitation, because a zero-page PDF is not a file you can open again.
The refused case is also handled properly, which is not automatic. In my test I rotated page 1 to 180°, then tried to delete all six pages. The delete was refused and the rotation was still there afterwards, because the tool rolls back the change it did not complete instead of leaving the grid half-edited. Same rule for everything else on this page: nothing is written until you press Organize.
Positions, not page numbers
This trips up almost everyone, so it gets its own heading. Both boxes read positions in the grid as it looks right now. Reverse a six-page file first and the order becomes 6,5,4,3,2,1. Now type 1 in the Delete box and you do not delete the original page 1: you delete whatever is sitting first, which is the original page 6. Output: 5,4,3,2,1. The same applies to the order box: after that reverse, typing 1,2 gives you pages 6 and 5, not 1 and 2.
Practically, that means one operation at a time with a look at the grid between them. If you shuffle for a worksheet and then delete "page 2", you are deleting a page you have not looked at. Undo is the way out: twenty steps of it, covering reorder, delete, rotate and duplicate.
Finding the pages worth deleting
Blank pages from a duplex scanner arrive in pairs, and the same sheet of paper shows up twice. Scroll the grid in order and note the positions on paper first, then type them as a single comma list. On a 200-page file that is one action instead of two hundred clicks, and because the parse ignores anything that is not on the page list, an out-of-range position costs you nothing. If you are deleting to shrink a file rather than to clean it, deleting pages helps far more than compressing does, and the compress guide has the measured numbers for why.
The Page Order Box, Exactly As It Parses
Typing a sequence is faster than dragging once a file passes about thirty pages. Here is what the parser does with every shape of input, including the ones it accepts without complaint when it probably should not.
The box takes comma-separated numbers and ranges. Anything that is not on the resulting list is dropped, which is the single most important thing to understand about it: you are not saying "put page 5 first", you are saying "the new document is these pages, in this order".
| You type (6-page file) | New order | What it tells you |
|---|---|---|
1-3,5 | 1, 2, 3, 5 | Applied custom order: 4 pages. Pages 4 and 6 are dropped, not appended |
3,1,2 | 3, 1, 2 | Applied custom order: 3 pages. Explicit order is respected exactly |
1,1,1 | 1, 1, 1 | Duplicates are allowed: one page, printed three times |
9-3 | 3, 4, 5, 6 | Applied custom order: 4 pages. A backwards range is swapped, not rejected |
2,4- | unchanged | No valid pages found. A dangling dash voids the whole input |
0,99,abc | unchanged | No valid pages found. Out-of-range and non-numeric entries produce nothing |
2 , 4 | 2, 4 | Applied custom order: 2 pages. Spaces around commas are trimmed |
| empty | unchanged | Enter page order. |
Notice the difference between the two failure styles. A partially valid list still runs, so 1-3,5,88 quietly gives you four pages and drops the 88. A list where nothing resolves is refused outright and your grid stays as it was, which is the safer half of the behaviour. The toast is your pre-flight check either way: read the page count in it against the file you expected before you hit Organize.
Recipes worth keeping
- Page 40 to the front:
40,1-39,41-200. One line, no dragging through thirty-nine cards. - Odd pages only (single-sided print from a duplex scan):
1,3,5,7,9and so on. Write the last number first so you know where to stop. - Every second page, the other half:
2,4,6,8,10. Run the file twice, once per half, and you get both sides as separate documents. - Signature block moved to page 3:
1,2,58,3-57,59-60, using the real page number of the signature page. Check the toast says the original page count before exporting. - Reverse, without the button:
200-1. Same result as Reverse, and it works when you already have a half-typed list to merge.
Two limits on the box. It reads the grid, not original page numbers, so a recipe stops matching once you have dragged or shuffled. And it has no memory: the box keeps your text for reference, but pressing it again applies the same list to the grid as it stands now, which after the first run is a different document. If you need to try two arrangements, run one, look at the toast, then press Undo before typing the second.
Two-Sided Scans: Rebuilding the Real Order
A sheet-fed scanner that does not duplex gives you every front, then every back. Here is how to turn that back into a readable document without retyping forty page numbers by hand.
This is the most common mess I see, and it is worth being precise about which version you have, because the fix is different for each. Dump the grid and look at page 21 or so.
- True duplex: 1, 2, 3, 4. The scanner flipped the sheet and wrote the back as the next page. Nothing to fix.
- Two passes, backs in the same order: fronts 1 to 20, then backs 21 to 40, where back 21 belongs after front 1. Real order is 1, 21, 2, 22, 3, 23.
- Two passes, backs reversed: fronts 1 to 20, then backs 40 down to 21, because you flipped the stack over instead of turning it. Real order is 1, 40, 2, 39, 3, 38.
- Backs reversed within each sheet: the grid reads 2, 1, 4, 3, 6, 5. Real order is a plain 1 to 40, so a Reverse plus a swap fixes it faster than typing.
Build the list in a spreadsheet, paste it once
The order box needs an explicit list, and it will not interleave for you. Generating that list is a thirty-second job with two columns. For the 40-page two-pass case (fronts 1 to 20, backs 21 to 40 in reading order):
| Cell | Formula | What you get |
|---|---|---|
| A1 down to A20 | 1, 2, 3, and so on | The front pages |
| B1 | =A1+20 | 21, the back that follows front 1 |
| C1, filled down | =A1&","&B1 | 1,21, then 2,22, and so on |
| One cell | =TEXTJOIN(",",TRUE,C1:C20) | The whole string, ready to paste |
For the flipped-stack version, replace B1 with =41-A1, which counts 40, 39, 38 downward, so back 40 lands after front 1. Same C column, same paste. Paste the result into the Page Order box, press the button, and read the toast before exporting: it should say 40 pages. If it says 20, the join cell only picked up one column and you have just deleted every back.
Odd First and Even First reorder, they do not filter. On a six-page file, Odd First gives 1, 3, 5, 2, 4, 6 and Even First gives 2, 4, 6, 1, 3, 5. Both keep all six pages. That is exactly right for manual duplex printing, where you print the whole file twice with a different first page, and exactly wrong for a two-pass scan, where you need fronts and backs alternated one at a time rather than grouped.
When the count is odd
A two-pass scan of an odd number of sheets always ends with a blank back, and a reversed-stack version ends with that blank in the middle of the interleave rather than at the end. Rather than hunting for it by eye, delete it before you interleave: it is the last page of the file if the backs ran forwards, and the first back if they were flipped. Undo exists, so the cheaper test is to run the interleave, scroll to the seam in the grid, and fix the one page that looks wrong.
If your scanner writes each side as its own file instead of one PDF, stop here and merge first: Merge PDF in the same order you scanned, then come back to this page. The merge guide covers what merging does to page order, which matters for the same reason the grid reads positions rather than page numbers.
Booklet and Imposition Sequences
Printing a folded A5 booklet from A4 sheets is a page-order problem, not a page-edit problem. The grid handles it, but only if you know the sequence.
When you fold sheets in half and staple the spine, page 1 and the last page end up on the same side of the same sheet. A printer does not know that. If you send it a document in reading order with "2 pages per sheet, duplex" ticked, you get a stack of unrelated spreads. What it needs is the physical order in which the pages pass through the tray: outermost spread first, innermost spread last.
For a document of n pages, the sequence is: n, 1, 2, n-1, n-2, 3, 4, n-3 and inward from both ends. Here it is worked out for the sizes people actually print. Type the whole string into the Page Order box, press the button, and check that the toast still reports the original page count before exporting.
| Pages | Sheets | Paste this into the Page Order box |
|---|---|---|
| 4 | 1 | 4,1,2,3 |
| 8 | 2 | 8,1,2,7,6,3,4,5 |
| 12 | 3 | 12,1,2,11,10,3,4,9,8,5,6,7 |
| 16 | 4 | 16,1,2,15,14,3,4,13,12,5,6,11,10,7,8,9 |
| 20 | 5 | 20,1,2,19,18,3,4,17,16,5,6,15,14,7,8,13,12,9,10,11 |
| 24 | 6 | 24,1,2,23,22,3,4,21,20,5,6,19,18,7,8,17,16,9,10,15,14,11,12,13 |
Every page appears exactly once, so nothing is lost and the toast count matches the input. After you export, the imposed file is no longer a document you can read on screen: page 1 of the PDF is the outside cover spread. Keep the reading-order original and treat the imposed copy as a print artefact. If you need to go back, Undo in the grid, or re-upload the original, because the imposition itself is just a page order.
Printing it
Send the imposed file to the printer with 2 pages per sheet, duplex, and scale to fit turned on. The one setting that varies by printer is which edge it flips on: half of them need flip on short edge for a landscape sheet, the other half want long edge. Print the first sheet only, fold it, and look at it before committing twenty sheets of card. If the backs are upside down, change that one setting and print the same sheet again.
Two limits worth stating plainly. This tool reorders pages, it does not impose them: the 2-up layout is the print driver's job, which is why the sequence above is a flat list rather than pairs. And n has to be a multiple of four, because a folded booklet always has four panels per sheet. A 14-page file cannot be saddle-stitched without two blank panels, so either add padding pages in another tool or print the final sheet separately.
Add page numbers before imposing, not after. Once the pages are in imposition order, a numbering pass counts the imposed sequence, so sheet 1 gets "1" even though it is physically the back cover. Number first, impose second.
The Same Job in pdfarranger, Acrobat and Preview
Three desktop options, what each one is actually good at, and the one job the browser grid does better.
If you reorder pages twice a year, a browser tab is enough. If it is part of a weekly workflow, a desktop tool earns its place, mostly because it keeps the file on disk and can be scripted. Here is the honest split, not a sales page.
| Capability | AFFLIGO (browser) | pdfarranger | Acrobat | Preview (macOS) |
|---|---|---|---|---|
| Cost | Free, no account | Free, open source | Paid subscription | Free with macOS |
| Install | None | Needs install | Needs install | Already there |
| Drag to reorder | Yes | Yes | Yes | Yes, in the sidebar |
| Type an explicit page order | Yes | No | No | No |
| Delete, rotate, duplicate | All three | All three | All three | Delete and rotate |
| Undo | 20 steps | Edits stay in memory until you save | Yes | Yes |
| Imposition presets | Typed sequences (section 07) | Booklet layout built in | Print dialog only | No |
| Also does OCR, redaction, forms | No, other tools | No | Yes | No |
pdfarranger is the closest free equivalent and the only one on this list with a real booklet layout feature, so if you print folded booklets every month, install it and skip my sequence table. Its weakness is the other end: it is a pure drag interface, so restacking a 200-page scan means dragging or cutting and pasting page by page, and there is no order box to type into. It is also the tool I would reach for if a file had to stay on a machine with no network.
Acrobat is worth the subscription only if you need what the subscription actually sells: OCR on scans, redaction that removes text rather than covering it, form authoring, and preflight for print. Page reordering is the free tier of that skill set, and paying $19.99 a month on an annual plan ($29.99 month to month) to drag a page out of a PDF is hard to justify. Standard sits at $22.99 month to month. Prices are Adobe's own listings, and they move, so check before you subscribe.
Preview on macOS is the one people already have open. Drag a thumbnail in the sidebar, press Backspace to delete, Cmd+S to save. It is genuinely fast for fixing one page in a ten-page file. What it will not do is accept a typed sequence, which means anything from section 06 or 07 turns into an hour of manual dragging.
Typed sequences. A 24-page saddle-stitch imposition is 24 numbers pasted once, or 24 drags in a desktop app where a single misdrop shifts everything after it. No desktop option on this list has an equivalent.
Limits, and the Ones That Actually Stop You
There is no page-count limit and no account limit. What exists is a set of guards sized to your device, and they behave differently from the numbers most pages quote.
Four gates run in a fixed order every time you drop a file. Knowing which one fired tells you what to do next, because three of them can be worked around and one of them cannot.
| Gate | Trigger | What you see |
|---|---|---|
| Not a PDF | Any other file type | Toast: Please select a PDF file. Nothing loads |
| Device cap | File larger than your tier allows | Modal: File too large for this device, with your RAM, cores, tier and the safe limit, plus a Close button |
| Hard ceiling | Over 1 GB | Toast: exceeds 1GB, too large |
| Page-count confirm | 300 pages or more on a computer, 150 or more on a phone | Browser confirm dialog. Decline and the file is removed from the organizer |
The device cap is the one people hit, and it is not a fixed number. It comes from a tier table: 30 MB, 60 MB, 100 MB, 200 MB or 300 MB per file, chosen from your reported RAM, your core count, and how full the browser's JavaScript heap currently is. That last signal is why the same laptop can accept a 150 MB file in the morning and refuse it in the evening after forty tabs: using more than about 70 percent of the heap drops you to the lowest tier regardless of hardware. The line under the dropzone that reads "Max N MB per file on this device" is not decoration, it is the exact figure the guard will enforce.
The 1 GB ceiling is a backstop, not a working limit. Every tier cap sits far below it, so in normal use you will never see that message; it exists for the case where the tier detection gives up entirely. In the same way, 300 pages is a confirm rather than a refusal, because thumbnails render only for the cards you scroll to: a 600-page file is perfectly usable provided you do not scroll it end to end at speed.
What is actually consuming memory
The PDF itself is the small half. A 40 MB scan renders around forty canvas thumbnails at preview width, and those bitmaps, not the file, are what fill the tab. That is why the guard is per file rather than per queue, and why the page-count dialog exists on top of it. If a large file feels sluggish, the fix is to work in passes: organize the first hundred pages, export, then do the rest, rather than loading everything at once.
Undo is capped at twenty steps, covering reorder, delete, rotate and duplicate. On a file you have shuffled five times, the twenty-first action quietly pushes the oldest state out of the stack, so the thing to undo is always the most recent mistake rather than the one from ten minutes ago.
All of the above happens in the tab: the PDF is read with pdf-lib and PDF.js from a local file handle, and the export is assembled in memory before the download starts. There is no request carrying your document, which is also why the limits are your device's limits and not a server quota.
Message Decoder
Every toast and dialog this tool can produce, what triggered it, and the shortest way past it.
These are copied from the code rather than paraphrased, because "No valid pages found" and "Cannot delete all pages" look similar on screen and mean completely different things.
| Message | What produced it | What to do |
|---|---|---|
| Please select a PDF file. | A file that is not a PDF, or a renamed one | Check the extension and the file itself; a DOCX renamed to .pdf is still a DOCX |
| Failed to load PDF. Try a different file. | pdf-lib parsed the header but the structure is broken | Truncated download, or a file exported by a broken generator. Re-export the source |
| File too large for this device | The tier cap in section 09 | The modal names your RAM and the safe limit. Split or compress the file first |
| Large document: N pages. Continue? | 300+ pages on a computer, 150+ on a phone | Declining removes the file. Accept and scroll carefully |
| Removed large file from organizer. | You declined that dialog | Nothing to fix; drop the file again if you changed your mind |
| Enter page order. / Enter pages to delete. | Empty box | Type a list first. Typing into the box does not apply anything by itself |
| No valid pages found. | Nothing in the input resolved to a real position | Almost always a dangling dash (2,4-) or numbers beyond the page count |
| Applied custom order: N pages. | Success, and N is your new page count | Read N. If it is lower than expected, pages were dropped rather than moved |
| Deleted N page(s). | Success, counted after out-of-range numbers were ignored | If N is smaller than the list you typed, part of it did not exist |
| Cannot delete all pages. | The delete list covered the whole document | Remove the last remaining page by hand instead, or keep it |
| First click the Page Order or Delete Pages box, then click pages. | You clicked a card expecting it to fill a box that was never focused | Click into the box, then click cards to append their positions |
| Page N already added. | The same position clicked twice into the same box | Harmless. Each position is only listed once by clicking |
| Cancelled. Your file and page order are kept. | Cancel pressed during the export loop | Nothing was lost. Press Organize again when ready |
| PDF Organization Failed | An exception during the copy loop, with the reason underneath | Read the small line under the title. A password prompt cancelled mid-run lands here |
One message deserves a note of its own: a password-protected PDF usually never reaches any of these, because the tool asks for the password in-page first and unlocks a copy in memory. Cancelling that prompt is the most common cause of the generic failure card, which is why the two are listed separately above.
This tool takes one PDF at a time, and the grid is the reason: each page card tracks a source page in one document. For a mixed document, merge first, then organize the merged file, then compress once at the end. Doing it in that order means one compression pass instead of three, and the merge guide explains what merging does to page order before you touch the grid.
How This Was Tested
Every number and behaviour on this page came from running the tool and reading the output back, not from the documentation.
The method matters if you want to trust the rest of the page, so here it is in full. I built test PDFs with pdf-lib, drove the live tool in a headless browser, and then re-opened each download and measured it rather than judging it by eye.
The fixtures
- Six-page identification fixture. Every source page draws its own page number in a slightly different text length, so the width of the text in each output page identifies exactly which source page landed there. Without that trick, a reorder looks identical whichever way it runs.
- The same fixture also carried a document title, author, subject, keywords, a two-entry outline, one fillable form field, one link annotation, and a pre-set 90 degree rotation on page 3, so the export's handling of each could be read back separately.
- Two 12-page scan fixtures. The first gave every page its own JPEG. The second pointed all twelve pages at one shared image, to test whether object sharing survives a rebuild.
The runs
Nineteen UI cases through the real interface: identity, Reverse, Odd First, Even First, Shuffle twice, Undo, two rotate-plus-export combinations, six page-order strings and three delete strings, plus the two "does it act on positions or page numbers" tests. Each run was a fresh page load and a fresh upload, so no state carried over.
Every download was then reopened and checked for: page count, page order (via the text-width trick), per-page rotation angle, annotation count per page, document metadata, outline presence, form-field count, file size, and whether the content and image streams were byte-identical to the source.
| What was measured | Result |
|---|---|
| Identity run output size | 3,273 bytes from a 3,800-byte fixture |
| Reverse, six pages | 6,5,4,3,2,1 with the 90 degree page following its own page number |
| Shuffle, two runs | 6,5,1,4,2,3 and 3,2,6,5,1,4, so the order really is random per run |
| Page-order string that works | 1-3,5 produced four pages, not six |
| Page-order string that refuses | 0,99,abc left the grid untouched |
| Delete that is blocked | 1-6 refused, and a 180 degree rotation survived the refusal |
| Positions vs page numbers | Reverse then delete 1 removed the original page 6 |
| Scan with one image per page | 1,498,520 bytes in, 1,498,592 bytes out, streams identical |
| Scan with one shared image | 129,726 bytes in, 1,515,500 bytes out |
What I did not test
Being explicit about the gaps is more useful than pretending there are none. I did not test files above 200 MB, because the results would describe one machine's memory rather than the tool. I did not test a 1,000-page document end to end. I did not test every PDF flavour: files from LaTeX, InDesign and a few scanner apps behaved the same as the fixtures, but a heavily structured PDF with tagged accessibility content may drop more than the table in section 02 lists. And I did not test the password path beyond confirming that a correct password unlocks and a cancelled prompt lands on the failure card.
Two claims in earlier versions of this guide did not survive the testing, and both are corrected below rather than quietly deleted. That is the honest trade of publishing measurements: the numbers can contradict you.
Corrections to Earlier Versions
Six things this page used to state that the measurements contradicted, left visible instead of quietly edited out.
A guide that never corrects itself is either very new or not checking. The previous version of this page was written from the feature list, which is how the usual claims get made: limit is 1 GB, metadata is preserved, invalid input is ignored. Running the tool showed four of those to be wrong and two to be true only in a narrow case.
| What this page used to say | What the tests showed |
|---|---|
| Bookmarks and document metadata survive organizing, and links may not remap | Title, author, subject and keywords come back empty, and the outline is removed entirely. The one link annotation I planted did survive, so the old sentence had the two halves the wrong way round |
| Each file can be up to 1 GB | Your device tier caps it at 30, 60, 100, 200 or 300 MB, and that cap is enforced with a modal. 1 GB is a backstop above every tier, so the limit you actually meet is a fraction of it |
| Invalid or out-of-range page numbers are ignored with a notification | True only while at least one entry resolves. A list with nothing valid in it is refused and nothing changes. The bigger correction is that the order box is a whitelist: pages you do not list are deleted, not appended |
| Odd First and Even First help with duplex-scanned documents | Both buttons sort by position parity and keep every page: a six-page file becomes 1,3,5,2,4,6. That is right for manual duplex printing and wrong for a two-pass scan, which needs a typed interleave |
| File size barely changes after organizing | True when each page carries its own image: 1,498,520 bytes became 1,498,592. False when one image is shared across pages: 129,726 bytes became 1,515,500, about eleven times larger |
| Deleting pages removes them from the arrangement | Correct, and worth restating because it is the surprising half. Nothing touches the file until Organize, and a refused delete rolls the whole change back rather than leaving a half-edited grid |
The previous version also carried seven sections explaining what a page organizer is, why people need one, which operations exist, and what the tool's own feature list contains. None of that survived the rewrite, because none of it is something a reader cannot get from the first paragraph of the tool page. The space went into the measurements above instead.
If a claim on this page is wrong, the test that produced it is reproducible: build a six-page file with a unique text width per page, run it, and read the widths back. That is how every number here was produced, and it is the standard I would want applied to any guide that quotes figures.
Frequently Asked Questions
Nine questions this tool actually gets asked, answered from the code and from the runs in section 11 rather than from the feature list.
Want to explore more?
Key Takeaways
- Reorder, delete and rotate act on positions in the current grid, so reverse first and the page you delete is not the page you had in mind
- The Page Order box is a whitelist:
1-3,5exports four pages, and everything you do not name is dropped - Page content is copied, not re-rendered, so text and images are byte-identical; metadata and bookmarks are rebuilt from nothing and come out empty
- A file that shares one image across pages grows on export (11.7x in testing) while a normal scan moves by 72 bytes
- Odd First and Even First are for manual duplex printing, not for two-pass scans; a scan needs a typed interleave such as
1,7,2,8,3,9 - Your device sets the size cap (30 to 300 MB) and the undo stack holds twenty steps, so a mistake is recoverable until the tab closes
