Does fancy text work on numbers and emoji on iPhone?
Style a caption in bold or bubble text and the letters transform while a price, a phone number, a comma and any emoji sit there exactly as typed. That is not one gap — it is two unrelated ones. Punctuation missing is a genuine hole in Unicode. Numbers passing through is closer to a choice, made on purpose, for reasons that have nothing to do with Unicode running out of characters.
Style a whole sentence in bold or bubble text and something inconsistent-looking happens: the letters all change, and everything that is not a letter does not. A price stays “$14.99”, not some stylised version of it. A phone number stays a plain string of digits. The exclamation mark at the end stays a perfectly ordinary exclamation mark, and any emoji sitting in the message looks untouched next to a sentence that otherwise reads completely differently. It looks like the conversion just gave up partway through. It did not — two separate, unrelated reasons are stacked on top of each other here, and only one of them is actually a limitation.
What a fancy style is actually doing to a sentence
None of iPhone’s fancy text styles are fonts. Each one is a fixed set of separate Unicode characters that happen to already look bold, or italic, or circled, or upside down, sitting in their own corner of the standard. Typing in one of these styles works by swapping every ordinary letter for its look-alike counterpart from that set, character by character, as you type. It is a substitution, not a rendering choice, which is the same reason a fancy-text word behaves like a foreign character to search, to sorting and to anything else that expects an ordinary letter — a fact covered in more depth elsewhere. What matters here is narrower: which characters actually have a look-alike counterpart to substitute in, and which never got one.
Punctuation was never part of the deal
The Unicode ranges these twelve styles borrow from were scoped for one job: telling a bold variable apart from an italic one in a piece of mathematical notation. That scope covers the 26-letter Latin alphabet, upper and lower case, and for a handful of the styles, the ten digits. It stops there. There is no bold exclamation mark anywhere in Unicode, no italic question mark, no circled ampersand, no upside-down comma — not because a decorative alphabet was designed and punctuation got left out of it, but because nobody was ever asked to design a decorative alphabet in the first place. A period or a hyphen typed inside a fancy-styled sentence has nothing to convert into, in any of the twelve styles, on any device, for the same reason an accented letter often has nothing to convert into either: the substitution set simply never reached that far.
Numbers are a different story
A few of these Unicode ranges do go further than letters and include a matching set of ten digits somewhere in the standard — bold and double-struck numerals exist, for instance, tucked into the same mathematical block their letters come from. So for a handful of styles, a stylised “7” is technically available for a keyboard to use. Kibo does not use it, on any of the twelve styles, ever. Every digit you type passes through exactly as typed, regardless of which style the rest of the sentence has taken on.
Why leave a working conversion sitting on the table
Because a digit is rarely just decoration inside the number it belongs to. iOS reads a plain string of digits in a text field and quietly turns it into something tappable — a phone number becomes a link that opens the dialer, a date becomes something Calendar can offer to add, a tracking number in an email becomes a link to a carrier site. That recognition runs on ordinary Unicode digits, the same 0-9 every system on earth expects. Swap even one of those digits for a bold or double-struck look-alike from a different part of Unicode and the recognition has no reason to still work, because to the system doing the parsing, a stylised “7” is not the character it was looking for at all — it just happens to look identical to a human eye. A price, a PIN, a phone number, a house number, an amount on an invoice: all of them are meant to be read correctly by something other than the person receiving the message, and a keyboard that occasionally swaps digits for look-alikes has no reliable way to know, key by key, which number in front of it is decorative and which one someone is about to tap, copy into a form, or ask Siri to dial. Passing every digit through untouched, on every style, avoids needing to guess.
Emoji were never in this alphabet to begin with
Letters and digits get remapped because Unicode drew a bold or double-struck or circled version of the Latin alphabet somewhere in its tables, ready to be swapped in. Emoji are not part of that alphabet at all — they live in an entirely separate section of the standard, built for pictographs rather than for stylised letterforms, with no bold or upside-down or squared version of a single one of them anywhere in Unicode. There has never been a codepoint for a “circled” 😊 for a fancy-text style to reach for, so an emoji passing through untouched is not a workaround or a limitation being politely respected. There was simply never a matching character to substitute, in the same way there is no stylised version of a Chinese character or a musical note — the styling trick only ever applied to one specific alphabet, and emoji sit outside it entirely.
What this looks like in an actual message
Type “Call me at 555-0142, it’s urgent 😊” in bold and the result reads 𝗖𝗮𝗹𝗹 𝗺𝗲 𝗮𝘁 555-0142, 𝗶𝘁’𝘀 𝘂𝗿𝗴𝗲𝗻𝘁 😊 — every letter converted, the phone number sitting there in ordinary digits, the comma and apostrophe untouched, the emoji rendering exactly as it would in plain text. The phone number still turns into a tappable link. The emoji still renders as an emoji rather than a missing-character box in an app that has never seen a fancy-styled Latin letter before. Nothing about the message’s underlying meaning changed — only the letters picked up a different look.
Where Kibo fits
Kibo generates all 12 fancy text styles on the keyboard itself as you type, rather than through a separate converter site, and numbers, punctuation and emoji pass through untouched the same way on every one of them — not selectively on the styles that happen to have a matching digit set, but consistently on all twelve, so a phone number or a price in a styled sentence behaves the same regardless of which style is active. None of it touches Full Access, since fancy text is generated locally on the keyboard and never goes near the clipboard. Kibo is free to download.
Frequently asked questions
Why didn’t the numbers in my sentence turn into fancy text?
Kibo passes every digit through untouched on all 12 styles, on purpose, even for the handful of styles where Unicode does define a matching stylised digit. Digits are commonly read by more than the person receiving the message — a phone number, a date, a price — and swapping them for look-alike characters from a different part of Unicode can quietly break that recognition.
Will punctuation ever get a fancy version?
No, and not because of a missing feature — there is no bold exclamation mark, no italic comma, no circled hyphen anywhere in Unicode, in any style. The ranges these fancy styles borrow from were built only for the Latin alphabet and, for a few styles, the digits. Punctuation was never included.
Does leaving numbers untouched mean fancy text is broken for phone numbers or prices?
The opposite — it is what keeps them working. A phone number in ordinary digits still becomes a tappable link, and a price still reads as a price to anything that parses the message, because the digits were never swapped for look-alike characters in the first place.
Why do emoji never change at all, even the ones that look like faces?
Emoji live in a completely separate part of Unicode built for pictographs, not in the alphabet fancy text styles borrow from. There is no bold, circled or upside-down version of any emoji anywhere in the standard, so there is nothing for a fancy style to substitute in the first place.
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.