Unicode Text Converter

What the conversion actually does

Every conversion here is a character-for-character substitution. The letter A (U+0041) becomes MATHEMATICAL BOLD CAPITAL A (U+1D400), or FULLWIDTH LATIN CAPITAL LETTER A (U+FF21), or CIRCLED LATIN CAPITAL LETTER A (U+24B6). No formatting is applied, because plain text has no formatting to apply.

That distinction matters when you count characters. Most of the mathematical alphabet lives above U+FFFF, so a single styled letter takes two UTF-16 code units. Platforms that count code units — rather than characters — will treat a ten-letter styled word as twenty characters, which is why a styled bio can hit a limit sooner than the plain version.

Combining marks work differently

Strikethrough, underline and overline are not substitutions. They append a combining character after each letter, and the renderer draws it on top of the previous glyph. The base letters stay exactly as they were, which is why struck-through text remains searchable and readable when the mark fails to render.

Zalgo uses the same mechanism, just with many marks stacked at once. Some apps normalise or strip long runs of combining marks, so heavy stacks are the first thing to break.

• Substitution: bold, italic, script, blackletter, outline, monospace, fullwidth, circled
• Combining marks: strikethrough, underline, overline, slash, zalgo, glitch
• Reordering: reversed and upside-down text, which flips the sequence as well as the glyphs

Normalisation and what survives it

Unicode defines normalisation forms, and some systems apply them to text you submit. Under compatibility normalisation (NFKC) many styled letters collapse back to plain ASCII — a bold A becomes a plain A again. That is a feature, not a bug: it lets search and comparison work. It also means a styled username can silently become plain in a database that normalises input, so never rely on the styling being preserved in a system you do not control.