
An Affinity text style whose EPUB Export Tag is set to [No change] inherits that setting from the style it is based on. If a custom heading exports as the wrong element, inspect the style relationship and choose the intended tag deliberately. Font size alone does not determine its role.
Key Takeaways
- [No change] can inherit an unexpected export tag.
- A custom visual style still needs a meaningful document role.
- Check the actual exported structure, not just appearance.
Trace the style relationship
The Affinity fixed-layout EPUB documentation describes export tags and inheritance. Its built-in Heading 1, Heading 2 and Body styles have documented default roles, but a custom style can inherit from another base.
For a hypothetical photo handbook, a custom “Technique Title” style may be based on body text for visual convenience. If its export tag remains inherited, the output may not express the intended section heading. Confirm the actual based-on style before changing a global base used throughout the book.
Assign the role that matches the content
Open the custom style's settings from Text Styles and inspect Export Tags under EPUB. Choose the intended structural role in the context of the publication's heading hierarchy. Do not turn every large caption into a top-level heading merely because it is visually prominent.
The heading-tagging guide explains the broader semantic distinction. Its commands belong to another application, so use the current Affinity controls here.
If the style is genuinely a caption, preserve that meaning rather than using a heading tag to force a particular visual result.
Check related publication behavior
Heading structure can affect navigation planning, but a correct tag alone does not establish a complete contents menu. The EPUB section-splitting guide illustrates how publication structure and styling can interact in another workflow.
Keep important text editable when revisions are expected. The personalized book-text guide provides that separate source-preservation context. Neither editability nor attractive typography proves that export semantics are correct.
Verify one section end to end
Export a representative section and inspect its actual HTML structure with a suitable EPUB tool. Then check how the target reader exposes the heading and its surrounding content. Verify parent and child headings rather than checking a single isolated tag.
Affinity preflight can help identify supported issues, but it does not supply an editorial hierarchy for the handbook.
Acceptance might require the chapter title as the intended top-level heading, technique titles at the next appropriate level and photo captions outside that hierarchy. Record the explicit tag choice and style relationship so later style changes do not reintroduce ambiguity.
This workflow is documentation-based and uses a hypothetical style. It does not claim an EPUB structure was inspected or certify a complete accessible heading hierarchy.
Related tasks
- Why Does My Large InDesign Heading Export as an Ordinary Paragraph in an Accessible PDF?
- Why Did My InDesign EPUB Become One Long Chapter Instead of Separate Sections?
- How Do I Add a Child’s Name to an AI Picture Book Without Garbled Text or Broken Pages?
Sources and scope
- Fixed-Layout EPUB: No change inheritance under text-style Export Tags.
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.