A long PDF becomes easier to use when readers can jump to a named section without remembering its page number. A useful bookmark outline answers two questions: where does this topic belong, and where should I start reading? A long list of vague labels can make both questions harder.
This walkthrough uses Adobe Acrobat Pro desktop on Windows to add ordinary navigation bookmarks to an existing PDF. Keep an untouched original and work in a separately named copy, such as handbook-navigation-working.pdf. The checks below are instructions for your own file; no hands-on software test or screenshot is claimed here.
Decide where the outline should be maintained
If you own the editable source and revise it regularly, generate bookmarks during export. Manual PDF repairs become another maintenance task whenever you publish a replacement. If you received only the PDF, or assembled a stable packet from several documents, adding bookmarks directly is more practical.
For Word desktop on Windows, use File > Save a Copy or Save As, choose PDF, then open More Options > Options. Enable Create bookmarks using and select Headings; save the PDF. Microsoft documents this in its PDF export guidance. This route assumes the source already has meaningful heading styles. Reopen the export and inspect its bookmark outline before deciding manual additions are needed.
Keep this choice narrow: you do not need to rebuild a contents page just to make a received PDF navigable. Equally, avoid repairing the exported outline every week when fixing the source once would keep future editions consistent.
Draft the destinations before clicking Add
Imagine a hypothetical volunteer handbook with an introduction, joining instructions, expenses, event procedures and reference forms. A coordinator usually needs the expenses rules or an incident form, rather than the cover. Build the outline around those retrieval tasks while retaining the document's actual section names.
| Top level | Useful child | Destination to verify |
|---|---|---|
| Joining | First-shift checklist | The checklist heading and first item |
| Expenses | Claim deadlines | The paragraph introducing deadlines |
| Event procedures | Report an incident | The reporting instructions |
| Reference forms | Incident form | The actual form, not its earlier mention |
Start with main sections, then add children only where readers benefit from a direct jump. Two levels are a sensible starting design for this example, not a PDF limit. A child should clearly belong to its parent. Put an appendix at the top level when it serves the whole document.
Prefer “Expenses — claim deadlines” to “Important information.” Repeated labels such as “Overview” need context if readers might encounter them with surrounding branches collapsed. Avoid adding page numbers to names unless the document's reference scheme requires them: those numbers create another thing to update.
Record a recognizable heading or opening phrase beside each planned destination. A printed page number alone is weak evidence when covers, Roman numerals or unnumbered inserts precede the body. Your acceptance check will be the content you reach.

Create one bookmark and prove that it jumps
Open the working PDF. In Acrobat's current interface, select the bookmark icon on the right. Go to your first destination and set a readable view. From the Bookmarks panel's Options menu choose New Bookmark, then enter its label. Adobe's bookmark instructions document this route.
Adobe also documents creating a bookmark without selecting text. That is useful for an image-only scan: type the intended label rather than making text recognition a prerequisite.
Now move several pages away and activate the new bookmark. Success means the intended heading is visible with enough surrounding content to orient you. Landing on the cover, the previous section's last paragraph or an unreadable enlargement is a failed pilot. Fix that single entry before repeating the process throughout the document.
Save the working copy, close it and reopen it. Confirm the entry remains and repeats the same jump. This small persistence check catches a problem before you spend time building the whole outline. If saving is blocked, resolve that first.
Build branches that match the document
Create the remaining entries from your plan. Adobe's bookmark tutorial describes dragging bookmark icons to rearrange entries or nest them beneath a parent. Use the placement indicator, then inspect the resulting indentation.
For the hypothetical handbook, “Claim deadlines” belongs beneath “Expenses.” After nesting it, collapse Expenses: the child should disappear with that branch. Expand it again and check that “Event procedures” remains a sibling of Expenses. If it disappears too, your branch contains more than you intended. Reposition the misplaced entry before continuing.
Keep the order aligned with the document unless a clearly explained task-based arrangement is necessary. Readers should not have to discover that the third bookmark points to an appendix while the fourth returns to the introduction. For this walkthrough, use ordinary bookmarks you created manually; leave existing structure-generated branches intact.
Review labels as a set. “Incident reporting” and “Incident form” should remain distinct because one explains the process and the other starts the form. A reader choosing the second should not have to scroll through the first to find it.
Repair the destination, not just its name
For a wrong jump, select the existing bookmark, navigate to the correct location, adjust the view and choose Set Bookmark Destination in Options. Adobe notes that this command appears only with an existing bookmark selected. To change a label, use Rename Bookmark.
Treat naming and targeting as separate checks. In the handbook example, renaming “Incident form” to “Incident report form” improves wording but does not prove that the destination moved. Jump away and back after every destination repair, then compare the landing content with your written plan.
If bookmark creation is unavailable, Adobe says document security settings must permit it. Ask the owner for an editable copy or a newly exported bookmarked PDF. Do not assume a different menu will overcome a document restriction.
If a branch becomes tangled, use your saved working copy as the recovery point. Adobe warns that deleting a parent bookmark also deletes subordinate bookmarks. Avoid clearing an entire branch to remove one unwanted label; first identify which children you would lose.
Check the saved file as a reader would
W3C's bookmark technique checks both that bookmarks appear and that they link to the correct sections. Apply that baseline to the final saved copy, then use your destination plan for a more demanding review:
- Open every main entry and every child you added or changed. Compare the heading and opening content with the plan.
- Try a task without using page search: find the claim deadline, then the incident form. Ambiguous labels are a navigation defect even when their jumps work.
- Inspect the exact delivery file in the reader your audience expects to use. If its outline is hidden or unavailable there, provide a clear instruction to use a reader that exposes PDF bookmarks.
- After replacing, inserting or rearranging pages, repeat the destination checks. Do not infer correctness from unchanged labels.
Bookmarks do not make scanned words searchable or establish complete accessibility. Keep those as separate requirements. Preserve the original and the editable source, if available, alongside your maintenance plan. Release the bookmarked copy only when its outline survives reopening and its destinations match what the labels promise.
Sources, versions & scope
The steps describe the documented controls and expected checks; they are not a claim that every device or software release has been physically tested. Platform and version differences are stated with the procedure.
Knowligent Editors
First published · Updated
Documentation-led digital-life guidance, with AI-assisted research and drafting. Examples are identified, source links are provided, and device-testing limits are stated.
Editorial standards

