
If Generate CSS is disabled during Affinity fixed-layout EPUB export, no CSS is generated for text styles even when their individual Emit CSS controls are enabled. Inspect the global export setting before editing every style or assuming the document's typography is corrupted.
Key Takeaways
- Global Generate CSS can override per-style Emit CSS.
- Class names and generated rules are different output decisions.
- External stylesheet workflows need their own deliberate verification.
Check the global control first
The Affinity fixed-layout EPUB guide explicitly documents the override. Reopen the intended export setup and inspect Generate CSS. Record whether the book is meant to use generated styling or a separately managed stylesheet.
For a hypothetical photo workbook, the heading styles may all have Emit CSS enabled while a previous export preset disabled CSS globally. Changing each heading style again does not address that global decision.
Inspect one representative style
Open the intended style from the Text Styles panel, choose its edit command and inspect Export Tags under EPUB. Check the export tag, Include class in HTML, class name and Emit CSS as relevant to the workflow.
A class attached to an element is not itself a definition of how that class looks. Conversely, disabling generated style rules can be intentional when a separate stylesheet supplies them. Do not create several conflicting copies of the same rules merely to make one preview look right.
The object-level override guide illustrates a related hierarchy question in another application. It does not change Affinity's documented precedence.
Keep semantic roles separate
A heading's HTML tag communicates structure; CSS controls presentation. A visually bold paragraph is not necessarily an appropriate heading. The export-tagging guide provides conceptual background for that separate decision.
Retain important wording as text when it needs revision or personalization. The editable-name guide reinforces that keeping text editable does not remove the need for correct semantic roles and styling.
Inspect the final EPUB
Export a representative section and verify the actual stylesheet and element relationships with suitable tools. Then open the book in the target reader and inspect the intended headings, body text and captions. A screenshot cannot establish which rules were generated or applied.
Affinity's preflight guide lists some export-related issues, including conflicting class names, but it cannot decide whether your external stylesheet implements the design correctly.
Acceptance might require the intended global policy, a known heading class with the correct rule source, readable captions and no unexpected fallback appearance. Record the export preset so the next revision preserves that policy.
This is documentation-based troubleshooting with a hypothetical workbook. It does not claim that a stylesheet was executed or that one reader's appearance proves universal EPUB support.
Keep external stylesheet ownership clear when several editors collaborate.
Related tasks
- Why Does One InDesign Object Export Differently From the Rest of My EPUB?
- Why Does My Large InDesign Heading Export as an Ordinary Paragraph in an Accessible PDF?
- 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: Document export Generate CSS overrides style-level setting.
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.