Merging PDFs from different sources is straightforward until the files share identically named bookmarks, links, or form fields that point to different destinations. When two PDFs each contain a bookmark labeled "Chapter 1" or a named destination called "TOC", the merge operation must decide which one wins. The PDF specification offers no default resolution rule for collisions, so the behavior depends entirely on the merge tool internal logic, and the results range from silently overwritten links to completely non-functional navigation.
Named destinations are the internal address labels that PDF bookmarks, hyperlinks, and cross-references use to jump to a specific page and view. Unlike page numbers, which change when pages are inserted or removed, named destinations remain anchored to their target content regardless of where it ends up in the merged document. This is what makes them valuable, and it is also what makes them fragile during a merge. Two documents created by the same authoring tool often use the same auto-generated destination names, and when those names collide, only one destination survives. Understanding how destinations are resolved is the first step toward producing merged documents with reliable navigation.
What Are Named Destinations and Why Do They Collide During Merging?
A named destination is a PDF object that maps a text string, like "Section2" or "fig_4", to a specific page, a zoom level, and a position on that page. Bookmarks use these destinations to know where to jump. Internal hyperlinks use them to cross-reference sections within the document. When you Merge PDF files, the merge tool assembles all the pages from all the sources into a single page sequence, and it must also merge the destination name spaces. If two source documents both define a destination called "Intro", the merge tool faces an unresolvable conflict: two different pages cannot both be the target of the same name.
According to ISO 32000, the PDF specification, named destinations within a single PDF must have unique names. The specification does not define how merging tools should resolve collisions, leaving the behavior implementation-defined. A 2024 technical report by the PDF Association documented five different collision-resolution strategies used by commercial and open-source merge tools, and no two tools handled all collision scenarios identically (PDF Association, "Interoperability Challenges in PDF Merging", 2024). This means the same two source files merged in two different tools can produce documents with completely different navigation behavior, a fact that surprises many users who assume merging is a deterministic operation.
The collision problem extends beyond bookmarks. PDF files can contain named destinations that are referenced from outside the document, for example from a web page that links to a specific section. If a merge operation silently overwrites or drops a named destination, external links to that destination break. In regulated industries where documents must maintain consistent references across versions, this kind of silent breakage can have compliance implications.
How Different Merge Tools Handle Destination Name Conflicts
Some tools apply a last-write-wins policy, where each subsequent file destinations overwrite any identically named destinations from earlier files in the merge order. This produces a merged document where bookmarks from the first file may silently point to pages in the last file, a particularly confusing outcome because the bookmark text says one thing but the destination goes somewhere else entirely. Other tools apply a first-write-wins policy, preserving the destinations from the first file and discarding collisions from all subsequent files.
A third approach, used by more sophisticated merge engines, is to prefix each source document destination names with a unique identifier derived from the file name or a user-supplied label. This guarantees uniqueness in the merged output but also means that any cross-references between documents that relied on knowing the destination name will break unless they are updated to use the prefixed names. Some enterprise document management systems use this approach and then run a post-merge script to update all internal references with the new prefixed names.
Yet another approach, supported by a small number of professional tools, is to detect collisions during the merge and prompt the user to resolve each one manually. This gives the user full control but becomes impractical when merging documents with hundreds of named destinations. A single technical manual can easily contain several thousand auto-generated destination names, and manually resolving each collision is not realistic. For large documents, automated renaming with a predictable prefix scheme is the only practical solution.
How to Prevent Collisions Before You Merge
The most reliable way to avoid destination collisions is to rename them before merging. If each source document destinations use a unique prefix or naming convention, no two destinations will share a name even when the documents are combined. Some PDF editors allow batch-renaming of bookmarks and their associated destinations, which you should do systematically before merging. Assign each source document a short prefix, such as "r1_" for the first report and "r2_" for the second, and rename every bookmark and named destination in each document to include that prefix.
When generating the PDFs from an authoring tool such as Microsoft Word, Adobe InDesign, or a LaTeX processor, configure the tool PDF export settings to use descriptive, unique bookmark names rather than auto-generated ones. In Word, the heading text becomes the bookmark name by default, which is usually sufficiently unique across documents. In LaTeX, the hyperref package allows you to set custom PDF Bookmarks names through the texorpdfstring command, giving you full control over what appears in the merged navigation tree.
For documents generated programmatically, such as PDF reports produced by a server-side library, include a unique document identifier in every destination name at generation time. A destination named "sales_fig_2025Q3" is far less likely to collide than a destination named "figure1". The small effort of using descriptive names saves substantial debugging effort after the merge.
Fixing a Merge Where Links Already Point to Wrong Pages
If you have already merged PDFs and discovered that bookmarks or PDF Links point to the wrong pages, the first step is to diagnose the scope of the problem. Open the merged file and use the bookmark panel to test every top-level bookmark. Note which ones jump to incorrect locations. The pattern of failures usually reveals how the merge tool handled collisions. If all bookmarks from the first file work correctly and all bookmarks from subsequent files are broken, the tool used a first-write-wins policy and the subsequent files had destination collisions with the first file.
If your tool supports it, use the "replace destination" or "set destination" function to reassign each broken bookmark to its correct page and view. This is a manual process that involves opening each bookmark properties dialog, navigating to the intended target page, and setting the current view as the new destination. For documents with a small number of broken links, this is the fastest fix. For documents with hundreds of broken links, you may need to go back to the pre-merge source files, rename the destinations with unique prefixes, and redo the merge.
A useful diagnostic technique is to export the bookmark list as a text file before and after the merge. Comparing the two exports reveals exactly which bookmarks were dropped, renamed, or redirected. This gives you a precise fix list and prevents the situation where a broken bookmark goes unnoticed until a reader reports it weeks or months later.
Rebuilding the Bookmark Tree After a Problematic Merge
When the bookmark tree of a merged document is too damaged to repair link by link, rebuilding it from scratch is the most efficient path. Many PDF editors allow you to create bookmarks by selecting text on a page and designating it as a bookmark target. Work through the merged document sequentially, creating new bookmarks for each section and subsection. For very long documents, check whether your editor supports auto-generating bookmarks from text patterns or heading styles. Some tools can scan a PDF for text formatted in a specific font and size and create bookmarks from each instance, which can rebuild a table of contents structure in minutes rather than hours.
WukongPDF handles destination conflicts during merging by automatically prefixing each source document internal names with a unique identifier, so navigation from each original file stays intact regardless of how many documents you combine. The merged output maintains a clean bookmark hierarchy that reflects the structure of each source document, with no silently overwritten links.
Testing Navigation After Any Merge Operation
After merging, test every top-level bookmark and a random sample of second-level bookmarks to verify they navigate to the correct pages. Check any cross-reference links within the document, such as "see page 12" or "refer to Appendix B," to confirm they still point to the correct locations after the page renumbering caused by the merge. If the merged document will be distributed externally, this testing step is not optional. A quick navigation test after merging catches errors before they reach the reader and ensures the document internal links remain reliable over the lifetime of the file. Spending two minutes testing after every merge saves hours of confusion later.