All PDF Tools
Navigation
Home
PDF Tools
🔒 Your files never leave your device

Merge Odd & Even PDF Pages

Combine separately scanned odd and even PDF pages into the correct page order entirely in your browser. Automatically corrects a reversed even-page scan.

Odd Pages File (1, 3, 5…)

Drop your ODD pages PDF

Click to browse or drag & drop

No signup 100% private

Even Pages File (2, 4, 6…)

Drop your EVEN pages PDF

Click to browse or drag & drop

No signup 100% private

SSL encrypted transfer to your own browser's memory — nothing is ever uploaded to a server.

Pair Merge Odd & Even PDF With These Tools

The Two-File Scanning Problem, Solved

If you've ever scanned a stack of double-sided paper on a single-sided (simplex) scanner, you already know the problem: you get two separate PDFs — one holding every odd page, one holding every even page — and neither is usable on its own. Merge odd and even PDF pages is the process of interleaving those two files back into one document in the correct reading order: 1, 2, 3, 4, and so on.

This tool does that entirely inside your browser. It helps office staff, teachers, law firms, students, librarians, and anyone else stuck with a two-file scan turn them into one clean, correctly ordered PDF in seconds — no signup, no software install, and no file ever leaves your device. It also automatically expects the most common scanner quirk: the even-page file usually comes out back-to-front, and the tool defaults to correcting that for you.

Quick Answer

Merge Odd & Even PDF Pages is a browser-based tool that combines two separately scanned PDFs — one with odd-numbered pages, one with even-numbered pages — into a single document with the correct page order. It automatically handles the common case where the even-page file was scanned in reverse.

TL;DR

  • What it does: interleaves an odd-pages PDF and an even-pages PDF into one correctly ordered document — page 1, 2, 3, 4… — optionally reversing the even file first.
  • How to use it: upload both files, leave (or toggle) "Even pages file is in reverse order," check the live preview, then click Merge.
  • Privacy: runs 100% in your browser using pdf-lib and PDF.js — neither file is ever uploaded to a server.
  • Cost & limits: completely free, no signup, no watermark, no daily limit.
  • Limitation: only page order changes — fonts, images, and page content are untouched, but bookmarks, annotations, and links from the source files are not currently carried into the merged output, and document metadata (title/author) is copied from the odd-pages file only.

Quick Answers

Fast Answers to Common Questions

Short, standalone answers — each one true on its own, without needing the rest of the page for context.

What is Merge Odd & Even PDF Pages?

A free browser tool that combines two separately scanned PDFs — one with odd pages, one with even pages — into a single document in correct reading order. It runs entirely locally and can automatically reverse a backwards even-page scan.

How do I combine odd and even scanned pages?

Upload the odd-pages PDF and the even-pages PDF into their upload slots, confirm whether the even file needs reversing, check the live preview, then click Merge. The tool downloads one correctly ordered PDF.

Why are my even pages reversed?

Flipping a paper stack to scan the back sides puts the last sheet on top, so it scans first. The resulting even-pages file reads last-page-to-first instead of first-to-last — a normal side effect of simplex scanning.

What is PDF interleaving?

Interleaving is alternating pages from two separate PDF sources into one merged sequence — one page from source A, one from source B, repeated — rather than appending one file after the other.

Can I merge scanned books?

Yes. Books scanned in separate odd/even or left/right-page batches merge the same way as any other duplex-style scan — upload both batches and let the tool interleave them into reading order.

Does this tool upload my files?

No. Both PDFs are read and merged entirely inside your browser using pdf-lib and PDF.js. Neither file is sent to a server at any point in the process.

Does merging affect PDF quality?

No. Pages are copied as-is with no re-encoding — fonts, images, vector graphics, and resolution are unchanged. Only the page order changes; bookmarks, annotations, and links are not currently carried over.

Can I merge large PDFs?

Yes, including scans hundreds of pages long. Very large files (roughly 750MB+) show a size warning since extremely large PDFs can strain browser memory, but typical large scans merge without issue.

Can I preserve OCR?

Yes. An existing OCR text layer is part of a page's content and is copied along with it during merging, so a searchable scan stays searchable in the merged output.

Is browser processing secure?

Yes. Since files never leave your device, there's no upload to intercept and no server-side copy to secure or later breach — the most common risks in cloud-based PDF tools simply don't apply.

Can I use this tool on mobile?

Yes. It works in modern mobile browsers on Android and iOS — tap either upload zone to open your device's file picker, since drag-and-drop isn't available on touchscreens.

Can I merge PDFs offline?

The page itself must load once over the internet, but the actual merge runs locally with no ongoing network requirement — a lost connection mid-merge won't interrupt the process.

How do duplex scanners work?

Duplex scanners have sensors on both sides of the paper path, capturing front and back in a single pass and producing one correctly ordered file — no odd/even merging needed.

What is simplex scanning?

Simplex scanning captures only one side of the paper per pass. A double-sided document needs two separate passes — one for fronts, one for backs — producing two files to reassemble.

Can I reverse even pages automatically?

The tool defaults its "Even pages file is in reverse order" toggle to on, since that's the outcome of the most common flip-the-stack scanning workflow — you can switch it off if not needed.

Why are page counts different?

A one-page difference is normal when a document has an odd total page count — the very last page has no corresponding back side. Larger gaps usually mean a missed or duplicated sheet.

What happens if pages are missing?

The tool merges whatever pages are present and appends any leftover pages from the longer file at the end — it can't detect a missing sheet, so always verify the physical sheet count first.

Does this work with password-protected PDFs?

It handles basic print-restricted PDFs, but files that require a password to open should be unlocked first with a dedicated unlock tool before merging, since the browser can't read encrypted content it can't decrypt.

Can I combine two scanned contracts?

Yes — if a double-sided contract was scanned into separate odd and even files, this tool reassembles them into one correctly ordered document, exactly as it does for any duplex-style scan.

Is this tool free?

Yes, completely free with no signup, no watermark on the output, and no daily limit on how many files you can merge.

Definition

What Is Merge Odd & Even PDF Pages?

Merge Odd & Even PDF Pages is a document-management operation that takes two PDFs produced by a one-sided scan pass — an odd-pages file and an even-pages file — and combines them into a single PDF with pages in natural reading order. The purpose is simple: a simplex (single-sided) scanner or an older automatic document feeder can only capture one side of a sheet per pass, so a two-sided document has to be scanned twice and reassembled afterward.

