Why does my Kindle conversion lose its table of contents?

Because the navigation a Kindle uses is a structural feature that a PDF often does not carry in a form the conversion can reuse. On a Kindle, the working table of contents is the "Go To" / navigation menu, which is built from a logical TOC embedded in the ebook’s structure — not from a printed contents page. A PDF frequently has only a visual contents page (static text and page numbers) and maybe some bookmarks, and those do not automatically become the EPUB/Kindle logical TOC during a naive conversion. So you end up with a book that may show a contents page but offers no working chapter navigation on the device, and whose page-number references are meaningless because the text now reflows. The fix is to rebuild the logical TOC from the document’s real heading structure as part of the conversion, rather than hoping the PDF’s existing contents survive.

What is the difference between a printed contents page and the Kindle navigation?

They are two different things, and conflating them is the root of most lost-navigation problems. A printed (or on-page) contents page is content that appears as a page in the book — a list of chapter titles, historically with page numbers. The Kindle navigation (the "Go To" menu and the progress controls) is a structural, device-level feature that lets the reader jump to any chapter from the menu regardless of where they are. A good ebook usually has both: a linked contents page for in-text browsing and a logical TOC powering the device menu. Crucially, page numbers on a contents page are meaningless once text reflows to the reader’s screen and font size, so the navigation must work by linking to chapter locations, not by citing page numbers. When you convert, you are really building the structural navigation, with an optional linked contents page on top.

How do I preserve (or rebuild) the TOC when converting a PDF for Kindle?

Rebuild it from real headings rather than trying to carry over the PDF’s page-based contents. The reliable workflow: extract and clean the text, then mark each chapter title as a proper heading in the document structure, and set chapters to start on a new section. From that heading structure, generate the logical TOC (the EPUB navigation) so the Kindle "Go To" menu lists every chapter and jumps to it. If you also want an in-text contents page, make it a list of links to those chapters — not page numbers. Then validate: open the converted file in a previewer or on a device and actually use the navigation menu to confirm every chapter is listed and lands correctly. The key mental shift is that the TOC is generated from structure, so getting the headings right is what makes the navigation work.

Why are the page numbers in my converted ebook useless?

Because a reflowable ebook has no fixed pages — the text re-flows to each reader’s screen size and chosen font, so "page 42" means nothing universal. On Kindle, what was page 42 in your PDF could be anywhere depending on the device and settings, which is exactly why ebook navigation is built around chapters and locations rather than page numbers. This is why simply carrying over a printed contents page with page numbers produces a broken-feeling ebook: the numbers do not correspond to anything the reader sees. The right approach is to drop reliance on page numbers for navigation and instead provide a linked TOC and the structural navigation menu, which point to chapter locations that remain valid no matter how the text reflows. Page numbers belong to the print edition; the ebook navigates by structure.

How do I make chapters start cleanly on Kindle?

Use real heading markup with a page-break (section break) before each chapter, rather than relying on the blank space that created the break in the PDF. In a fixed PDF, a chapter "starts on a new page" because of where it sits on the paper; in a reflowable ebook that visual gap disappears, so chapters can run straight on from the previous one unless the structure explicitly says "new chapter starts here." Marking each chapter title as a heading and applying a break-before at the chapter level makes each chapter begin cleanly on its own screen, which both reads better and reinforces the structure your TOC is generated from. So the same heading work that builds your navigation also fixes chapter starts — another reason getting the document structure right is the heart of a good Kindle conversion.

Is it safe to convert my manuscript with online tools?

Use a tool that runs on your own device for an unpublished manuscript. The first conversion steps — extracting and cleaning the PDF’s text and structure — are where many online tools upload your file to a third-party server, which you do not want for unreleased work. Client-side (in-browser) tools handle the PDF-side extraction, cleanup, and TOC/structure work locally so the manuscript never leaves your computer — ScoutMyTool’s PDF tools work this way. For the EPUB build and Kindle preview, use reputable tools and keep a private master. Confirm a tool is client-side before uploading, and always preview the converted book’s navigation on a device or in the store previewer before publishing, since that is the only way to be sure the TOC actually works for readers.

8 min read

How to convert an ebook PDF for Kindle — preserve TOC and bookmarks

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

The conversion that taught me this lesson produced a Kindle file that looked fine — until I tried to jump to chapter five and discovered there was no navigation at all. The printed contents page was there, but the device’s "Go To" menu was empty, and the page numbers on the contents page pointed at nothing, because the text now reflowed. That is the classic failure of converting a PDF ebook for Kindle: the navigation breaks, because Kindle’s chapter navigation is a structural feature a PDF usually does not carry in a reusable form. This guide is specifically about preserving — really, rebuilding — the table of contents and chapter navigation, so your Kindle edition lets readers move around it the way an ebook should.

How navigation must change from PDF to Kindle

Navigation element	In the PDF	For Kindle
Logical TOC (device "Go To" menu)	Often absent or only a printed page	Must be a real navigable TOC built from headings
Chapter jumps	PDF bookmarks (outline)	Rebuilt from heading structure, not carried over automatically
Printed contents page	Static text + page numbers	Page numbers meaningless when text reflows; link to chapters instead
Chapter starts	Visual page breaks	Real heading + page-break-before, so chapters begin cleanly
Reading position	Fixed page	Reflows; navigation is by section, not page

Step by step — keep the navigation working

