HTML to Markdown
Text from a web page, a CMS field or an email often arrives as HTML while you need markdown — for a README, a documentation site or a static site generator. This tool converts the common structure: headings from level one to six, paragraphs, bold, italic, line breaks, list items and links. The rest of the formatting falls away and the text remains, which is exactly the point: markdown has no colours, typefaces or inline styles. One thing is deliberately strict: only links starting with http or https keep their address. References to javascript or data addresses are carried over as plain text, so you can convert HTML of unknown origin without dragging an executable link into your documentation. Everything happens locally in your browser: nothing is uploaded, logged or stored. Free and unlimited to use, including commercially — no account, no licence, no limits.
What people use this for
<h2>Heading</h2><p>Text with <strong>bold</strong> and <em>italic</em>.</p><ul><li>First item</li><li>Second item</li></ul> → dashed list<a href="https://westcube.nl">Westcube</a> → [Westcube](https://westcube.nl)
What others think of this tool
No reviews for this tool yet. Yours would be the first.
Do you work with Westcube?
Leave a review on Google tooFrequently asked questions
Which HTML elements are converted?
Headings h1 through h6 become hashes, p becomes a paragraph surrounded by a blank line, strong and b become double asterisks, em and i single asterisks, br becomes a line break, li becomes a dash and a becomes a markdown link. Anything outside that — tables, images, div structures, styled spans — loses its formatting but keeps the text inside it. That is a deliberate floor: markdown is a text format and simply has no equivalent for most HTML constructs.
Why does the link disappear on some references?
Only addresses starting with http:// or https:// are carried over as a markdown link. For a reference to a javascript address, a data address or a relative path, the link text remains but the address is dropped. For javascript and data addresses that is a safety measure: you would not want those slipping unnoticed into your documentation. For relative paths it is practical — a path like /about only works on the original site and would point somewhere wrong in your README. If you need relative links, add them back manually.
Why are there no tables in the output?
Tables do not exist in standard markdown. The pipe-based table syntax you know from GitHub is an extension that varies per platform and is not supported everywhere. This tool sticks to the standard and therefore carries over the text from the cells without the table structure. If you need a table, build it manually in the syntax of the platform you publish on.
Can I convert an entire web page with this?
Technically yes — there is no size limit — but the result is rarely usable. A complete page contains navigation, footers, cookie notices and script blocks, leaving you with loose text you still have to clean up. You get a far cleaner result by selecting just the article section in your browser, copying that as HTML and pasting it here.