Skip to content
All posts

Slack Markdown: Complete Formatting Guide for Messages & Posts (2026)

Every Slack Markdown feature explained — bold, italic, code, lists, quotes, links, block Kit vs mrkdwn, Canvas formatting, and the quirks that break when you paste from GitHub.

Slack calls its message formatting language mrkdwn — a Markdown-inspired syntax that looks familiar until your **bold** renders as nothing and your [link](url) shows up as literal brackets.

If your team lives in Slack, you format hundreds of messages a week. Getting the syntax right means clearer standups, cleaner incident threads, and release notes people actually read.

This guide is the complete Slack formatting reference: what works in messages, what works in Canvas, what breaks when you paste from GitHub or Notion, and the patterns power users rely on every day.

Slack mrkdwn vs. standard Markdown

Slack uses mrkdwn, not CommonMark or GFM. The overlap is partial:

You typeSlack resultStandard Markdown
*bold*bolditalic in GFM
_italic_italicitalic
~strike~strike~~strike~~ in GFM
`code`codesame
> quoteblock quotesame
• item or - itembulletbullet
1. itemnumbered listsame
# Headingbold line (not a heading block)H1
[text](url)literal text in messageslink
**bold**literal ** in many contextsbold

The #1 mistake: using GitHub-style **double asterisks** for bold. In Slack messages, bold is single asterisks: *bold*.

Bold, italic, and strikethrough

*bold text*
_italic text_
*bold with _nested italic_*
~strikethrough~

Keyboard shortcuts (desktop app):

ActionmacOSWindows / Linux
Bold⌘BCtrl+B
Italic⌘ICtrl+I
Strikethrough⌘Shift+XCtrl+Shift+X

Select text first, then use the shortcut — more reliable than typing delimiters around long phrases.

Inline code and code blocks

Inline code uses single backticks:

Run `npm run build` before deploy.

Multi-line code blocks use triple backticks on their own lines:

{
  "status": "ok",
  "version": "2.0.0"
}

Add a language hint for syntax highlighting in Slack:

{"status": "ok"}

Supported languages include javascript, typescript, python, bash, json, yaml, sql, go, rust, and markdown. Unknown tags still create a monospace block without colors.

Tip for incident channels: wrap logs and stack traces in fenced blocks — Slack collapses long unformatted text and makes threads unreadable.

Block quotes

Start a line with >:

> Production is degraded. ETA 30 minutes.
> Tracking in #incidents.

Multi-line quotes: prefix each line with >, or use the Block quote button in the formatting toolbar.

Quotes work well for:

  • Quoting a previous message's decision
  • Highlighting action items at the top of a thread
  • Separating context from the ask

Lists

Bulleted

• First item
• Second item
  ◦ Nested item (use bullet toolbar or paste)

You can also type - or * at the start of a line — Slack converts them to bullets.

Numbered

1. Deploy to staging
2. Run smoke tests
3. Promote to production

Press Enter after 1. and Slack continues the sequence automatically.

Checklists (Canvas and posts)

In Slack Canvas and some Channel posts, interactive checklists are available via the UI. In regular DMs and channel messages, simulate tasks with emoji:

:white_check_mark: Done — API keys rotated
:hourglass_flowing_sand: In progress — dashboard migration
:x: Blocked — waiting on DNS

Use the emoji picker tool to copy :shortcode: names fast.

In messages composed with Shift+Enter (full composer) or via the API, links use angle brackets:

<https://trymarkdownviewer.com|Markdown Viewer>

Format: <URL|display text>. Without the pipe, Slack shows the raw URL as a clickable link.

What does NOT work

Standard Markdown links fail in most message contexts:

[Markdown Viewer](https://trymarkdownviewer.com)

This renders as literal brackets and parentheses — one of the most common Slack formatting frustrations.

Workarounds:

  1. Paste a bare URL — Slack auto-links it.
  2. Use Cmd/Ctrl+K on selected text (composer toolbar).
  3. Use <url|label> mrkdwn when posting via workflows or bots.

Headings in Slack

Typing # Heading in a message does not create a heading block — Slack bolds the line or treats # inconsistently depending on context.

For visual hierarchy in long posts:

*Release v2.0 — API Platform*

*What shipped*
• 28 REST endpoints
• Stripe billing

*Breaking changes*
• Old `/api/render` path removed — use `/api/v1/render`

Use bold lines as faux headings. For real document structure, use Canvas or a Channel post.

Slack Canvas formatting

Canvas (Slack's collaborative doc surface) supports richer formatting than chat messages:

  • True headings (H1, H2, H3)
  • Tables
  • Checklists with clickable boxes
  • Code blocks with highlighting
  • @mentions and linked channels
  • Embedded images and files

Canvas is where you draft runbooks, onboarding docs, and meeting notes that need structure. Chat is for fast updates; Canvas is for persistent team knowledge.

When exporting or copying Canvas content to Markdown, expect layout loss — tables and checklists may flatten. Preview cleanup in the Markdown formatter before committing to a Git repo.

Slack Block Kit (for apps and bots)

If you build Slack apps, Block Kit replaces mrkdwn for structured layouts. Block Kit uses JSON, not Markdown:

{
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "*Deploy complete*\n<https://example.com|View logs>"
      }
    }
  ]
}