The typical workflow looks like this: scan the front of every sheet first (producing pages 1, 3, 5, 7…), flip the whole stack over, scan the backs (producing pages 2, 4, 6, 8… — often in reverse), then combine the two results. This tool exists because that reassembly step is tedious and error-prone to do by hand in a general-purpose PDF editor, especially past a few dozen pages.

Key takeaways:
  • It combines exactly two source files — an odd-pages PDF and an even-pages PDF — into one.
  • It exists to solve a hardware limitation (simplex scanning), not a software one.
  • The output page count equals the odd count plus the even count.
  • Only page order changes — page content is copied, not edited.

Background

Why Are Odd & Even Pages Scanned Separately?

Whether a scan produces one file or two comes down to the hardware doing the scanning:

  • Simplex (single-sided) scanners capture only the side facing the sensor — a double-sided document needs two passes, hence two files.
  • Duplex scanners capture front and back in one pass, producing one already-correct file. If you have one, this tool isn't needed.
  • Automatic Document Feeders (ADF) without duplex hardware are the most common source of this problem — "scan both sides" becomes "scan all fronts, flip the stack, scan all backs."
  • Manual (flatbed) scanning hits the same issue when someone scans all fronts first, then flips every sheet for the backs.
  • Book and bound-document scanning often produces separate odd/even batches too, from a left-page/right-page scanning rhythm.

Real example: a 10-page contract scanned on a basic office ADF produces contract-odd.pdf (pages 1, 3, 5, 7, 9) and contract-even.pdf (pages 10, 8, 6, 4, 2 — reversed, since the stack was physically flipped between passes).

Key Facts

  • Simplex scanners capture one side per pass; duplex scanners capture both sides in one pass.
  • ADF-based office scanners are the most common source of split odd/even files.
  • Flipping the stack between passes is what causes reversed even-page order.
  • Book scanning often produces the same odd/even split from a left/right-page rhythm.

Workflow

How This Tool Works

The tool takes your two files and zips them together, one page at a time, alternating sources:

Odd PDF1357
+
Even PDF2468
↓ interleave ↓
Merged PDF12345678

Odd page 1 → position 1, Even page 1 → position 2, Odd page 2 → position 3, and so on.

  1. Upload both files. The odd-pages PDF goes in the left slot, the even-pages PDF in the right slot. Each is read and a thumbnail preview and page-count/file-size summary appear instantly.
  2. Confirm the reverse-order toggle. On by default, since a flipped-stack scan is the common case — turn it off if your even file is already front-to-back.
  3. Check the live preview. Three thumbnail rows show the odd file, the even file (in the order it will actually be used), and the final merged result, so you can catch a mistake before downloading.
  4. Merge and download. The tool builds the combined PDF and offers it as a single download — nothing is uploaded at any point in this process.

Key Facts

  • The merge alternates pages: odd 1, even 1, odd 2, even 2, and so on.
  • Both files are read entirely in the browser before merging begins.
  • A live 3-grid preview shows the exact result before download.
  • The output downloads as a single PDF file.

The Most Common Fix

Reverse Even Pages Explained

When you scan the fronts of a stack, flip the whole stack over, and scan the backs, the very last back-side sheet is now on top of the stack — so it gets scanned first. The result is an even-pages file ordered from the last even page to the first:

As scanned8642
↓ Reverse Even Pages: ON ↓
Used order2468

The tool cannot see the physical scanning process, so it doesn't detect this from the file contents — instead it defaults the "Even pages file is in reverse order" toggle to on, since that's the outcome in the overwhelming majority of flip-the-stack scanning workflows. You should turn it off only when you know your scanner or scanning software already reorders the even-page output for you (some duplex-simulation software does this automatically before saving).

When to enable it: your even-pages file's last page is page 2 of the original document, not the second-to-last. When to disable it: your even file already reads 2, 4, 6, 8 from first page to last. The live preview shows you the actual result either way, so you never have to guess — just look at the "Even pages (source order)" thumbnail row before merging.

Key Facts

  • The "Reverse Even Pages" toggle defaults to on.
  • It corrects the last-scanned-first order caused by flipping a stack mid-scan.
  • The tool can't detect this from file contents — it defaults on because that's the most common case.
  • The live preview always shows the actual order that will be used, regardless of the toggle state.

Concept

The Merge Algorithm, Explained Simply

Conceptually, the algorithm is a "zip" operation — the same idea as interleaving two decks of cards by taking one card from each pile in turn:

Odd 1Even 1Odd 2Even 2

Take the next unused page from the odd file, place it, take the next page from the even file (reversed first, if that option is on), place it, and repeat until both files are exhausted. If one file has an extra page — common when a document has an odd total page count, since the last page has no back side — the leftover page is simply appended at the end.

AspectDetail
AdvantageHandles unequal file lengths gracefully; no page is ever dropped or duplicated.
AdvantageDeterministic — the same two inputs and toggle state always produce the same output order.
LimitationAssumes a strict alternating pattern; it cannot repair a scan where pages were skipped or duplicated mid-batch.
LimitationWorks on exactly two files at a time — batching more than one odd/even pair requires merging the outputs afterward.

Key Facts

  • The algorithm is a zip/interleave operation, not a sort or content analysis.
  • Extra pages from a longer file are appended at the end, never dropped.
  • The same two inputs and toggle state always produce the same output order.
  • It merges exactly two files at a time.

Performance Theory

Time Complexity

Computing the merged page order is O(n) — linear in total page count — since it's a single pass through both page lists, placing one page at a time with no comparisons that grow with document size. Doubling the page count roughly doubles the time; it never grows faster than that.

Assembling the output file scales the same way: each page is copied once from its source into the merged document, so total work is proportional to page count and, for image-heavy scans, total file size. The tool holds both source documents and the in-progress merged document in memory at once, so very large scans use proportionally more browser memory — why extremely large files get a size warning rather than silently struggling.

Key Facts

  • Computing the merge order is O(n) — linear in total page count.
  • Assembling the output file is also linear in page count and file size.
  • Memory use scales with the combined size of both source files.
  • Very large files are flagged with a warning rather than failing silently.

Architecture

Browser Processing, Explained

Every step — reading both PDFs, generating thumbnails, computing the merge order, and assembling the final file — happens inside your browser tab using two open-source libraries: pdf-lib (page-level document editing) and PDF.js (rendering page previews). Neither file is read by, sent to, or stored on any server; there's no upload step to skip.

This matters for three reasons: privacy (a scanned contract or medical record never leaves the device that scanned it), speed (no upload/download round-trip, so merging starts instantly), and security (nothing to intercept in transit, no server-side storage that could later be breached).

