You generated a great-looking bio, pasted it somewhere, and got back three empty squares: □□□. Annoying, and completely fixable once you know what’s happening.

What those boxes actually are

That square is a replacement glyph, officially called .notdef. Every font file contains one. When your device is asked to draw a character that the active font has no drawing for, it reaches for the fallback shape — and most fallback shapes are an empty rectangle or a box with a question mark in it.

So the boxes are not a bug in your text. They’re your device telling you: “I have the code point, but I don’t own a picture of it.”

The real cause: font coverage, not Unicode support

This distinction trips people up constantly.

  • Unicode support means the operating system understands the number U+1D5A4 and can store, sort, and transmit it.
  • Font coverage means some font on your device contains an actual drawing for that number.

Your phone can support Unicode perfectly and still render boxes, because the default system font simply doesn’t include a glyph for that specific code point. Older Android builds and low-cost devices ship thinner fonts and hit this far more often than iPhones do.

Which styles break most often

Ranked by how frequently we see reports:

  1. Fraktur / gothic (𝔉𝔯𝔞𝔨𝔱𝔲𝔯) — the worst offender. These live in the Mathematical Alphanumeric Symbols block and many system fonts skip them entirely.
  2. Double-struck (𝔻𝕠𝕦𝕓𝕝𝕖) — same block, same problem.
  3. Full-width (Ｆｕｌｌｗｉｄｔｈ) — renders fine on most phones, but looks broken in apps that use tight line spacing.
  4. Braille and upside-down — upside-down relies on obscure combining ranges and often collapses mid-word.

Which styles are safest

If you need it to render on essentially every device made in the last decade, use:

  • Bold (𝐛𝐨𝐥𝐝) and italic (𝑖𝑡𝑎𝑙𝑖𝑐) — widest coverage of any styled alphabet.
  • Circled (ⓒⓘⓡⓒⓛⓔⓓ) — well supported, but caps-only for many letters.
  • Small caps (sᴍᴀʟʟ ᴄᴀᴘs) — good coverage, subtle look.
  • Combining decorations — strikethrough (s̶t̶r̶i̶k̶e̶) and underline (u̲n̲d̲e̲r̲) keep your original letters and layer marks on top. Because the base characters are plain A–Z, they render almost everywhere. This is the single most reliable decorative option.

Platform-by-platform notes

Instagram — bio renders most styles fine. Display names get rejected more often than bios. Stories are stricter than feed captions.

TikTok — display names and bios generally accept styled text, but the app silently strips some combining marks on older versions.

Discord — server nicknames allow fancy text; usernames mostly do not. Discord also normalizes some characters, so test before you commit.

WhatsApp — status and bio are permissive. Group names are fine.

X / Twitter — display names are fine, but the character counter counts some styled characters as two.

YouTube comments — the strictest of the major platforms. Many styled alphabets get filtered out.

The 30-second test before you commit

  1. Paste your text into a plain notes app first. Boxes there = it’ll be boxes everywhere.
  2. Paste into the real target field.
  3. Switch apps, then come back and look again. Some platforms render on write but normalize on reload.
  4. Ask a friend on a different phone to screenshot it. Android and iOS disagree more often than you’d expect.

Why screen readers struggle too

Even when the glyph renders, accessibility tools often read these characters badly. A screen reader may spell out “mathematical bold capital A” or skip the character entirely. That’s the reason we recommend using fancy text for display names and short bios, never for body copy, headings, or anything a person genuinely needs to read.

Decorate the label. Keep the content plain.