A font decides how a character is drawn. Unicode decides which character it is. Changing the font leaves your text identical underneath and only affects your own document; changing the characters alters the text itself, which is why it travels but also why it breaks search, sorting and screen readers.
Two separate layers
Text has an identity layer and a presentation layer. Unicode owns the identity layer: this is the letter A, code point U+0041. Fonts own the presentation layer: here is how A looks in Helvetica. The two are independent by design, which is what lets the same document render in any typeface.
What a real font change does
Selecting a different typeface tells the rendering system to draw the same characters with different glyphs. The stored text is byte-for-byte unchanged. Anyone who copies it gets ordinary letters, and it will display in whatever font their context uses. Your styling was never part of the text.
What a Unicode generator does
It substitutes different characters. Your A becomes 𝐀, U+1D400, which is a distinct character that happens to be drawn in a bold serif shape in most fonts. The text now contains different data. Copy it anywhere and the bold look persists, because you are carrying different characters, not different formatting.
Why the difference is the whole story
Everything else follows from it. Unicode styling works in an Instagram bio precisely because it is not formatting. It fails in search precisely because it is not the letters people type. It confuses screen readers precisely because the characters are mathematical symbols being used as decoration. One mechanism, one set of trade-offs.
Which to use
If you control the rendering — a website, a document, a design file — use a real font. It keeps the text searchable, accessible and semantically correct. Use Unicode substitution only where you do not control rendering and there is no formatting available: social bios, display names, chat handles. Those are its legitimate home.
References
Related tools and guides
Last updated September 2026 · Editorial policy · How we verify Unicode claims