Why Fancy Text Shows Boxes and How to Avoid It

See why boxes appear

Fancy text is made of characters, not of a font. A character is a number in the Unicode standard. A glyph is the drawing of that character in a particular font. Your text carries the characters; each reader's device has to find glyphs for them in the fonts it has.

How a reader's device might draw itFont has itFallback fontNo font has it

꧁𝓗𝓲꧂

This is how your browser draws these four characters right now. If you see boxes here, your device lacks a font for one of them.

Illustration: the letters come from one font, and the outlined ornaments at each end from another font the device found. Glyphs from a fallback font can differ in size, weight or style.

Illustration: when no font on the device has a glyph, it draws a placeholder instead, often an empty box. Type designers call these boxes "tofu". The characters are still there; copied elsewhere, they can show correctly again.

What you copy is the same in every case

U+A9C1JAVANESE LEFT RERENGGAN
U+1D4D7MATHEMATICAL BOLD SCRIPT CAPITAL H
U+1D4F2MATHEMATICAL BOLD SCRIPT SMALL I
U+A9C2JAVANESE RIGHT RERENGGAN

Illustration only. FontBlaze cannot see which fonts your readers have, so this is not a test of your device or of any app.

The text holds characters. Copying fancy text copies Unicode characters, such as MATHEMATICAL BOLD SCRIPT CAPITAL H at U+1D4D7. No font travels with them.
The device looks for a glyph. To show each character, the reader's device checks its fonts in order, starting with the font the app asks for.
Fallback fills gaps. If that font has no glyph for a character, the system tries other fonts. A fallback glyph can look slightly different from its neighbors.
No glyph means a box. If no font has a glyph, the device draws a placeholder, usually an empty box. Older systems, devices with few fonts and apps that use only their own fonts show boxes more often, which is why the same text can look fine on one device and broken on another.

What the boxes are

Each device ships with a set of fonts. When it needs to draw a character, it looks for a font that includes that character. If none does, it draws a placeholder, often an empty rectangle. Type designers call these placeholders “tofu” because of their shape. Google even named its Noto font family after the goal of “no more tofu”.

Fancy text is especially prone to tofu because it uses characters most people never type: mathematical letters, enclosed letters, phonetic small capitals, and combining marks.

Why it happens to some readers and not others

The text you send is identical for everyone. What differs is the reader’s device:

Older operating systems may not include fonts for newer Unicode characters.
Some apps use their own fonts and do not fall back to the system fonts.
Smart TVs, game consoles, car screens and older e-readers often have small font sets.
Custom fonts chosen in an app may cover fewer characters than the defaults.

So a style can look perfect on your phone and show boxes for a follower using an older laptop.

Which styles are most at risk

From lower to higher risk, roughly:

Fullwidth letters, which come from widely supported East Asian fonts.
Bold, italic, script, Fraktur, double-struck, sans-serif and monospace letters from the Mathematical Alphanumeric Symbols block. Current major phone and desktop systems include fonts for them.
Circled letters and digits, which are old and common.
Small capitals, where a few letters (F, Q, S) come from a newer block.
Filled circles, squares, and parenthesized capitals, from newer enclosed blocks, plus a few that may appear as emoji.
Decorative symbols and wrappers, such as Javanese ornaments, that need a specific script font.
Very recent characters. FontBlaze leaves out anything newer than Unicode 11.0 for this reason. For example, subscript w, y and z exist in Unicode 18.0 but are not used.

How to check before you post

Look at it on a second device. If you have an older phone or a different computer, open your post there.
Read the style notes. FontBlaze shows a short note on each style card when a style uses newer or unusual characters.
Use the Unicode inspector. Paste your text into the Unicode inspector to see exactly which characters it contains. Code points above U+1F000 are usually from newer blocks.

The safest choices

If you want styling that most readers will see correctly, start with Bold or Bold Sans, keep it to a short line, and leave the rest plain. The copy and paste fonts page orders styles with the most widely supported first.

Boxes are not the only failure

Sometimes the characters display but look wrong. Letters from the older Letterlike Symbols block, such as the script capital B, can come from a different font than the rest of the word, so they look slightly mismatched. Combining marks used for underline and strikethrough can sit in odd positions. And some apps quietly convert or strip characters. These are all reasons to test where it matters and keep important information in plain text.

Frequently asked questions

Can I fix boxes on someone else's phone?

No. The boxes appear because of the fonts on their device. The only fix on your side is to choose characters with wider support, or to use plain text.

Why do boxes sometimes have a question mark or code inside?

Systems draw missing characters differently. Some show an empty rectangle, some show a question mark in a box, and some show the character's code point in tiny digits. They all mean the same thing.