Why Your Bookmarks Disappeared After Merging PDFs
This is not a bug in your tool — it is a consequence of how bookmarks work inside a PDF. Here is the explanation and the native fix using our platform.
The Problem: Bookmarks Are Page Addresses, and Merging Shifts All the Addresses
Short answer: Bookmarks store page numbers, not attached labels. When you merge documents, the page numbers change, but the bookmarks remain hardcoded to the old page numbers.
💡 Insight A PDF bookmark is not a sticky note attached to a specific page. It is a navigation instruction stored in the document's outline tree that says: "Go to page index N." For example, a bookmark labelled "Section 3" might internally read: "Go to page index 14."
When you merge Document A (30 pages) with Document B (20 pages), the pages of Document B become pages 31 through 50 in the combined file. Any bookmark from Document B that said "Go to page index 14" now points to page 14 of the combined file — which is a page from Document A. Section 3 of Document B is now unreachable via that bookmark.
This is not corruption. The bookmarks still exist. They are just pointing to page numbers that no longer correspond to the correct content.
Why We Remove Bookmarks During Merging
Short answer: Remapping bookmark addresses requires rebuilding the entire navigation tree — which is computationally expensive and bloats file sizes.
Evidence: To correctly preserve bookmarks across a merge, a tool must:
- Read the complete outline tree from every source document.
- Calculate the page offset that each source document will receive in the merged file.
- Update every bookmark destination address by adding that offset.
- Write a new unified outline tree that covers all pages of the combined document.
This operation must be performed for every single navigation entry. For a 200-page technical manual with 400 bookmarks, this is a significant computation that slows down processing and significantly increases the final file size. Our native Merge tool prioritizes speed, privacy, and a lightweight output, so it deliberately strips the outline tree. The result is a clean, optimized document.
The Fix: Intelligent Workflow Substitution
Since our tool optimizes for size and speed over complex navigation trees, you cannot rely on digital bookmarks to survive the merge. Instead, pivot to a physical navigation strategy using visual divider pages. This ensures your sections remain clearly demarcated without relying on fragile metadata.
Action: Insert title or divider pages between your PDFs.
| Phase | Action | Tool Required | Outcome |
|---|---|---|---|
| 1. Prepare | Create a simple 1-page PDF that acts as a title or divider (e.g., "Section 2"). | Any basic text editor (Save as PDF) | A reliable visual marker is created. |
| 2. Combine | Upload Document A, the Divider, and Document B to the Merge tool. | Merge PDF | Files are queued in the correct sequential order. |
| 3. Execute | Click Merge and download the combined file. | Merge PDF | A single, cohesive PDF is instantly generated. |
| 4. Split | (Optional) Use the visual dividers to easily find section breaks later. | Split PDF | Easily divide by page ranges using the dividers as guides. |
Why this is better: Visual dividers are baked directly into the document content. They will never break when merging, they print perfectly, and they require no special PDF reading software to navigate.
✓ Success Verification The new merge workflow is successful when:
- The merged document contains all pages from the source files in the correct order.
- Visual dividers clearly separate distinct sections of the document.
- The file size remains optimal and lightweight.