Slack Markdown & Formatting Guide: Bold, Lists, Code Blocks, Tables, Links, Quote Blocks (+ Fixing the Missing Toolbar)

Slack Markdown & Formatting Guide: Bold, Lists, Code Blocks, Tables, Links, Quote Blocks (+ Fixing the Missing Toolbar)

Here is the first thing every Slack markdown guide should say and most don't: Slack doesn't use Markdown. It uses its own dialect, which Slack's developer docs call mrkdwn, and it is close enough to the real thing to be confusing. Bold is one asterisk, not two. Underscores mean italic, not bold. There are no headings. There are no tables. If you've ever typed **important** into a message and watched it post with the asterisks still attached, you've met the gap this Slack formatting guide exists to close.

Below is the full cheat sheet — bold, italic, strikethrough, code, quote blocks, lists, links, mentions, emoji — with the exact characters to type. Then the two things people search for most: how to fake a Slack markdown table, and how to get the formatting toolbar back when it vanishes. Everything here describes Slack on desktop; mobile shares the syntax but hides most of the toolbar.

The Slack Formatting Cheat Sheet

Type the characters in the second column and Slack converts them as you go. All of it works in channels, DMs, threads, and message edits.

Format Type this Shortcut (Mac / Windows)
Bold *bold text* ⌘ B / Ctrl B
Italic _italic text_ ⌘ I / Ctrl I
Strikethrough ~struck text~ ⌘ ⇧ X / Ctrl Shift X
Inline code `code` (single backticks) ⌘ ⇧ C / Ctrl Shift C
Code block ``` on its own line, code, ``` ⌘ ⌥ ⇧ C / Ctrl Alt Shift C
Quote block > quoted line ⌘ ⇧ 9 / Ctrl Shift 9
Bulleted list - or * at the start of a line ⌘ ⇧ 8 / Ctrl Shift 8
Numbered list 1. at the start of a line ⌘ ⇧ 7 / Ctrl Shift 7
Link on selected text select words, then the link icon ⌘ ⇧ U / Ctrl Shift U
New line without sending — ⇧ Enter / Shift Enter
Show or hide the toolbar the Aa icon ⌘ ⇧ F / Ctrl Shift F

Shortcuts suit text you've already selected; typed markup suits text you're still writing. More keystrokes live in our Slack keyboard shortcuts guide.

Text Styles: Bold, Italic, Strikethrough

*one asterisk* is bold. This is the biggest source of Slack markdown confusion, because in GitHub, Notion, Discord, and nearly everywhere else one asterisk is italic and two are bold. Type **two** in Slack and you get a bold asterisk on each side of your word.

_underscores_ give you italic, ~tildes~ give you strikethrough, and styles nest: *_bold italic_* works. The markers must hug the text with no space inside (* not bold * stays plain) and open and close on the same line. To keep a literal asterisk or underscore, wrap it in inline code; Slack has no backslash escaping in the composer.

Inline Code and Code Blocks

Single backticks produce inline code: a monospace span that Slack leaves exactly as typed — no smart quotes, no auto-linking, no emoji conversion. A file path with underscores, or a :), gets mangled in plain text and survives inside backticks.

Three backticks start a code block. On desktop, typing ``` turns the composer into a grey monospace box; paste your content, then arrow out of the block to continue in normal text. Code blocks preserve indentation and line breaks, which makes them the right home for logs, stack traces, SQL, and anything else a machine produced. There is no syntax highlighting and no language tag — ```python just puts the word "python" on the first line.

Quote Blocks

Start a line with > (angle bracket, space) and it becomes a Slack quote block: indented, with a vertical bar down the left. Each new line inside the quote needs its own > unless you're using the toolbar's quote button, which keeps quoting until you toggle it off. The legacy >>> form, which quotes everything to the end of the message, still works with raw markup turned on (more below); the default visual composer treats it as a single-line quote.

Quote blocks are underused: paste the exact sentence you're replying to, write under it, and the "wait, which part?" round-trip disappears.

Bulleted and Numbered Lists

Type - or * (hyphen or asterisk, then a space) at the start of a line and Slack converts it into a bullet. Type 1. and you get a numbered list that keeps counting as you press Enter. Press Enter on an empty item to end the list. Tab indents a sub-item; Shift Tab outdents.

One gotcha: lists are a feature of the composer, not of mrkdwn itself. Sending via the API or a workflow, there's no list markup — you insert a literal bullet character (•) or use Block Kit's rich_text list elements. And if you want a list people can vote on or tick off, that's what polls and Slack Lists are for.

