⌘ K
GFM → Discord · headings → bold · bullet glyphs · >>> block quotes

Convert Markdown for Discord messages

Reformat Markdown for Discord chat — flatten headings to bold, render bullets with glyphs, switch quotes to multi-line >>>, and keep code fences intact.

Markdown → Discord
Input
236 B
15 lines
Output
238 B
14 lines
Status
ready
live
Ratio
1.01×
out/in
input · markdown
output · discord
**Server announcement**

**v1.5** is live with _better_ moderation tools.
• New auto-mod rules
• Custom welcome flow
• See docs (https://example.com/docs)

`inline` example:

```js
console.log("hi");
```

>>> Heads up: requires re-invite.
Quick Start

How to convert Markdown for Discord

Discord supports most Markdown verbatim, but headings, lists, and links need rewriting. This converter flattens what Discord cannot render and keeps the rest.

  1. 01

    Paste Markdown

    From your README, notes, or release post.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    inputGFMmarkedCommonMarklive
    input · markdownmd · GFM
    # Title
    loaded · GFMGFM · ready
  2. 02

    Flatten headings

    Discord has no headings in messages, so all become bold lines.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    flatsoft-breaksoptionsconfiglive
    fix · optionsbold · live
    **Title**
    options applied · livelive
  3. 03

    Map lists + quotes

    - item becomes • item; > line becomes a >>> block.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    mappreviewscoped CSSrenderstable
    out · rendereddc · ready
    • item
    rendered · liverendered
  4. 04

    Paste into Discord

    Drop into chat — fences render with syntax highlighting.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    OK · exporteddc · done
    sent
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsSlackNotionJiraConfluenceHTMLEditor
Use Cases

When to convert for Discord

Server announcements, bot output, community posts.

Patch notes

Post engineering changelogs to a #releases channel. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Server announcements

Reformat Markdown updates for #announcements. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Game guides

Convert Markdown guides for clan / guild servers. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Bot output

Pre-format text payloads from Discord bots. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Onboarding

Welcome rules and onboarding checklists. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Cross-posting

Share blog snippets in a community Discord. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

Discord messages don't support h1/h2 headings (servers' new heading syntax differs from Markdown), so the converter renders them as bold lines for predictable output.
Discord doesn't render [text](url) syntax in plain messages — the converter writes text (url) so both are visible and the URL auto-unfurls.
Yes — Discord renders ``` blocks with optional language tag and syntax highlighting.
No transformation needed — Discord's ||spoiler|| syntax has no Markdown equivalent and passes through as-is.
No. Conversion runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!