Convert HTML code to clean Markdown syntax. Paste HTML and get Markdown instantly.
Select part of a rendered page in your browser, copy it, and paste it into the input above. Browsers put the underlying HTML on the clipboard alongside the plain text, so the converter reads the real markup — you never have to open View Source or dig through developer tools.
Pasted markup is cleaned before conversion: inline styles, class and id attributes, editor metadata, and empty wrapper elements are stripped, so the Markdown you get back is the document rather than the page’s styling scaffolding.
Many converters either leave <table> markup untouched or flatten each cell into a paragraph. Here tables become GitHub Flavored Markdown pipe tables, with the header row and alignment separator intact and in document order. If you need to reshape one afterwards, send it to the table generator.
Output uses ATX headings (## Heading) and fenced code blocks with triple backticks, not the underlined Setext style or four-space indentation. That is what GitHub, GitLab, Obsidian, and static site generators expect, so the Markdown drops straight into a repo without a reformatting pass.
HTML exported from an app carries that app’s scaffolding. Google Docs, Notion, and Confluence each get a dedicated tool that strips their specific wrapper classes and editor metadata first. Confluence info, tip, and warning macros additionally become GitHub-style [!NOTE] callouts instead of being lost.
<h1>-<h6>→# to ######<strong>, <b>→**bold**<em>, <i>→*italic*<a href="">→[text](url)<img src="">→<ul>, <ol>→- or 1.<pre><code>→```code```<blockquote>→> quotePaste your HTML into the input area and click Convert to Markdown. You can also copy a section of a rendered web page and paste it straight in — the underlying HTML is read from your clipboard automatically, so you do not need to open View Source first.
Yes. Table elements are converted to GitHub Flavored Markdown pipe tables with a header row and alignment separator, not flattened into paragraphs or left as raw HTML. This is where most HTML-to-Markdown converters fall down, so it is worth checking your output if you are comparing tools.
ATX headings (# Heading rather than the underlined Setext style), fenced code blocks with triple backticks rather than four-space indentation, and hyphens for unordered list bullets. That combination is what GitHub, GitLab, Obsidian, and most static site generators expect.
Layout wrappers such as divs and spans are unwrapped so the text inside them survives rather than being dropped, and empty wrappers left behind are removed. Elements with no text at all, like iframe embeds, have nothing to carry over — Markdown does allow inline HTML, so you can paste those back into the output if you need them.
Yes, and there are dedicated tools that clean the platform-specific noise first: Google Docs to Markdown, Notion to Markdown, and Confluence to Markdown all strip the wrapper classes and editor metadata before running the same conversion. Confluence info panels also become GitHub-style [!NOTE] callouts.
Yes. The conversion runs entirely in your browser using JavaScript. Your HTML is never uploaded, stored, or logged, so you can safely convert internal pages and unpublished content.