Markdown to HTML

Type or paste Markdown on the left and the HTML appears on the right. Swap the boxes to go backwards.

The output is escaped, so a < in your text becomes &lt; rather than opening a tag. Code spans are pulled out before anything else runs, so `**this**` stays literal rather than turning bold.

ATX and setext headings, bold, italic, strikethrough, inline code, fenced code with a language class, links, images, ordered and unordered lists, blockquotes, horizontal rules and pipe tables.

Left out on purpose: reference links, footnotes and raw HTML blocks. Those are the parts flavours disagree about most, and a converter that half-supports them produces output you have to check by hand anyway.

Two trailing spaces still make a hard line break, which is the one piece of Markdown syntax nobody can see in their own file.

John Gruber released Markdown in March 2004, with help from Aaron Swartz on the syntax. What shipped was a description in prose and a Perl script called Markdown.pl, and where the two disagreed the script won.

Prose is not a grammar. The description said nothing definite about nested lists, and nothing at all about emphasis inside a word, so every implementation answered differently and all of them were defensible. By 2012 the same document rendered four ways on four sites.

CommonMark started in 2014 to settle it with a real specification and a test suite that any implementation could be measured against, and Gruber objected to the original name, Standard Markdown, so it was renamed. GitHub switched its own rendering over in 2017. This converter follows the common ground.

HTML to Markdown is the return trip, and it loses more than you might expect. Remove line breaks is worth running first on Markdown pasted out of a hard-wrapped email.

For what the characters are underneath, text to hex shows the bytes.