Drag pages into the sequence you want and download the rearranged document. Pages are copied rather than redrawn, so nothing loses quality on the way through.
Runs in your browser. Nothing is uploaded.
Rearranging means building a new document and copying pages into it in the order you specified. Each page object is transferred with the resources it depends on, references are renumbered so they still resolve, and a fresh index is written. Nothing is rendered and nothing is recompressed, so a scanned page arrives at exactly the resolution it left at and the file barely changes size: a 50,563 byte document came back at 50,562 bytes, one byte smaller, in 25 milliseconds.
That copying is also why this operation loses more than rotating does. PDFs keep some things per sheet and some things once for the whole file, and only the per-sheet half is carried into a rebuilt container. In practice that means fillable fields stop accepting input and the chapter outline vanishes. Merging and splitting work the same way. Rotating or stamping the same file keeps both, because those edit what is already there instead of assembling something new.
Choose a PDF
The same questions a security review would ask, answered plainly.
Every page is a thumbnail you can pick up and move. The list is the document, so what you arrange is exactly what you download.
Pages are copied as objects, not redrawn, so text stays selectable and scanned images keep their original resolution and file size.
Your source is opened read-only and the rearranged copy saves separately, so an arrangement you dislike costs one download and nothing else.
Rebuilding a twelve page document took 25 milliseconds. There is no upload at either end, which on most connections is the entire wait elsewhere.
There is no upload step and no server to receive one. The page loads once, then all work on your PDFs happens in local JavaScript.
No daily limits, no per-file ceilings imposed by a server tier, no watermarks, and no account. The practical limit is your own device's memory.
Measured on a real document, plus the everyday editorial case.
What the operation costs, measured with the order left alone.
Input
12-page text PDF, 50,563 bytes
Output
50,562 bytes, 25 ms
One byte smaller, which is the old cross-reference table being replaced. Rearranging pages is close to free in both time and size, because the content itself is only ever copied.
The common editorial case.
Before
Pages 1-9 body, pages 10-12 appendix
After
Pages 10-12 first, then 1-9
Drag the three appendix pages above the body and download. The pages themselves are identical afterwards; only the order in the new document's page tree differs.
Real files, real numbers, and the machine they were run on.
| Scenario | Input | Output | Time | Notes |
|---|---|---|---|---|
| 12-page text PDF rebuilt, order unchanged | 50,563 bytes | 50,562 bytes | 25 ms | content copied, never re-rendered |
How this was measured: Measured by driving this page in headless Chrome 152 on an Apple M4 Pro running macOS 15.5, on 2026-09-17. The fixture is handed to the page's own file input, the page's own button is pressed, and the figure recorded is the size of the file the page produces. Timings come from a warm page on a fast machine with no network involved, so treat them as a floor rather than a typical result.
Sections assembled out of sequence, or an appendix that belongs at the front, are fixed by dragging rather than by exporting the whole thing again from the source application.
A sheaf fed in the wrong order, or a document scanned back to front, becomes correct without rescanning anything.
Applications and tenders frequently specify the order documents must appear in. Rearranging locally keeps the contents private while you get it right.
Putting pages in the order they need to be produced avoids relying on printer settings that behave differently on different machines.
Reordering chapters into the sequence you actually work through makes a long reference document far easier to read on a tablet.
The rearranging happens in your browser once the page is open, so it continues to work with no connection.
The first item catches people out, because the document still looks correct.
The document is rebuilt from copied pages, and anything held at document level does not survive that. A fillable form comes back looking right and no longer accepting input, and the outline tree disappears. Rotating or watermarking would keep both.
This changes the order and nothing else. Removing a page means extracting everything except it, and there is no way to repeat a page in the output.
You are rearranging one file. Bringing in a page from elsewhere means merging the documents first and then reordering the combined result.
No. The document is read into this tab, a new one is assembled in the order you set, and that copy goes to your downloads. No request carries the document at any point, and disconnecting the machine before you start changes nothing about how it works.
No. Pages are copied as objects rather than redrawn, so text stays selectable and scanned images keep their exact resolution. The rebuilt twelve page document came out one byte smaller than it went in.
No, and it is the thing worth checking before you rearrange one. Field definitions are registered once for the whole file, not attached to individual sheets, so rebuilding from copied sheets leaves them behind. What you get back looks identical and silently refuses to accept typing.
They are lost, for the same reason. The navigation tree belongs to the document, and copying pages into a new one leaves it behind. A long manual will reorder correctly and arrive with no chapter list.
Not from this page. Reordering changes sequence only. To drop a page, extract every other page into a new document, which produces the same result by a different route.
Only by dragging, since there is no reverse button. For a short document that is quick; for a hundred pages it is genuinely tedious and a desktop editor will be faster.
Yes, each keeps the number it had in the source document as you move it around. That makes it straightforward to confirm the new sequence is what you intended and that no page has gone missing.
Nothing caps it here. Memory decides, because the source and the document under construction both sit in the tab at once, and drawing a preview for every sheet is the part that actually slows down on a long file.
No. Your selected file is opened read-only, and the rearranged version goes to your downloads as a separate document. Trying several arrangements costs nothing, because the source is never rewritten.
Yes, once the page has loaded. Reading the document and writing the new one are both done in the browser, so no connection is needed afterwards.
There is no limit imposed by us, because there is no server tier to enforce one. The real constraint is your device's available memory, since the whole file is held in RAM while it is processed. Very large files are slower on phones than on a laptop.
No. There is no sign-up, no email, and no usage tracking tied to an identity. The tool works the first time you open it.