Why Fancy Text Doesn't Work on Every Platform
Rendering, moderation and validation are three separate reasons a style can fail. Knowing which one you hit tells you what to do next.
Three different failures
When a style "does not work", one of three quite different things has happened, and they call for different responses.
- Rendering failure: the characters arrived but appear as boxes. A font problem on the reader’s device.
- Validation failure: the platform refused to save your input. A rule about which characters a field accepts.
- Normalisation: the platform silently converted your text back to plain letters. A deliberate policy choice.
Why platforms normalise or reject
Usernames and display names are the strictest fields, and for good reason. Visually confusable characters are a standard impersonation technique, and text that search cannot match makes accounts harder to find and to moderate. Many platforms therefore restrict identity fields to a narrow character set while allowing far more in bios and posts.
Heavily stacked combining marks are restricted for a different reason: they can overflow their line, obscure surrounding interface elements and slow text layout badly. Most platforms cap or strip them.
What to expect in practice
Platform behaviour changes without notice and differs between the web, iOS and Android clients of the same service. Treat any compatibility claim — including ours — as a starting point to test rather than a guarantee. The reliable move is to paste your text, save it, and then view your own profile from a different device before relying on it.