Boxes Are the Reader's Device Talking, Not Yours
You styled your name, it looked perfect, and a friend replied: "it's just squares for me." The instinct is to assume you did something wrong. You didn't.
Here is the one fact that explains the whole thing: the styled "fonts" you copy from a generator are not fonts at all. They're ordinary text made of special Unicode characters — the bold "𝗮" is a different character from a normal "a," not the same letter wearing a costume. When you paste them, the characters travel with your message. What happens next is entirely up to the reader's device.
Every device keeps a set of fonts that map characters to little pictures called glyphs. When a device meets a character it has no glyph for, it draws a placeholder: the .notdef box — □ or ▯ — nicknamed "tofu" (the font family Noto is literally named "no more tofu"). So the box isn't your text failing. It's the reader's device saying "I received this character, but I don't own a picture for it."
The Failure Is Invisible to the Author
This is what makes boxes so frustrating: you can't reproduce the problem on your own phone. Your device has the glyph, so it renders perfectly for you, every time. Meanwhile a chunk of your audience — often older Android phones, certain web browsers, or specific apps — sees a row of squares.
That asymmetry is why "my bio looks broken to some people" is one of the most-asked questions across Discord, Instagram and TikTok. The author and the audience are looking at the same characters through different fonts.
The Style Safety Tiers
Not all styles are equally risky. Support tracks how widely a style's underlying Unicode block is shipped in device fonts. Here's the hierarchy, safest first.
| Tier | Styles | Why | Use for |
|---|---|---|---|
| 1 · Universal | Bold & italic sans, bold/italic serif, 𝚖𝚘𝚗𝚘, small caps | Mathematical Alphanumeric block — shipped almost everywhere | Anything important: names, hooks, CTAs |
| 2 · Mostly safe | Fullwidth, Ⓒⓘⓡⓒⓛⓔⓓ, monospace symbols | Common blocks, occasional gaps on very old devices | Decorative emphasis, captions |
| 3 · Risky | 𝔉𝔯𝔞𝔨𝔱𝔲𝔯, 𝕯𝖔𝖚𝖇𝖑𝖊-𝖘𝖙𝖗𝖚𝖈𝖐, enclosed/squared, decoratives | Sparse coverage on older Android & some apps | Throwaway flair only — never load-bearing |
| 4 · Fragile | Z̸̢a̵l̷g̶o, obscure symbol runs, regional decoratives ꧁☬꧂ | Combining marks & rare glyphs break or look broken | One-off jokes; expect breakage |
The rule of thumb: the prettier and more unusual a style looks, the fewer devices can draw it. Decorative cursive and blackletter are exactly the styles people reach for in bios — and exactly the ones most likely to turn into tofu.
Three Rules That Keep Your Text Readable
1. Never style a load-bearing word alone
If a word must be read — your name, a link, a price, a call to action — keep it in plain text or a Tier 1 style. If it turns to boxes, your message still survives.
2. Keep meaning in the plain layer
Treat styling as a topcoat, not the structure. A reader who sees only boxes should still get your point from the unstyled words around them.
3. Apply the 2-device test
Before a style goes into a bio, view it on a second device — ideally an older Android phone, the worst-case renderer. If it survives there, it'll survive almost anywhere.
Boxes vs Question Marks vs Garbled Text
The character arrived fine; the device has no glyph to draw it. A font problem. Fix it by choosing a safer style.
The character was lost or mis-decoded in transit. A data problem. The styling won't help — the text itself changed.
"Mojibake" — bytes read with the wrong encoding. Also a data problem, usually from a broken copy/export step.
This guide is about the first one — a font problem you fix by choosing a safer style. The other two are data problems: the characters themselves changed in transit, so no style choice will bring them back.
Where Boxes Show Up Most
- Discord — styled names render for most desktop users, but older Android clients and screen readers struggle. See Discord text formatting decoded.
- Instagram & TikTok — bios render via the viewer's system fonts, so the same bio can look crisp on iPhone and broken on a budget Android.
- Older Android, generally — the single most common source of tofu. If you only test on an iPhone, you're testing the easy case.
- iPhone specifically — testing on iOS isn't a free pass. Apple's system font, San Francisco, doesn't cover the same Unicode ranges Google's Noto font does on Android, so certain decorative and rare-block styles that render fine on Android can still turn to boxes on iPhone. Treat both platforms as separate tests, not one stand-in for the other.
The reader's device simply ran out of pictures.
Style for the worst phone in the room, not the best.
Generate text in a device-safe style
Pick a Tier 1 style — bold, italic or small caps — and it'll render almost everywhere. Type it once, copy it, paste it anywhere.
Open the Text Generator →