Key Facts

  • Processing uses two open-source libraries: pdf-lib and PDF.js.
  • No file is transmitted over a network during processing.
  • There is no server-side component in this workflow.
  • Closing the browser tab discards all in-memory data.

Quality

Does This Affect PDF Quality?

No re-encoding happens during a merge — each page is copied as-is from its source file. The table below states plainly what is and isn't carried over.

FeaturePreserved?
Fonts✓ Yes — copied unchanged
Images✓ Yes — no re-compression
Vector graphics✓ Yes
OCR text layer✓ Yes — travels with its page
Page dimensions✓ Yes — unchanged
Compression✓ Yes — unchanged
Document metadata (title, author)~ Partial — copied from the odd-pages file only
Bookmarks / outlines✗ Not currently carried over
Annotations & comments✗ Not currently carried over
Links✗ Not currently carried over

Key Facts

  • Fonts, images, vector graphics, and OCR text layers are copied unchanged.
  • Compression and page dimensions are not altered.
  • Bookmarks, annotations, and links are not currently carried over.
  • Document metadata is copied from the odd-pages file only.

Compatibility

Browser Compatibility

Built on standard, widely-supported web APIs (File, Canvas, Blob, ES modules) — no experimental features required.

BrowserSupport
Google Chrome✓ Full support
Microsoft Edge✓ Full support
Mozilla Firefox✓ Full support
Safari (macOS)✓ Full support
Brave✓ Full support (Chromium-based)
Opera✓ Full support (Chromium-based)
Mobile browsers (iOS Safari, Android Chrome)✓ Supported

Key Facts

  • The tool uses standard File, Canvas, and Blob web APIs.
  • Chrome, Edge, Firefox, and Safari are all fully supported.
  • Chromium-based browsers (Brave, Opera) inherit the same support as Chrome.
  • No browser extension or plugin is required.

On the Go

Mobile Compatibility

The tool works on Android phones and tablets, iPhone, and iPad through the device's default browser — tap either upload zone to open the native file picker (drag-and-drop isn't available on touch devices, but tap-to-browse covers the same job). The reverse-order toggle and Merge button are full-size touch targets, and the thumbnail previews scale to fit narrow screens.

Practical limitation: merging very large scanned books on an older or memory-constrained phone can be slower than on desktop, since mobile browsers typically have less available memory — for a 500+ page scan, a laptop or desktop will feel noticeably faster.

Key Facts

  • Mobile browsers use tap-to-browse instead of drag-and-drop.
  • Android and iOS are both supported through their default browsers.
  • Large scanned books may process more slowly on memory-constrained phones.

Real-World Scans

Common Scanning Workflows

📋

Office Documents

Memos and reports batch-scanned on a shared office ADF, split into odd/even by habit or scanner default.

📄

Contracts

Signed double-sided contracts scanned front-then-back for a client or records file.

📚

Books

Bound books photographed or scanned in separate left/right or odd/even passes.

🔬

Research Papers

Double-sided journal printouts or archival papers scanned in two passes for digitization.

🧾

Invoices

Two-sided invoices or receipts batch-scanned for accounting records.

🏥

Medical Records

Patient intake forms and charts scanned double-sided at a front desk.

🏛️

Government Forms

Double-sided applications and permits scanned for a records office or archive.

📐

Architectural Drawings

Double-sided plan sheets scanned in an office without a duplex-capable large-format scanner.

⚙️

Engineering Plans

Technical specification sheets printed and scanned on both sides for archival copies.

✏️

Student Notes

Double-sided lecture notes or worksheets scanned on a shared library or dorm scanner.

Don't Confuse These

Merge Odd & Even vs. Other PDF Tools

ToolWhat it doesUse it when…
Merge PDFCombines any number of whole files, in the order you arrange themFiles are already in correct order and just need combining
Merge Odd & Even PagesInterleaves exactly two files (odd + even) into one, alternating pagesYou have a two-file duplex scan to reassemble
Split PDFBreaks one file into multiple smaller filesYou need to separate pages out, the opposite of merging
Rearrange PagesPuts pages into any custom order you choose by handThe needed order isn't a simple odd/even interleave
Reverse Page OrderFlips the order of pages within a single fileOnly one file's order is backwards, not two files needing interleaving
Rotate PDFChanges page orientation (0°/90°/180°/270°)Pages face the wrong way — a different problem from page order

In Depth

Detailed Tool & Concept Comparisons

Six side-by-side breakdowns to help you pick the right tool or understand the right scanning concept.

Merge Odd & Even Pages vs. Merge PDF

PurposeBest Use CaseAdvantagesLimitationsTypical Users
Merge Odd & EvenInterleave two files into correct page orderDuplex-simulated scans (odd/even split)Auto-handles reversed even pages; live order previewOnly works with exactly two source filesAnyone with a two-file simplex scan
Merge PDFCombine any number of whole files in sequenceFiles already in correct orderHandles unlimited files; manual drag-to-reorderNo automatic interleaving of alternating pagesAnyone combining already-ordered documents

Merge Odd & Even Pages vs. Reverse PDF Page Order

PurposeBest Use CaseAdvantagesLimitationsTypical Users
Merge Odd & EvenCombine two files into one, alternating pagesTwo-file duplex-style scansSolves the two-file problem directlyNot useful for a single already-complete fileTwo-file scanning workflows
Reverse PDF Page OrderFlip page order within one existing fileA single file that reads back-to-frontWorks on one file; supports partial-range reversalDoesn't combine two separate filesAnyone with one backwards file, not two to merge

Merge Odd & Even Pages vs. Rearrange Pages

PurposeBest Use CaseAdvantagesLimitationsTypical Users
Merge Odd & EvenApply one specific, automatic interleave patternThe output order is a predictable alternationOne click; no manual drag-and-drop neededCan't produce a fully custom, non-alternating orderPredictable duplex-scan patterns
Rearrange PagesPut pages into any custom order by handAn irregular order that isn't a simple alternationTotal flexibility over final orderManual and slow for large page countsOne-off, non-standard reordering needs

Merge Odd & Even Pages vs. Split PDF

PurposeBest Use CaseAdvantagesLimitationsTypical Users
Merge Odd & EvenCombine two files into oneReassembling a split scanDirect fix for the two-file scanning problemDoesn't extract or remove pagesPost-scan reassembly
Split PDFBreak one file into multiple smaller filesExtracting a range of pages, or one page per fileFine-grained control over what gets extractedThe opposite operation — doesn't combine filesExtracting or distributing specific pages

Browser Processing vs. Cloud Processing

