Why Does Fancy Text Show Up as Boxes (□)?
Those empty boxes are called "tofu". They appear when a device lacks a font for the Unicode characters behind fancy text — here is the full explanation, and how to avoid them.
Why Fancy Text Looks Like Gibberish to Other People
⚡
Fancy text can look like gibberish to others because each device decides for itself how to render and read those Unicode characters. A missing font shows boxes; an app that strips styling shows plain letters; a screen reader announces each character by its formal Unicode name, such as "mathematical bold a". The data is consistent — the presentation is not.
You see style, they see something else — why?
When you copy fancy text, you are sending exact Unicode code points, not a picture. What the recipient sees depends on three independent decisions their system makes: which font to draw each character with, whether the app keeps or strips unusual characters, and how assistive technology reads them aloud. You control none of these from your end.
So the same string can arrive three different ways: styled (their font has the glyphs), boxed (it does not — see why fancy text shows up as boxes), or flattened to plain letters (the app normalised it).
What screen readers do with fancy text
This is the part most people never see, and it is the strongest reason to use styled text sparingly. Screen readers identify characters by their Unicode names. A normal "h" is read "h", but a mathematical-bold "𝐡" carries the formal name listed in the Mathematical Alphanumeric Symbols chart, so it may be announced as "mathematical bold h" — or skipped entirely if the reader has no entry for it. A whole styled word can become a slow stream of "mathematical italic" prefixes, which is genuinely hard to follow.
This is not a niche edge case the standards bodies overlooked; it is the documented downside of the characters. For accessibility, keep styled text decorative and short — a name or a flourish — and never put essential information (instructions, links, important words) in fancy characters only.
Why does some text arrive as plain letters?
Some platforms run Unicode normalization or simply restrict input, which can convert or remove styled characters. Username fields are the clearest example: they reject styled Unicode by design, so your careful styling lands as plain text or is refused. This is the same mechanism behind Discord's lowercase username rule and Instagram's handle restrictions.
The three ways styled text can degrade
| What the other person gets | Cause | Means |
|---|---|---|
| Boxes (□) | Their font lacks the glyph | Device font gap |
| Plain letters | App normalised or stripped styling | Platform restriction |
| "Mathematical bold a"… | Screen reader announces Unicode names | Assistive technology |
How to keep fancy text readable
You cannot control the recipient's device, but you can lower the odds of gibberish:
- Use widely supported styles — bold, italic, script and double-struck render almost everywhere.
- Keep it decorative — style a name or a highlight, not a full paragraph.
- Never hide essential info in fancy characters — links, handles and instructions stay plain.
- Test on a second device before anything important goes out.
Our generator labels each style's platform safety and flags missing letters, so you can choose a low-risk look from the start.
How can you check what other people will see?
Since you cannot control the recipient's device, the fix is to preview the text the way they will see it. Paste it into the actual destination — the real bio, message or caption box, not just a generator preview — and read it there. Then check it on a different system: if you wrote it on an iPhone, look on Android, an older phone, or a desktop browser.
The most honest test is another person. A friend on a different platform sees precisely what your audience sees, including boxes and stripped styling. For anything that matters, that thirty-second check beats discovering the problem in the replies. A generator's platform-safety label is a useful first filter, but a real second device is the proof.
Does fancy text affect search and SEO?
Yes, and it matters more than most people expect. Search engines and on-platform search read the underlying characters, and styled Unicode does not match a plain-text query — someone searching your normal name may not find a fully stylised version. This is exactly the problem the W3C flags: using these math symbols just to pick a font "would create problems for searching, restyling (e.g. for accessibility), and many other kinds of processing." Some systems normalise the text back to plain letters; others simply fail to match. Either way, heavy styling in the words people search for can cost you visibility.
So keep names, handles, headings and anything you want found in plain text, and treat fancy characters as decoration around them. The same logic applies to links and instructions: a styled URL is neither clickable nor typeable. Used as a flourish rather than a wrapper for essential words, styled text looks good without quietly hurting how people reach you.
The one-sentence summary
Fancy text is real, portable Unicode — but how it looks and reads is decided entirely by the viewer's device, so favour well-supported styles and keep anything important in plain text. Experiment safely in the FancyTextZone generator, and if you specifically see boxes rather than gibberish, start with why fancy text shows up as boxes.
Frequently asked questions
Their app normalised or stripped the styling — common in fields that restrict input, like usernames. The characters were converted to plain letters on their end. The data you sent was still the styled Unicode.
Often poorly. They announce characters by Unicode name, so styled letters become "mathematical bold a" and similar, or get skipped. Keep styled text decorative and never put essential information in fancy characters alone.
Used heavily, yes. Styled Unicode is hard for screen readers and can be unreadable on devices with limited fonts. A short decorative flourish is fine; a full styled message is not.
Boxes mean the viewer's font lacks a glyph; plain letters mean the app stripped the styling; a screen reader spelling out "mathematical bold" is assistive technology reading Unicode names. The code points you sent never changed — only each device's response to them did.
Use the core styles, keep it short and decorative, and keep essential information in plain text. Then preview it somewhere other than the phone you typed it on — that one check catches most surprises. The generator's platform-safety labels help you pick a low-risk style up front.
It can. Search matches the underlying characters, so a fully stylised name or heading may not match a plain-text query, and some platforms normalise styled text back to plain letters. Keep anything you want found — names, handles, headings — in plain text.
Each phone renders the characters with its own fonts and may normalise text differently. One device has glyphs for a style and shows it; another lacks them and shows boxes, or strips the styling to plain letters. The text you sent is identical — the devices differ.
→
Ready to try it yourself? Open FancyTextZone generator