Fancy Text Generator
Turn plain text into fancy Unicode styles for social media bios and posts — with a clear warning about what they do to screen readers and search.
There is no letter H in 𝓗𝓮𝓵𝓵𝓸
This is the thing worth understanding before you paste any of it anywhere. These are not fonts and not formatting — they are different characters that happen to be shaped like letters. Mathematical alphanumeric symbols, fullwidth forms, enclosed alphanumerics. Each one is a distinct entry in Unicode with its own number.
| Style | Looks like | Bytes | A search for "Hello" finds it |
|---|---|---|---|
| Plain | Hello | 5 (1×) | yes |
| Fullwidth | Ｈｅｌｌｏ | 15 (3×) | no |
| Circled | Ⓗⓔⓛⓛⓞ | 15 (3×) | no |
| Bold script | 𝓗𝓮𝓵𝓵𝓸 | 20 (4×) | no |
| Bold serif | 𝐇𝐞𝐥𝐥𝐨 | 20 (4×) | no |
| Bold sans | 𝗛𝗲𝗹𝗹𝗼 | 20 (4×) | no |
A plain substring search finds the plain text and none of the
5 styled forms. Nor does lower-casing help, because case folding
maps a styled capital to a styled small letter rather than to a plain one. A database
LIKE, a username uniqueness check, and ctrl-F in most applications all fail
the same way, because they compare code points and the code points genuinely differ.
Though normalisation does recover them, which cuts both ways
It would be easy to stop there and say fancy text is invisible to search. That would be overstating it. Unicode has a compatibility normalisation, NFKC, which maps every one of these back to plain letters — circled and fullwidth included — so a system that normalises before indexing finds them perfectly well.
The awkward part is that normalising is a choice each system makes separately, and the two choices give opposite answers on the same text. Search engines generally normalise. String comparison in application code generally does not. It also has to be the compatibility form specifically: ordinary NFC normalisation recovers none of these, which is a distinction most code gets wrong by default because NFC is the one people have heard of.
The size cost has no such escape. Every style here is five characters on screen and three to four times the bytes:
| Style | Characters | Bytes | Fits a 160-character bio | Fits 160 bytes |
|---|---|---|---|---|
| Plain | 100 | 100 | yes | yes |
| Fullwidth | 100 | 300 | yes | no |
| Circled | 100 | 300 | yes | no |
| Bold script | 100 | 400 | yes | no |
| Bold serif | 100 | 400 | yes | no |
| Bold sans | 100 | 400 | yes | no |
The same 100-character bio fits a character limit in every style and blows a byte limit in 5 of them. Which one a field enforces is an implementation detail you cannot see from outside, and it is why a bio sometimes gets rejected for being too long when you can count the characters yourself and see that it is not.
The accessibility cost is the one that should decide it. A screen reader given a mathematical bold H announces it as a mathematical symbol, not as the letter — so a bio written this way is read aloud as a stream of symbol names rather than as words. That is the real argument against using it for anything that matters: not that it looks bad, but that it stops being text for the people who most need it to be text. It is fine for a one-off flourish, and a poor choice for your name, your handle, or anything someone might need to find you by.
How to use
- Type your text.
- Browse the generated styles.
- Copy the one you want.
- Keep essential information in ordinary text as well.
Frequently asked questions
Are these actually fonts?
No, and the distinction matters. They are separate Unicode characters that happen to look like styled letters — mathematical alphanumeric symbols, mostly, intended for equations. You are not changing the font; you are substituting entirely different characters that resemble one.
How do screen readers handle them?
Badly. Because these are not the letters they resemble, a screen reader may read them as their formal Unicode names, spell them out one at a time, or skip them silently. A bio written entirely in fancy text can be completely unintelligible to a blind user, which is worth weighing against the visual effect.
Will search find text written this way?
Usually not. Search treats these as different characters from ordinary letters, so a name or keyword in fancy text will not match a search for the normal spelling. The same applies to a site's own search and to anyone trying to copy your handle.
Why does it look wrong on some devices?
Because the characters have to exist in an installed font to display. Coverage of the mathematical and enclosed alphanumeric ranges varies, so text that looks striking on one phone can show as empty boxes on another, and older devices fare worst.
Can I use these in a username?
Sometimes, and many platforms restrict it. Where they are allowed, they make you harder to find and harder to mention, since nobody can type your name. Several platforms have tightened the rules specifically because fancy text is used to evade moderation filters.
What is the responsible way to use it?
Sparingly, and never for anything essential. A decorative flourish alongside readable text is harmless; a whole bio, a call to action, or contact details rendered this way excludes people and hides you from search. Keeping the important content in plain letters costs nothing.
🔒 This tool runs entirely in your browser. Nothing you enter is uploaded, logged, or stored.