Links, Mentions, Channels, and Emoji

Paste a URL and Slack auto-links it, usually with a dismissable preview card. To put a link behind words instead, select the text and press ⌘ ⇧ U (Ctrl Shift U), or click the toolbar's link icon, and paste the URL into the popover. The Markdown [text](url) form does not work in the composer — you'll post it verbatim. In Block Kit and the API, the form is <https://example.com|link text>.

Mentions and channel links are just @name and #channel typed inline; a picker appears after a couple of characters and Enter locks it in. @here notifies active members, @channel everyone, and user groups like @design-team a defined set — use the narrowest one that works. Emoji are shortcodes between colons: :tada: renders 🎉, :white_check_mark: renders ✅, and custom emoji use the same syntax.

The Formatting Toolbar vs. Raw Markup

By default, Slack's composer is WYSIWYG: a toolbar sits under the message box with buttons for bold, italic, strike, link, lists, quote, and code, and typed markup converts live — type *hello* and the word turns bold before you send. The Aa icon collapses or expands the toolbar; ⌘ ⇧ F does the same.

Some people hate this — the live conversion eats characters you meant literally. For them there's a switch: Preferences → Advanced → "Format messages with markup." Check it and the toolbar goes away, the composer stops converting as you type, and your message shows the raw *asterisks* until you hit send, at which point Slack renders them. It's cleaner if you already know the syntax, and it's the only mode where >>> multi-line quoting still behaves the old way.

Fixing the Missing Formatting Toolbar

If your toolbar disappeared, it's almost always one of three things, in this order:

  1. It's just collapsed. Click the small Aa icon at the bottom-left of the message box, or press ⌘ ⇧ F / Ctrl Shift F. This is the most common cause.
  2. "Format messages with markup" is on. Open Preferences (⌘ , / Ctrl ,) → Advanced and uncheck the box. The toolbar returns and live formatting switches back on.
  3. You're on mobile. The phone apps don't show the full toolbar; long-press selected text for a short format menu, or type the markup. Nothing is broken.

What Slack Can't Do (and the Workarounds)

No headings. There is no # heading syntax; a # at the start of a line is treated as a channel reference. The convention is a bold line on its own, followed by a Shift Enter line break. For anything longer than a few sections, write a canvas instead — canvases support real headings — and post the link.

No tables. Searches for "slack markdown table" are a monument to hope: there's no pipe syntax, and pasting a Markdown table posts the pipes. Three workarounds, in order of effort:

  • Code-block table. Put the table inside ```, pad columns with spaces, and let monospace do the alignment. Ugly, but it works everywhere. Keep it under five columns or it wraps.
  • Canvas table. Canvases have a proper table block with sortable, editable cells. Create one in the channel, build the table there, and share it. Best for anything that will change.
  • Slack Lists. If each row is really a task or record with an owner and a status, it isn't a table, it's a List. Lists give you columns, filters, and assignees without any formatting at all.

No colour, font size, or underline either. Bold and emoji are the whole emphasis palette, which is what keeps a shared channel from turning into a ransom note.

Formatting a Shout-Out So It Actually Gets Read

Recognition is where Slack formatting earns its keep, because a shout-out competes with everything else in the channel for a two-second glance. A formula that works:

  • Bold the person's name so it jumps out when they — and their manager — skim: *@Priya*.
  • Be specific. "Great job" is noise; "stayed on the incident call until 2am and wrote the postmortem before standup" is signal. Two sentences, tops.
  • Link the work — the PR, the doc, the dashboard — with text behind the link rather than a bare URL.
  • One emoji, at the start or end. Six emoji read as a notification, not a compliment.
  • Quote block the customer's words if there are any. Nothing you write beats what the customer said.

More in our employee shout-out examples. If your team does this a lot, a bot will format it for you: with Propsly — yes, it's ours — /props +10 @priya for the 2am postmortem #ownership posts a consistently formatted card to your recognition channel, DMs Priya, and keeps a leaderboard. How to give kudos in Slack covers the norms; the free tier covers unlimited users.

Quick Recap

Slack markdown is mrkdwn: *bold*, _italic_, ~strike~, backticks for code, > for quotes, - and 1. for lists. No headings, no tables — use a bold line, a code block, or a canvas. Toolbar gone? Click Aa or uncheck "Format messages with markup." Once that's muscle memory, the rest of our Slack tips and tricks will make the app fight you a little less.

Recognition that formats itself

Propsly adds /props to Slack so a shout-out is one line, posted to your feed channel, consistently formatted — free for unlimited users.

Get Started with Propsly
Back to Blog