Styled text fails in three distinct ways, and the fix depends on which one you hit. Empty boxes mean your font lacks a glyph. Characters that vanish or revert mean the app rejected them. Text that reads as gibberish to a screen reader means the characters are working exactly as designed and are simply not letters.
Boxes, also called tofu
A rectangle — sometimes with hex digits inside — means the character is valid Unicode but the font in use has no glyph for it. Nothing is broken; the drawing instructions are simply absent. This is most common with newer additions and with supplementary-plane characters above U+FFFF, which many older fonts skip entirely. It varies by device, so a style that looks fine on your laptop can break on someone's phone.
Characters that disappear after saving
You paste a styled name, save, and it comes back plain or truncated. That is input validation, not rendering. Many services normalise text on submission, restrict identifier fields to a basic character set, or strip characters from scripts they do not expect. This decision is made by the app and can change without notice, which is why no site can honestly promise a style will keep working.
Only part of the text converted
Unicode's styled alphabets were designed for mathematical notation, not for decoration, so they have gaps. Several Fraktur and script letters live in the Letterlike Symbols block rather than the main range and are drawn differently. Digits have no italic form at all. A good generator leaves unsupported characters visible rather than substituting unrelated lookalikes, so what you see is the honest result.
It looks different on another device
Unicode standardises which character a code point is, not how it is drawn. Every platform ships its own fonts. The same string can be a different weight, width or shape elsewhere, and characters with an emoji presentation can appear as flat text in one place and a colour image in another.
How to narrow it down
Test the exact field you plan to use — a bio and a username often follow different rules on the same service. Try a simpler style such as bold or small caps, which use the oldest and best-supported ranges. Paste a suspect character into a Unicode lookup to confirm what it actually is. And check on the kind of device your audience uses, not only your own.
When to stop fighting it
If a style keeps reverting after two or three attempts, the service is rejecting it. No amount of retrying changes that. Pick a style from a better-supported range, or keep the field plain and put the decoration somewhere with fewer restrictions.
References
Related tools and guides
Last updated September 2026 · Editorial policy · How we verify Unicode claims