Markdown to Slack / Discord / Telegram Converter
Paste standard Markdown and get the equivalent formatting for Slack mrkdwn, Discord, and Telegram MarkdownV2 side by side. Code blocks are preserved. Runs in your browser.
Slack (mrkdwn)
*Release notes* *Bold* highlights, _italic_ asides, and ~struck~ items. Inline `code` and a <https://scoutmytool.com|link> stay intact.
Discord
# Release notes **Bold** highlights, *italic* asides, and ~~struck~~ items. Inline `code` and a link (https://scoutmytool.com) stay intact.
Telegram (MarkdownV2)
*Release notes* *Bold* highlights, _italic_ asides, and ~struck~ items. Inline `code` and a [link](https://scoutmytool.com) stay intact.
Telegram MarkdownV2 also requires escaping certain literal characters (. ! - ( ) etc.) outside of entities; this tool converts the formatting markers but does not auto-escape every reserved character.
About this tool
Every chat platform invented its own dialect of Markdown, so text that looks right in a README looks broken when pasted into Slack, Discord, or Telegram. The biggest trap is bold and italic: standard Markdown uses **double asterisks** for bold and single for italic, but Slack and Telegram use a single *asterisk* for bold and an _underscore_ for italic — so a naive paste turns your bold into italic. This converter takes ordinary Markdown and rewrites the formatting for each platform at once: Slack mrkdwn (with its <url|text> link syntax and bold-as-headers), Discord (which is close to standard but does not render inline links in messages), and Telegram MarkdownV2. Inline code and fenced code blocks are detected first and passed through untouched, so Markdown symbols inside code are never mangled. It runs entirely in your browser, updating live as you type, so you can copy the right version straight into your chat client.
How to use it
- Write or paste standard Markdown in the input.
- Read the Slack, Discord, and Telegram versions side by side.
- Copy the one you need with its copy button.
- Paste it into the chat app — bold, italic, strike, links, and code will render correctly.
Frequently asked questions
- Why does my bold turn into italic when I paste Markdown into Slack?
- Because Slack (and Telegram) use a single *asterisk* for bold, while standard Markdown uses single asterisks for italic and double for bold. So **bold** pasted raw is misread. This tool converts **bold** to *bold* and *italic* to _italic_ so it renders as intended.
- How does Slack handle links?
- Slack mrkdwn does not use [text](url); it uses <url|text>. The converter rewrites Markdown links to that syntax. It also converts Markdown headers to bold lines, since Slack mrkdwn has no heading syntax.
- Why are Discord links shown as "text (url)"?
- Discord only renders masked [text](url) links inside embeds, not in normal messages, where they appear literally. To stay readable, the converter outputs "text (url)" so both the label and the destination are visible. Bold, italic, strike, code, and headers are otherwise standard on Discord.
- Does it preserve code blocks?
- Yes. Inline `code` and fenced ``` blocks are extracted before any conversion and restored afterward, so Markdown characters inside code (like ** or _) are never altered. All three platforms use backticks for code, so they pass through unchanged.
- What about Telegram's character escaping?
- Telegram MarkdownV2 requires escaping reserved characters such as . ! - ( ) outside of formatting entities. This tool converts the formatting markers (bold, italic, strike, headers) but does not auto-escape every reserved literal, so very punctuation-heavy messages may need a final manual escape.
- Is my text uploaded anywhere?
- No. The conversion is pure in-browser string processing with no network calls, so whatever you paste stays on your device.