Text
Markdown to HTML Converter
Convert Markdown (headings, lists, links, code, quotes, bold and italics) into clean HTML markup.
Written by Jay Sudha · Published · Last updated
Press ⌘ Enter to run
23 words · 8 lines
Common uses
- Render README snippets as HTML
- Preview Markdown without a full editor
Limitations
- Tables are not converted; raw HTML in the Markdown is escaped
Turning README and doc snippets into HTML
Markdown is comfortable to write and HTML is what a web page, a CMS field or an email template actually needs. This converter turns the first into the second, so a README section, release notes or a help article drafted in Markdown can be pasted into a place that only takes HTML.
It suits developers moving documentation into a site without a Markdown pipeline, writers preparing copy for a CMS with an HTML source view, and anyone who wants to see exactly which tags a piece of Markdown produces. Copy the result, or download it as formatos-markdown-to-html.html.
Which Markdown syntax is supported
Headings from # to ###### become <h1> to <h6>. Paragraph lines are joined, and a line ending in two spaces forces a <br>. Lines starting with -, * or + become a bulleted list and lines starting with 1. or 1) a numbered list (a list that starts at 3 keeps start="3"); indenting an item nests it. A heading or a blank line followed by ordinary text closes the list, so nothing lands inside it by accident.
Blockquotes (> ), fenced code blocks (``` or ~~~, with the language kept as a class) and code indented by four spaces become <blockquote> and <pre><code>. A line of three or more -, * or _ becomes <hr>. Inline, `code`, [links](url "title"), , **bold**, *italic* and ~~strikethrough~~ are converted, and <https://…> becomes a link.
Tables are the main thing it does not convert; their lines are left as paragraph text. Footnotes, task-list checkboxes and definition lists are also outside what it reads.
Escaping and safety
Everything happens in your browser, and on this site the text is not uploaded, so internal docs and unpublished notes can go through it.
Your text is HTML-escaped before formatting is applied: <, > and & become <, > and &. That means raw HTML written inside the Markdown appears as text rather than being passed through, and code samples display correctly. Links and images whose address starts with javascript: or data: are not turned into tags, so pasting the output into a page cannot run a script.
Checking the HTML
Paste the result into the page, preview it, and check the parts that depend on indentation: nested list items and indented code blocks follow the spaces at the start of each line, so a mixed tab and space indent can put an item at the wrong level.
If a table or another unsupported element matters, add its HTML by hand after converting.
Frequently asked questions
The Markdown found in most READMEs and notes: # to ###### headings, paragraphs, bullet and numbered lists (nested by indentation), blockquotes, fenced and indented code blocks, horizontal rules, and inline links, images, code, bold, italic and strikethrough.
Tables are not converted: their lines stay as paragraph text, so build a table in HTML separately if you need one.
Your text is escaped before formatting is applied, raw HTML inside the Markdown is escaped rather than passed through, and links with javascript: or data: addresses are left as plain text, so the output cannot run scripts.
No. Conversion runs entirely in your browser.
Related text tools
Tool last reviewed: September 27, 2026 · Report a problem