Tolz.me
DiscordFormattingMarkdown

Discord Text Formatting Guide: Every Style With Examples

A practical Discord markdown reference for bold, headers, subtext, masked links, code blocks, ANSI colors, spoilers, timestamps, and small text.

Tolz.me team8 min read
Illustration of chat bubbles containing bold, italic, and code-styled text in a Discord-style chat

Discord formatting is markdown with a few platform-specific extras. Most of it is quick to type once you have used it a few times, but the edge cases matter. A header that starts one space too far right stays a header only if the client agrees, a masked link works in one place and not another, and colored code blocks look different on a phone.

This reference covers the styles you will actually use, with an example for each. Keep the text formatter open if you would rather copy the syntax than type it.

Bold, italic, underline, and strikethrough

**bold**
*italic*
__underline__
~~strikethrough~~
***bold italic***

Bold uses two asterisks on each side. Italic uses one. Underline uses two underscores. Strikethrough uses two tildes. You can combine bold and italic with three asterisks, and some mixed combinations such as bold plus underline also parse. Nested styles get less predictable across clients, so check the preview if the formatting carries meaning.

Do not use underscores for emphasis inside a word. Discord may read them as literal characters or create unexpected italics. Asterisks are safer for general emphasis. Save bold for labels and short warnings, not entire paragraphs. A wall of bold text is harder to read than plain text.

Headers

# Large header
## Medium header
### Small header

A header marker has to be at the start of a line, followed by a space. Discord renders three heading sizes. They work well in pinned messages, server guides, and long announcements where members need to scan sections. They are less useful in a fast-moving chat, where a large heading pushes the conversation off screen.

If a header does not render, check for a leading space before the `#`. That one space is enough to make Discord treat the line as ordinary text.

Subtext

-# This line renders as subtext

Subtext is the small gray line you see under some Discord announcements. The `-#` prefix must start the line and be followed by a space. It is a message format, not a font, so it will not work in a display name or nickname. Every line needs its own prefix.

Use it for timestamps, footnotes, and secondary details. Do not put rules or warnings in subtext. Small gray text is easy to skip, especially on a phone.

Lists

- First item
- Second item
  - Nested item

1. First step
2. Second step

Discord accepts hyphens or asterisks for bullet lists and numbers followed by a period for ordered lists. Indent nested items with spaces. Keep each item short. A list with long wrapped sentences stops looking like a list and starts looking like paragraphs with dots.

For a checklist in a pinned message, a plain bullet list is usually clearer than a row of emoji. If you need actual checkboxes, a bot or an external task tool is a better fit. Discord does not turn `[ ]` into an interactive checkbox.

Block quotes

> This line is quoted.
>>> This line and everything after it
is part of the same block quote.

A single `>` quotes one line. Three of them (`>>>`) quote the rest of the message, which is handy for pasting a longer excerpt without adding a marker to every line. Quotes are useful for rules, support replies, and separating an announcement from the discussion around it.

Inline code and code blocks

Use `npm run build` to check the project.

```js
const message = "Hello";
console.log(message);
```

Single backticks style a short piece of text as inline code. That is the right choice for file names, commands, and short strings. Triple backticks create a code block, which keeps spacing and turns off markdown inside the block.

Adding a language tag after the opening fence enables syntax highlighting for that language. `js`, `json`, `python`, `css`, `html`, and many others are recognized. Highlighting depends on the client, so a block that looks colored on desktop may appear plain elsewhere. The text itself is unchanged.

Code blocks are also the safest way to show markdown syntax to someone else. A code block full of asterisks will not turn into bold text.

ANSI colored code blocks

```ansi
\u001b[0;31mRed text\u001b[0m
\u001b[0;32mGreen text\u001b[0m
\u001b[0;34mBlue text\u001b[0m
```

The backslash-u sequence above stands for the escape character that starts each ANSI sequence. Discord needs the real character, not the printed notation, which is why copying a block from a generator is safer than retyping it.

Discord can render a limited set of ANSI colors inside a code block tagged `ansi`. The block contains escape sequences around the text. The color text generator builds those sequences for you so you do not have to paste invisible control characters by hand.

Colored text is a desktop feature in practice. Some mobile clients show the code block in monospace without applying the colors. Never use color alone to carry meaning. If red means urgent, add the word urgent as well.

Masked links

[Tolz.me tools](https://tolz.me/tools)

A masked link shows your label instead of the full URL. The syntax is regular markdown: square brackets for the label, parentheses for the address. The important catch is where it works. As of writing, masked links render in embed descriptions and field values, and in embeds sent by bots or webhooks. They do not reliably render in ordinary user messages, where the raw markdown may show instead.

If you need a clickable label in a normal message, send the plain URL. If you control the embed, use the markdown link and test it in a private channel first.

Spoilers

The ending is ||the ship sinks||.

||A whole hidden sentence.||

Double pipes hide text behind a gray bar until someone clicks or taps. You can spoil a single word, a whole line, or several adjacent sections. Nested spoilers are not reliable, so keep one layer. A pipe character inside the hidden text can end the spoiler early, which is why the spoiler text generator checks for stray pipes.

Images use a different mechanism. Attach the image, then choose Mark as spoiler in the upload preview before sending. On mobile, select the attachment and use the spoiler option in the preview. Bot uploads can prefix the filename with `SPOILER_`.

Timestamps

<t:1760000000:F>
<t:1760000000:R>

Timestamps use a Unix time in seconds inside a `<t:...>` tag. The letter after the second colon sets the style. `t` is short time, `T` is long time, `d` is short date, `D` is long date, `f` is short date and time, `F` is long date and time, and `R` is relative time such as in two hours.

The value is always the same moment. Discord translates it into each reader's local timezone, which is the reason to use a timestamp instead of typing a time by hand. The timestamp generator converts a date and lets you compare styles before copying.

Unicode small text and fancy names

There are two different kinds of small text. Subtext uses the `-#` prefix and works in messages. Unicode small caps, superscript, and subscript use separate characters that look smaller or styled. They work in display names, nicknames, bios, and messages, but they are not real font changes. Each device renders them with the fonts it has installed.

Unicode styles have gaps. Not every letter has a subscript form, and screen readers may pronounce small caps letter by letter or skip them. Use them for short labels and decorative names, not for instructions or anything a member must understand on the first read. The small text generator shows which letters convert cleanly.

Discord usernames are stricter than display names. They allow lowercase letters, numbers, periods, and underscores, so fancy Unicode usually fails there. Put styled text in your display name or server nickname instead.

Combining styles without making a mess

  • Use one heading level for the main sections of a long post and subtext for the small details.
  • Bold a label, then write the value in plain text. Do not bold the value too.
  • Use inline code for commands and exact text, and code blocks for anything that depends on spacing.
  • Keep ANSI color for short highlights. It is not a substitute for structure.
  • Use spoilers for genuine surprises and content warnings, not for ordinary text that people need to read.

A useful test is to strip the formatting and read the message as plain text. If it still makes sense, the formatting is supporting the content. If it falls apart, the structure was doing too much work.

Client differences to expect

Discord desktop, web, iOS, and Android do not render every style the same way. Headers and code blocks are broadly consistent. ANSI colors are the least consistent. Spoiler reveal gestures vary. Masked links depend on whether you are inside an embed. When a post matters, check it on the device your members use most.

Formatting is also only half the message. A well-formatted announcement still needs a clear time, a short explanation, and one obvious next step. The style should make that easier to find, not compete with it.

Tools used in this guide

Open a tool, make the change, and copy the result. No account needed.