Utility guide
Why Markdown became the default way to write for the web
Markdown is plain text that reads like the formatted document it describes — a line starting with # is obviously a heading, even before anything converts it. That readability is the whole reason it caught on for writing that eventually needs to become HTML: READMEs, documentation, blog posts drafted in a plain text editor, content stored in a CMS as Markdown and rendered on the way out.
What this converter supports
- Headings —
# H1through###### H6. - Emphasis —
**bold**,*italic*,~~strikethrough~~. - Lists — ordered, unordered, and nested.
- Links and images —
[text](url)and. - Code — inline
`code`and fenced blocks with a language tag for syntax-highlighting classes. - Blockquotes — lines starting with
>. - Tables — the GitHub-flavored Markdown table syntax, not part of original Markdown but supported everywhere that matters now.
- Horizontal rules —
---on its own line.
Why the output is shown as text, not rendered live
Rendering arbitrary Markdown as real HTML in the page (rather than showing the HTML as text to copy) would mean any raw HTML or script embedded in the input executes right there in the browser. Markdown intentionally allows inline HTML to pass through unchanged, which is exactly the behavior that makes a live preview of untrusted input a real risk rather than a hypothetical one — so this tool shows you the generated HTML, and you decide where it’s safe to render it.
Where the HTML goes from here
Paste it into a CMS field that accepts raw HTML, a static site generator’s template, an email tool, or anywhere else HTML is the expected input. If the destination expects Markdown natively (most modern CMSs and static site generators do), converting first is an extra step you don’t need — this tool is for the cases where the destination only takes HTML.
Frequently asked
Does this support CommonMark, GitHub Flavored Markdown, or something else?
GitHub Flavored Markdown (GFM) — CommonMark plus tables, strikethrough, automatic URL linking and task lists — since that’s the dialect most Markdown actually written today uses, whether or not it ends up on GitHub.
Does it sanitize the HTML output?
No — the output is exactly what the Markdown describes, including any raw HTML you wrote inline. If the HTML is going somewhere that renders user-supplied content (a comment system, for example), sanitize it there with a purpose-built library before rendering, the same as any other HTML from an untrusted source.
Can I convert HTML back to Markdown?
Not with this tool currently — it converts one direction, Markdown to HTML.
