You set a fancy name, it looked perfect — then a friend (or the game) shows it as □□□ or ???. Nothing is broken on your end. The other device just can’t draw those characters.
Because the app, game or phone that’s displaying your name doesn’t have a picture (a glyph) for the fancy characters you used, so it draws an empty box (□) or a question mark instead. This is called tofu, and it’s decided by the viewer’s device, not yours — which is why your name looks fine to you and broken to them. The fix is to switch to a widely-supported style: bold, italic, small caps and script render almost everywhere, while fraktur, double-struck, zalgo and rare symbols are the ones that box out.
Your name is ordinary Unicode text — the fancy letters are real characters. To show them, each device reaches into its own fonts for a matching picture. When a font has no picture for a character, it falls back to the “not defined” box (□) or a ?. Old phones, game clients with a small built-in font, and some desktop apps hit this most.
The key point: the box is drawn where the name is read, so the same name can look perfect on your phone and broken on someone else’s. See the full mechanism in why fonts show as boxes and boxes vs mojibake vs question marks.
Re-generate the same name in a more compatible style and paste it again:
𝗕𝗼𝗹𝗱 · 𝘐𝘵𝘢𝘭𝘪𝘤 · ꜱᴍᴀʟʟ ᴄᴀᴘꜱ — safe · 𝕯𝖔𝖚𝖇𝖑𝖊 — risky
Game name fields usually ship a small built-in font, so a character it can’t draw shows as a box and can trip the game’s filter — some games then refuse to save the name at all. If a symbol shows as □ or ? in the preview, treat it as unsupported and replace it before you spend a rename card. More on that in why was my game name rejected.
Generate your name in bold, italic or small caps — the styles that display on every device — and copy it in one tap.
Open the Text Generator →Because the device or app displaying your name has no glyph for the fancy characters you used, so it draws an empty .notdef box instead. It is a missing-font problem on the viewer’s side, not corrupted text, and it happens most with fraktur, double-struck, zalgo and rare symbols.
Same cause, different fallback. Some systems substitute a question mark for an unsupported character rather than a box. Both mean the character could not be rendered on that device.
Re-create it in a widely-supported style — bold, italic, small caps or script — and avoid fraktur, double-struck, zalgo and obscure symbols. Those safe styles render on virtually every phone and app.
The box is drawn by the reader’s device using its own fonts. Your phone has the glyph, theirs does not, so the same text renders on yours and boxes out on theirs — especially on older devices.
No. The underlying characters are intact; only the picture is missing on that device. Copy the name into a plain-text field and it is still the same text.