Discord Markdown vs Unicode fonts: which one do you need?

A side-by-side of what Discord Markdown can format (bold, italic, spoilers, headers) versus what pasted Unicode letters add to nicknames, channel names and statuses.

Updated 25 September 2026

Discord has two completely separate ways to make text look different, and people constantly reach for the wrong one. Markdown is built into the message box: type two asterisks around a word and it comes out bold. Unicode fonts are pasted characters that look styled on their own, with no syntax at all. The first works only inside messages; the second works almost everywhere else. Knowing which is which saves a lot of “why is my nickname full of asterisks” moments.

What Discord Markdown can do

Markdown is a formatting shorthand that Discord converts when it displays a message. It is invisible to the reader, it uses Discord’s own font, and it is read perfectly by screen readers because the underlying letters are ordinary. The full set at the time of writing:

A few things Markdown will never do: change the typeface, change the colour of ordinary text, or apply to anything that is not a message. Nicknames, display names, server names, channel names, role names, custom statuses, “About me” bios and thread titles all ignore Markdown completely. Type **Nova** into the nickname box and your name will literally be Nova with the stars showing.

There is one trick within Markdown for colour: certain code-block language names (diff, fix, ini, css) colour parts of the block, which some servers use for coloured announcements. It is fragile, breaks on mobile in places, and is not readable as normal text, so treat it as a novelty.

What Unicode letters add

Unicode fonts are not formatting. Each 𝕹 or ɴ is a real character with its own code point that happens to resemble a styled letter. Discord stores it like any other text. That has two consequences that matter here.

First, the styling survives in places Markdown cannot reach. Anything that accepts text accepts these characters:

• Display name and per-server nickname, up to 32 characters. Nicknames are set per server, so you can be 𝕹𝖔𝖛𝖆 in one community and plain Nova elsewhere. Your unique username stays lowercase letters, digits, underscores and periods; nothing styled will save there.
• Custom status, the line under your name in the member list.
• Channel names. Text channel names are lowercased and spaces become hyphens, but styled letters are accepted, which is how servers end up with 「𝐠𝐞𝐧𝐞𝐫𝐚𝐥」 or ┃𝘢𝘯𝘯𝘰𝘶𝘯𝘤𝘦𝘮𝘦𝘯𝘵𝘴 channels. Voice channels and categories allow spaces and capitals as well.
• Server names and role names. Role names show in the member list and on hover, so a Small Caps role label reads as a heading.
• Messages, mixed freely with Markdown. **𝕹𝖔𝖛𝖆** is valid, though bolding an already-bold character does nothing visible.
• Embed fields and webhook names, if you run bots.

Second, the style is fixed at paste time. Markdown adapts to the reader’s theme and font size; a Unicode letter always looks like that letter, and on a device without the right font it becomes a box. The why fonts show as boxes guide explains which styles are safest; for Discord, Bold Sans, Bold Serif, Small Caps and Double Struck are broadly safe on desktop and mobile.

Side by side

The short version: inside a message, use Markdown. Outside a message, Unicode is the only option. If you want a look Markdown cannot produce, such as a Gothic Fraktur clan name or a ꜱᴍᴀʟʟ ᴄᴀᴘꜱ divider, Unicode is the tool even in messages.

Practical patterns servers use

Nicknames with a tag. A bracketed clan tag plus a styled name, for example 「ᴋɪɴɢ」 𝗡𝗼𝘃𝗮. The discord fonts page has frames like ☬ and 【】 built for this. Keep it under 32 characters including the frame.

Channel prefixes. Many servers give each channel a symbol prefix such as 📌, ┃ or ꒰, then a lowercase styled word. Because channel names appear in the sidebar at a small size, thin styles (Cursive Script, Italic Serif) look scratchy there; Bold Sans, Bold Italic Sans and Small Caps stay crisp. The symbols collection has the vertical bars, dots and arrows people use as separators.

Role headers. Some admins create hoisted roles with names like ─── ꜱᴛᴀꜰꜰ ─── purely to act as headings in the member list. This works because role names accept any text and Unicode dividers draw at the same width on most fonts.

Statuses and bios. A Small Caps or Bold Cursive status line reads as a signature. The About me section supports Markdown links but not other formatting, so styled letters are the only way to make a bio line stand out.

For a competitive look, the gaming fonts page groups the styles that suit gamer tags, and the gothic fonts page collects Fraktur and Old English variants for darker server themes.

Zalgo and glitch text etiquette

Glitch text, often called Zalgo, stacks dozens of combining accent marks on each letter so the text appears to bleed upward and downward across other lines. Discord renders it, and that is precisely the problem. Heavy glitch in a message overlaps the messages above and below, hides usernames and timestamps, and on some clients makes the whole channel scroll strangely. Used as a nickname it spills over the member list; used as a channel name it can make the sidebar unreadable.

Most moderated servers treat this as spam or “unreadable text” under their rules, and the Discord automod can be configured to block messages with a high density of combining characters. Practical guidelines:

• Use the Glitch Light variant, which adds only a few marks and stays within the line height.
• Keep it to a single word, not a whole message or name.
• Never put it in a channel or role name that other people have to navigate.
• Ask before using it in a server you do not run; a mod will simply rename you otherwise.
• Remember that a screen reader either reads every combining mark by name or gives up entirely, so the word is lost to blind users.

The glitch fonts page includes the lighter version alongside the heavy one so you can pick a level that fits the room.

Quick checklist

• Markdown formats messages only; use **, *, __, ~~, backticks, || and # there.
• Nicknames, statuses, channel, role and server names ignore Markdown, so paste Unicode fonts instead.
• Unicode letters are not searchable and may not be read by screen readers; keep a plain version of anything important.
• Prefer Bold Sans, Small Caps, Double Struck or Gothic Fraktur; they render reliably across Discord clients.
• Keep glitch text light, short, and out of channel and role names.