Key takeaways
- Use real heading styles instead of manually styled text.
- Provide the required logical Kindle TOC and useful front-of-book navigation.
- Update paperback page numbers only after layout is stable.
- Test every destination and entry in the final files.
Understand the two Kindle TOCs
KDP currently requires a logical TOC for Kindle books with chapters or sections. It appears through the Go To navigation and supports progress and movement through the book.
Amazon also strongly recommends an HTML TOC that appears as a normal page near the beginning. The two may be generated by a tool, but both depend on correct semantic structure and links.
Build a clean heading hierarchy
- One consistent style for part titles
- One Heading 1 treatment for primary chapters
- Heading 2 and lower levels only where useful for navigation
- Short, unique headings that make sense out of context
- No empty headings or styled body text masquerading as headings
- Stable order matching the manuscript
For the broader publishing workflow, continue with How to Format Tables in an Amazon KDP Paperback.
Create and test Kindle navigation
Apply heading styles
Mark chapter and section titles semantically in the source document.
Generate navigation
Use Kindle Create or a valid navigation document and HTML TOC.
Check labels
Confirm the displayed entry text matches the destination heading.
Test links
Open every entry in Kindle Previewer across representative device views.
Check Go To
Verify cover, beginning, contents, and chapter navigation where applicable.
Create the paperback contents page
Insert an automatic table of contents from heading styles rather than typing page numbers manually. Choose a level of detail appropriate to the book; listing every subheading can make the contents less useful.
Update the entire table after final pagination changes. Review right- and left-facing starts, blank pages, front-matter numbering, and whether displayed page numbers match the printed destinations.
For the closely related decision, read How to Format a Paperback for Amazon KDP.
Maintain separate format outputs
A reflowable Kindle book should not display fixed print page numbers as if they control digital locations. A paperback does not use clickable Kindle navigation.
Keep a shared heading inventory but generate and test the TOC separately for each format. If the manuscript changes, mark both outputs for re-verification.
Before moving to the next stage, use The Complete Amazon KDP Upload Guide for First-Time Authors as a practical follow-through.
Run a final TOC audit
- All intended chapters appear once and in order.
- No removed or renamed heading remains.
- Kindle entries open the correct destination.
- Paperback page numbers match final pages.
- Indentation communicates hierarchy consistently.
- Long entries wrap cleanly without colliding with page numbers.
- The cover and metadata use the same chapter naming where relevant.
Common questions
Does every Kindle eBook need a table of contents?
KDP requires a working logical TOC for Kindle books with chapters or sections and strongly recommends an HTML contents page.
Should a Kindle TOC include page numbers?
Reflowable Kindle content does not use fixed print pagination. Use working links and digital navigation rather than paperback page numbers.
How do I stop paperback TOC numbers from becoming wrong?
Generate the table from heading styles, stabilize layout, update the entire TOC, and inspect the final PDF and proof after all pagination changes.
Official sources and further reading
Platform policies and royalty terms can change. Check the current Amazon documentation before publishing.
Move from research to production
Create the nonfiction manuscript you plan to publish on KDP.
Give Draft Fast your reader, promise, and project details, then review an organized manuscript prepared for editing and publishing.