Skip to content

Markdown to HTML

Write Markdown, get HTML. Live preview and raw output side by side.

The widget below renders Markdown to HTML using the marked library’s GFM-compatible parser — the same dialect GitHub, Discord, Reddit, and most modern Markdown editors implement. Tables, task lists, strikethrough, fenced code blocks, and autolinking are all supported. Output is plain HTML you can drop into a static site, email template, or documentation page.

402 chars

Convertitive

Free converters for length, weight, time, and everything else.

Features

  • Markdown to HTML in real time
  • Tables, task lists, code blocks
  • GFM compatible
Tool Status
Length
Weight
Markdown
console.log("hello world");

Built for the web, runs in your browser.

Visit Convertitive

How to use

  1. Write or paste Markdown

    GFM syntax in the left pane. The right pane updates instantly with either a rendered preview or the raw HTML.

  2. Toggle Preview / HTML

    Preview: rendered output as it would appear in a browser. HTML: the raw output ready to copy into your CMS, blog, or docs.

  3. Copy and use

    One tap copies the full HTML. The output is plain HTML, no inline styles — your site's CSS will style it.

GFM syntax cheat sheet

MarkdownHTML / Rendered
# Heading 1<h1>Heading 1</h1>
**bold**bold
*italic*italic
~~strike~~strike
`inline code`inline code
[text](url)<a href="url">text</a>
- item<ul><li>item</li></ul>
- [x] done☑ done (task list)
| col | col |Table

Frequently asked questions

Which Markdown dialect does this use?
GitHub Flavored Markdown (GFM). The most widely-implemented superset of CommonMark, adding tables, task lists, strikethrough, autolinks, and fenced code blocks with language hints. Most modern Markdown sources you'll encounter are GFM-compatible.
Does the output include any styling?
No — the output is semantic HTML with no inline styles or classes. Your destination site's CSS styles it. If you want a self-contained styled output, paste the HTML into a wrapper that includes a Markdown-targeting CSS (e.g. GitHub's markdown.css).
Is the input sanitised?
No — the tool renders your Markdown faithfully, including any embedded HTML. Don't paste content from untrusted sources expecting XSS to be stripped. For untrusted Markdown rendering on a public site, post-process the HTML with a sanitizer like DOMPurify before publishing.
Can it handle math (LaTeX/KaTeX)?
Not out of the box. GFM doesn't include math. You can write LaTeX as plain text and post-process the output through KaTeX or MathJax at your site's rendering layer.
What about syntax highlighting in code blocks?
The HTML output preserves the language hint as a class (e.g. <code>&lt;code class=&quot;language-js&quot;&gt;</code>), which Prism, highlight.js, or Shiki can pick up on your site. The widget itself doesn't apply highlighting — that's a downstream concern.

About

GFM vs CommonMark vs original Markdown

John Gruber's original 2004 Markdown was loose — many edge cases were undefined. CommonMark (2014) standardised the syntax precisely. GFM (GitHub Flavored Markdown) extends CommonMark with tables, task lists, strikethrough, autolinks. Every modern Markdown processor implements either CommonMark or GFM; the differences only matter for edge cases.

When to use Markdown vs HTML directly

Markdown for human-written content that humans edit. HTML for anything generated programmatically, or where the structure exceeds Markdown's expressiveness (deeply nested layouts, custom components). See our Markdown vs HTML comparison for the full decision tree.