PPennary

Guide · Updated 23 July 2026 · Reading time 6 minutes

Merging, Splitting and Reordering PDF Pages

Most PDF work is not editing at all. It is assembly: gathering scattered files into one submission, pulling three pages out of a forty-page report, fixing the order the scanner produced, turning a sideways page the right way up. These operations are lossless — they rearrange pages without touching what is printed on them — which makes them the safest things you can do to a document.

Merging

Combining several PDFs into one is the most common request, usually because something on the other end demands a single file. Application bundles, tender submissions, expense claims, case files: all the same job.

Two rules save most of the trouble:

A merged PDF can mix page sizes and orientations freely — an A4 letter followed by a landscape drawing is valid and will display correctly. It may look inconsistent when printed, so if the bundle is going to paper, consider whether the odd sizes matter.

Where merging is submitted: many portals specify not just a single file but a required order, and reject bundles that deviate. Read the instruction sheet before assembling, not after being rejected.

Splitting and extracting

The reverse job: taking pages out. Usually because only part of a document is relevant, or because a file is too large to send whole.

Extracting is worth reaching for more often than people do. It is completely lossless — the extracted pages are byte-identical in appearance to the originals — which makes it strictly better than compression whenever it will get you under a size limit. If a portal wants proof of address and you have a twelve-page bank statement, send the one page that shows it.

Two habits worth forming:

Reordering and deleting

Scanned bundles arrive out of order constantly — a document feeder pulling two sheets at once, pages fed reversed, a stack scanned back to front. Reordering fixes it without rescanning.

Deleting handles the rest: blank versos, the separator sheets people put between documents, the accidental photograph of a desk. Removing them is lossless and makes the file smaller for free.

The one caution: deletion is applied when you export the file. Check the page count and skim the result before you send it. A deleted page is not recoverable from the exported document, only from the original you kept.

Rotation

Sideways and upside-down pages come from the scanner's feed direction, or from a phone held in the other orientation. Rotating fixes the display.

Worth understanding: rotation in a PDF is normally stored as an instruction attached to the page rather than as a re-drawn image. This matters in one specific way — a viewer that ignores the rotation flag will show the page as it was originally stored. This is rare in modern software, but if a recipient reports a page sideways that looks correct to you, this is why. Exporting the rotated file rather than sending the original resolves it.

What gets preserved, and what does not

Page-level operations preserve the page content exactly. Some document-level features are a different matter, and this catches people out:

FeatureAfter merge or split
Page content — text, images, layoutPreserved exactly
Text layer and searchabilityPreserved — a searchable PDF stays searchable
Page size and orientationPreserved per page; a merged file can mix them
Bookmarks and outlineCommonly lost or partially lost when merging
Internal links and cross-referencesMay break, since target page numbers shift
Form fieldsMay not survive; check any fillable form after merging
Digital signaturesInvalidated. A signature certifies a specific file — altering it necessarily breaks that
The signature point is the important one. If a document is digitally signed and the signature must remain valid, do not merge, split or reorder it. Send it as its own file alongside the bundle. This trips up people assembling official submissions more than any other issue on this page.

A reliable working order

  1. Assemble first, then process. Merge the bundle before compressing or running OCR, so those run once over the finished document rather than separately on each part.
  2. Rotate before assembling. Fixing orientation in the individual files is easier than hunting for page 23 of a merged bundle.
  3. Delete unwanted pages early. No point compressing or recognising pages you are going to discard.
  4. Check the page count against your checklist before exporting.
  5. Open the exported file and page through it. Not a skim of the first page — page through. Order errors are invisible until someone else finds them.

Common problems

SymptomCauseWhat to do
Pages in the wrong order after mergingFiles were added in a different order than intendedReorder pages in the merged file, or merge again deliberately
Merged file will not open on the recipient's deviceUsually size, or a very old viewerSplit into parts, or send a link
Bookmarks goneExpected behaviour when mergingRecreate if needed, or keep the original for reference
Signature now shows as invalidThe file was altered after signingUnavoidable. Send the signed document unmodified
Rotation looks right here, wrong for the recipientRotation flag not honoured by their viewerSend the exported file, not the original
Merged file much larger than expectedOne component was a large scanIdentify and compress that part before merging
Some pages searchable, some notThe bundle mixes born-digital and scanned sourcesRun OCR over the merged document

Privacy note

These operations run in your browser. Nothing is uploaded, which matters when the bundle being assembled contains identity documents, financial records or official correspondence — which, for this particular set of tasks, it very often does.

Open the tool →

Related guides