PurposeBest Use CaseAdvantagesLimitationsTypical Users
Browser ProcessingRun the entire operation on your own deviceSensitive documents; privacy-first workflowsNo upload, no server storage, no transit riskPerformance depends on the local device's memoryAnyone handling private or sensitive scans
Cloud ProcessingRun the operation on a remote serverVery large jobs needing server-grade hardwareNot limited by the local device's memoryRequires uploading the file; server must store and later delete itJobs too large for local device memory

Simplex vs. Duplex Scanning

PurposeBest Use CaseAdvantagesLimitationsTypical Users
Simplex ScanningCapture one side of the paper per passBasic or older single-sensor scannersWidely available, lower-cost hardwareNeeds two passes and manual reassembly for double-sided documentsHome and small-office scanners
Duplex ScanningCapture both sides of the paper in one passHigh-volume double-sided document scanningOne pass, one already-correct fileRequires dedicated duplex-capable hardwareOffices with duplex-capable scanners

Audiences

Who Should Use This Tool?

🎓 Students

Reassemble double-sided lecture notes scanned on shared library equipment.

🏫 Teachers

Combine two-sided worksheets or exams scanned in bulk for grading or archiving.

⚖️ Law Firms

Reassemble double-sided contracts and discovery documents into a correctly ordered case file.

📚 Libraries

Digitize bound volumes scanned in separate odd/even batches for public archives.

📖 Publishers

Reassemble manuscript proofs scanned on simplex equipment during production review.

🏛️ Government

Process double-sided public records and applications into unified case files.

🏢 Businesses

Reassemble two-sided invoices, HR paperwork, and internal forms scanned in batches.

🏥 Healthcare

Combine double-sided patient intake and consent forms scanned at check-in.

⚙️ Engineers

Reassemble double-sided spec sheets and technical drawings for project archives.

📐 Architects

Combine double-sided plan sets scanned without duplex-capable large-format equipment.

🔬 Researchers

Digitize double-sided source documents and archival papers for citation and analysis.

🏠 Home Users

Reassemble double-sided bills, tax documents, and personal paperwork from a home scanner.

Decision Trees

Which Setting — or Which Tool — Do You Need?

Scenario 1: Setting Up Your Merge

Do you have two separate PDFs — one odd-pages, one even-pages?
Is the even-pages file in reverse order (last page first)?
Yes, reversed
Enable "Reverse Even Pages"
Merge the two files
No, already forward
Leave the toggle off
Merge the two files

Scenario 2: Choosing the Right Tool

What's actually wrong with your PDF's pages?
Two files to combine
Merge Odd & Even Pages (this tool)
One file, backwards order
Pages face the wrong way

Do This

Best Practices

  • Verify page counts in the info panel before merging.
  • Check orientation on both files — sideways pages need Rotate PDF first.
  • Always preview the merged-result grid before downloading.
  • Keep your originals until you've confirmed the output is correct.
  • Use Reverse Even Pages for any flip-the-stack scan.
  • Turn it off if your scanning software already reorders the even file.
  • Use consistent scanner settings for both passes to avoid mismatched pages.
  • Name files clearly (doc-odd.pdf / doc-even.pdf) so slots never get mixed up.
  • Count physical sheets before scanning so you know the expected total.
  • Scan both passes in one sitting to reduce the odds of a missed sheet.
  • Run OCR after merging, not before, for one consistent text layer.
  • Remove blank separator pages the scanner may have inserted.
  • Expect a one-page difference when the document has an odd total page count.
  • Re-add metadata afterward if you need fields beyond title/author.
  • Test with a small file first before merging a very large scanned book.

Avoid This

Common Mistakes

  • Swapping the odd/even slots — usually from unclear file names.
  • Leaving Reverse Even off when the file actually was flip-scanned.
  • Turning Reverse Even on when the file was already forward-ordered.
  • Skipping the preview and downloading straight away.
  • Treating a one-page mismatch as an error — it's normal for odd page totals.
  • Mixing scanner resolutions between the odd and even passes.
  • Missing a sheet mid-scan, throwing off every page after it.
  • Scanning a sheet twice by accident.
  • Expecting bookmarks or comments to carry over — they currently don't.
  • Merging a password-protected file directly instead of unlocking it first.
  • Reaching for this tool when only one file needs reversing, not two interleaving.
  • Reaching for this tool when the real issue is orientation, not order.
  • Not checking that the final count equals odd-count plus even-count.
  • Deleting your originals before confirming the merged file opens correctly.
  • Merging a huge scanned book on a low-memory phone and expecting desktop speed.

Beyond the Basics

Expert Tips

More specific than the basics above — for recurring or high-volume scanning jobs.

  • Scan both passes at identical DPI and color-mode settings — mismatched resolution between odd and even pages is visually obvious in the merged result.
  • If your scanning software offers a "duplex simulation" mode, test whether it already reorders the even file — you may not need the Reverse toggle at all.
  • For documents you plan to OCR, scan at 300 DPI or higher so text recognition accuracy stays high after merging.
  • On an ADF, check whether the feeder reads the tray top-to-bottom or bottom-to-top — it changes which page ends up first in each file.
  • Adopt a strict naming convention (e.g. project-odd.pdf / project-even.pdf) if you do this regularly, to eliminate slot mix-ups across many jobs.
  • When digitizing a bound book, scan all recto (right-hand) pages in one clean pass and all verso (left-hand) pages in a second, rather than alternating mid-session.
  • Run a 4-page test scan first to confirm your scanner's flip-the-stack behavior before committing to a large batch.
  • Use the live preview's O1/E1/O2 thumbnail badges to trace exactly which source page landed in which merged position.
  • For forms with printed page numbers, cross-check the merged order against those printed numbers, not just the total page count.
  • Keep all sheets from one physical stack in a single scanning session — splitting a job across sessions raises the odds of a missed sheet.
  • Decide upfront whether OCR runs before or after merging; running it after avoids two separate OCR passes on the same content.
  • For a very large scanned book, merge odd/even chapter-by-chapter, then combine the chapters afterward with a general merge tool.
  • If two people split a scanning job, agree on identical scanner settings beforehand to avoid a resolution mismatch partway through.
  • Close unused browser tabs before merging an especially large or image-heavy scan to free up available memory.
  • Don't judge whether even pages are reversed by file size alone — always check the actual thumbnail preview.
  • If a page appears twice in the merged result, check both source files individually for a duplicate scan before re-merging.
  • Give the merged output a filename clearly distinct from both sources, so a later edit doesn't accidentally target the wrong file.
  • As a final sanity check, count physical sheets and confirm it matches the merged file's total page count.
  • If your even-pages file has extra blank separator sheets from the scanner, remove them before merging rather than after.
  • For recurring monthly or weekly scanning jobs, keep a written note of your scanner's specific odd/even behavior so you don't have to re-verify it every time.

