Copy a character
Tap any character above. Hangul filler (U+3164) is the most reliable for Discord nicknames — braille blank (U+2800) is the fallback if a server filters U+3164.
Platform guide
Copy Hangul filler and braille blank characters for Discord server nicknames, display names, the 190-character About Me bio, and messages. Each one is tested against Discord's actual field limits — and against the new username system that rejects them.
Discord split its name system in 2023. The unique @username (lowercase letters, digits, period, underscore, 2–32 characters) rejects invisible characters outright. The display name and per-server nickname both accept most Unicode up to 32 characters, which is where invisible characters still work — a single Hangul filler (U+3164) in the nickname field renders as a blank name in the member list. The About Me bio gives you 190 characters with full Markdown, emojis, and links, and standard messages give you 2,000 (4,000 on Nitro). Discord's own API docs note that it 'limits some zero-width and non-rendering characters,' so braille blank (U+2800) is the safer default over zero-width space (U+200B), which gets filtered more often.
Tap any character above. Hangul filler (U+3164) is the most reliable for Discord nicknames — braille blank (U+2800) is the fallback if a server filters U+3164.
Paste into a server nickname (Edit Per-Server Profile), your display name, your About Me, or a message. The unique @username is the one exception: lowercase alphanumeric only, no invisible characters.
Long-press the field, choose Paste, then save. The name or message disappears from view, but Discord still counts it toward the 32-character nickname cap or the 190-character bio cap.
Paste a Hangul filler into the per-server nickname field and your name shows blank in that server's member list and chat. Your global display name stays unaffected.
The 190-character bio supports Markdown but trims trailing spaces. Invisible characters give you real indentation and centered text layouts that plain spaces can't hold.
Discord blocks truly empty messages. One invisible character posts a blank line — useful as a spacer between spoilers or sections of a longer message.
If you build Discord bots, a zero-width space (U+200B) in an embed field name satisfies the API's non-empty requirement while keeping the field visually blank.
Make your name blank in a specific server. Caps at 32 characters; overrides your global display name only inside that server.
Add invisible padding to your global name. Accepts most Unicode up to 32 characters — though Discord now often requires at least one visible glyph.
Send a blank line or use invisible spacing inside a 2,000-character message (4,000 with Nitro).
Lay out a 190-character bio with real line breaks and indentation. Markdown renders, but invisible characters survive places Markdown can't reach.
The 2023 username migration is the defining fact. Unique @usernames accept only lowercase a–z, 0–9, period, and underscore — no invisible character will save there, full stop. Display names and server nicknames both accept most Unicode up to 32 characters, and Discord's API documentation explicitly says it 'limits some zero-width and non-rendering characters,' which is why Hangul filler (U+3164) outperforms zero-width space (U+200B) in practice. The About Me bio holds 190 characters and supports full Markdown, links, and emojis — same limit on Nitro. Standard messages cap at 2,000 characters, Nitro at 4,000. One gotcha: a growing number of moderation bots scan messages for zero-width characters as a spam signal, so invisible text in a public server can trip an automod rule even when Discord itself accepts it.
Server nicknames (1–32 characters), display names (1–32), the About Me bio (190), and messages (2,000 standard, 4,000 Nitro) all accept invisible Unicode characters, with Hangul filler (U+3164) and braille blank (U+2800) the most reliable. The unique @username is the hard exception — Discord restricts it to lowercase a–z, 0–9, period, and underscore, so no invisible character will save there. Discord's API docs state it 'limits some zero-width and non-rendering characters,' which is why zero-width space (U+200B) is hit or miss outside of bot embeds. Rendering is consistent across the desktop app, browser client, iOS, and Android; some third-party moderation bots independently filter invisible characters, so behavior in a given server depends on what the admins have installed.
No. The unique @username accepts only lowercase letters, digits, period, and underscore. You can make your per-server nickname or display name appear blank, but your @handle always shows on your profile page.
Hangul filler (U+3164). It renders as blank across desktop, iOS, and Android, and passes Discord's name validation more reliably than zero-width space (U+200B). Braille blank (U+2800) is the fallback if a specific server filters U+3164.
Three common causes. You pasted into the @username field, which strips them. Discord's validation flagged the specific character on that build. Or the server has a bot that reverts blank nicknames. Re-paste with Hangul filler (U+3164) and test in a private server.
Yes. The About Me bio caps at 190 characters and standard messages at 2,000 (4,000 on Nitro). Invisible characters count the same as visible ones.
Invisible characters are standard Unicode and aren't prohibited by Discord's guidelines. That said, some moderation bots treat zero-width characters as a spam signal, and using blank names to evade or impersonate can still get you actioned.
Yes — this is one of the better uses. A zero-width space (U+200B) in an embed field name satisfies Discord's non-empty requirement while keeping the field visually blank. It's a common layout trick for rich embeds.
Pick Hangul filler (U+3164) for a blank nickname, or braille blank if you want a fallback. Paste it into a server nickname and check the member list.
Copy a characterExplore invisible text generators for other platforms