Discord Font Generator

Where Discord fonts work: every field and its limit

Fancy fonts do not work in Discord usernames, and any page telling you otherwise is out of date. Since Discord’s 2023 username migration, usernames are 2 to 32 characters of lowercase a–z, digits, underscore and period only, and styled characters are rejected outright. The place for a styled name is your display name or a per-server nickname, both of which accept most Unicode and allow up to 32 characters.

Everywhere else, styled text is fair game, and each field has a hard cap worth knowing before you paste. Server names take 2 to 100 characters and channel names 1 to 100, which is why server owners style category headers and channel titles so heavily. Channel topics allow 1,024 characters (4,096 in Forum and Media channels). The About Me bio caps at 190 characters and explicitly accepts Unicode characters, emojis, markdown and links.

Messages allow 2,000 characters on a free account and 4,000 with Nitro; go past your cap and Discord converts the message into an attached .txt file instead of sending it as text. A styled letter still counts as one character against these limits, and the counter on this page proves your styled output fits before you paste. All limits above are taken from Discord’s own support and developer documentation as of August 2026.

Unicode fonts vs Discord markdown: two different systems

There is no setting to change Discord’s font. The app renders everything in gg sans, the typeface that replaced Whitney, and no native option swaps it out. What a font generator does instead is substitute each letter with a lookalike character from a different Unicode block (𝕕 for d, 𝖋 for f), so the “font” is baked into the text itself and works in any field that accepts Unicode: names, nicknames, channels, topics, bios and messages alike.

Markdown formatting is the other system, and it only works inside messages and your bio. Wrap text in *asterisks* for italic, **double asterisks** for bold, __double underscores__ for underline, ~~tildes~~ for strikethrough, and stack them freely. Start a line with #, ## or ### followed by a space for headers, or -# for subtext, the small grey line most guides still miss. Masked links use [text](url), quotes use > or >>>, spoilers use ||double pipes||, and a backslash escapes any of it.

Two markdown behaviours trip people up. Spoiler tags are negated inside code blocks, so you cannot hide code behind a spoiler. And Discord collapses runs of extra whitespace in messages, which is what breaks pasted ASCII art. Wrap it in a code block (triple backticks) and the spacing is preserved exactly.

Colored text is possible too, though only through code blocks: open a code block tagged with a language for syntax highlighting, or tagged ansi with ANSI escape codes for specific colors. It renders on desktop and web, and it is the closest thing Discord has to colored messages.

Why fonts show as boxes, and other honest fixes

Styled text shows up as boxes or question marks when the reader’s device lacks a glyph for that Unicode block. Older phones and some system fonts simply do not ship every mathematical alphanumeric character. The fix is choosing widely supported styles for anything important: bold and italic variants render almost everywhere, while the more ornate scripts fail more often on older Android builds.

Search and mentions match literal characters. A styled channel name or nickname will not match a plain-text search inside Discord, and typing a plain @name will not autocomplete a fully styled nickname. Keep at least part of any name you want findable in normal characters.

If what you actually want is to change the font of the Discord app itself, be aware of the trade-off: client mods can restyle the interface, but modified clients violate Discord’s Terms of Service. Pasting Unicode-styled text carries no such risk. It is ordinary text, the same as typing an accented letter, and breaks no rule.

Accessibility: use fancy fonts as decoration, not content

Screen readers handle Unicode-styled text badly. They either announce each styled letter one code point at a time or skip the word entirely. A message written wholly in a fancy script can be unreadable to a blind member of your server.

The practical rule: style names and decoration, keep content plain. A styled display name, a decorated category header or a channel title reads fine as an identifier, because members recognise it visually and rarely need it read aloud. Announcements, rules and anything members must actually read belong in plain text, with markdown bold or headers for emphasis. Markdown styling is real text underneath, so screen readers handle it normally.