Troubleshooting

Common Problems & How to Fix Them

Missing Pages

ProblemThe merged file has fewer pages than expected.
CauseA sheet was skipped during one of the two scanning passes.
SolutionCount physical sheets against the total, and re-scan the missing side if needed.

Incorrect Order

ProblemPages don't read in a sensible sequence.
CauseThe odd and even files were placed in the wrong upload slots.
SolutionRemove both files and re-upload, double-checking each file's actual content first.

Reversed Even Pages

ProblemEven pages appear in the wrong order in the result.
CauseThe Reverse Even Pages toggle doesn't match how the file was actually scanned.
SolutionFlip the toggle and re-check the live preview before merging again.

Blank Pages

ProblemThe merged file contains unexpected blank pages.
CauseThe scanner inserted separator sheets, or a physical page was genuinely blank.
SolutionRemove blank pages from a source file first, or clean up the merged result afterward with a dedicated blank-page remover.

Mixed Paper Sizes

ProblemSome pages look a different size than others.
CauseThe two scanning passes used different paper-size or scaling settings.
SolutionRe-scan using identical paper-size settings for both passes.

Memory Issues

ProblemThe browser feels sluggish or unresponsive while merging.
CauseA very large or image-heavy file is using most of the available browser memory.
SolutionClose unused tabs, use a desktop browser, or split the job into smaller batches.

Slow Rendering

ProblemThumbnails take a while to appear.
CauseA large page count means many thumbnails to render as you scroll.
SolutionThis is expected for very long documents — thumbnails render lazily, so scrolling slower helps.

Browser Limitations

ProblemThe tool doesn't load or behaves unexpectedly.
CauseAn outdated browser version may lack a required web API.
SolutionUpdate to a current version of Chrome, Edge, Firefox, or Safari.

Corrupted PDFs

ProblemA file won't load, showing an error message.
CauseThe file is damaged, incomplete, or not a valid PDF.
SolutionRe-export or re-scan the source file, then try uploading it again.

Trust

Security & Privacy

Both files stay entirely on your device. There is no upload step, so there is no server-side copy to secure, nothing to intercept in transit, and nothing tracked. Processing happens in the browser tab's own memory and is discarded the moment you close or refresh the page — nothing is written to disk unless you explicitly download the result.

Server-based PDF tools must encrypt files in transit, store them temporarily, and delete them afterward. Browser-only processing skips all three requirements, because the file never leaves the device in the first place.

Key Facts

  • No file upload occurs at any point in the workflow.
  • No analytics are tied to file contents.
  • Data exists only in browser memory and clears on tab close or refresh.
  • There is no server-side storage to delete, because none is ever created.

Speed & Scale

Performance

Page thumbnails render lazily — only the ones scrolled into view are drawn, so a 500-page scanned book doesn't stall the page on load. Merge time is proportional to page count and file size: a typical office document merges in well under a second, while a large image-heavy scanned book can take several seconds, mostly spent on final file assembly rather than computing page order.

For best results on large scans: use an up-to-date Chrome, Edge, or Firefox on desktop, and expect mobile devices to run noticeably slower on very large files.

Key Facts

  • Thumbnails render lazily, only as they scroll into view.
  • Merge time scales with page count and file size.
  • Desktop browsers generally outperform mobile browsers on very large files.

At a Glance

Quick Reference

📄 Supported File Types

  • PDF only (.pdf)
  • Both odd and even files must be valid PDFs
  • Scanned or digitally-generated PDFs both work

🌐 Browser Compatibility

  • Chrome, Edge, Firefox, Safari — full support
  • Brave, Opera (Chromium-based) — full support
  • Mobile Safari & Chrome — supported

🔒 Privacy Summary

  • No file upload, ever
  • No tracking tied to file contents
  • Nothing stored after you close the tab

📦 Recommended File Sizes

  • Comfortable up to a few hundred MB per file
  • 750MB+ triggers a size warning
  • Desktop handles large files better than mobile

⚙️ Processing Workflow

  • Upload odd file, upload even file
  • Confirm the reverse-order toggle
  • Preview, then merge and download

🗂️ Typical Scanning Scenarios

  • Flip-the-stack duplex simulation on an ADF
  • Bound book scanned in odd/even batches
  • Two people scanning halves of one job

Glossary

Key Terms Explained

PDF
Portable Document Format — a file format that preserves fixed page layout, fonts, and images consistently across devices and software, standardized as ISO 32000.
OCR
Optical Character Recognition — technology that detects text within a scanned image and adds it as a searchable, selectable text layer on the page.
Duplex scanning
Scanning that captures both sides of a sheet of paper in a single pass through the scanner, producing one correctly ordered file.
Simplex scanning
Scanning that captures only one side of a sheet per pass, requiring two separate passes to digitize a double-sided document.
ADF
Automatic Document Feeder — a scanner mechanism that feeds multiple sheets through the scan sensor automatically, without manual page-by-page placement.
Interleaving
Alternating pages from two separate sources into one combined sequence, such as odd page, even page, odd page, even page.
Page sequence
The order in which pages appear when a document is read from beginning to end.
Page order
Synonymous with page sequence — the specific arrangement of pages within a PDF's internal page tree.
Metadata
Document-level information such as title, author, and creation date, stored separately from page content in a PDF's Info dictionary.
PDF page tree
The internal structure defined by the PDF specification that lists a document's pages in the order they should be displayed.
Browser processing
Performing a computing task entirely within a web browser's own memory, without sending data to an external server.
Vector graphics
Images described mathematically as shapes and paths, which scale to any size without losing sharpness — common in diagrams and drawings.
Raster image
An image made of a fixed grid of pixels, such as a photograph or scanned page — the typical output of a scanner.
Annotation
A comment, highlight, note, or markup element attached to a specific location on a PDF page, separate from the underlying page content.
Bookmark
Also called an outline entry — a named link in a PDF's navigation panel that jumps to a specific page or section.
Hyperlink
A clickable link within a PDF, either pointing to another page in the same document or to an external web address.
Compression
Reducing file size by encoding data more efficiently, ideally without a visible loss of image or text quality.
Rendering
The process of converting a page's underlying data into a visible image, such as drawing a PDF page onto a canvas for preview.
Thumbnail
A small preview image representing a full-size page, used to quickly browse or verify a document's pages.
Page rotation
Changing a page's display orientation — typically 90°, 180°, or 270° — without altering the order pages appear in.
Page rearrangement
Changing the order pages appear in a document, whether by a specific pattern (like interleaving) or a fully custom sequence.
ISO 32000
The International Organization for Standardization's formal specification defining the PDF file format's structure and behavior.
PDF library
Software code that reads, creates, or edits PDF files programmatically — pdf-lib and PDF.js are examples used by this tool.
Local processing
Running a task using only the device's own resources, with no data sent to or processed by a remote server.
Document digitization
Converting a physical, paper-based document into a digital file, typically through scanning and optionally OCR.

