Why does fancy text look broken on Android?
Bold, script or circled text that looks perfect on your iPhone can arrive as empty boxes on a friend’s Android phone. Why that is a different, harder failure than emoji simply looking different, and what you can actually do about it.
You style a message in bold or script, it looks exactly right in the text field as you type it, and you send it. Your friend on an Android phone writes back asking why half your message is a row of little boxes. Nothing went wrong on your end — your iPhone showed you the truth the whole time. The gap opened up on the other phone, for a reason that has nothing to do with how carefully you typed.
It is a character swap, not a font
Fancy text on a phone was never a font choice, because a bio field, a text message or a caption box stores plain characters with no formatting layer underneath. A bold 𝗔 is not the letter A drawn in bold — it is a separate Unicode character, sitting at its own position in the standard, that happens to already look like a bold A. Typing in a fancy style substitutes one of those standalone characters for the ordinary letter, the same trick behind script, circled and every other decorative alphabet.
Why this is not the same problem as emoji looking different
People often reach for the emoji comparison here, because everyone has seen 😂 look slightly different on an Android phone than it does on an iPhone. That is a real effect, but it is a milder one, and understanding why makes the boxes easier to make sense of.
Every major platform draws its own artwork for the emoji Unicode defines, so an emoji you send is guaranteed to show something on the far end — Apple’s version, Google’s version, Samsung’s version — just not identical artwork. Fancy text characters carry no such guarantee. They are ordinary characters that a font either has a picture for or does not. When the font on the receiving phone has no glyph for that specific character, there is no fallback drawing to fall back to. The device draws a small empty rectangle instead, a placeholder that means, roughly, “a character exists here and I do not have a picture for it.” That box is what your friend is actually seeing.
Why an iPhone rarely shows the gap, and an Android phone sometimes does
iOS ships one system font, maintained by one company, with unusually broad coverage across Unicode blocks that most people will never type into directly — mathematical notation, enclosed alphanumerics, the ranges fancy text styles are built from. That is why sending styled text from one iPhone to another almost always looks identical on both ends: the same font, with the same coverage, is doing the drawing on both sides.
Android is not one company shipping one font. Every manufacturer ships its own default font and its own fallback fonts, and how completely any of them cover an obscure Unicode block varies by device and by how recent its software is. A budget or older Android phone is meaningfully more likely to be the one showing boxes; a recent flagship is more likely to render most of it correctly. Neither phone is malfunctioning — they simply carry different answers to a question as narrow as “does a drawing exist for this exact character.”
A second, unrelated gap: styles that were never complete to begin with
Some of the boxes people run into have nothing to do with the receiving phone at all. A handful of fancy text styles are missing letters in Unicode itself, on every device, because the character was never assigned in the first place — there is no small-capital Q anywhere in the standard, and no lowercase set at all in squared text. Sending one of those letters does not risk a box on the far end; it never had a matching character to send.
- A missing codepoint — small caps’ Q, squared text’s lowercase — fails identically everywhere, including on your own iPhone, because the character simply does not exist.
- A missing glyph — the Android box — is specific to one device and one font. The character exists; that particular phone just has no drawing for it.
What actually helps
- Style a name or a single word rather than the whole message, so a box in the middle costs little if the recipient’s phone cannot draw one of the characters.
- For anything that has to land correctly — a work message, something time-sensitive — plain letters are simply the more reliable choice, not a downgrade.
- There is nothing to fix in your own Settings. Your iPhone displayed the message correctly the entire time; the gap lives on the device receiving it, out of your reach.
- If you message the same person often and are curious, send one styled test message. What renders for them today is a fair guide to tomorrow, since it depends on their phone and font rather than anything that changes message to message.
Where Kibo fits
Kibo’s keyboard carries all 12 fancy text styles built in — Bold, Italic, Bold Italic, Script, Double-struck, Mono, Small Caps, Wide, Circled, Squared, Upside Down and Strikethrough — applied as you type instead of through a separate generator site. For the letters that never got a match anywhere, the small-caps Q, the squared lowercase set, it leaves the ordinary letter in place rather than sending a character guaranteed to fail, which closes the first kind of gap described above. The second kind, a missing glyph on someone else’s phone, is not something any keyboard app can reach from the sending side — that gap belongs to the device on the other end. Kibo is free to download and works with Full Access left off, since fancy text is generated on the keyboard itself and never touches the clipboard.
Frequently asked questions
Why did my fancy text message show up as boxes on my friend’s Android phone?
The font on their phone has no drawing for that specific character. Fancy text swaps ordinary letters for separate Unicode characters, and unlike an emoji, there is no guarantee every font on every device has a picture for one — when it does not, the device draws an empty box to mark the gap instead.
Does this happen between two iPhones too?
Rarely. iOS ships one system font with unusually broad coverage of these characters, so styled text sent from one iPhone almost always displays correctly on another. The risk goes up specifically when a message crosses to a different operating system, since Android manufacturers each ship their own fonts with their own coverage.
Is this the same reason emoji look different on iPhone and Android?
No, it is a different mechanism. Every major platform draws its own artwork for the same standard emoji, so an emoji always shows something, just possibly a different expression. Fancy text has no guaranteed artwork on the far end at all — the character can fail to render altogether.
Try it on your own keyboard
Kibo is a free custom keyboard for iPhone with real mechanical key sounds, a wardrobe of themes and RGB backlight effects. No account, no ads, and it works with Full Access left off.