Fancy Text Compatibility Guide
Our fancy text compatibility guide covers 8 Unicode styles — bold, italic, script, gothic, bubble, monospace, underline, and strikethrough — across 6 major platforms, plus why boxes, missing glyphs, and accessibility issues happen.
8
Text Styles Compared
6
Platforms Covered
4
Limitations Explained
Free
Cheat Sheet Download
Ratings reflect Unicode block coverage and widely-reported platform rendering behavior, not exhaustive device-by-device lab testing. Click a style to open its generator.
| Style | Example | TikTok | Discord | X | |||
|---|---|---|---|---|---|---|---|
| Bold | 𝗕𝗼𝗹𝗱 𝗧𝗲𝘅𝘁 | Reliable | Reliable | Reliable | Reliable | Reliable | Reliable |
| Italic | 𝘐𝘵𝘢𝘭𝘪𝘤 𝘛𝘦𝘹𝘵 | Reliable | Reliable | Reliable | Reliable | Reliable | Reliable |
| Script / Cursive | 𝒮𝒸𝓇𝒾𝓅𝓉 𝒯𝑒𝓍𝓉 | Reliable | Reliable | Mixed | Mixed | Reliable | Reliable |
| Gothic / Fraktur | 𝔊𝔬𝔱𝔥𝔦𝔠 𝔗𝔢𝔵𝔱 | Reliable | Mixed | Mixed | Mixed | Reliable | Reliable |
| Bubble / Circled | Ⓑⓤⓑⓑⓛⓔ Ⓣⓔⓧⓣ | Reliable | Reliable | Reliable | Reliable | Reliable | Reliable |
| Monospace | 𝙼𝚘𝚗𝚘𝚜𝚙𝚊𝚌𝚎 | Reliable | Reliable | Mixed | Reliable | Reliable | Reliable |
| Underline | U̲n̲d̲e̲r̲l̲i̲n̲e̲ | Mixed | Mixed | Mixed | High risk | Mixed | Mixed |
| Strikethrough | S̶t̶r̶i̶k̶e̶t̶h̶r̶o̶u̶g̶h̶ | Mixed | Mixed | Mixed | High risk | Mixed | Mixed |
Rendering issues almost always trace back to which Unicode block a style comes from and how complete that block is.
Mathematical Alphanumeric Symbols (Bold), U+1D400–U+1D433
Full A–Z, a–z, and 0–9 coverage in one contiguous block, so fonts almost never substitute a box. The safest fancy style for bios, captions, and usernames where usernames allow Unicode at all.
Open the Bold Fonts generator →Mathematical Alphanumeric Symbols (Italic), U+1D434–U+1D467
Nearly complete coverage. One quirk: italic mathematical "h" isn't in this block. It lives at U+210E (the Planck constant symbol), so generators substitute it in. On a few older fonts that one letter can look subtly different from the rest of the word.
Open the Italics Fonts generator →Mathematical Script, U+1D49C–U+1D4CF (with gaps filled from Letterlike Symbols)
The script block has real gaps. Capital B, E, F, H, I, L, M, and R aren't defined in the math-script range, so generators borrow them from the older Letterlike Symbols block instead. Most modern phone fonts cover both blocks. Some desktop apps and older Android system fonts only ship one, which is where you occasionally see a stray box in an otherwise clean script word.
Open the Cursive Fonts generator →Mathematical Fraktur, U+1D504–U+1D537 (with gaps filled from Letterlike Symbols)
Same gap pattern as script text: capital C, H, I, R, and Z fall back to Letterlike Symbols glyphs. Fraktur is also the style most likely to get flagged or auto-stripped by display-name filters, since it can resemble an attempt to impersonate normal text.
Open the Gothic Fonts generator →Enclosed Alphanumerics, U+24B6–U+24E9
One of the oldest, most completely defined Unicode blocks for this purpose, so rendering stays reliable everywhere. The real downside isn't boxes. Screen readers often read each character out as "circled latin small letter a" instead of the plain letter, which hurts accessibility more than any other style in this table.
Open the Bubble Fonts generator →Mathematical Monospace, U+1D670–U+1D6A3
Character coverage is complete and boxes are rare. The catch is cosmetic, not technical: these characters only look evenly spaced if the app's font renders them at a fixed width. Discord already has real backtick-code monospace via markdown, so pasting this style there is usually redundant and can look uneven next to Discord's own code font.
Open the Monospace Fonts generator →Combining Low Line, U+0332 (applied after every character)
This isn't a letter substitution. It's a combining mark stacked on top of every normal character. Short strings usually display fine. Long strings risk clipped marks (each one counts against character limits), marks dropped by text normalization, or removal by anti-spam filters that treat repeated combining marks as a zalgo pattern. Cursor placement and editing inside the field can also behave oddly.
Open the Underline Text generator →Combining Long Stroke Overlay, U+0336 (applied after every character)
Same combining-character mechanics and the same risks as underline text. WhatsApp is the most likely to disappoint here, since it already has its own native ~strikethrough~ markdown. Pasted Unicode combining marks can render inconsistently across WhatsApp mobile, desktop, and Web depending on the client version.
Open the Strikethrough Text generator →Four limitations apply to fancy Unicode text no matter which platform you're posting on.
A box, sometimes called "tofu," appears when the viewer's device has no font installed for that exact Unicode code point. Fancy text styles aren't new letters. They're separate, lookalike characters from specialized Unicode blocks, mostly Mathematical Alphanumeric Symbols and the older Letterlike Symbols block. Bold, italic, bubble, and monospace styles sit in cleanly defined ranges that almost every modern system font covers. Script and gothic/fraktur are the most exposed, since a handful of their letters are historical carry-overs from a different block, and not every font ships both.
Underline and strikethrough work by inserting an invisible combining character after every visible letter, instead of swapping in a new letter shape. That makes them fragile in three ways. Character-limit counters count each combining mark separately, so a caption can run out of room faster than it looks. Some apps run text through Unicode normalization that merges or drops combining marks. Anti-spam filters sometimes flag long runs of combining marks as a zalgo/glitch-text pattern and strip or reject them outright.
Every style in this table uses a different set of Unicode code points than plain A-Z. A search engine, in-app search bar, or hashtag index matching the word "bold" won't match "𝗯𝗼𝗹𝗱" unless the platform specifically normalizes styled Unicode back to plain letters before indexing, and most platforms don't. That means fancy text in a bio or caption headline generally won't surface in on-platform search. Using it for an entire caption, instead of just a short stylized hook, can hurt discoverability.
Screen readers pronounce characters by their formal Unicode name, not their visual shape. Circled/bubble letters often get read out as "circled latin small letter a," character by character, instead of the word itself. Mathematical bold, italic, script, and fraktur letters may be read with their formal Unicode names, or skipped, depending on the screen reader's symbol-handling settings. Combining marks like underline and strikethrough can be announced as separate characters or force words to be read letter by letter. Treat fancy text as a short decorative accent, not a substitute for body copy that needs to stay accessible.
The full compatibility table above, condensed into a single printable PDF — handy for content calendars, moderator FAQs, or a quick reference when you're not sure a style will render.
Bold, italic, and bubble/circled text have the most complete Unicode coverage and render reliably across Instagram, TikTok, Discord, WhatsApp, Facebook, and X. If you only want one style that "just works," pick one of those three.
Rendering depends on the fonts installed on the viewer’s device and the app’s own font stack, not on the text itself. The same Unicode characters can display perfectly on a recent iPhone or Android phone and show as boxes on an older device, a desktop browser missing certain fonts, or a third-party client with a limited font set.
It depends on the platform and the specific field. Bio and caption fields are usually permissive. Username/handle fields are frequently restricted to plain ASCII on Instagram, TikTok, and Facebook, while display-name fields (which are separate from the handle) are often more permissive but may still filter out styles like fraktur/gothic that resemble impersonation attempts.
Only partially. Fancy characters are different code points than plain letters, so in-app search and hashtags matched against plain text usually won’t surface fancy-text captions. Keep hashtags and key search terms in plain text, and use fancy styles for a short decorative hook instead.
They’re built from combining characters stacked on top of normal letters rather than single lookalike letters. That makes them more likely to be clipped by character limits, altered by text normalization, or stripped by anti-spam filters — especially in WhatsApp, which also has its own native strikethrough formatting that can conflict with pasted Unicode versions.
Every style in the table above is available in the free generator — type once, preview all styles, and copy the one that fits your platform.