Convert Markdown to clean HTML as you type, with a live preview beside the source — headings, lists, links and code rendered by GitHub-flavoured rules. Runs entirely in your browser — your numbers never leave this device.
Type or paste Markdown on the left and the HTML appears on the right, rendered by a full Markdown parser (the marked parser, loaded only on this page) with GitHub-flavoured Markdown enabled — so tables, fenced code blocks, task lists and strikethrough behave the way they do in a README or an issue comment. A rendered preview sits beside the generated markup, because the two answer different questions: the preview shows what readers will see, and the HTML is what you copy into a template, an email builder or a static site.
The rules that surprise people are worth stating. A single Enter inside a paragraph is treated as a space — paragraphs are separated by blank lines, and a line that should break visibly needs a list, a new paragraph or two trailing spaces. Emphasis markers must hug their text: ** bold ** with spaces inside the asterisks stays literal. And Markdown deliberately allows raw HTML in the source, which the parser passes through into the output — convenient for your own documents, and the reason converted output from an untrusted source still needs sanitising before it goes on a page, a job this converter does not claim to do.
Everything you type stays in the page: conversion happens in your browser as you type, drafts are never uploaded or stored, and closing the tab discards them — copy the HTML you need before you close it.
GitHub-flavoured Markdown (GFM), the dialect used by READMEs and issue trackers: fenced code blocks with language hints, tables, strikethrough with ~~text~~, and autolinked URLs, on top of the core CommonMark-style rules for headings, lists, emphasis and links. If a document renders on GitHub, it renders the same way here.
Because a single newline inside a paragraph is a space in Markdown — paragraphs end at blank lines. The rule exists so source files can wrap long paragraphs at 80 characters without changing the output. For a visible break, start a new paragraph, use a list, or end the line with two spaces, which the parser turns into a <br>.
For your own documents, yes. Two cautions: raw HTML written in the Markdown source passes through into the output unchanged — that is standard Markdown behaviour — so HTML converted from someone else's untrusted Markdown should be sanitised by a dedicated library before publication. And relative links and images keep their relative paths, so check them against where the HTML will actually live.
Usually spacing or pairing: ** bold ** with a space inside the markers stays literal, and an odd number of ** markers leaves the last one unpaired and printed as-is. Markers must hug the text they wrap — **bold** — and every opening pair needs its closing pair on the same line or paragraph.
No — this tool converts in one direction, Markdown to HTML. The reverse is a different and lossier problem (most HTML has no Markdown equivalent for its attributes and structure), and rather than offer a half-faithful version, the page does the one direction properly. The HTML Entity Encoder in this category covers the related job of showing markup as text.
No. The parser runs in your browser and converts as you type — your text is never uploaded, stored or tracked, and it disappears when the tab closes, so copy finished HTML first.
More in Developer Tools · Browse all tools