Convert Markdown to HTML code. See the rendered preview and copy the output.
This is a bold and italic text example.
console.log("Hello, World!");This is a blockquote.
| Column 1 | Column 2 |
|---|---|
| Cell 1 | Cell 2 |
Converters disagree about the details, so here is exactly what this one emits. Every row is the real output — no inline styles, no wrapper divs you did not ask for.
| Element | Markdown | HTML output |
|---|---|---|
| Heading | ## Getting Started | <h2 id="getting-started">Getting Started</h2> |
| Bold | **bold** | <strong>bold</strong> |
| Italic | *italic* | <em>italic</em> |
| Strikethrough | ~~gone~~ | <del>gone</del> |
| Inline code | `value` | <code>value</code> |
| Fenced code | ```js | <pre><code class="hljs language-js"> |
| Link | [docs](https://example.com) | <a href="https://example.com">docs</a> |
| Image |  | <img src="a.png" alt="alt"> |
| Task list | - [x] Done | <li><input checked disabled type="checkbox">Done</li> |
| Table | | A | B | | <table><thead><tr><th>A</th>… |
| Blockquote | > quoted | <blockquote><p>quoted</p></blockquote> |
| Callout | > [!NOTE] | <div class="markdown-callout markdown-callout-note"> |
| Mermaid | ```mermaid | <div class="mermaid"> |
| Horizontal rule | --- | <hr> |
This converter treats a single newline inside a paragraph as a line break, the way GitHub comments, Discord, and most note apps do. Strict CommonMark ignores it and needs two trailing spaces or a blank line. If your output has more line breaks than a reference implementation gave you, this is why.
## Getting Started becomes <h2 id="getting-started">. Duplicate heading text is de-duplicated with a numeric suffix, so two “Notes” headings become notes and notes-1 instead of colliding. In-page links and a generated table of contents both work without you editing the HTML.
Markdown allows raw HTML, but the result here is run through DOMPurify. Script tags, onclick-style handlers, and javascript: URLs are removed. That is what makes the output safe to publish when the Markdown came from somewhere you do not control — but it also means a deliberate embed can be stripped.
Fenced code blocks come out as <pre><code class="hljs language-js"> with highlight.js span classes already applied. Add any highlight.js theme stylesheet to your site and the colour appears; without one the code still renders correctly in a single colour.
GitHub Flavored Markdown: headings, bold, italic, strikethrough, links, images, ordered and unordered lists, task lists, tables, blockquotes, fenced code blocks, and horizontal rules. On top of GFM it also converts footnotes, GitHub-style callouts ([!NOTE], [!TIP], [!IMPORTANT], [!WARNING], [!CAUTION]), KaTeX math, and Mermaid diagram blocks.
This converter runs with the "breaks" option on, so a single newline inside a paragraph becomes a <br> tag. That matches how Markdown behaves in GitHub comments, Discord, and most note apps. Strict CommonMark instead requires two trailing spaces or a blank line, so if you are comparing output against a CommonMark reference implementation, this is the difference you are seeing.
Yes. Every heading is emitted with a slugified id — "## Getting Started" becomes <h2 id="getting-started">. Repeated heading text is de-duplicated with a numeric suffix so two "Notes" headings become "notes" and "notes-1", which keeps in-page anchor links unambiguous.
The generated HTML is sanitized with DOMPurify before it is shown, so script tags, event-handler attributes like onclick, and javascript: URLs are stripped out. That makes the output safe to inject into a page even when the Markdown came from an untrusted source. Sanitizing again on your own server is still good practice for defence in depth.
Code blocks are emitted as <pre><code class="hljs language-js"> with highlight.js span classes already applied, but the classes need a matching stylesheet to show colour. Add any highlight.js theme CSS to your page and the highlighting appears. Without it the code still renders correctly, just in a single colour.
Yes. The output is plain semantic HTML with no framework dependencies and no inline styles, so it drops into any site, CMS, or email template. You supply the CSS for tables, code blocks, and callouts to match your own design.
No. The conversion runs entirely in your browser using JavaScript. Your Markdown is never uploaded, stored, or logged, which means you can safely convert internal documentation and unreleased content.