FAQ

Frequently Asked Questions

38 questions, organized by topic — General, Scanning, Quality, Privacy, Compatibility, and Advanced.

General

Merge Odd & Even PDF Pages combines two separately scanned PDF files — one containing every odd-numbered page and one containing every even-numbered page — into a single PDF with pages in correct reading order (1, 2, 3, 4…). It's built specifically for the common scanning situation where a single-sided (simplex) scanner or an automatic document feeder without duplex hardware captures a double-sided document in two separate passes. The tool reads both files, lets you confirm whether the even-pages file needs reversing (a very common scanner quirk), shows a live preview of the exact merged result, and then produces one downloadable PDF. Everything happens inside your browser, so neither file is ever uploaded anywhere, and there's no signup or software to install first.
Anyone who has ended up with two PDF files from a double-sided scan and needs them combined into one correctly ordered document. In practice that includes office staff processing double-sided paperwork, students and teachers with two-sided worksheets or notes, law firms reassembling scanned contracts, libraries and archives digitizing bound books, healthcare offices scanning double-sided intake forms, government records offices, engineers and architects with two-sided technical drawings, and home users dealing with double-sided bills or personal documents. If you only have one file that needs its order flipped rather than two files that need combining, a plain page-reversal tool is the better fit, since this tool is specifically built around interleaving two separate documents.
Yes, completely free, with no hidden tier. There's no signup, no account creation, no watermark added to the merged output, and no daily limit on how many times you can use it. The tool doesn't have a paid plan or premium features gated behind a subscription — every capability described on this page, including the reverse-even-pages toggle, the live before/after preview, and unlimited file size up to the browser's practical memory limits, is available without payment of any kind, now or in the future.
No. You can open the page and start merging files immediately with no account, email address, or login of any kind required. Because the tool never uploads your files to a server, there's no user account system to manage in the first place — registration would serve no functional purpose here, since there's nothing being stored against a user profile. Each visit is a fresh, self-contained session: nothing about you or your previous merges is remembered between visits, which is a natural consequence of how the browser-only architecture works.

Scanning

This happens because of a hardware limitation, not a software choice. A simplex (single-sided) scanner, or an Automatic Document Feeder (ADF) without duplex capability, can only capture the side of the paper facing its sensor during a single pass. To digitize a double-sided document, you have to run the whole stack through once for the front sides, physically flip the stack over, then run it through again for the back sides. Each pass typically gets saved as its own PDF — one for all the odd pages, one for all the even pages — because the scanning software has no built-in way to weave the two passes together automatically into one final sequence. That reassembly step is exactly what this tool automates, replacing a manual, error-prone process with a one-click merge.
When you flip an entire stack of paper over to scan the back sides, the physical order of the stack flips too — the sheet that was on the bottom (the last page) ends up on top, and gets scanned first. So instead of producing an even-pages file ordered 2, 4, 6, 8, you get one ordered 8, 6, 4, 2 (last to first). This is normal, expected behavior for a flip-the-stack scanning workflow, not a malfunction or a mistake on your part. It's common enough that this tool's "Reverse Even Pages" toggle defaults to on, since that's the outcome in the large majority of real-world cases where people end up needing to merge two files like this.
Yes. Bound books and other bound documents are frequently scanned or photographed in separate odd/even or left-page/right-page batches, especially in library digitization and archival projects, since a bound spine makes it awkward to capture pages in strict numerical order during a single continuous pass. As long as you have one file containing the odd-numbered pages and one containing the even-numbered pages, the merge process works exactly the same way it does for a double-sided office document — upload both files into their slots, confirm the resulting page order in the live preview, adjust the reverse toggle if needed, and merge.
Yes, this is one of the most common real-world use cases for this tool. Automatic Document Feeders without duplex hardware are the typical source of the two-file odd/even problem in office and home scanning setups, since they can only read one side of each sheet per pass through the feeder mechanism. If your ADF-based scanning software saved the two passes as separate files, simply upload the odd-pages file and the even-pages file into their respective slots here, check whether the even file needs the reverse-order correction by reviewing the live preview, and merge them into one correctly sequenced document.
This tool is specifically built to combine two files into one — if you only have a single file whose page order is backwards (for example, an entire document that reads last-page-first with no second file involved), you don't need to merge anything at all, you need to reverse the order of the one file you already have. PDFcrest's separate Reverse PDF Page Order tool handles that specific case directly and is the more appropriate choice whenever there's no second file to interleave pages with, since this tool's whole workflow assumes two distinct source documents.

Quality

No. The merge operation copies each page from its source file into the new combined document without decompressing, re-encoding, or resampling any image data along the way. There is no quality-loss step anywhere in the process — a scanned page that looks a certain way in the odd-pages or even-pages source file will look identical in the merged output, at the exact same resolution and with the same compression it already had going in. The only thing that changes across the entire operation is which position each page occupies in the final page sequence; the pixels themselves are never touched.
Yes. Any embedded fonts used in either source PDF are copied over exactly as part of each page's own content, with no substitution, re-embedding, or subsetting changes made during the merge process. This matters most for PDFs that were digitally generated rather than purely scanned images and therefore contain real embedded text — the merged file will display and print that text using the exact same font data as the two originals, with no risk of a font being swapped for a similar-looking system default.
Yes. If either source PDF already has an OCR-generated text layer — the invisible, searchable text that sits behind a scanned page image — that layer is stored as part of the page's own content stream and is carried over intact when the page is copied into the merged document. You do not need to re-run OCR after merging if it was already applied to the source files beforehand; the searchable, copy-pasteable text will continue to work exactly as it did in the original file, on the same pages, without any extra steps.
This is one of the current limitations worth being aware of: link annotations and other page-level interactive elements are not explicitly carried over by this tool's merge process today. If either source file contains clickable links — whether pointing elsewhere in the document or out to a website — don't assume they will automatically survive in the merged output. Treat this as an area to verify manually after merging, especially for documents where working links genuinely matter, such as contracts with cross-references or reports with a table of contents that jumps to sections.
Document-level metadata such as the title and author field is copied from the odd-pages file only, and applied to the merged output as a whole. Other metadata fields from either source file — such as subject, keywords, or original creation date — are not currently copied over into the new document. If your workflow depends on complete and accurate document metadata for search, cataloging, or compliance reasons, it's best to add or correct it after merging using a dedicated PDF metadata editor rather than assuming everything transferred automatically.
No, not currently. Bookmarks, also called outline entries, are stored at the whole-document level rather than attached to individual pages, and the merge process builds a new document out of copied pages without also copying either source file's outline tree structure. If either of your original files had a bookmark structure you rely on for quick navigation, you will need to rebuild that structure in the merged file afterward using a PDF editor that supports outline or bookmark editing, since it won't appear automatically in the result.