Extract and clean the text. Pull the text from the PDF (OCR a scan first) and clean it for reflow — rejoin paragraphs, strip page furniture.
Mark chapter titles as headings. Apply real heading structure to every chapter title — this is what the logical TOC is generated from.
Start chapters with a break. Set a page/section break before each chapter heading so chapters begin cleanly on their own screen.
Generate the logical TOC. Build the navigable TOC from the headings so the Kindle "Go To" menu lists and jumps to every chapter.
Make the contents page link, not number. If you include an in-text contents page, link each entry to its chapter — drop page numbers, which are meaningless when text reflows.
Validate the navigation on a device. Preview in a reader or the store previewer and actually use the navigation menu and contents links to confirm every chapter is listed and lands correctly.

The principle: navigation is generated from structure

The insight that fixes lost Kindle navigation is that the table of contents is not something you copy across — it is something generated from the document’s heading structure. A PDF’s printed contents page and page numbers are artefacts of fixed pages; a Kindle’s navigation is a structural menu that only exists if the ebook has real headings to build it from. So the work is not "preserve the PDF’s TOC" but "give the conversion the structure it needs to build a TOC" — mark the chapters as headings, break them cleanly, and let the logical TOC be generated, with any in-text contents page as links rather than numbers. Get the structure right and the navigation, the chapter starts, and the device menu all fall out of it together. Then verify it on a real device, because a TOC that exists in the file but does not actually jump is no better than no TOC at all to the reader trying to find chapter five.

FAQ

Why does my Kindle conversion lose its table of contents?: Because the navigation a Kindle uses is a structural feature that a PDF often does not carry in a form the conversion can reuse. On a Kindle, the working table of contents is the "Go To" / navigation menu, which is built from a logical TOC embedded in the ebook’s structure — not from a printed contents page. A PDF frequently has only a visual contents page (static text and page numbers) and maybe some bookmarks, and those do not automatically become the EPUB/Kindle logical TOC during a naive conversion. So you end up with a book that may show a contents page but offers no working chapter navigation on the device, and whose page-number references are meaningless because the text now reflows. The fix is to rebuild the logical TOC from the document’s real heading structure as part of the conversion, rather than hoping the PDF’s existing contents survive.
What is the difference between a printed contents page and the Kindle navigation?: They are two different things, and conflating them is the root of most lost-navigation problems. A printed (or on-page) contents page is content that appears as a page in the book — a list of chapter titles, historically with page numbers. The Kindle navigation (the "Go To" menu and the progress controls) is a structural, device-level feature that lets the reader jump to any chapter from the menu regardless of where they are. A good ebook usually has both: a linked contents page for in-text browsing and a logical TOC powering the device menu. Crucially, page numbers on a contents page are meaningless once text reflows to the reader’s screen and font size, so the navigation must work by linking to chapter locations, not by citing page numbers. When you convert, you are really building the structural navigation, with an optional linked contents page on top.
How do I preserve (or rebuild) the TOC when converting a PDF for Kindle?: Rebuild it from real headings rather than trying to carry over the PDF’s page-based contents. The reliable workflow: extract and clean the text, then mark each chapter title as a proper heading in the document structure, and set chapters to start on a new section. From that heading structure, generate the logical TOC (the EPUB navigation) so the Kindle "Go To" menu lists every chapter and jumps to it. If you also want an in-text contents page, make it a list of links to those chapters — not page numbers. Then validate: open the converted file in a previewer or on a device and actually use the navigation menu to confirm every chapter is listed and lands correctly. The key mental shift is that the TOC is generated from structure, so getting the headings right is what makes the navigation work.
Why are the page numbers in my converted ebook useless?: Because a reflowable ebook has no fixed pages — the text re-flows to each reader’s screen size and chosen font, so "page 42" means nothing universal. On Kindle, what was page 42 in your PDF could be anywhere depending on the device and settings, which is exactly why ebook navigation is built around chapters and locations rather than page numbers. This is why simply carrying over a printed contents page with page numbers produces a broken-feeling ebook: the numbers do not correspond to anything the reader sees. The right approach is to drop reliance on page numbers for navigation and instead provide a linked TOC and the structural navigation menu, which point to chapter locations that remain valid no matter how the text reflows. Page numbers belong to the print edition; the ebook navigates by structure.
How do I make chapters start cleanly on Kindle?: Use real heading markup with a page-break (section break) before each chapter, rather than relying on the blank space that created the break in the PDF. In a fixed PDF, a chapter "starts on a new page" because of where it sits on the paper; in a reflowable ebook that visual gap disappears, so chapters can run straight on from the previous one unless the structure explicitly says "new chapter starts here." Marking each chapter title as a heading and applying a break-before at the chapter level makes each chapter begin cleanly on its own screen, which both reads better and reinforces the structure your TOC is generated from. So the same heading work that builds your navigation also fixes chapter starts — another reason getting the document structure right is the heart of a good Kindle conversion.
Is it safe to convert my manuscript with online tools?: Use a tool that runs on your own device for an unpublished manuscript. The first conversion steps — extracting and cleaning the PDF’s text and structure — are where many online tools upload your file to a third-party server, which you do not want for unreleased work. Client-side (in-browser) tools handle the PDF-side extraction, cleanup, and TOC/structure work locally so the manuscript never leaves your computer — ScoutMyTool’s PDF tools work this way. For the EPUB build and Kindle preview, use reputable tools and keep a private master. Confirm a tool is client-side before uploading, and always preview the converted book’s navigation on a device or in the store previewer before publishing, since that is the only way to be sure the TOC actually works for readers.

Citations

Build a navigable contents — in your browser

Generate a logical, linked table of contents from your document’s headings with ScoutMyTool — client-side, so your unpublished manuscript never leaves your computer — the structure your Kindle navigation is built from.

Open the TOC Generator →