Rearrange PDF pages with drag-and-drop and visual previews. Move pages to any position and download the reorganized PDF — all in your browser.
The pages are all there and all the right way up — they are just in the wrong order. A scanner fed the stack backwards. A signature page ended up at the front. Two sections were assembled out of sequence. This tool rebuilds the PDF with the pages in an order you choose, and hands you the new file.
Nothing is uploaded. The file is read with the browser's file API and rewritten by a JavaScript PDF library on this page. There is no server, no queue and no stored copy — which is the point when the document is a contract, a payslip or a patient record.
Load a PDF and you get a vertical list, one row per page, in current order. Each row is labelled with both facts you need: Position 3: Original Page 7. A page that has moved is highlighted and tagged (moved), so you can always see how far the current arrangement has drifted from the file you started with.
Three ways to change the order:
Then press Apply Reorder and download the result, named after your original with _reordered appended. Nothing is written until you press Apply.
Be aware of what that list of three does not include: there is no drag-and-drop, no thumbnails, and no "move to position N" box. Reordering is done by adjacent swaps. That makes some jobs trivial and others tedious, and it is worth knowing which is which before you start.
| Job | Effort |
|---|---|
| Reverse a scan fed in backwards | One click — Reverse Order |
| Move the last page to the front of a 5-page document | Four clicks |
| Swap two adjacent pages | One click |
| Move page 2 down past three pages | Three clicks |
| Move page 40 of 40 to the front | 39 clicks — use a split-and-merge instead |
| Interleave two halves of a duplex scan | Not practical here |
The honest guidance: this tool is built for local corrections and full reversal. If you need to substantially reshuffle a long document, split it into pieces and reassemble them in the order you want with the PDF Merger — that is far less work than dozens of adjacent swaps.
Document feeders that scan face-up produce the pages in reverse. You end up with a perfectly good PDF that reads from the back forwards, and every page is individually correct — the sequence is the only thing wrong. Reverse Order fixes it in a single click, which is exactly the case the button exists for.
Two related situations that look similar but are not:
This is the part worth understanding, because it has real consequences and it is the main technical difference between reordering a PDF and rotating one.
Rotation edits the existing document in place. Reordering cannot — the page tree has to be rebuilt. So when you press Apply, the tool creates a new, empty PDF document and copies the pages into it in the order you specified. Each copied page brings its own content, fonts, images and page-level annotations with it, so the visible content is preserved exactly and losslessly. No page is re-rendered and no image is re-compressed.
What does not survive the rebuild is the document-level structure that lived outside the pages:
| Preserved | Not carried into the new file |
|---|---|
| Page content, text, fonts, images | Bookmarks / the outline tree |
| Page size and orientation | Document metadata such as title and author |
| Page-level annotations | Internal links that pointed to page destinations |
| Existing rotation flags on each page | Document-level attachments and structure trees |
For the documents people actually reorder — scans, assembled paperwork, signed forms — none of that matters, because a scan has no bookmarks to lose. For a structured document with a table of contents made of internal links, it matters a great deal, and you should reorder it in the authoring application instead and re-export.
The other honest note: existing page rotation is a page property, so it travels with each page. A page that was rotated 90° before you moved it is still rotated 90° afterwards, at its new position. Order and orientation are genuinely independent, which is why they are separate tools rather than one crowded one.
Expect the output to be close to the input, and do not be alarmed if it is not identical. The document is written fresh, so incremental-update history from previous saves is dropped, unreferenced objects are not carried over, and the cross-reference table is rebuilt. A PDF that had been edited and saved repeatedly can come out noticeably smaller; a very compact one can come out marginally larger from the rewrite. Neither indicates a quality change — the page content is copied, not re-encoded.
A recurring source of confusion: reordering pages inside the file is not the same as changing how they come out of a printer. Two things people expect a reorderer to do that it deliberately does not:
Reorder the file when the file is wrong. Change the print settings when the printer is wrong. Conflating the two produces a document that is correct in exactly one context and wrong everywhere else.
For a repeatable job or a batch of files, two command-line tools express an arbitrary page order directly, which sidesteps the adjacent-swap limitation entirely:
qpdf in.pdf --pages . 3,1,2 -- out.pdf writes the pages in exactly that order. Ranges work too, and z-1 means the whole document reversed.pdftk in.pdf cat 3 1 2 output out.pdf is the equivalent, and pdftk in.pdf cat end-1 output out.pdf reverses.These are the right tools for moving page 40 to the front, or for any reshuffle where you can write the target order down as a list. For a single file and a handful of moves, the browser is quicker than installing anything.
The list shows positions, not previews, so decide the target order first. The reliable method:
If it goes wrong, Reset Order is one click and costs you nothing, because the source file is still loaded and untouched.