calibre MOBI Table of Contents Wrong: How to Fix It

If your converted Kindle book has duplicate chapters, missing entries, links that open the wrong section, or a table of contents at the end of the book, the problem may not be a simple conversion failure. MOBI handles navigation differently from EPUB and other modern e-book formats. The visible content table of contents, the navigation table of contents used by Kindle menus, and the MOBI-generated end-of-file table of contents can look similar while serving different purposes. The safest fix is to identify which one is wrong, test the source independently, and change one conversion option at a time.

1. Confirm the Symptom With a Small Safe Test

Before editing the book or resetting calibre, determine exactly what the reader is showing. This prevents you from deleting a generated table of contents that Kindle may need for navigation features.

1.1 Identify Which Table of Contents Is Wrong

An e-book can contain two kinds of table of contents:

• Content table of contents: A normal page inside the book containing clickable chapter links.
• Metadata table of contents: A navigation structure exposed through the reader's table of contents or Go To menu.

MOBI complicates this distinction. The older format does not provide the same clean metadata table of contents support as modern formats. To represent navigation, a converter may add a generated table of contents to the book's text, commonly near the end. Kindle can then use that structure for its navigation interface.

Therefore, seeing a table of contents after the final chapter is not automatically an error. It may be the generated MOBI navigation table. A duplicate-looking table can occur when the source already contains a visible content table of contents and calibre also creates the MOBI navigation version.

1.2 Test the Navigation and Visible Page Separately

Open the newly converted file in the calibre E-book viewer. Perform two tests:

1. Open the viewer's table of contents panel and click several entries, including the first, middle, and final chapters.
2. Navigate through the book itself and click links on any visible table of contents page.

Record whether the problem affects the navigation panel, the visible page, or both. If the panel works but the visible page is wrong, repair the source's content table of contents. If the visible links work but the navigation panel is wrong, inspect the metadata table of contents and conversion rules.

Next, copy the converted book to the Kindle using your normal supported method and repeat the test. Success means each tested entry opens the correct heading and the chapter order matches the book. If that happens, stop changing settings even if Kindle places the generated MOBI table of contents somewhere you would not have chosen.

1.3 Use a Copy Instead of the Only Book File

Keep the original source format untouched. If possible, work from an EPUB, DOCX, HTML, or another editable source rather than repeatedly converting an already converted MOBI. Repeated conversions can preserve or amplify bad headings, duplicate links, and structural mistakes.

Save test outputs under recognizable names such as Book-test-default.mobi and Book-test-auto-toc.mobi. Delete old test copies from the Kindle before transferring a new one so that you do not accidentally open the previous conversion.

2. Check the Settings Directly Related to the MOBI Table of Contents

A calibre MOBI table of contents wrong result usually begins with the source navigation, automatic chapter detection, or MOBI Output settings. Start with these areas before investigating USB drivers, firewalls, or reinstalling calibre.

2.1 Inspect the Source Table of Contents

If the source is EPUB or AZW3, select the book and open Edit book. Use the table of contents editing tool to inspect every entry. Look for duplicate labels, incorrect nesting, entries pointing to the previous heading, and links that target an empty paragraph instead of the chapter title.

Use the location-changing control to redirect a bad entry to the correct heading. Reorder entries only when their sequence is genuinely incorrect. Run the book-checking tool afterward to find broken internal links, missing files, malformed markup, or package errors that could disrupt navigation.

Do not delete the complete table of contents simply because Kindle displays a second one. First establish whether you are looking at a deliberate content page plus the MOBI-generated navigation table. Success at this stage means the source's table of contents panel contains one correctly ordered entry per intended section and every tested entry reaches the right location.

2.2 Review the Table of Contents Conversion Options

Open Convert books and select the Table of Contents section. calibre normally prefers a table of contents already present in the input metadata. Automatic generation becomes important when the source lacks usable navigation or contains a structure you intentionally want to replace.

Check these options carefully:

• Force use of auto-generated Table of Contents: Use this only when the existing metadata table of contents is absent or demonstrably wrong.
• Do not add detected chapters: This can prevent chapter detection from adding entries you do not want.
• Number of links: Set this to zero when links from a visible source table are being added as unwanted navigation entries.
• Chapter threshold: This affects when calibre supplements detected chapters with links found in the source.
• TOC Filter: Use it cautiously to remove predictable unwanted titles, not as a substitute for repairing a badly structured source.
• Level 1, Level 2, and Level 3 expressions: Clear old custom expressions unless you know they match the current source structure.

Duplicate entries often appear when calibre detects chapter headings and also imports links from an inline table of contents. Missing entries can occur when headings are plain styled text rather than real headings, or when a custom detection expression does not match them.

For a first test, restore the Table of Contents section to its defaults and convert again. If the default conversion works, stop there. Reintroduce custom settings only when they solve a specific, confirmed problem.

2.3 Review MOBI Output Without Removing Navigation Blindly

In the MOBI Output section, pay particular attention to the inline table of contents options. calibre can add the generated table at the end of the book, place it at the beginning, or suppress it. Placing it at the beginning is generally not recommended, and suppressing it can interfere with expected Kindle behavior.