Privacy

No. Both the odd-pages PDF and the even-pages PDF are read and processed entirely within your browser's own memory, using the pdf-lib and PDF.js JavaScript libraries running locally on your device. At no point in the upload, preview, merge, or download steps is either file transmitted to any server — there is no upload step to skip, because the tool's underlying architecture never establishes a network connection for your actual file data in the first place. The only network activity involved is loading the page and its JavaScript itself, before you've selected any files.
Yes, and in several concrete, verifiable ways it's safer than a typical server-based alternative. Because your files never leave your device, there's no file transmission in transit to intercept, no server-side copy of your document that could later be exposed in a data breach, and no third party or company employee who could ever gain access to your document's contents. The main practical trade-off is that processing speed depends on your own device's hardware rather than a remote data center's, which matters mostly for very large or image-heavy files on older hardware.
You need an internet connection to load the tool's page initially, since it's hosted on the web like any other website, but the actual merging process itself doesn't depend on an ongoing connection once that page has loaded. After the page and its JavaScript files have finished loading, uploading your two PDFs, reviewing the live preview, and merging them all happen entirely locally in your browser — losing your internet connection partway through a merge won't interrupt, corrupt, or otherwise affect the process in progress.
No. Nothing about your file's content is written to persistent storage anywhere, whether on a remote server — since none is ever contacted during the process — or, beyond ordinary temporary browser memory, on your own device. Once you close the browser tab or navigate to a different page, any in-memory data from that session is discarded automatically. The only file that persists anywhere afterward is the merged PDF you explicitly choose to download, which gets saved wherever your browser normally puts downloaded files.
No. There is no analytics, logging, or tracking mechanism tied to the content of the files you merge — the tool has no visibility into what's actually inside your PDFs beyond what's needed to render thumbnail previews and compute the page order, and that work happens entirely inside your own browser. Since the files are never transmitted anywhere over the network, there is no remote system, database, or third party that could inspect, log, or analyze their contents even if it were designed to try.

Compatibility

Yes, Google Chrome is fully supported, including every core feature: drag-and-drop upload, live thumbnail previews for both source files and the merged result, the reverse-order toggle, and the final merge-and-download step. The tool relies only on standard, long-established web APIs — File, Canvas, Blob, and ES modules — that have been stable in Chrome for years, so any reasonably current version of Chrome on Windows, macOS, Linux, or Chrome OS works without any reduced functionality or special configuration needed. There's nothing to enable in Chrome's settings beforehand; it works out of the box.
Yes, Mozilla Firefox is fully supported with the exact same feature set available in Chrome. Firefox implements the same standard web APIs — File, Canvas, Blob, and ES modules — that this tool depends on internally, so uploading both PDFs, previewing the merge order live, and downloading the final combined file all work identically well in Firefox as in any other supported browser, with no missing capabilities or workarounds required. Firefox's stricter default privacy settings don't interfere with this tool, since it never makes any outbound network requests with your file data in the first place.
Yes, Safari on macOS is fully supported. As with the other supported browsers, all processing happens locally using standard web technologies that Safari has implemented reliably for years, so there's no reduced functionality, missing preview capability, or slower merge behavior compared to using Chrome, Firefox, or Edge on the same task. Safari on iOS (for iPhone and iPad) is also supported, using tap-to-browse in place of drag-and-drop, with the same underlying WebKit rendering engine handling thumbnail generation on both desktop and mobile versions of Safari.
Yes, Microsoft Edge is fully supported. Modern Edge is built on the same Chromium engine that powers Google Chrome, so it supports exactly the same underlying web APIs this tool relies on, with essentially identical behavior, rendering, and performance characteristics to Chrome for this specific merging workflow. Windows users who default to Edge don't need to switch browsers or install anything extra to get full functionality out of this tool — every feature described on this page works identically to how it works in Chrome.
Yes, the tool works on Android and iPhone through their respective default mobile browsers — Chrome on Android and Safari on iOS. The main interaction difference on a phone is that drag-and-drop isn't available on a touchscreen, so you tap the upload zone to open your device's native file picker instead of dragging a file in. The reverse-order toggle and the Merge button are both sized as full-width touch targets specifically so they're comfortable to use on a small screen.
Yes, both Android tablets and iPad are fully supported through their respective default browsers, using the same tap-to-browse upload interaction described for phones. The larger screen size on a tablet generally makes it noticeably easier to review the three-grid thumbnail previews and visually confirm the merge order before downloading, compared to doing the same review on a smaller phone screen where thumbnails are more cramped. Tablets also tend to have more available memory than phones, which helps with larger scanned documents.
No. There is no browser extension, plugin, desktop application, or mobile app to install at any point — the tool runs entirely on standard JavaScript technology that's already built into every modern browser. You simply open the page in any supported browser, upload your two files, and start using every feature immediately, with nothing to download, install, or configure beforehand, and nothing left behind afterward beyond the merged PDF you chose to download yourself. There's also no account setup or license key required to unlock any feature described on this page.
Any current desktop browser — Chrome, Edge, or Firefox — will generally outperform a mobile browser on large or image-heavy scanned documents, simply because desktop devices typically have significantly more available memory to work with. Among the desktop browsers themselves, differences in raw speed are usually minor for this specific tool's workload; closing other unused browser tabs to free up available memory tends to have a bigger practical impact on merge speed than which specific desktop browser you happen to choose.

Advanced

