Why are the entries in my PDF table of contents not clickable?

Because a contents page is, by default, just text — a list of titles and page numbers printed on a page, with no behaviour attached. When a PDF is exported without generating navigation, or created by scanning or converting a document, the contents page looks like a table of contents but is inert: clicking "Chapter 3 ... 42" does nothing because there is no link object connecting that line to page 42. Making it work means adding actual link annotations — either by generating a linked TOC from the document’s heading structure, or by placing a clickable link over each existing contents entry that points to the right page. The visual contents page and the working navigation are two separate things; a static PDF has the first without the second, and the job is to add the second.

What is the difference between a linked TOC, bookmarks, and cross-reference links?

They are three forms of PDF navigation that often get conflated. A linked table of contents is a contents page within the document where each entry is a clickable link jumping to that section — it lives on a page and prints. Bookmarks (the PDF "outline") are the collapsible side-panel list of destinations your viewer shows; they are navigation chrome, not part of the printed page. Cross-reference links are inline links in the body text — a "see page 12" or a citation that jumps when clicked. A well-navigated long PDF often has all three: bookmarks for the panel, a linked TOC on the contents page, and cross-references in the text. They complement rather than replace each other, and which you add depends on how readers move through the document.

How do I make an existing contents page clickable?

Add an internal link over each entry that targets the page the entry refers to. If your contents page already exists as static text, the direct route is to place a link annotation covering each line (or its page number) and set its destination to the corresponding page, so clicking jumps there. For documents with proper heading styles, it is usually faster to let a tool regenerate the contents as a linked TOC from the headings, which creates the links automatically. Either way you end up with link objects connecting contents entries to destinations. The manual per-entry approach is fine for a short contents list; for a long one, generating from headings saves a lot of clicking — but it only works if the document actually uses heading styles the tool can detect.

My links point to the wrong pages — what happened?

Almost always a page-number shift: the links target page positions, and something changed the pagination after the links (or the printed numbers) were set. Adding or removing pages, inserting a cover, or merging documents all renumber the pages, so a link that pointed to "page 42" now lands a few pages off, and the printed numbers in the contents may no longer match the real page positions either. The fix is to set or regenerate the links after the document’s pages are final, not before — finalise the page order and any front matter first, then build the TOC links so destinations and printed numbers agree. If you must edit pages afterward, regenerate the links rather than trusting the old ones. Treat TOC linking as one of the last steps, after pagination is locked.

Does a clickable TOC help accessibility?

It helps navigability for everyone, and proper structure helps accessibility specifically. Clickable contents and bookmarks let any reader — and especially anyone navigating a long document without scrolling page by page — jump straight to a section, which is a real usability win. For accessibility in the fuller sense (screen readers), what matters most is that the document has genuine structure: tagged headings and a logical reading order, from which navigation can be derived. So the best practice is to build the document with real heading styles and tags, then generate the linked TOC and bookmarks from that structure. That way the same underlying structure serves the clickable navigation, the side-panel outline, and assistive technology together, rather than bolting on links over an untagged document.

Is it safe to add TOC links with an online tool?

Use a tool that runs on your own device for anything non-public. Adding navigation often happens on reports, manuals, and books that may be confidential or unpublished, and many online tools upload your file to a third-party server. Client-side (in-browser) tools generate the TOC and links locally so the file never leaves your computer — ScoutMyTool’s PDF tools work this way. For confidential documents, confirm a tool is client-side before uploading, or use offline software. The convenience of quick online linking is not worth uploading an unpublished manuscript or internal report to a server you do not control.

7 min read

How to convert a PDF table of contents to live hyperlinks

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

I downloaded a 200-page report with a beautiful contents page, clicked "Section 7," and... nothing happened. The contents looked like navigation but was just printed text — titles and page numbers with no links behind them. Anyone who has scrolled forever through a long PDF looking for a section knows the frustration, and the fix is specific: a contents page and working navigation are two different things, and you have to add the second. This guide is about turning a static table of contents into live internal hyperlinks that actually jump to the right page — the methods that do it, the page-number gotcha that quietly breaks the links, and how it relates to bookmarks and accessibility.

Ways to add PDF navigation

Method	How it works	Best for
Auto-generate from headings	Tool builds a linked TOC from heading styles	Documents with proper heading structure
Bookmarks (outline panel)	Side-panel entries that jump to pages	Navigation without a printed contents page
Link an existing TOC page	Add a link over each contents entry to its page	A static contents page you want clickable
Cross-reference links in body	Inline "see page X" become clickable jumps	References scattered through the text

Step by step — make the contents clickable

