Why your fancy text isn't working

Guide · About 8 minutes

Find your symptom below. Some of these are fixable from your side, some are the receiving app's behaviour and cannot be worked around — knowing which is which saves a lot of time.

1. Empty boxes instead of letters

What you see: rectangles, sometimes with tiny digits inside, where letters should be. Often called tofu.

Cause A — the reader's device has no font for it. The character is valid and correct; that particular phone or program simply has no drawing of it. Older Android builds, budget devices, smart TVs and some desktop applications ship cut-down font sets.

Cause B — the generator produced an invalid character. If you see boxes on every device including your own, and always on the same letters, this is the culprit. Several alphabets have gaps where a letter was encoded separately years earlier. A generator that calculates positions by arithmetic lands in those gaps and emits characters that do not exist. Cursive is the usual victim — watch for boxes on B, E, F, H, I, L, M and R.

Fix: for cause A, switch to a more widely supported style — Ｗｉｄｅ and Ⓑⓤⓑⓑⓛⓔ ⓣⓔⓧⓣ have the best coverage. For cause B, use a generator that maps those letters properly; the cursive tool here fills all eleven gaps, so every letter renders.

2. Only some letters converted

What you see: a mix of styled and plain characters in the same word.

Cause: the style does not cover what you typed. Most alphabets cover A–Z and 0–9 only. Punctuation almost never converts, and accented letters such as é, ü and ñ have no styled equivalents at all. A few alphabets have individual holes: there is no superscript q, and no small capital Q or X anywhere in Unicode.

Fix: this is a limit of the character set rather than a bug, so the options are to accept the mixture, drop the accents, or choose a style with fuller coverage. Full-width text is the most complete — it covers the entire printable ASCII range including punctuation.

3. Text reverted to plain after saving

What you see: you paste styled text, submit the form, and it comes back as ordinary letters.

Cause: the field normalised your input. Unicode's NFKC normalisation deliberately converts styled mathematical characters back to plain ones, on the sensible grounds that they are the same letters. Sites apply it wherever text must be compared reliably — usernames, search boxes, and increasingly display names.

Fix: none. This is the field working as designed, and no styling survives it. Put your styled text in a different field.

4. The field rejected it outright

What you see: an error such as "username can only contain letters, numbers, periods and underscores", or the characters simply refuse to appear as you type.

Cause: you are in an identity field. Handles and usernames are validated against a small allowed character set before anything is saved.

Fix: use the display name instead. On Instagram, TikTok, X and Discord the display name sits directly above or beside the handle, accepts styled characters, and is the field most people actually mean when they talk about a styled username.

5. Looks fine to you, broken to everyone else

What you see: nothing wrong — until someone sends you a screenshot.

Cause: your device has a font covering the characters and theirs does not. This is the most common failure precisely because it is invisible to the person who caused it.

Fix: test on hardware you do not own before committing. Send the text to yourself and open it on a second device, ideally one Android and one iPhone. The compatibility guide ranks the styles by how safely they travel.

6. The strikethrough line is broken or crooked

What you see: the line through your text has gaps, or sits too high or low.

Cause: the strike is not one line. Each character gets its own short stroke, and those strokes are meant to butt together into a continuous rule. Fonts with loose letter spacing leave gaps; fonts with unusual metrics put the stroke at the wrong height.

Fix: largely out of your hands, since the reader's font decides. Trying the short-stroke or slashed variant sometimes looks more deliberate. Inside Discord messages, use the real markdown strikethrough instead — it is cleaner and costs no extra characters.

7. You ran out of characters

What you see: the counter says you are over the limit, though the text looks short.

Cause: combining marks. Strikethrough, underline and cursed text insert an invisible mark after every letter, so a twenty-character phrase costs forty. The spaced-out wide style has the same problem for a different reason — every inserted space is a character.

Fix: switch to a substituted alphabet. Bold, cursive, bubble, gothic and full-width all cost exactly one character per letter, the same as plain text, however dramatic they look.

8. Cursed text came out tame

What you see: dramatic in the generator, flat after pasting.

Cause: the receiving app limited it. Many platforms cap how many combining marks they will render on one character, and some strip the excess on submission. iOS caps the visible stack more aggressively than Android or desktop browsers.

Fix: nothing forces an app to draw the full stack. Raising the intensity before copying sometimes helps where the cap is on rendering rather than on storage, but where the app strips marks on save the result is fixed.

9. Your ASCII banner is scrambled

What you see: rows of blocks that do not line up into letters.

Cause: it landed in a proportional font, where every character is a different width. Block letters depend on every column being identical.

Fix: put it in a monospace context. In Discord and most chat apps, wrap it in a triple-backtick code block. In a README or a code comment it works unchanged. It will never work in a bio, because those fields are proportional and wrap text at their own width.

Still stuck?

If a character renders incorrectly on a device you own, that is worth reporting — which tool, which letter, which phone or browser. Those three details are what make it fixable. The contact page has an address.