How to create a PDF with a table of contents that people can click
The cleanest way to create a PDF with a table of contents is to not build it in the PDF at all. Write the document in Word or Google Docs, style your headings properly, insert an automatic table of contents, then export. The entries become clickable links and, if you tick the right option, a bookmarks panel as well. Fixing a PDF that already exists is possible, but it is the slower route.
I have sent a lot of reports, proposals and long decks over the last decade, and the contents page was always the thing I did last, by hand, at 11pm. Then someone added a page and every number was wrong. That is the real problem with a table of contents: not making it, but keeping it true.
Build the table of contents before you make the PDF
A table of contents in a PDF is only as good as the document it came from. If you type the entries and page numbers yourself, you have made a picture of a contents page. It looks right until the first edit.
So the order is: headings first, table of contents second, PDF last.
Create a table of contents in Word
Word builds the table from heading styles. Apply Heading 1 to your main sections and Heading 2 to the sub-sections, using the actual styles rather than bold text at a bigger size. Then insert an automatic table of contents where you want it. Word reads the headings and lists them with page numbers.
The habit that saves you: update the table right before you export. Add a section, change a title, move a page, and the contents page does not know until you refresh it.
Create a table of contents in Google Docs
Google Docs works the same way. Its table of contents is built from your title and headings, and each item links to its heading. Add a new heading, hit refresh, and the table catches up. If you only use Docs for the odd report, this is the lowest effort route there is.
Export it so the links and bookmarks survive
This is the step people skip, and it is where a working table of contents turns into a flat page.
In Word's PDF export options there is a setting to create bookmarks, and you can build them from your headings (or from Word bookmarks if you have added your own), as Microsoft's guide to saving as PDF explains. Turn it on. You get a navigation panel down the side of the reader, a second way into the document that sits alongside the contents page.
Then open the exported file and click every entry. Printing to PDF or using a "best for printing" style setting can drop interactivity, and Microsoft itself flags hyperlinks as an issue with one of the print-focused options on Mac. I covered why links go missing on export in how to create a PDF with hyperlinks, and the same advice applies here: test the file you are sending, never the source.
Add a table of contents to a PDF you already have
Sometimes the source is gone, or someone else made the file. Then you are working in a PDF editor such as Acrobat Pro or an online equivalent, and you have two jobs.
Add bookmarks. Bookmarks are the entries in the side panel. Each one points to a page. You name it, point it at the right place, and nest sub-sections underneath. This is the closest thing a PDF has to a native table of contents.
Add a contents page with links. Insert a page near the front, type the section names, and draw a link over each one pointing to its page. This is the visible version the reader sees first. The mechanics of linking one page to another, including what to set for the zoom when they land, are in how to hyperlink to a page in a PDF. If you only need a standard outbound link rather than an internal jump, adding a link to a PDF for free lists the routes.
I would do both, bookmarks and a contents page, when the document is long. They serve different readers. Some people read from the front. Others open the side panel and never look at page two.
The catch with this route is that nothing updates. Insert a page later and every link after it points one page too early. If the document will change, go back to the source and export again.
Keep the table of contents short enough to use
A table of contents is a navigation tool, not an index. Here is where I have an opinion: most contents pages list too much.
If your document is ten pages, you probably do not need one. If it is forty, stop at two levels of heading. Once the contents page runs longer than a screen, people stop reading it, and then it is not saving them any time.
Name the entries the way the reader would look for them. "Pricing" beats "Commercial considerations". Someone scanning for the numbers should find them in one glance.
Check it like the reader will
Before you send it:
- Click every entry in the contents page, in the exported file.
- Open the bookmarks panel and check the nesting matches the headings.
- Check the page numbers against the actual pages after your last edit.
- Try it on a phone, because small tap targets on a contents page are a quiet failure.
If you want to add interactivity beyond navigation, there is a shorter answer in how to create an interactive PDF file.
FAQ
How do I create a PDF with a table of contents?
Write the document in Word or Google Docs, apply heading styles, insert an automatic table of contents, then export to PDF with bookmarks and links switched on. Click through the exported file to confirm every entry works.
How do I create a table of contents in a PDF that already exists?
Open it in a PDF editor, add bookmarks for each section, and optionally insert a contents page with a link over each entry. It does not update itself, so any later page change means redoing the links.
Do I need both bookmarks and a contents page?
Not strictly. A contents page is what readers see first, and bookmarks are the side panel navigation. For a long document I would include both, since people navigate in different ways.
Why is my table of contents not clickable after I save as PDF?
The export probably dropped the links, which can happen with print-focused export settings. Re-export using the standard option, make sure bookmarks and links are enabled, and test the exported file rather than the original.
I built LiveDocument because I was tired of sending documents I had worked hard on and then guessing what happened to them. If that sounds familiar, it is at livedocument.com.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.