Kindle e-reader displaying a book with a table of contents
kdp

KDP 'No TOC Found' Error: Exact Cause and Step-by-Step Fix

Fateh7 min read

You upload your EPUB to KDP and get stopped by an error: "No table of contents (TOC) found." Or maybe KDP accepts the file but sends a warning that no TOC was detected, and your book publishes with a broken navigation experience. Either way, you have a problem.

This error is one of the most common KDP upload problems, and it almost always has the same root cause. Here's what's happening, what the error messages look like, and how to fix it without rebuilding your entire file. For a wider look at how Amazon KDP works, including the other checks it runs at upload, see our beginner guide.

Why KDP Requires a Table of Contents

Kindle devices have a dedicated TOC button. When a reader taps it, the Kindle opens your book's navigation structure — chapter by chapter. Without a valid TOC in your EPUB, that button doesn't work. Readers on Kindle Paperwhite, Kindle Oasis, and the Kindle app on iOS and Android all lose the ability to jump between chapters directly.

KDP is also protecting the reader experience. A 300-page book with no navigable TOC is genuinely frustrating on an e-reader where you can't flip pages quickly. KDP enforces this requirement to maintain baseline quality across the store.

The Two Types of TOC in an EPUB

This is where most authors get confused. EPUB files have two different table of contents structures, and KDP needs at least one of them to be present and correctly formed.

NCX file (EPUB 2.0 format): A file called toc.ncx inside your EPUB package. This is the older format, used in EPUB 2.0 and supported by all Kindle generations including legacy e-ink devices. It lists chapters as <navPoint> elements with <navLabel> and <content src="..."> child elements pointing to each chapter file.

Nav document (EPUB 3.0 format): An XHTML file (usually nav.xhtml or toc.xhtml) that contains a <nav epub:type="toc"> element with an ordered list of chapter links. This is the current standard and required for EPUB 3.0 compliance.

KDP supports both formats but requires the one that matches your EPUB version declaration. EPUB 3.0 files should have a nav document. EPUB 2.0 files should have an NCX. Files with neither — or with both present but broken — get the "No TOC Found" error.

Real Error Messages From KDP

KDP surfaces TOC problems in several ways depending on severity:

"Your file does not contain a table of contents. Kindle books
 should include a table of contents so readers can navigate
 between chapters."

"We couldn't detect a table of contents in your file. The file
 was published, but readers may not be able to navigate your
 book from the Kindle menu."

"Error: Unable to parse the navigation document (nav.xhtml).
 The table of contents structure is invalid."

"TOC reference in spine not found: the NCX navMap contains
 entries pointing to files that do not exist in this EPUB."

The first two messages mean KDP published but flagged the TOC as missing or undetected. The last two mean a hard parse failure — KDP found a TOC file but couldn't read it because of structural errors inside it.

The Most Common Cause: Empty or Broken NCX/Nav

The most frequent cause of "No TOC Found" is a conversion tool that created the NCX or nav file but left it empty or generated broken links inside it.

A broken NCX file might look like this — a valid file structure with no actual chapter entries:

<?xml version="1.0" encoding="utf-8"?>
<ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1">
  <head>
    <meta name="dtb:uid" content="book-001"/>
  </head>
  <docTitle><text>My Book</text></docTitle>
  <navMap>
    <!-- navPoint elements should be here but aren't -->
  </navMap>
</ncx>

Or the navPoints might exist but point to wrong file paths:

<navPoint id="nav-1" playOrder="1">
  <navLabel><text>Chapter 1</text></navLabel>
  <content src="Text/Chapter001.xhtml"/>  <!-- file is actually Chapter01.xhtml -->
</navPoint>

A single mismatched filename breaks the entire TOC because reading systems can't verify the link resolves to a real file.

How to Fix "No TOC Found": Step by Step

Step 1: Validate your current EPUB. Upload your file to the EPUB Validator. The validator identifies whether you're missing an NCX, whether the nav document is empty, whether TOC links are broken, and whether the manifest entry for the TOC file is correctly formed. This tells you exactly what you're fixing before you start touching anything.

Step 2: Check what TOC files exist. Unzip your EPUB and look inside the package. You should find either a toc.ncx file (EPUB 2.0) or a nav.xhtml file (EPUB 3.0), or both. Open each one and check whether the chapter entries are actually present and pointing to files that exist.

