Markdown to Slack Converter

How to use

1. 1Pick a direction: Markdown to Slack or Slack to Markdown. The toggle at the top of the tool swaps which side reads as input.
2. 2Paste your text into the left panel. Output appears on the right and updates as you type.
3. 3Load a sample (release announcement, bug report, standup notes, or doc snippet) to see how a typical message converts.
4. 4Click Copy to put the converted text on your clipboard. Paste it straight into Slack, or back into a README, issue, or wiki page.
5. 5Use Swap output into input to chain conversions: convert a Markdown draft, edit the Slack-format result, then convert it back to Markdown for the docs.

About this tool

Markdown to Slack Converter rewrites a CommonMark or GitHub-Flavored Markdown document into Slack's mrkdwn dialect, the format Slack uses inside messages, channel topics, and the Block Kit mrkdwn element. The transform is a sibling-syntax rewrite, not a render: bold goes from **double-asterisk** to *single-asterisk*, italic stays inside underscores (and *single-asterisk* italic becomes _underscore_ italic so it does not collide with bold), strikethrough drops from ~~double tilde~~ to ~single tilde~, and Markdown's [label](url) becomes Slack's <url|label> with the right escapes for pipe and angle-bracket characters inside the URL. Bare http(s) URLs are wrapped in angle brackets so Slack autolinks them with a hostname-only preview. Headings are flattened to bold lines because Slack has no real heading level; GFM tables and horizontal rules are kept by being wrapped in a monospaced code block; reference-style links are expanded inline; and ordered or unordered lists are emitted as plain text with bullet glyphs or numbers because mrkdwn has no list primitive. Code spans and triple-backtick code blocks pass through untouched, except that the language hint is dropped (Slack ignores it). The reverse direction, Slack to Markdown, applies the inverse rewrite so a message copied out of Slack becomes paste-ready for a README, GitHub issue, or doc: single-asterisk bold becomes **bold**, underscore italic becomes *italic*, single-tilde strike becomes ~~strike~~, <url|label> becomes [label](url), and user or channel references like <@U12345> are kept as plain text. Both directions run entirely in the browser; the messages and drafts you paste here never leave your device. Useful when posting a PR description in #engineering, sharing a changelog from a release branch, copying a doc snippet into #support, or pulling a thread out of Slack and into a wiki page.

Free to use. Works in your browser. No signup, no login.