TL;DR / Summary: Decorative Unicode looks elegant in a chapter heading and often fails on an e-reader. Embedded fonts, missing glyph coverage, and device-specific fallbacks can turn a styled heading into a row of boxes.
Why e-readers behave differently
An e-ink device renders an EPUB with its own font stack. Many readers bundle a small set of fonts and either ignore embedded fonts or substitute them for the whole book.
Decorative characters live in Unicode blocks that basic fonts may not cover. When a glyph is missing, the reader displays a fallback — sometimes a different font, sometimes a blank box.
The result is a heading that looks curated in the editor and broken on the device, which is exactly the failure authors notice last.
How the styling gets into the file
There are two routes. One is to keep plain text and style it with CSS in the EPUB. The other is to paste decorative Unicode characters directly into the text.
CSS is robust: the text stays searchable, selectable, and accessible, and the reader chooses the font. Direct Unicode is dramatic but fragile, because the appearance depends entirely on glyph coverage.
For chapter headings, use CSS first. Reserve direct Unicode for ornaments that can disappear without breaking meaning.
A safe hierarchy
- Chapter number: plain text, styled with CSS
- Chapter title: plain text, CSS letter-spacing for effect
- Ornament: Unicode acceptable if it is decorative only
- Scene break: three asterisks, not a decorative symbol
Anything a reader must understand stays in characters that every device renders.
Testing the glyphs
Before committing, test on the actual device with the actual file. Previewing in the editor’s HTML view tells you nothing about e-ink rendering.
Check three things: whether the glyph appears at all, whether it sits on the baseline, and whether it survives a font-size change. Misaligned glyphs are common and look like a formatting error.
If a character needs explaining, it is not decoration.
Also check the table of contents. Readers generate the TOC from the heading text, and decorative characters there can produce an unreadable navigation list.
Accessibility and screen readers
Screen readers may announce decorative characters by name or skip them entirely. A heading full of ornate symbols can produce a long, confusing announcement before the actual title.
Mark purely decorative elements so assistive technology can ignore them, or use CSS-generated ornaments instead of characters. CSS ornaments are not read aloud.
This is not a niche concern: audiobook-adjacent reading and accessible EPUBs are a growing part of the market, and a broken heading is a real defect.
Fonts and embedding
If you do embed a font, embed only the subset you need and confirm the licence permits it. Many decorative fonts restrict embedding, and an EPUB is a distribution.
Test with the embedded font disabled. If the book still reads well without it, the typography is doing its job; if the headings collapse into boxes, the design depends on something most readers will not load.
Keep file size in mind. A full decorative font can add megabytes to a novel, and readers on older devices will feel it on every page turn.
A practical style that survives
Use a plain heading with generous letter-spacing, a small caps effect, and a thin rule. It reads as designed on every device and needs no special characters.
Add one decorative element at the start of each part rather than each chapter. Rarity makes it feel intentional, and a single ornament is easy to test.
If you do want decorative letters, generate them, paste them, then test on two devices and one phone app. Any character that fails on one of the three should be removed.
Generators such as the freaky font generator are convenient for drafts and social posts; for a book file, treat their output as a proposal rather than a final. The device decides.
Finally, read the chapter opening on the smallest screen you own. If it looks deliberate there, it will look deliberate everywhere.
Checking the table of contents and search
Many readers build navigation from heading text. Decorative characters in a heading appear in the contents list, often truncated or converted to boxes.
Test the contents panel on a real device after conversion. It is the fastest way to see how the styling survives.
Search is affected too. A reader searching for a chapter name will not find it if the letters are mathematical script characters.
If a heading cannot be searched, it is a picture of a heading.
Keep decorative elements out of the heading tag entirely. Put them in a separate element that styling can hide without losing the text.
Run one full conversion through the retailer’s previewer before publishing. Previewers are stricter than readers, and passing them is a good sign.
Small screens and large type
Readers with large type settings reflow everything. Decorative Unicode does not reflow; it scales unevenly and can collide with the line above.
Test at the largest font setting the device offers. That setting is where headings break first.
Test at the extremes, because that is where readers who need help actually are.