Yes, including scanned documents that run into the hundreds of pages per file. There's no artificial page-count cap built into the tool itself. Very large files — roughly 750MB or more — trigger a size warning because extremely large PDFs can strain a browser tab's available memory and potentially slow the whole browser down, but typical large scans well under that threshold merge without any special handling, extra steps, or noticeable slowdown needed on a reasonably modern desktop or laptop.
No fixed page-count limit is enforced by the tool. Practical limits come from your browser's available memory rather than any artificial cap written into the code itself, so very long documents — 500 or more pages per file — are genuinely supported, though they will naturally take longer to process than a short document and are generally better handled on a desktop or laptop browser than on a memory-constrained mobile device with less RAM available to the browser tab. If you regularly work with extremely long documents, a desktop browser is the more reliable choice.
The tool has no way to detect that a physical page was accidentally skipped during scanning — it simply merges whatever pages already exist in the two files you provide it. If your merged result seems shorter than expected, count the physical sheets you originally scanned against the merged file's total page count, and re-scan any genuinely missing side if there turns out to be a real gap. Note that a one-page difference between the odd and even counts is normal and expected whenever a document has an odd total number of pages.
Blank pages that come from your source files — whether they're genuinely blank original pages or separator sheets automatically inserted by your scanner between batches — are merged along with everything else, since the tool doesn't attempt to detect or strip out blank content automatically during the process. If you want them removed from the final result, either delete them from a source file before merging, or clean up the merged output afterward using a dedicated blank-page-removal tool built for exactly that purpose.
The tool doesn't resize, scale, or normalize page dimensions in any way — each page keeps its original size exactly as it existed in its source file. If your odd and even scanning passes were done with different paper-size or scaling settings, the merged document will genuinely contain pages of different physical sizes side by side. This is fundamentally a scanning-setup issue best fixed by re-scanning with consistent settings across both passes, rather than something the merge step itself is designed to correct after the fact.
Similarly, page orientation — portrait versus landscape, or any rotation flag already applied to a page — is preserved exactly as it exists in each source file and isn't adjusted or normalized during merging in any way. If some pages face the wrong way relative to others, that's an orientation problem that's entirely independent of the page-order problem this tool solves, and it's best resolved separately using a dedicated page-rotation tool, either before or after running the odd/even merge itself.
Yes — a page's existing rotation setting doesn't prevent it from being merged in any way; it will simply carry that existing rotation value into the merged document completely unchanged, exactly as it appeared in the source file. If pages come out sideways or upside down in the result, that's a separate orientation issue from the page-order problem this tool specifically solves, and it can be corrected using a rotation tool as part of the same overall workflow, applied either before or after merging.
Yes. Landscape-oriented pages merge exactly the same way portrait-oriented pages do — the tool doesn't require a specific page orientation and doesn't alter page dimensions or orientation in any way during the merge process itself. Engineering drawings, architectural plans, spreadsheets, and other landscape-format double-sided scans all work through the exact same odd/even upload-and-merge workflow as any standard portrait document, with identical live preview and toggle behavior throughout the entire process from upload to download, regardless of how the individual pages happen to be oriented.
Partially. The tool can open PDFs that only have basic print-restriction permissions set, but a file that requires a password just to open at all cannot be read by the browser in that state, since its content is genuinely encrypted and there's no password-entry prompt built into this particular workflow. If either your odd-pages file or your even-pages file requires a password to open, unlock it first using a dedicated PDF unlock tool, then upload and merge the two now-unlocked versions normally.
If a PDF is damaged, incomplete, or simply isn't a valid PDF file at all, the tool will show a clear, friendly error message rather than attempting to merge broken data or exposing a raw, confusing technical error message to you. The practical fix in that situation is to go back to the source — re-export the file from whatever software originally created it, or re-scan the physical pages again — and then try uploading the corrected, valid file a second time.

Summary Blocks

AI-Ready Summary

Eight standalone summaries covering the essentials of this tool, each accurate without needing the rest of the page for context.

Definition

Merge Odd & Even PDF Pages is a free, browser-based tool that combines two separately scanned PDFs — one containing odd-numbered pages, one containing even-numbered pages — into a single document in correct reading order, with an option to automatically reverse a backwards even-page scan.

Benefits

It eliminates manual page-by-page reassembly of two-file duplex scans, runs without uploading files anywhere, preserves fonts/images/OCR exactly, shows a live before/after preview, and costs nothing — no signup, watermark, or daily limit.

Workflow

Upload the odd-pages PDF and the even-pages PDF into their respective slots, confirm or adjust the reverse-order toggle, review the three-grid live preview showing the exact final order, then click Merge to download one combined PDF.

Privacy

Both files are processed entirely inside the browser using pdf-lib and PDF.js. Neither file is ever uploaded, transmitted, or stored on a server — there is no network destination for the files at any point.

Browser Processing

All computation — reading both files, generating thumbnails, computing the merge order, and assembling the output — happens on the user's own device. This removes upload time, server storage risk, and any need for an internet connection mid-process.

OCR Preservation

An existing OCR text layer is part of a page's content stream, so it's copied along with the page during merging. A searchable scan going in remains a searchable scan coming out, with no re-processing needed.

Best Practices

Verify page counts before merging, always check the live preview, use identical scanner settings for both passes, keep original files until the result is confirmed correct, and enable Reverse Even Pages for typical flip-the-stack scans.

Common Mistakes

The most frequent errors are swapping the odd/even upload slots, leaving the reverse toggle in the wrong state for the actual scan, skipping the preview before downloading, and expecting bookmarks or annotations to carry over automatically — they currently don't.

Related Tools

Other PDFcrest Tools That Pair Well

Once your odd and even pages are merged, a few other free tools often come next. Combined more than two batches? Merge PDF handles that. Only one file's order is backwards instead of two files needing interleaving? Use Reverse PDF Page Order instead. Make the result searchable with OCR PDF, strip leftover blanks with Blank Page Remover, and catch accidental duplicates with Duplicate Page Remover. For orientation instead of order, use Rotate PDF or, for tilted scans, PDF Deskew; for noisy scans, Scan Quality Enhancer. Trim the result with Delete PDF Pages or Split PDF, shrink it with Compress PDF, add a proper title and author with PDF Metadata Editor, diagnose size with PDF Size Analyzer, and manage passwords with Protect PDF or Unlock PDF.

Summary

Final Summary

Merge Odd & Even PDF Pages solves one specific problem: a simplex scanner or ADF splitting a double-sided document into two files that need to become one. It interleaves an odd-pages PDF and an even-pages PDF into correct reading order, defaults to expecting the common reversed-even-page pattern, and shows a live preview before you download.

Everything runs in your browser — no upload, no account, no watermark, no daily limit. Fonts, images, and page content are preserved exactly; only order changes, and bookmarks/annotations/links are honestly not yet carried over. It's built for office staff, students, teachers, law firms, libraries, publishers, government, healthcare, engineering teams, and home users alike — anyone whose two-file scan needs to become one correctly ordered document.