Finalise pagination first. Lock the page order and any front matter before adding links, so destinations and printed page numbers will not shift afterward.
Pick your method. If the document uses real heading styles, auto-generate a linked TOC from the headings; if not, plan to link each existing contents entry by hand.
Generate or place the links. Let the tool build links from headings, or add a link annotation over each contents line targeting its page.
Add bookmarks too. Generate the side-panel outline so readers get both the on-page linked TOC and the viewer’s navigation panel.
Test every link. Click through the contents entries and confirm each lands on the correct section, not a few pages off.
Regenerate if you edit pages. If you add or remove pages later, rebuild the links rather than trusting the old destinations.

The principle: structure first, links last

Two ideas make TOC linking reliable. First, build on structure: a document with real heading styles can have its linked contents, bookmarks, and even accessibility derived automatically from that structure, whereas an untagged document forces you to bolt links on by hand and gives screen readers nothing to work with. So the highest-leverage move is to author with proper headings in the first place. Second, link last: because links and printed page numbers both depend on pagination, you set them after the page order is final, or they drift out of alignment the moment you insert a cover or merge in another file. Get the structure right and add the navigation as a final step, and a long PDF stops being an endless scroll and becomes a document readers can move through in a click.

FAQ

Why are the entries in my PDF table of contents not clickable?: Because a contents page is, by default, just text — a list of titles and page numbers printed on a page, with no behaviour attached. When a PDF is exported without generating navigation, or created by scanning or converting a document, the contents page looks like a table of contents but is inert: clicking "Chapter 3 ... 42" does nothing because there is no link object connecting that line to page 42. Making it work means adding actual link annotations — either by generating a linked TOC from the document’s heading structure, or by placing a clickable link over each existing contents entry that points to the right page. The visual contents page and the working navigation are two separate things; a static PDF has the first without the second, and the job is to add the second.
What is the difference between a linked TOC, bookmarks, and cross-reference links?: They are three forms of PDF navigation that often get conflated. A linked table of contents is a contents page within the document where each entry is a clickable link jumping to that section — it lives on a page and prints. Bookmarks (the PDF "outline") are the collapsible side-panel list of destinations your viewer shows; they are navigation chrome, not part of the printed page. Cross-reference links are inline links in the body text — a "see page 12" or a citation that jumps when clicked. A well-navigated long PDF often has all three: bookmarks for the panel, a linked TOC on the contents page, and cross-references in the text. They complement rather than replace each other, and which you add depends on how readers move through the document.
How do I make an existing contents page clickable?: Add an internal link over each entry that targets the page the entry refers to. If your contents page already exists as static text, the direct route is to place a link annotation covering each line (or its page number) and set its destination to the corresponding page, so clicking jumps there. For documents with proper heading styles, it is usually faster to let a tool regenerate the contents as a linked TOC from the headings, which creates the links automatically. Either way you end up with link objects connecting contents entries to destinations. The manual per-entry approach is fine for a short contents list; for a long one, generating from headings saves a lot of clicking — but it only works if the document actually uses heading styles the tool can detect.
My links point to the wrong pages — what happened?: Almost always a page-number shift: the links target page positions, and something changed the pagination after the links (or the printed numbers) were set. Adding or removing pages, inserting a cover, or merging documents all renumber the pages, so a link that pointed to "page 42" now lands a few pages off, and the printed numbers in the contents may no longer match the real page positions either. The fix is to set or regenerate the links after the document’s pages are final, not before — finalise the page order and any front matter first, then build the TOC links so destinations and printed numbers agree. If you must edit pages afterward, regenerate the links rather than trusting the old ones. Treat TOC linking as one of the last steps, after pagination is locked.
Does a clickable TOC help accessibility?: It helps navigability for everyone, and proper structure helps accessibility specifically. Clickable contents and bookmarks let any reader — and especially anyone navigating a long document without scrolling page by page — jump straight to a section, which is a real usability win. For accessibility in the fuller sense (screen readers), what matters most is that the document has genuine structure: tagged headings and a logical reading order, from which navigation can be derived. So the best practice is to build the document with real heading styles and tags, then generate the linked TOC and bookmarks from that structure. That way the same underlying structure serves the clickable navigation, the side-panel outline, and assistive technology together, rather than bolting on links over an untagged document.
Is it safe to add TOC links with an online tool?: Use a tool that runs on your own device for anything non-public. Adding navigation often happens on reports, manuals, and books that may be confidential or unpublished, and many online tools upload your file to a third-party server. Client-side (in-browser) tools generate the TOC and links locally so the file never leaves your computer — ScoutMyTool’s PDF tools work this way. For confidential documents, confirm a tool is client-side before uploading, or use offline software. The convenience of quick online linking is not worth uploading an unpublished manuscript or internal report to a server you do not control.

Citations

Build a clickable contents page — in your browser

Generate a linked table of contents and bookmarks for your PDF with ScoutMyTool — client-side, so an unpublished report or manuscript never leaves your computer.

Open the TOC Generator →