Discord Text Formatting: The Complete Guide

Published May 6, 2026 · 9 min read

Discord gives you two completely separate ways to style text, and mixing them up is the single most common source of frustration. Markdown works inside messages. Unicode fonts work everywhere else — bios, display names, server names, channel names, status. This guide covers both, plus colored text, spoilers, and the formatting quirks that trip people up.

1. Markdown: Formatting Inside Messages

Discord uses a trimmed-down version of Markdown. Type the syntax on the left, get the result on the right. Everything here works in messages, thread replies, and forum posts.

A few rules that are not obvious:

• Escape a character with a backslash to show it literally: \*not italic\*.
• Markdown does not parse inside inline code or code blocks. That is the easiest way to show syntax to someone.
• Headings and lists only render at the start of a line.
• Shift+Enter inserts a line break without sending the message.

2. Colored Text with ANSI Code Blocks

Discord has no color syntax for normal messages, but it renders ANSI escape codes inside a code block tagged ansi. Open the block with three backticks followed by ansi, then use escape sequences before your text.

The foreground codes are 30–37 (gray, red, green, yellow, blue, pink, cyan, white) and the background codes are 40–47. Add 1; for bold or 4; for underline. Reset with 0 at the end so the color does not bleed into the next line.

Writing escape characters by hand is tedious — our Discord color text generator lets you pick colors visually and copies the finished code block. Two caveats worth knowing: colors render reliably on desktop and web, and mobile support has historically lagged; and because it is a code block, the text appears in monospace on a dark panel.

3. Unicode Fonts: Formatting Where Markdown Fails

Type **bold** into your Discord bio and you will see the asterisks, not bold text. That is because Discord only parses markdown in messages. Every other field is a plain text box.

Unicode fonts solve this. Characters like 𝗕 and 𝓑 are not styled letters — they are separate Unicode characters that happen to look bold or cursive. Since they are already the right shape, they need no formatting support at all and survive anywhere text is stored:

• Display name — 𝗬𝗼𝘂𝗿 𝗡𝗮𝗺𝗲
• About Me / bio — full Unicode support, including symbols and line breaks
• Custom status — works, with a fairly short character limit
• Server name and channel names — channels lowercase your input and replace spaces with hyphens, but Unicode letters survive
• Role names — useful for making a role visually distinct in the member list

Generate any style you need with our Discord fonts generator, then paste it straight into the field.

4. Spoilers, Quotes, and Embeds

• Spoilers: ||text|| hides content until clicked. You can also mark an attachment as a spoiler when uploading.
• Suppressing link previews: wrap a URL in angle brackets — <https://example.com> — to post it without the embed card.
• Masked links: [text](url) only renders inside embeds sent by bots and webhooks, not in a normal user message.
• Syntax-highlighted code: three backticks followed by a language name (js, py, diff) gives you colored code. diff is a popular way to fake green and red text.

5. Making Announcements Look Designed

A pattern that works well for rules channels and announcements: a Unicode-font title, a divider line, markdown headings for structure, and small subtext for the fine print.

• Use # and ## headings rather than bolding everything — headings create real hierarchy.
• Use -# subtext for timestamps, credits, and disclaimers so they recede visually.
• Break sections with a divider like ✦ ─────────── ✦ from our symbol collection.
• Box a title with our text border generator inside a code block, where monospace keeps the box aligned.

Common Problems and Fixes

• Asterisks showing literally: you are in a bio, name, or code block. Use a Unicode font instead.
• ASCII art losing alignment: put it in a code block. Proportional fonts break box drawing; monospace fixes it.
• Name showing as boxes for some users: their device's font lacks that character. Pick a more common style like bold or italic.
• Fancy text failing search: Unicode-styled names are hard to search for since the characters differ from plain letters. Keep your handle plain and style the display name.
• Screen readers: Unicode fonts are read out character by character or skipped entirely. Avoid them for anything that must be accessible, like rules text.

FAQ