Why Cursive Text Doesn't Show Up on Some Devices (and How to Fix It)

By Sam·May 5, 2026·Updated 2026-05-05·4 min read

You generated a beautiful cursive bio. You sent it to a friend. They reply: "all I see is rectangles." Now you're wondering whether the tool is broken, whether the friend's phone is broken, or whether you missed a step.

None of those. The rectangles ("tofu" in Unicode jargon) come from a specific gap in how some devices ship fonts. Once you understand why, you can choose styles that just work on every audience.

The 60-second explanation

Every character on the internet is a Unicode code point — a number that says "this is the letter B" or "this is a face-with-tears-of-joy emoji." For your device to render a code point, two things must be true:

Your operating system must include a font that has a glyph for that code point.
The app you're viewing must use that font (or be willing to fall back to it).

When either step fails, you see a placeholder rectangle. That's it. The text is fine — your device just does not have the picture for it.

Cursive characters live in a Unicode block called Mathematical Alphanumeric Symbols (range U+1D400 to U+1D7FF). Most modern devices ship a system font that covers it. A few do not, and that's where rectangles appear.

Which devices and apps are the worst offenders

Based on testing roughly 30 device-OS-app combinations:

Mostly safe:

iOS 15+ and iPadOS 15+ — every modern iPhone and iPad
Android 10+ on devices made by Google, Samsung, OnePlus, Pixel, Sony
macOS 11+ (Big Sur and newer)
Windows 10/11 with the default fonts installed
Modern browsers (Chrome 90+, Safari 14+, Firefox 90+, Edge 90+) on any OS

Sometimes broken:

Android 8–9 on budget devices — common in price-sensitive markets
WhatsApp on older Android (the renderer often falls back to a font without Mathematical Alphanumeric)
Outlook on Windows for Mathematical Bold Script specifically
Some Linux distributions that ship a minimal font set

Reliably broken:

KaiOS / older feature phones (very small remaining audience but exists in some emerging markets)
Email clients on outdated phones — the worst combination is "old Android + Yahoo Mail"
Terminal emulators not configured with a Unicode-friendly font

How to pick styles your audience actually sees

If you want a single rule of thumb: prefer styles whose underlying Unicode characters were added before 2010. Older characters have had a decade-plus to be included in default fonts.

Concretely, in our cursive generator:

✅ Always-safe: Italic (𝐴𝐵𝐶), Bold (𝐀𝐁𝐂), Bold Italic (𝑨𝑩𝑪), Sans Serif variants, Monospace, Small Caps
✅ Almost-always-safe: Script (𝒜𝒷𝒸), Bold Script (𝓐𝓑𝓒), Double-Struck (𝔸𝔹ℂ)
⚠️ Risky for older Android: Fraktur (𝔄𝔅ℭ) — gothic blackletter style
⚠️ Risky for older Android and some email clients: Bubble Filled (🅐🅑🅒)

If you do not know your audience's device mix, default to the always-safe row.

How to test before publishing

Three quick tests, in order of how representative they are:

1. The friend test. Send the styled text to two friends — one on iPhone, one on Android. If both report it works, you are 95% safe.

2. The screenshot test. Open Instagram (or whichever target app) on your own phone, paste a sample, screenshot the result, and view the screenshot at 100% zoom on a desktop. If the rendered text looks like the input, the rendering pipeline is fine.

3. The font picker test. On your desktop browser, open the page, right-click the text, and view it in different fonts (System, Inter, Verdana). If a system font shows boxes but Inter does not, you know the problem is font coverage rather than the actual characters.

What to do if it's already broken for some followers

If you already published a bio and are getting "boxes" reports:

Check which characters are the offenders — usually filled bubble (🅐) and Fraktur (𝔄).
Switch to a safer family. Italic and Small Caps render almost everywhere.
If you must use the affected character (your username has it baked in), consider adding a plain-text version as a fallback in your bio.

The deeper "why this is so messy"

The Mathematical Alphanumeric block was added in Unicode 3.1 (2001) for mathematical writing. OS font teams treated it as low priority — math symbols are rare in everyday writing, and shipping a full math font on a phone with limited storage was a real tradeoff. Once social media users started using those characters as "fancy fonts," what was a math edge case became a daily user-facing problem.

Android 12+ and iOS 16+ include Mathematical Alphanumeric coverage in the default font fallback chain. Older devices stuck on Android 9 with a minimal ROM are the ones that struggle.

To switch styles quickly, paste into the fancy text generator and use the category chips — the tool shows every safe and risky variant side by side.