The mrkdwn field inside blocks does support *bold*, _italic_, ~strike~, and <url|label> links — but not full GFM tables or fenced code with all languages.

For programmatic message formatting at scale, use the Markdown API render endpoint to convert Markdown to HTML, then map sections to Block Kit blocks.

Threads, mentions, and special tokens

<@U12345678>          @mention a user by ID
<#C12345678>          Link a channel
<!here>               Notify active channel members
<!channel>             Notify everyone in channel
<!everyone>            Notify all workspace members (admin-gated)

User mentions by display name: type @ and pick from the autocomplete — do not guess the ID syntax.

Emoji: :rocket: :white_check_mark: :warning: — Slack ships with 2,600+ shortcodes. :emoji_name: works in messages, Canvas, and Block Kit mrkdwn fields.

Pasting from GitHub, Notion, or email

SourceWhat breaks in SlackFix
GitHub README**bold**, [links](url)Convert ** → *, use <url|label> or bare URLs
Notion exportHeadings, callouts, tablesPaste into HTML to Markdown, simplify, re-paste
Discord__underline__, `
Email HTMLAll formattingStrip with HTML to Markdown first

Fast conversion workflow:

  1. Paste source into HTML to Markdown or the editor.
  2. Run GFM checklist if coming from GitHub.
  3. Find-replace ** → * for Slack-bound text.
  4. Copy sections into Slack.

Formatting for common workplace scenarios

Daily standup

*Standup — June 5*

*Yesterday*
• Shipped API playground error reference
• Fixed robots.txt crawl rules

*Today*
• Publish platform guides
• Load-test rate limiter

*Blockers*
• None

Incident update

```
:red_circle: *INC-284 — Elevated API latency*

*Impact:* ~15% of render requests > 2s
*Status:* Investigating
*ETA:* Update in 20 min
*Lead:* @alice

```json
{"p99_ms": 2100, "region": "us-east"}
```
```

Release announcement

:rocket: *v2.0 — Markdown API Platform*

*Highlights*
• 28 REST endpoints — render, convert, extract, audit
• Pro plan: $3/mo, 10k requests/day
• <https://trymarkdownviewer.com/docs|API docs> and <https://trymarkdownviewer.com/api/playground|playground>

Full changelog: <https://trymarkdownviewer.com/changelog|/changelog>

Customer-facing post (channel post)

Use Channel posts for formatted announcements that should not get buried in chat. They support richer layout and can be cross-posted to multiple channels.

Slack vs. Discord vs. GitHub formatting

FeatureSlackDiscordGitHub
Bold*text***text****text**
Italic_text_*text**text*
Strikethrough~text~~~text~~~~text~~
Link syntax<url|label>bare URL[label](url)
Headings in chatfaux bold# H1# H1
TablesCanvas onlynoyes
Spoilersno||text||no

Keep the Discord Markdown guide and this page bookmarked if you work across communities and workplace chat.

Common Slack Markdown mistakes

1. **double asterisks** for bold. Use *single asterisks* in Slack messages.

2. Markdown link syntax in chat. Use <url|label>, bare URLs, or Cmd+K.

3. Fenced code without blank lines. Triple backticks must sit on their own lines.

4. Pasting huge tables from GitHub. Slack messages are not table renderers — use Canvas or attach a file.

5. @everyone for non-urgent news. Reserve channel-wide pings for real emergencies.

6. Mixing Canvas and message syntax. Canvas headings do not copy cleanly into mrkdwn messages.

7. Forgetting thread etiquette. Long updates belong in a thread, not the main channel — formatting cannot fix notification spam.

Preview before you post

Paste your draft into the Markdown editor to sanity-check structure. Map formatting mentally:

  • **bold** in preview → change to *bold* for Slack
  • [links](url) → convert to <url|label>
  • Headings → bold lines or move to Canvas

For automated pipelines (CI → Slack webhook), render Markdown to HTML with the API, then format the summary as mrkdwn for Block Kit.

Quick reference

SyntaxPurpose
*bold* _italic_ ~strikethrough~Inline styles
`inline code`Inline code
Triple-backtick fenceCode block
> quote lineBlock quote
• item or - itemBulleted list
1. itemNumbered list
<https://url>Auto-linked URL
<https://url|Label>Named link (mrkdwn)
:emoji_name:Emoji shortcode
<@USERID> <#CHANNELID>Mentions
*Section title*Faux heading in messages

Slack formatting is learnable in an afternoon and pays back every message you send. Master *bold*, fenced code, <url|label>, and bold-line sections — that covers 95% of workplace communication.

Written by Markdown Viewer Team. Found this useful? Try the editor →

Keep reading

Hand-picked articles related to this one.