You paste your styled text and it snaps back to plain. The twist: it was never "formatting" in the first place — so nothing was lost. Something was converted.
Fancy text isn't bold applied to a letter — it's a different Unicode character that happens to look bold. So when you paste it somewhere that normalizes text — a search box, a username field, some editors — that system folds the special characters back to their plain equivalents, and 𝗯𝗼𝗹𝗱 becomes bold. Nothing was stripped in the formatting sense; the special characters were simply converted to normal ones. It survives in fields that store text as-is (display names, bios, chat) and reverts in fields that clean it up.
Real formatting (like a word processor's Bold button) is a separate instruction attached to normal letters. Fancy text has no such instruction — the "boldness" is baked into the character itself. The bold 𝗮 and a normal a are two different code points that happen to look related.
Many systems run text through a cleanup step called normalization — and one common form (NFKC) is defined to strip these styled variants back to plain, because they're meant for maths, not styling. That's the step that turns your fancy text back to normal on the way in.
Fields that store your text exactly as pasted:
Fields that normalize or restrict input:
Here's the upside of the same mechanism: because search normalizes styled text to plain, your content still gets indexed correctly. The trade-off is that fancy text isn't searchable — a search for "bold" won't match 𝗯𝗼𝗹𝗱, and Ctrl+F skips it. Keep anything you want found in plain text.
Make your styled text, then drop it into a display name, bio or caption — the fields that keep it exactly as you copied it.
Open the Text Generator →Related reading: fancy fonts & accents, why Instagram won't accept a fancy username, and is LinkedIn bold text safe for the searchability angle.
Because it was never formatting to begin with. A fancy font isn't bold applied to a letter — it's a different Unicode character that happens to look bold. When you paste it somewhere that normalizes text (search boxes, username fields, some editors), the system folds those special characters back to their plain equivalents, so 𝐛𝐨𝐥𝐝 becomes bold. Nothing was 'removed' in the formatting sense; the special characters were converted to normal ones.
It depends on whether the destination normalizes or restricts text. Display fields that store text as-is (social display names, bios, most chat messages) keep the styled characters. Fields that canonicalize input — search bars, @username fields, some form fields, and document editors saving to certain formats — convert or reject them. Same clipboard, different handling on the other end.
It can. Word converts mathematical alphanumeric characters back to plain letters when writing certain formats or inside a math zone, and both Word and Docs may substitute a fallback font so the styling looks inconsistent. Because the styled look is baked into the character rather than a font setting, a document that normalizes or re-encodes text can flatten it to plain.
Because a styled 'a' (𝗮) is a different character from a plain 'a', so a search for the normal spelling doesn't match it. Search engines and in-app search deliberately normalize styled Unicode to plain for indexing, which is good for being found — but it also means Ctrl+F, on-platform search and SEO won't match your fancy text against a normal query. Keep anything you want found in plain text.
Paste it into fields that store text as-is: social display names, bios, chat messages and captions. Avoid putting it in search boxes, @username fields, or documents you'll export to formats that normalize text. And never rely on it for anything that must be searchable or machine-read — those systems are exactly the ones that flatten it back to plain.