Markdown to HTML Converter

Headings (# to ######), paragraphs with single-line breaks preserved, bold, italic, bold-italic, strikethrough, inline code, fenced code blocks with a language class, links, images, unordered and ordered lists including nesting, blockquotes, horizontal rules and GFM pipe tables with alignment.

Reference-style links ([text][ref]), footnotes, setext headings (underlined with = or -), definition lists, task-list checkboxes rendered as inputs, and raw HTML passthrough. These are either rare in pasted text or unsafe to render, and leaving them out keeps the output predictable.

Because every character is escaped before conversion. That is the trade-off that makes previewing pasted text safe: no tag from the source can execute or restructure the page. If you need HTML passthrough, run your Markdown through a build-time library instead.

Yes, by construction rather than by filtering afterwards. Input is escaped, code content is isolated, and URL schemes are allowlisted, so there is no path for a script to reach the DOM. Nothing is stripped after the fact, which is where sanitiser bypasses usually happen.

End the line with two spaces, or with a backslash. Both produce a <br />. A single newline without either is kept in the output as a newline inside the same paragraph, which HTML renders as a space — the standard Markdown behaviour.

Yes: ```js becomes <code class="language-js">, the convention Prism and highlight.js expect. The tool does not highlight anything itself — it just leaves the hook in place for whatever highlighter your page already loads.

Emphasis needs the marker to hug the text: *word* works, * word * does not, and an asterisk inside a word is left alone. If your text uses asterisks as literal characters, wrap them in backticks so they are treated as code.

Paste its contents — that is the fastest route and there is no size limit beyond your browser’s. There is no file upload on purpose: the document never has to leave your machine to be converted.

The header row fixes the column count, and short rows get empty cells at the end. That keeps columns aligned instead of shifting the remaining values one place left, which is what happens when a converter simply splits on pipes.

No. The HTML is plain and semantic — h2, ul, pre, table — so it inherits whatever styles your page has. The preview here adds its own local styling only so lists and tables look right on this page.

No, blocks are separated by newlines so the output stays readable and diffable. If you need it compact, run the result through the HTML minifier.

No. The conversion is a pure function running in the page: no server, no storage, no analytics on content. Reload the page and the document is gone.