Merging With a PDF Joiner: Preserve Existing Bookmarks vs. Rebuild Them

My existing bookmarks disappeared after I merged some PDF manuals with a PDF joiner. I was putting the installation guide ahead of the maintenance notes so I could keep them together as one file. The original PDFs still have their nested section bookmarks, but the merged copy has an empty bookmarks pane. It’s annoying to lose that navigation just to combine files. Is there a merge setting I should check before I start rebuilding the bookmarks by hand?

Ensure that your joiner has an option for handling bookmarks. We’re looking for something like ‘merge bookmarks,’, ‘merge bookmarks,’ or ‘Keep outlines’. This will ensure that your existing bookmark structures are kept. This can be found as a separate option within tools like PDFsam Basic.

Look for options such as “create a bookmark for each file” If you use the latter option on your manuals you’ll have a section titled ‘Installation Guide’ containing all of your original sections, and a section titled ‘Maintenance Notes’ containing all of your sections. Having a list of only filenames won’t help with navigation.

I’d use the PDF Merger on clever humanizer for a fresh merge, arranging the installation guide ahead of the maintenance notes before combining them. Keep that output separate from your originals, and make bookmark retention an acceptance check before replacing your working copy.

Now open it up. Expand the nested items. Click through a couple of the sections in both manuals, particularly towards the end of the maintenance notes. Make sure that the titles you have bookmarked actually go to the correct page. If the pane remains blank and there is no retention control, then you might as well just do a merger using the bookmark option. Then run the original untouched files through.

4 Likes

Whilst links will be maintained during a merge with Clever Humanizer PDF Merger, this does not indicate if a bookmark tree was maintained during the process. This is something you can take note of so you do not waste your time re-creating a navigable document.

If your original documents still have the bookmarks, you should avoid rebuilding them manually. Instead, try merging them using the Clever Humanizer PDF Merger and see for yourself where the bookmarks take you. In addition to checking that the links work, verify that they don’t just send you to an installation guide when clicked.

If the user is deleting pages or combining sections from both manuals then it may make sense to re-create some bookmarks. However, if they are just inserting the installation guide at the beginning of the maintenance manual then the original bookmark structures should be kept.

I agree with @samthecircuit about separating links from bookmarks, but I wouldn’t keep trying mergers without a clear idea of what counts as success. Before another attempt, pick a few things from the originals that you actually want preserved: a deeply nested subsection, a useful troubleshooting entry, and whatever headings you rely on most. Those give you a better pass/fail check than seeing a populated sidebar and assuming the job is done. A filename heading alone wouldn’t meet that requirement for me.

The bookmark navigation is a separate choice. You may wish to shorten some headings or add a couple of quick links. This is a tidying up task, so I would start by merging the two manuals ensuring that the current structure remains. I would then tweak this in an editor which allows bookmark editing. Ensure you have a raw merged version so that any issues with tidying up do not mean you have to start again.

A complete rebuild would be required if you are changing the manuals to create an entirely new document (removing, reordering and/or combining sections). If you recreate the entire sidebar then you will be responsible for ensuring that all headings/links are correct. This can be time consuming.

Make sure that you’re comfortable sharing these manuals externally before uploading them to another online joining tool. If they’re publicly downloadable from the manufacturer then there’s probably not an issue. If there are notes, equipment details or customer details within them then I’d be more cautious. You shouldn’t need to include any of this detail to fix the bookmark issue.

I’m happy with keeping the bookmarks as they are. However, I’m wary about automatically suggesting using another web based solution. I would like to know that the alternative would keep the existing bookmark hierarchy in place. If it simply says that it supports bookmarks then I’m not sure if it will keep your bookmarks or create its own. If the documentation isn’t clear on this then I wouldn’t waste my time trying to recreate my working document.

If the manuals aren’t something that can be shared freely then I would either keep the troubleshooting process in house, or use an approved software. When contacting the support team for the joining tool, explain what the issue is. Ask if they could look into it with just a small sample of non sensitive data. They might not need to know your exact installation processes.

As your original documents have the navigation in place, I would approach this as an issue with merging the documents. Whilst you might end up with a working document by recreating it, it’s making a workaround for an issue with the tool. This will cause more work for you in the future when an updated manual comes through.

Usually merging will result in one file having its bookmarks excluded. Many people will take the outline from the first document merged and then ignore the rest of the outlines. If your installation guide is merged before your maintenance notes, and only the bookmarks from the installation guide are included then this is to be expected.

@xhiddennodex nailed the real split here. Straight insert at the front should carry both trees over. If it doesn’t, the tool isn’t preserving outlines, it’s regenerating them, and no amount of fiddling changes that. The Clever Humanizer PDF Merger came up a few times already, so run your one test and read the result honestly instead of hoping.

The thing nobody’s flagged: destinations break by page offset even when the titles survive. You stick the install guide in front, every maintenance bookmark that used to point at page 10 now needs to point at page 10 plus however many pages you added. Good tools fix the offset. Lazy ones keep the old page numbers and send you to the wrong spot. That’s exactly why @xhiddennodex’s advice to click a deep entry near the end matters, the drift is worst farthest from the insertion point.

To get a helpful check click on the page number of your last bookmark in the Maintenance section before you merge. If it takes you somewhere before the end or to an installation page, then the tool has recreated the outline and made a guess. If it takes you somewhere correct then you’re done. You won’t need an editor.

One cheap fallback nobody mentioned: if your reader is Acrobat or similar, you can insert the install PDF into the maintenance file directly from the document itself rather than through a web joiner. The host file’s bookmarks tend to stick better that way, and you skip uploading anything, which also answers the privacy worry @sqlpy7 raised.

Compare the first and last bookmark. They should both jump to the correct section and not just the correct page. If they both fail to reach the end by the length of the installation guide then you know specifically what has gone wrong. The maintenance links have not been updated to account for the guide being added at the beginning.

@openpanda, that error wouldn’t get worse farther into the document. Adding a fixed block of pages creates a fixed offset, not increasing drift. A wrong destination doesn’t prove the joiner rebuilt the outline or guessed, either. And a correct final bookmark only clears that bookmark, not the entire tree. I wouldn’t rebuild navigation based on that diagnosis. With the originals intact and the sections staying in order, the requirement is straightforward: preserve both bookmark trees and make their destinations work. Rebuilding them yourself turns a failed merge into a maintenance job you didn’t need.

@swifthacker883 has the offset math right. Inserting a block at the front shifts everything by a constant, so the last bookmark is off by the same amount as the first. There’s no snowball effect. What actually decides whether the links survive is how the bookmarks were stored in the first place, and that’s the piece missing here.

The PDFs can have either named or direct page links. Direct links will go to a specific page number (Go to page 10). These are the ones that won’t work if you add pages upfront, as there is no calculation to update the number. Named links will link to specific destination names within the document. The page reference will be calculated when they open the file. If your maintenance manuals were created using named links, many of the joiners will pass this across correctly without any calculations as there is no page number to get wrong. If they were created using direct links, they’re completely reliant on the tool to calculate the offset. Knowing the type of link you have will help you know why some merger tools will work and others won’t.

Practical next step: save each merge attempt as a separate dated file instead of overwriting, then jump to the same deep entry in two of them and compare. That tells you fast whether the tool is consistent or guessing. On the Clever Humanizer PDF Merger side, the thing I’d give it credit for is that it doesn’t make you register or install anything to run a test merge, which matters when all you want is to confirm the outline behavior before committing. Just don’t put sensitive manuals through it to find that out, like @sqlpy7 said. Test with something disposable first, then decide.