Step 3: Fix or rebuild the TOC.

  • If the NCX has navPoints with wrong file paths, correct the src attributes to match your actual chapter filenames — exact capitalization matters on case-sensitive systems.
  • If the nav document is missing the <nav epub:type="toc"> element, add it with an <ol> list of links to each chapter.
  • If the TOC is completely missing, use the TOC Generator. Upload your manuscript and it creates a valid EPUB-compatible table of contents from your chapter headings — formatted correctly for both Kindle and EPUB 3.0.

Step 4: Fix the OPF manifest entry. The TOC file must be declared in the OPF manifest with the correct media type, and for EPUB 3.0 nav documents, the manifest item must have properties="nav":

<!-- For EPUB 3.0 nav document -->
<item id="nav" href="nav.xhtml"
  media-type="application/xhtml+xml"
  properties="nav"/>

<!-- For NCX (EPUB 2.0 or combined) -->
<item id="ncx" href="toc.ncx"
  media-type="application/x-dtbncx+xml"/>

Also check the <spine> element — for EPUB 2.0, it needs a toc="ncx" attribute referencing the NCX item ID.

Step 5: Repackage and test. Repackage with mimetype first and uncompressed. Run validation again to confirm the TOC is now detected. Upload to KDP. If you want extra confidence, open the EPUB in the Kindle Previewer and check that the TOC menu populates correctly before publishing.

Special Case: TOC Exists But KDP Still Flags It

Sometimes the error appears even when a TOC file exists. Three specific causes:

  • Wrong manifest entry: The NCX or nav file exists but isn't listed in the OPF manifest with the correct ID and media type. Add or fix the manifest item.
  • Missing properties="nav": EPUB 3.0 nav documents need this attribute in the manifest. Without it, reading systems don't recognize the file as the navigation document.
  • Broken chapter links: The TOC lists chapters but links point to wrong paths. Relative paths that don't match your actual file structure — even by a single slash or capitalization difference — cause link resolution failures.

Pro Tips

  • Generate TOC from headings, not manually. When you write H1 and H2 headings consistently in your manuscript, a proper EPUB builder auto-generates a correct TOC from those headings every time. Manual TOCs go stale as you edit chapters.
  • Include both NCX and nav for maximum compatibility. Including both an NCX file (for older Kindles) and a nav document (for EPUB 3.0) in the same EPUB ensures your TOC works across every generation of Kindle device and every reading system.
  • Don't copy chapters between EPUB files. Copying chapter files from one EPUB into another without updating the TOC links breaks navigation silently. Always regenerate the TOC after any structural change.
  • Test with Kindle Previewer after every TOC change. The Kindle Previewer's TOC menu shows you exactly what readers will see. Use it to verify chapter names and order before every upload.

Frequently Asked Questions

Does KDP require a TOC for short books like novellas or short stories?

Yes. KDP requires navigable TOC for all books regardless of length. Even a 5,000-word short story needs a valid TOC structure — though it can contain just one or two entries pointing to the start of the content. The requirement exists for technical reasons, not reader convenience, so there's no minimum length exemption.

Can I have both a visual TOC page and a navigation TOC?

Yes, and having both is good practice. A visual TOC is a regular HTML page in your EPUB that readers can see and read — it looks like a formatted chapter list with links. The navigation TOC (NCX or nav document) is the structural version that powers the Kindle's TOC button. Both serve different purposes and can coexist in the same EPUB. The visual TOC page should be listed in the spine; the nav document should not appear in the spine (it's a structural file, not a reading-order page).

Why does my book preview correctly in Kindle Previewer but KDP still shows a TOC error?

Kindle Previewer is more permissive than KDP's upload validator. It may render your book correctly even if the TOC structure isn't fully valid. The upload validator applies stricter checks. Always validate with an EPUB validator before relying on the Kindle Previewer as your only quality check.

What happens if I publish without fixing the TOC error?

If KDP publishes with a warning (not a hard block), your book is live but the Kindle TOC button won't work. Readers can't jump between chapters from the navigation menu. This often shows up in reviews — "no chapter navigation," "can't find chapter 12" — and affects the reading experience on all Kindle devices and the Kindle app.

Will a valid TOC improve my book's discoverability on Amazon?

Indirectly. A functional TOC doesn't directly affect Amazon search ranking, but it significantly affects reader experience and reviews. Books with broken navigation get lower ratings on average, and negative reviews about technical formatting issues affect conversion rates over time. A clean, working TOC is part of the baseline quality readers expect from a professional ebook.

kdpepubformattingtoc
← Back to Blog