Conversion Guides

Every markup format speaks a slightly different dialect, and the differences bite hardest at the edges — headings that don't exist, links written backwards, strikethrough with three different spellings. These guides document how each format pair maps, with syntax tables, worked examples, and the conversions that can't be done losslessly.

Open the converter →

Guides

• Markdown to HTML

  How Markdown elements map to HTML tags, what GitHub Flavored Markdown adds, how sanitization protects you, and why single line breaks disappear.

• Markdown to Slack mrkdwn

  Slack doesn't render standard Markdown. Single asterisks mean bold, links go in angle brackets, and headings don't exist at all — here's the full mapping.

• Markdown to Jira wiki markup

  Jira's wiki notation predates Markdown's dominance: h2. headings, {{monospace}}, pipe-delimited links, and {code} blocks explained.

Official format references

These guides cover conversion between formats. For the authoritative syntax of each format itself, see:

• Markdown — CommonMark specification and GitHub Flavored Markdown
• HTML — MDN documentation
• AsciiDoc — Asciidoctor documentation
• Slack mrkdwn — Slack formatting reference
• Jira wiki markup — Atlassian text formatting notation