Duplicate pages after a PDF merge: find and fix the cause

1. Find out whether a whole document or just one page repeats

Keep the original files and the first merged download until you have a checked replacement. Open the merged PDF and note the positions of the repeated-looking pages, counting from the beginning of the file. Compare their content with the sources; filenames and printed page numbers alone are not enough.

If an entire attachment repeats in the same order, look for that attachment twice in the input list. For example, adding a two-page reference letter as both reference.pdf and reference-copy.pdf can produce four pages in Simple merge. A duplicate warning does not reduce the result to two pages.

If only one page repeats, inspect the boundary between source files and the pages inside each source. A bundle containing pages A and B followed by another containing B and C produces A, B, B, C. Those are different files, even though one page overlaps. These lettered pages are an illustrative example, not a detection feature.

Before removing anything, compare names, dates, reference numbers, signatures, and small annotations on both versions. Two pages with the same layout may contain different information, and a recipient may intentionally require the same supporting page in more than one section.

2. Read the duplicate warning, but do not treat silence as an all-clear

After running Merge PDF, expand “All checks” below the result. Matching-file notices appear there in both Simple merge and Application packet. In Simple merge they use filenames without the extension; in Application packet they use the document names assigned to the slots. Match the notice to the actual inputs before changing them.

The check calculates a SHA-256 hash from the complete bytes of each input file. When two hashes match, it reports a duplicate, but still includes both inputs in the output. The notice is not itself a failed submission requirement. A green “Your PDF is ready to review” or “Size limit met” heading therefore does not mean the document is free of repeated pages.

Changing only a filename does not change the bytes being checked. Microsoft’s file-hash documentation explains this distinction between file content and filenames. In contrast, re-exporting a PDF or changing its internal metadata can produce different bytes while leaving the visible pages unchanged, so matching-looking copies may produce no warning.

This is not page-by-page duplicate detection. It does not identify a repeated page inside one input, overlapping pages in two different bundles, or similar-looking rescans. No warning means no matching whole-file hash was reported; it is not proof that every page is unique.

There is also a separate “already selected” message while adding files in Simple merge. That selection check uses filename, size, and last-modified time, not a page comparison. Do not confuse it with the whole-file warning after processing or rely on either check instead of reviewing the pages.

• Open Merge PDF to review the inputs and checks
• Microsoft: why a file hash follows content, not its filename

3. Correct an extra input before merging again

In Simple merge, use the × control titled “Remove file” beside the unwanted input. Check the remaining filenames and use the up/down arrows if the order needs correcting. Keep the intended original, not merely whichever copy appears first.

Simple merge needs at least two PDFs. If removing the extra attachment leaves just one correct PDF and you need no other changes, use that original file instead of adding another copy to make the merge button work.

In Application packet, use “Replace file” when the wrong attachment occupies a genuinely required slot. If the entire slot was added by mistake, use its “Remove document slot” control. The other × control only clears the attached file and leaves the slot in place.

Clearing a slot marked “Required” prevents the packet from being created until it has a file or is made optional. Do not uncheck Required merely to hide a missing document that the recipient actually needs. An optional slot with no file is skipped; an optional slot that still has a file is included.

Changing an input clears the old result. Run “Merge PDFs” or “Create packet” again and download the new output. The previous download on your device is not updated when you fix the input list.

4. If only part of a file repeats, fix that source copy

Removing a whole attachment is the wrong fix when it also contains pages you need. Identify the exact unwanted page in the source, save a corrected copy, and use that copy in the next merge. Keep the untouched source separately.

For the A, B plus B, C example, suppose the recipient needs A, B, C only once. Keep the first source unchanged. In a copy of the second source, remove its first page B and retain C. Then merge the first source with that corrected copy. You should get three pages, in the order A, B, C, with no generated contents page enabled.

In Organize PDF, choose the source PDF and check its page thumbnails. Use the × control titled “Remove page” on the confirmed unwanted page. The kept-page count changes, and “Undo page edit” can restore a mistaken removal before export. Run “Organize PDF,” download the corrected file, and reopen it to confirm that the right page was removed.

Use the source file’s page positions, not the positions from the merged packet: a page at position 4 in the packet might be position 1 in the attachment. If two pages are hard to distinguish at thumbnail size, inspect them at a readable zoom in your PDF viewer before deleting either.

If the only file you have is the merged PDF, Organize PDF can remove a confirmed unwanted page from a copy of that file. However, any existing printed contents references and page-number stamps will not be recalculated by that removal. For a packet you can rebuild, correcting the sources first is the cleaner route.

• Remove a confirmed unwanted page with Organize PDF
• Need only an excerpt? Choose extract or split deliberately

5. Rebuild contents and numbering from the corrected inputs

In Application packet, open “Advanced settings” and review “Contents page,” “Bookmarks,” and “Page numbers” before creating the replacement. Contents and bookmarks are enabled by default; page numbers are not. Rebuilding from the corrected inputs calculates new section starts and, if selected, new page-number stamps.

Include generated contents pages when checking the expected total. For example, a two-page source followed by a one-page source makes three content pages, or four pages with one generated contents page. In that four-page packet, the two sections start at file positions 2 and 4. Check those destinations rather than assuming each section starts where it did before the correction.

Do not add the old merged packet alongside its original attachments as a shortcut: that includes the attachment pages again. Use the corrected source set, and avoid feeding an already numbered packet back through numbering unless you intend to add another set of stamps.

6. Check the exact replacement file before sharing

Reopen the newly downloaded PDF, not the earlier attempt. Check every page in order, particularly where one source ends and the next begins. Confirm that the intended repeat is gone, every required page remains, and the total matches the corrected sources plus any generated contents pages.

If you included a contents page or bookmarks, check their labels and section starts. If you added visible page numbers, check the sequence and make sure the stamps do not cover existing content. A lower page count alone does not prove the right pages were removed.

Test any form fields, links, or other features that matter in the new copy. Packet assembly copies pages; it does not guarantee preservation of original form behavior, digital signatures, or source bookmarks. Keep signed originals, and confirm the recipient accepts a modified or combined copy when those features matter.

Give the checked replacement a clear filename and share that file. A duplicate-free-looking packet can still miss a recipient requirement, so finish with the recipient’s document checklist rather than the success message alone.