Paragraphs, bullets, numbered lists, and blockquotes become semantic HTML elements.
Raw HTML
Kept
Raw HTML in the Markdown passes through instead of being escaped.
Footnotes
Changed
Markdown footnotes become linked backreferences in the generated HTML.
Images
Changed
Image references stay as img src attributes; image files are not bundled into the HTML.
Document shell
Changed
Without standalone, output is an HTML fragment. With standalone, our document engine adds html, head, body, and minimal CSS.
Code blocks
Kept
Fenced code blocks become pre/code blocks with classes suitable for highlighting.
Headings Kept
Markdown headings become h1 through h6 elements.
Paragraphs and lists Kept
Paragraphs, bullets, numbered lists, and blockquotes become semantic HTML elements.
Raw HTML Kept
Raw HTML in the Markdown passes through instead of being escaped.
Footnotes Changed
Markdown footnotes become linked backreferences in the generated HTML.
Images Changed
Image references stay as img src attributes; image files are not bundled into the HTML.
Document shell Changed
Without standalone, output is an HTML fragment. With standalone, our document engine adds html, head, body, and minimal CSS.
Code blocks Kept
Fenced code blocks become pre/code blocks with classes suitable for highlighting.
Sample conversions
Docs page fragment
Input
Markdown docs page with H2 headings, fenced JSON examples, an inline HTML warning box, and two footnotes.
Output
The HTML fragment kept headings, pre/code blocks, and the raw warning div. Footnotes became linked anchors at the bottom of the fragment.
Standalone newsletter
Input
Markdown newsletter with title metadata, images referenced by HTTPS URL, lists, and blockquotes.
Output
Standalone mode added a full HTML document with minimal CSS. Images stayed remote src references, so private URLs would still fail for recipients.
A real Markdown → HTML run
We converted our Markdown sample (472 B) with Document engine on 2026-09-11. It took 28 ms and produced a 4 KB HTML file, 9.6× larger than the input. The engine raised no warnings.
Use for a complete HTML file with head, body, metadata, and minimal CSS; leave off for CMS fragments.
toc
Use when heading anchors and a generated table of contents should be included in the HTML output.
Do it yourself
pandoc
bash
pandoc in.md -t html -o out.html
This produces a fragment unless you add --standalone.
pandoc standalone
bash
pandoc in.md -t html --standalone --toc -o out.html
Pandoc's default CSS is minimal; bring your own stylesheet for publication design.
Markdown to HTML by API or MCP
The HTTP API and the MCP server run the exact engine this page uses (Document engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=md&to=html.