HomeText & GeneratorsFancy Text Generator

type anything. copy anything.

transform your text into 18 Unicode styles for Instagram, Twitter, TikTok, Discord, and anywhere else.

your text
Bold

𝐁𝐨𝐥𝐝 𝐓𝐞𝐱𝐭

Italic

𝐼𝑡𝑎𝑙𝑖𝑐 𝑇𝑒𝑥𝑡

Bold Italic

𝑩𝒐𝒍𝒅 𝑰𝒕𝒂𝒍𝒊𝒄

Cursive

𝒞𝓊𝓇𝓈𝒾𝓋ℯ 𝒯ℯ𝓍𝓉

Bold Cursive

𝓑𝓸𝓵𝓭 𝓒𝓾𝓻𝓼𝓲𝓿𝓮

Gothic

𝔊𝔬𝔱𝔥𝔦𝔠 𝔗𝔢𝔵𝔱

Double-Struck

𝕆𝕦𝕥𝕝𝕚𝕟𝕖 𝕋𝕖𝕩𝕥

Monospace

𝙼𝚘𝚗𝚘𝚜𝚙𝚊𝚌𝚎

Sans Bold

𝗦𝗮𝗻𝘀 𝗕𝗼𝗹𝗱

Circled

Ⓒⓘⓡⓒⓛⓔⓓ

Fullwidth

Wide Text

Small Caps

ꜱᴍᴀʟʟ ᴄᴀᴘꜱ

Superscript

Sᵘᵖᵉʳˢᶜʳⁱᵖᵗ

Upside Down

uʍoꓗ ǝpısd∩

Strikethrough

C̶r̶o̶s̶s̶e̶d̶ O̶u̶t̶

Underline

U̲n̲d̲e̲r̲l̲i̲n̲e̲d̲

Aesthetic

v a p o r w a v e

Dotted

Ḋȯṫṫėḋ Ṫėẋṫ

What this tool does

Convert plain text into stylized variants — bold, italic, cursive, double-struck, monospace, upside down, and a handful of decorative styles. The output uses Unicode characters that look like styled text but are not styled — they are entirely different code points that happen to resemble letters.

How this is not formatting

When a word processor makes text bold, the underlying characters do not change — just their visual rendering. Strip the formatting and the original text is intact.

Fancy text works the opposite way. The input hello becomes 𝐡𝐞𝐥𝐥𝐨 — but those bold h-e-l-l-o characters are completely different Unicode code points than regular Latin letters. The result looks like bold text and works in any text field, but it is not actually bold; it is a different sequence of characters that happen to look bold-like.

This is why “bold” fancy text works in Twitter bios and Instagram captions where actual bold formatting is not allowed. The platforms only filter markup, not Unicode characters that happen to look bold.

Where this is useful, where it backfires

  • Useful — social media bios where formatting is otherwise impossible, decorative section headers in plain-text contexts, occasional design flourishes.
  • Backfires— search engines do not index Unicode-styled text the same way as plain Latin characters. Screen readers may read “mathematical bold h” instead of just “h.” Form fields that expect Latin characters may reject the input entirely. Anything that needs to be searchable, accessible, or programmatically processed should stay in plain text.

Accessibility note

Screen readers handle stylized Unicode unevenly. Some skip the styled characters entirely; some announce them by their formal Unicode name (“mathematical italic small h, mathematical italic small e...”) which makes the text borderline unusable for blind users. If your audience includes people using assistive technology, keep critical content in plain text.

Browser-only

The conversion is a character-by-character lookup — no external service. Runs entirely in your tab.

What this tool does

Convert plain text into stylized variants — bold, italic, cursive, double-struck, monospace, upside down, and a handful of decorative styles. The output uses Unicode characters that look like styled text but are not styled — they are entirely different code points that happen to resemble letters.

How this is not formatting

When a word processor makes text bold, the underlying characters do not change — just their visual rendering. Strip the formatting and the original text is intact.

Fancy text works the opposite way. The input hello becomes 𝐡𝐞𝐥𝐥𝐨 — but those bold h-e-l-l-o characters are completely different Unicode code points than regular Latin letters. The result looks like bold text and works in any text field, but it is not actually bold; it is a different sequence of characters that happen to look bold-like.

This is why “bold” fancy text works in Twitter bios and Instagram captions where actual bold formatting is not allowed. The platforms only filter markup, not Unicode characters that happen to look bold.

Where this is useful, where it backfires

  • Useful — social media bios where formatting is otherwise impossible, decorative section headers in plain-text contexts, occasional design flourishes.
  • Backfires— search engines do not index Unicode-styled text the same way as plain Latin characters. Screen readers may read “mathematical bold h” instead of just “h.” Form fields that expect Latin characters may reject the input entirely. Anything that needs to be searchable, accessible, or programmatically processed should stay in plain text.

Accessibility note

Screen readers handle stylized Unicode unevenly. Some skip the styled characters entirely; some announce them by their formal Unicode name (“mathematical italic small h, mathematical italic small e...”) which makes the text borderline unusable for blind users. If your audience includes people using assistive technology, keep critical content in plain text.

Browser-only

The conversion is a character-by-character lookup — no external service. Runs entirely in your tab.

more free tools

PDF utilities, image tools, developer helpers — all free, no signup.

Something wrong?