The generated end-of-file table of contents may look redundant, but Kindle can use it for navigation-related functions, including Page Flip behavior on compatible books and devices. Do not select the option that removes the inline table of contents merely to hide the last pages until you have tested the Kindle's Go To menu, chapter navigation, and Page Flip.

If the book already has a manually created content table at the beginning, retaining the generated MOBI table at the end may still be the most functional result. Success means readers can open the Kindle navigation menu, select chapters reliably, and use supported navigation features. Cosmetic placement should be a secondary concern.

2.4 Consider AZW3 for USB Transfers to Kindle

When the destination Kindle accepts direct USB sideloading, AZW3 is often a better conversion target than legacy MOBI. AZW3 has stronger support for modern formatting and a proper metadata table of contents. It also gives calibre's editor more useful access to the book's internal structure.

AZW3 does not eliminate every Kindle limitation. Kindle firmware may still expect generated navigation structures for features such as Page Flip, so disabling generated table of contents output can remain counterproductive.

Convert the same clean source to AZW3, transfer it by USB, and compare its navigation with the MOBI version. If AZW3 works correctly and your delivery method and Kindle support it, use AZW3 and stop troubleshooting MOBI. Do not assume that an email delivery service or Content server will accept or transform every format in the same way as USB transfer.

2.5 Eliminate Saved Settings and Plugin Interference

Conversion settings can be saved for an individual book. As a result, changing global preferences may not affect the troublesome title. In the conversion dialog, restore defaults for the selected book before creating the test output.

Temporarily disable plugins that modify metadata, conversion input, conversion output, file names, or device transfers. A metadata-download plugin normally cannot rewrite navigation by itself, but a conversion or format-handling plugin can change which file becomes the input.

Also confirm the input format shown at the top of the conversion dialog. If the calibre record contains EPUB, MOBI, PDF, and DOCX, calibre may not be converting the format you expected. Choose the cleanest source explicitly.

3. Check the Source, Transfer Method, and Kindle Limitations

Operating system permissions and transfer problems rarely create chapter entries inside a finished MOBI. They can, however, cause you to test an outdated file or prevent calibre from replacing the copy on the device.

3.1 Remove Stale Copies From the Kindle

Delete the test book from the Kindle library, safely disconnect the device, reconnect it, and send the new conversion again. If the book was also delivered through an Amazon account, check whether a cloud copy and a USB copy are both present.

Use a visibly different title during testing, such as adding TOC Test to the metadata title. This makes it obvious which file you opened. Once navigation is correct, restore the proper title and perform one final conversion.

3.2 Check USB and File Access Only When Replacement Fails

If calibre reports that it sent the book but the Kindle continues to show the old table of contents, verify that the device is connected in file-transfer mode and appears in calibre. Safely eject it after the transfer so pending writes can finish.

On Windows, check whether security software is blocking calibre from writing to removable storage. On macOS, confirm that calibre has any requested removable-volume access. On Linux, verify that the mounted Kindle is writable by your user account.

Cloud-synchronized library folders can also create confusion. Avoid converting directly from a source file that another application is synchronizing or replacing. Copy the source to a normal local folder for the clean test.

3.3 Recognize Poor Source Structure

PDF is a particularly unreliable source for reflowable e-book navigation because it describes pages rather than a logical chapter structure. Chapter titles may be split across lines, stored in an unusual reading order, or represented only by font size. Automatic table of contents detection can therefore produce missing or misplaced entries.

DOCX files convert more predictably when chapter titles use Word's actual Heading styles. HTML sources should use meaningful heading elements and stable internal identifiers. A visible list that merely looks like a table of contents is not enough; its entries need valid links to chapter locations.

If the source is structurally poor, first convert it to EPUB, repair the EPUB table of contents with Edit book, and then convert that corrected EPUB to MOBI or AZW3. Success means the repaired EPUB works in the calibre viewer before you attempt the Kindle format.

3.4 Separate Conversion Problems From Delivery Problems

The Content server, email account, and network normally transport a completed file rather than creating its chapter structure. If the local MOBI is wrong in the calibre viewer, changing firewall or server options will not fix its table of contents.

If the local file works but the delivered Kindle copy does not, compare the actual files. Test a direct USB transfer to remove email conversion, account processing, server caching, and network delivery from the path. If USB works, the problem is likely in the delivery workflow or a service-side format transformation rather than calibre's table of contents generation.

4. Use Logs and Conversion Debug Output When the Cause Is Hidden

Logs are useful when the same settings produce different results or when a source appears correct but the output is not.

4.1 Read the Conversion Job Details

Open calibre's Jobs list after conversion and double-click the completed conversion job. Review the log for warnings involving table of contents generation, chapter detection, malformed links, missing anchors, input parsing, or output creation.

A completed job can still contain warnings that explain imperfect navigation. Save the log before running another test so you can compare the working and failing conversions.

4.2 Generate Conversion Debug Output

Use the conversion dialog's debug option and select an empty local folder. calibre can save intermediate stages of its conversion pipeline, including the parsed and structure-detected XHTML.

