Convert Markdown to Slack — and back

Frequently asked questions

Why doesn't normal Markdown work in Slack?

Slack uses its own flavor called mrkdwn. Bold is *single asterisks*, italic is _underscores_, strikethrough is ~single tildes~, and links are written <https://example.com|like this>. There are no headings or tables, so **double asterisks**, # headings, and [text](url) links show up literally unless they're converted.

What's the difference between "Paste" and "API" output?

Paste is for typing or pasting into the Slack message box: links become "label (url)" and nothing is escaped, because the composer shows <url|label> and &amp; literally. API is for bots, incoming webhooks, and Block Kit text fields: links use Slack's <url|label> syntax and &, <, > are escaped as &amp;, &lt;, &gt;, as Slack's API requires.

How are headings and tables converted?

Slack has neither, so headings become a bold line and tables become an aligned, monospaced grid inside a code block — the most readable way to show tabular data in a Slack message. Task lists become ☐ and ☑, and nested bullets use •, ◦ and ▪.

Can it convert Slack messages back to Markdown?

Yes. Switch to Slack → MD and it turns *bold*, _italic_, ~strike~, <url|label> links, code blocks, quotes (including >>>), and • bullets into Markdown. User, channel and @here mentions become readable @name and #channel text, and HTML entities are decoded.

Are my messages uploaded anywhere?

No. Conversion runs entirely in your browser with JavaScript — nothing is uploaded, logged, or stored, which matters when you're pasting internal messages. It's free with no sign-up; a single unobtrusive ad slot covers hosting.