Why Some Social Media Apps Don't Support Fancy Unicode Fonts

You pasted 𝒽𝑒𝓁𝓁𝑜 into a bio. The generator looked perfect. The app shows empty squares, or it silently deletes the letters, or it looks fine on your phone and broken on your laptop. That's not you "doing Unicode wrong." The receiving app never promised to draw those characters.

I get this complaint every week. I'd rather explain the three failure modes than ship another "works everywhere" claim. It doesn't. Here's why.

Tofu: the font never shipped the glyph

A font is a box of drawings and Unicode is only a list of numbers, so if the number isn't in the box the renderer has nothing to paint except a guess. Some systems substitute a fallback font. Some draw tofu, the empty rectangle. Some draw a question mark in a diamond. Same miss.

Phone vendors cut font files to save megabytes. A cheap Android build might skip Mathematical Alphanumeric Symbols entirely. iOS includes more of that block than it used to, and still drops odd corners. Desktop Chrome on Windows may pull in Segoe UI Symbol or Cambria Math. A WebView inside a social app may not.

That's why the same paste can live in Notes and die in an in-app browser. Two different font stacks. Unicode's FAQ on unsupported characters is blunt about this: the standard assigns the number. It does not ship the picture.

Sanitizers: the app throws the letters away

Some products treat unusual code points as an attack. Fair, sometimes. Zalgo stacks can blow up a layout. Homoglyphs can fake a username. A filter that strips "anything not Latin-1" will also murder your cute bold 𝗛𝗲𝗹𝗹𝗼.

I've seen bios saved on iOS, then stripped on Android after a sync, because two clients disagreed about the allowed set. I've seen comments that render in the composer and arrive as ?????. The composer used a full system font. The server stored a "safe" subset.

Usernames are stricter than bios. Captions are stricter than comments in a few apps, which feels backwards until you remember captions get indexed. Search teams hate mystery characters. They'd rather you shout in ASCII.

The generator lied about "fonts"

If another site rendered the preview in a webfont, you saw a costume the destination app doesn't wear. textzy previews with whatever your browser already has, which is closer to reality, and still not identical to Instagram's in-app WebView. The copy-paste fonts guide covers the character-vs-font mix-up. This page is the "and then the app shrugs" sequel.

Preview on the device you care about. Paste into a draft, not the live bio, if you're about to run an ad against that profile. I learned that after a campaign screenshot showed tofu in the handle. The ads account was on desktop. My phone had been lying to me for a week.

Which styles survive more often

Plain emoji: mostly fine, until a new one hasn't landed in the OS yet. Enclosed Ⓐ: mixed. Fullwidth Ｈｅｌｌｏ: mixed, and it looks like a ransom note in Western UI. Math bold and italic: better than Fraktur on recent iOS and Android, still not universal. Script: pretty, fragile. Zalgo: please don't, unless the glitch is the joke. Combining marks are how layouts explode. I wrote that up in the Zalgo guide.

Small caps and superscript fail in the same way bold math fails: missing glyphs, plus a second problem where the letters are too light to read at bio size. See the tiny letters guide if that's your whole aesthetic.

What I'd do instead of praying

Keep a Latin backup of the name in the same profile. Test paste in the actual app, both iOS and Android if you have friends. Avoid mixing five generators. Every extra block is another chance the font pack skipped a range.

If the look has to match on every screen, you're in image territory. A PNG of a word will look identical and will fail copy, search, and readers. That's a branding choice, not a Unicode choice. The Instagram fonts tool is for paste. Don't hire it as a logo renderer.

Version skew is its own failure

Your phone updated. Your follower's phone didn't. A new emoji is the famous version of this. Mathematical script is quieter and more annoying, because it fails as a box instead of a cute missing-face glyph. I'd rather a missing emoji than tofu in the middle of a name. At least people know what an empty emoji slot means.

Web apps that wrap a system WebView inherit whatever OS font pack is sitting there. Native apps can bundle a font. Most social apps don't bundle Cambria Math so your bio can look like a textbook. They bundle a UI font and pray. Prayer is not a rendering strategy, but it's the one we have.

If you're documenting a bug for a client, screenshot both ends, because "works on my iPhone 16" is not a repro when the ads account is on desktop and the follower who filed the ticket is on a two-year-old Android skin that never shipped Fraktur. Write the OS version. Write the app version. I've closed tickets that were just two people on different majors arguing about a character that only one of them could see, which is a font-pack fight dressed up as a generator bug. Preview in the actual composer, save as a draft, then check a second device before you print the handle on a poster that can't be patched with a paste.

I still preview a styled handle in a draft, then open the same draft on a friend's Android, because my laptop has been lying to me for years about what a cheap WebView will actually paint. Version skew is quieter than a missing emoji: you get tofu in the middle of a name instead of a cute empty-face glyph people already know how to read. If the look has to match on every screen, you're in image territory, which is a branding choice, not a Unicode choice, and the Instagram fonts tool on this site is for paste rather than a logo renderer that followers can't copy.

Common Questions

Why does it work in iMessage but not in the app? iMessage uses Apple's full font set. Lots of in-app WebViews use a thinner stack, or they filter on the way in.

Did Unicode break? No. Unicode assigned the characters. The app didn't draw them, or it refused to store them.

Can I force a font on my followers? Not with copy-paste text. Followers render with their OS. You don't ship a .ttf in a bio.

Is there a "safe" fancy set? Safer, not safe. Recent math bold/italic on current iOS and stock Android is the least cursed. I still wouldn't put a legal name in it.

The letters can be real and still be unwelcome, because a chat app would rather keep the layout standing than draw every souvenir you copied from a generator. Fancy paste is optional, and I'd rather a bio survive a cheap WebView than look expensive for one afternoon on my own phone.