
A visible contents page is not automatically the EPUB reader's navigation document. In current Affinity desktop, set the intended table of contents to EPUB: Primary on the Table of Contents panel so it supplies the navigation document for fixed-layout EPUB export.
Key Takeaways
- Printed-style contents and reader navigation are separate features.
- Use the intended generated TOC as the primary EPUB navigation source.
- Test destinations in the actual exported book.
Identify the real table of contents
The Affinity fixed-layout EPUB documentation describes an interactive navigation document that readers can open from anywhere. It instructs users to place the insertion point within an existing TOC and set its Type to EPUB: Primary.
Confirm that the visible list is a real table of contents rather than manually typed headings and page numbers. A decorative text list may look correct without participating in the documented navigation workflow.
Choose one deliberate navigation plan
For a hypothetical portrait handbook, the primary navigation might contain Preparation, Lighting, Retouching and Delivery. Decide which sections should be directly reachable and ensure the relevant headings and TOC configuration support that structure.
Do not substitute a manually drawn page list just to match the print design. The bookmarks-without-visible-contents guide provides a useful conceptual comparison: on-page appearance and reader navigation are independent, although PDF and EPUB use different mechanisms.
Keep generated content accurate
Review the TOC after edits to headings or document structure. A corrected chapter title in the body does not prove the navigation source has been updated. If the TOC is generated, make changes through its intended source and update workflow instead of relying on fragile manual corrections.
The TOC update guide discusses that broader production risk in another application. Affinity's preflight documentation explicitly flags TOC entries needing an update after referenced text is added, modified or deleted, and documents Fix for that issue. Use it when that specific finding appears, then recheck the source. The TOC instructions also provide Text > Table of Contents > Update for one selected TOC, or Update All Tables of Contents for all. An updated source TOC still needs the actual EPUB navigation test below.
Verify the reader's menu and destinations
Open the exported EPUB in the intended reader, display its navigation menu and follow every primary entry. Check both the entry wording and the destination content. A menu that opens is insufficient if “Delivery” leads to an earlier draft section.
Distinguish printed page numbers from actual reading locations. The page-order guide explains why visual numbering should not be used as the only validation evidence.
Acceptance could require four intended sections in the navigation menu, accurate titles, correct destinations and a usable way back to continued reading. Keep the visible contents page if it serves the design, but verify it separately.
This guide follows documented current-app controls and a hypothetical handbook. It does not claim an exported navigation file was inspected or promise identical menus in every EPUB reader.
Retest destinations after moving sections, since an earlier successful navigation check does not establish the accuracy of the revised edition.
Related tasks
- Can I Add PDF Navigation Bookmarks Without a Visible Contents Page in InDesign?
- Why Does Updating My InDesign Table of Contents Undo My Manual Corrections?
- Why Does PDF Page 1 Appear as Page 5 in the Viewer?
Sources and scope
- Fixed-Layout EPUB: EPUB: Primary TOC type creates navigation document.
- Preflight: A named TOC update warning and its documented Fix.
- Table of contents: Manual generated-TOC update controls.
Guidance follows current Affinity desktop documentation. Worked examples and checks are proposed, not measured software tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.