Inspect the structure stage to see which headings calibre recognized before MOBI output was created. If unwanted entries already exist there, adjust chapter detection or repair the source. If the structure stage is correct but the final MOBI is wrong, focus on MOBI Output behavior and Kindle interpretation.

This method is more reliable than changing multiple checkboxes because it reveals where the bad entry first appeared.

4.3 Use calibre-debug Only When Needed

For persistent application or plugin problems, restart calibre in debug mode. The graphical interface provides a restart-in-debug-mode option, and advanced users can run calibre-debug -g from a terminal or command prompt. The command calibre-debug --inspect-mobi can inspect MOBI files, while device-detection debugging is available when the Kindle itself is not being recognized.

Device-detection debugging is not a table of contents repair tool. Use it only if calibre cannot see the Kindle or cannot complete transfers. For a navigation problem inside a successfully created file, conversion debug output and the job log are more relevant.

5. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre rarely repairs one book's table of contents because book-specific conversion settings and source defects can survive the reinstall. A controlled test is faster and safer.

5.1 Build the Clean Test

1. Copy the original source file to a temporary local folder.
2. Add it to calibre as a new temporary book record.
3. Do not copy conversion settings from the old record.
4. Disable optional conversion-related plugins temporarily.
5. Convert once to EPUB and test the navigation panel.
6. If necessary, repair the EPUB table of contents with Edit book.
7. Convert the verified EPUB to MOBI using default settings.
8. Convert the same EPUB to AZW3 for comparison.
9. Test both locally, then transfer one clearly named file to the Kindle.

If the clean record works, the old record probably contains saved conversion settings, an unintended input format, or a stale output. Keep the working conversion and stop changing application-wide preferences.

If both formats fail at the same chapters, return to the source structure. If only MOBI fails, use AZW3 where appropriate or accept the MOBI-specific end-of-file navigation structure when it functions correctly.

5.2 Avoid Destructive Troubleshooting

Do not delete your calibre library, bulk-remove formats, or overwrite the only source file. Do not remove generated table of contents pages blindly. Do not change global detection expressions to repair one unusual book.

Reinstallation should be considered only when calibre itself cannot launch, conversion jobs fail across multiple known-good books, or program files appear damaged. A single wrong table of contents is usually a book structure or conversion configuration issue.

6. Quick Fix Checklist

• Determine whether the wrong item is the content table or Kindle navigation table.
• Test several links in the calibre viewer before transferring the book.
• Confirm that the intended source format is selected for conversion.
• Restore book-specific Table of Contents conversion options to defaults.
• Inspect and repair the source EPUB or AZW3 table of contents.
• Prevent link detection from duplicating already detected chapter headings.
• Review MOBI Output before disabling the generated inline table of contents.
• Leave the end-of-file MOBI table alone if Kindle navigation works.
• Test AZW3 by USB when the Kindle and workflow support it.
• Delete stale device copies before transferring a newly named test file.
• Check the conversion job log for missing targets or parsing warnings.
• Use conversion debug output to find where bad entries first appear.
• Disable conversion-related plugins during a clean temporary test.
• Stop changing settings as soon as all tested links open correctly.

7. Frequently Asked Questions

7.1 Why Does calibre Put the MOBI Table of Contents at the End?

Legacy MOBI cannot represent a metadata table of contents as cleanly as newer e-book formats. calibre can generate an inline table near the end to provide the navigation structure expected by Kindle. Its location may appear strange, but it is not necessarily a failed conversion.

7.2 Why Are There Two Tables of Contents?

The source may contain a visible content table near the beginning while calibre creates another structure for MOBI navigation. They can contain the same chapter names but serve different purposes. Test the visible links and the Kindle Go To menu separately before removing either one.

7.3 Can I Disable the Generated MOBI Table of Contents?

calibre provides an option to suppress it, but doing so can impair Kindle navigation and Page Flip behavior. Disable it only in a disposable test file, then verify chapter navigation and device features thoroughly. If any navigation feature stops working, restore the default output.

7.4 Why Does the Table of Contents Work in calibre but Not on Kindle?

The calibre viewer and Kindle firmware do not interpret every MOBI structure identically. You may also be opening an older device copy or a service-transformed copy. Delete stale copies, transfer a clearly renamed test file by USB, and compare MOBI with AZW3.

7.5 Is AZW3 Better Than MOBI for Kindle Navigation?

For supported Kindles and direct USB transfer, AZW3 is generally a better modern format. It supports richer formatting and proper metadata navigation. Kindle-specific firmware behavior can still make generated navigation structures important, so retain default table of contents output unless testing proves a change is safe.

7.6 Should I Delete and Regenerate the Entire Table of Contents?

Only if the source navigation is broadly unusable. When one or two entries are misplaced, redirect or reorder those entries in the editor. Regenerating everything can replace carefully chosen labels, nesting, and special sections with imperfect automatic detection.

The most reliable calibre MOBI table of contents wrong fix is to preserve the source, identify which table is failing, verify the source navigation, and test a default conversion before making advanced changes. Once the viewer and Kindle both open representative entries correctly, the problem is solved. Stop adjusting options at that point, even if MOBI's generated end-of-file table looks unfamiliar.