🗂️ Organize PDF

Drag pages to reorder them, rotate or delete individual pages, then download your reorganized PDF. Everything happens in your browser — no uploads, no watermark, no page limit.

🗂️

Drop a PDF file here or click to browse

How to Organize a PDF

Drop your PDF above (or click to browse). Page thumbnails appear instantly.
Reorder: drag any page and drop it onto the position you want.
Rotate: click the ↻ button on a page to turn it 90° clockwise.
Delete: click the ✕ button to remove a page.
Click Download Organized PDF to save the result.

Why use Organize PDF?

Private by design — your file never leaves your device. No server, no upload, no waiting.
No limits — no watermark, no page cap, no sign-up.
All-in-one — reorder, rotate, and delete in a single pass instead of chaining three separate tools.

What actually happens to your PDF

The tool does not edit your file in place. It creates a new, empty PDF and copies the pages you kept into it, in the order you arranged them. That single design decision explains everything below — including what survives the trip and what does not.

Two libraries do the work, both running locally: pdf.js renders each page to a 150-pixel-wide thumbnail so you can see what you are dragging, and pdf-lib rebuilds the document when you export.

What is preserved, and what is lost

Because the output is a freshly built document, anything stored on a page travels with that page, while anything stored once at the document level does not get carried across.

Preserved — page content. Text, vector graphics, embedded fonts and images come across exactly as they were. Nothing is re-rendered or re-compressed, so there is no quality loss.
Preserved — links. Link annotations are attached to their page, so a clickable URL on page 7 still works after page 7 becomes page 2.
Lost — bookmarks. The outline tree lives on the document catalogue and is not copied. A PDF with a chapter sidebar comes out without one. This is the single most common surprise, so check before you organise a long reference document.
Lost — form fields. Interactive fields are registered in a document-level form dictionary. After a rebuild the field definitions and any values typed into them are gone, leaving only the page's static appearance. Use a dedicated form tool if you need to keep fields intact.
Lost — document metadata. Title, author, subject and keywords are not carried over, and the producer is rewritten to pdf-lib. Page content is untouched; only the document properties panel changes.

Rotation is metadata, not pixels

Clicking ↻ does not redraw the page. It changes the page's rotation value, which every PDF viewer reads when deciding which way up to display it. The page content is byte-identical either way, which is why rotating is instant even on a scanned 300-page document and why it never degrades quality.

One consequence worth knowing: rotation adds to whatever the page already had. Scanned documents frequently arrive with pages already recorded at 90°. Clicking ↻ once on such a page produces 180°, not 90° — so a sideways page may need one click, and an upside-down one may need three. Judge it by the thumbnail rather than counting clicks.

Why the file often gets smaller

A PDF accumulates objects that nothing points at any more — revision history from earlier edits, orphaned resources, superseded page trees. Rebuilding copies only what the surviving pages actually reference, so the discarded material never reaches the output. Deleting pages compounds this. The saving depends entirely on how much dead weight the original carried; a clean single-pass export may barely shrink at all, and this is not a substitute for a real compressor.

Frequently Asked Questions

No. The tool uses pdf.js to render thumbnails and pdf-lib to rebuild the file, all inside your browser. Your document never leaves your device.

Yes. Reorder by dragging, rotate with the ↻ button, and delete with the ✕ button — then export once. No need to run separate Rotate or Split tools.

No. Deleting removes only that page; the rest keep their content and any rotations you applied. Page numbers in the grid simply renumber to reflect the new order.

There's a generous 100 MB guard to keep the browser responsive. Because processing is local, very large files depend on your device's memory.

No. Bookmarks (the chapter outline sidebar) are stored once at the document level rather than on individual pages, and the export builds a brand-new document from the pages you kept. The outline is not carried across. Page content, images and links are unaffected — but if you're organising a long reference document whose sidebar matters, expect to rebuild it afterwards.

They stop being fields. Interactive forms are registered in a document-level dictionary that isn't copied during the rebuild, so both the field definitions and anything typed into them are lost. The page still looks the same — you keep the printed boxes and labels — but it's no longer fillable. If you need to preserve a form, don't run it through this tool.

Because rotation is cumulative. Scanners often record a page as already rotated 90°, and the ↻ button adds another 90° on top, giving 180°. The thumbnail always shows the true result, so rotate until it looks right rather than counting clicks. Rotation only changes a stored angle — the page content is never redrawn, so there's no quality loss however many times you click.

No. Document properties — title, author, subject, keywords — belong to the document rather than to any page, so the rebuilt file starts with empty metadata and records pdf-lib as its producer. Nothing inside the pages changes; only what you'd see in a viewer's document-properties panel.

The rebuild copies only what the surviving pages actually reference, so objects left behind by earlier edits — orphaned resources, superseded revisions — never make it into the output. Deleting pages removes more still. How much you save depends entirely on how much dead weight the original was carrying, and a clean file may not shrink at all. It isn't a replacement for a proper compressor.