Fancy Unicode Text
Type plain ASCII and get ๐๐จ๐ฅ๐, ๐ผ๐ก๐๐๐๐, ๐ข๐ฌ๐ป๐ฒ๐น๐ฝ, ๐๐ฏ๐๐จ๐ฑ๐ฒ๐ฏ, ๐ผ๐๐๐ and sans-serif variants from the Unicode Math Alphanumeric blocks.
Variants
๐๐ก๐ ๐ช๐ฎ๐ข๐๐ค ๐๐ซ๐จ๐ฐ๐ง ๐๐จ๐ฑ ๐ฃ๐ฎ๐ฆ๐ฉ๐ฌ ๐จ๐ฏ๐๐ซ ๐๐ ๐ฅ๐๐ณ๐ฒ ๐๐จ๐ ๐ฌ.
๐โ๐ ๐๐ข๐๐๐ ๐๐๐๐ค๐ ๐๐๐ฅ ๐๐ข๐๐๐ ๐๐ฃ๐๐ 13 ๐๐๐ง๐ฆ ๐๐๐๐ .
๐ป๐๐ ๐๐๐๐๐ ๐๐๐๐๐ ๐๐๐ ๐๐๐๐๐ ๐๐๐๐ 13 ๐๐๐๐ ๐ ๐๐๐.
๐ฏ๐ฝโฏ ๐๐๐พ๐ธ๐ ๐ท๐โด๐๐ ๐ปโด๐ ๐ฟ๐๐๐ ๐ โด๐โฏ๐ 13 ๐๐ถ๐๐ ๐นโดโ๐.
๐ฃ๐ฑ๐ฎ ๐บ๐พ๐ฒ๐ฌ๐ด ๐ซ๐ป๐ธ๐๐ท ๐ฏ๐ธ๐ ๐ณ๐พ๐ถ๐น๐ผ ๐ธ๐ฟ๐ฎ๐ป 13 ๐ต๐ช๐๐ ๐ญ๐ธ๐ฐ๐ผ.
๐๐ฅ๐ข ๐ฎ๐ฒ๐ฆ๐ ๐จ ๐๐ฏ๐ฌ๐ด๐ซ ๐ฃ๐ฌ๐ต ๐ง๐ฒ๐ช๐ญ๐ฐ ๐ฌ๐ณ๐ข๐ฏ 13 ๐ฉ๐๐ท๐ถ ๐ก๐ฌ๐ค๐ฐ.
๐๐๐ ๐ข๐ฆ๐๐๐ ๐๐ฃ๐ ๐จ๐ ๐๐ ๐ฉ ๐๐ฆ๐๐ก๐ค ๐ ๐ง๐๐ฃ ๐๐ ๐๐๐ซ๐ช ๐๐ ๐๐ค.
๐๐๐ ๐๐๐๐๐ ๐๐๐๐ ๐ ๐๐๐ก ๐๐๐๐๐ ๐๐๐๐ ๐ท๐น ๐๐๐ฃ๐ข ๐๐๐๐.
๐ณ๐๐พ ๐๐๐๐ผ๐ ๐ป๐๐๐๐ ๐ฟ๐๐ ๐๐๐๐๐ ๐๐๐พ๐ ๐ฃ๐ฅ ๐ ๐บ๐๐ ๐ฝ๐๐๐.
๐ง๐ต๐ฒ ๐พ๐๐ถ๐ฐ๐ธ ๐ฏ๐ฟ๐ผ๐๐ป ๐ณ๐ผ๐ ๐ท๐๐บ๐ฝ๐ ๐ผ๐๐ฒ๐ฟ ๐ญ๐ฏ ๐น๐ฎ๐๐ ๐ฑ๐ผ๐ด๐.
These are real Unicode codepoints, not a font. Avoid for accessibility-critical text.
How to use
- Type plain text in the input.
- Copy whichever style you want into the destination.
- Some variants lack digits (italic, script, fraktur) โ those keep ASCII digits unchanged.
About this tool
ShowHide
Maps each ASCII letter (and digits, when supported) to its visual look-alike in Unicode's Mathematical Alphanumeric Symbols range. The result keeps its style when copy-pasted into chat, social media, plain-text email โ anywhere a real bold tag wouldn't survive. The script and Fraktur forms route around the BMP "holes" where letters like โ, โฌ, and โ already exist as letterlike symbols.
Those holes are the awkward part of the block. When Unicode encoded the mathematical alphabets it found that a couple of dozen letters had already been assigned years earlier as letterlike symbols, so rather than duplicate them it left gaps and scattered the missing glyphs elsewhere in the BMP. A naive offset calculation lands in those gaps and emits a reserved codepoint, which renders as a blank box. The mapping here substitutes the correct scattered character instead, which is why script and Fraktur come out complete.
Not every style covers digits. Bold, double-struck, sans-serif and monospace have their own digit sets, but italic, script, Fraktur and several others do not, so digits pass through as ordinary ASCII and a styled word containing a number comes out visibly mixed. The tool leaves those digits as they are rather than silently substituting something close.
The cost of this approach is that the output is no longer the letters you typed. Screen readers announce many of these codepoints as "mathematical bold small a" or skip them, search does not match them against the plain word, and a username or display name made of them is unsearchable by the name people expect. Several platforms also reject them in profile fields or normalise them away. These are decorative substitutions for running text, and where actual emphasis is meant, real markup remains both more accessible and more robust.
Frequently asked questions
Is this just a font?
No โ every character is a distinct Unicode codepoint in the Mathematical Alphanumeric Symbols block. That's why it survives plain-text destinations that would strip a CSS font change.
Why is screen-reader behaviour bad with these?
Screen readers don't always know that ๐ (Mathematical Bold A) is the letter A โ they may read it as "Mathematical Bold Capital A" or skip it entirely. Use these for headers and accents, never for body content meant to be read aloud.
Where don't these render?
Older Android keyboards, basic terminal fonts, and any environment without Unicode SMP support will show boxes. Most modern OSes and browsers handle them fine.
Why does search stop finding my text after styling it?
Because the styled letters are different characters, not the same letters wearing a font. A search for "hello" compares code points, and the mathematical bold h is not the letter h, so the match fails โ in a browser's find bar, in a site's search box, and in anything that indexes the page. The same applies to sorting and to autocomplete.
Where is this genuinely appropriate?
In a place that gives you no formatting at all and where the text is decorative rather than functional โ a social profile name, a one-off post title. Avoid it anywhere the words have to work: headings, links, buttons, anything a screen reader will read aloud (it may spell the characters out or skip them), any field that will be searched, and any name that someone will later have to type.
Related tools
Bionic Reading Converter
Convert any text into bionic reading format โ first letters of each word bolded as fixation points to help your eyes glide faster through long passages.
Text
Braille Translator (Text โ Braille)
Translate text to Unicode Braille (Grade 1) and decode Braille back to text, with capital and number signs, in your browser.
Text
Superscript & Subscript Maker
Type plain text and get Unicode superscript (ยฒ) and subscript (โ) variants โ paste into chat, docs, or anywhere fonts won't help you.
Text
Social / SEO Character Limit Checker
Type once and see how your text measures against 28+ platform limits โ Twitter, Instagram, SEO titles, ad copy, app stores.
Text
Unicode Character Inspector
Break a string into characters and show each codepoint, UTF-8 bytes, HTML entity, CSS escape, and Unicode block.
Text
Unicode Normalizer (NFC, NFD, NFKC, NFKD)
Normalize text to NFC, NFD, NFKC or NFKD, optionally strip diacritics, and compare codepoint and byte counts across all four forms.
Text