HTML to MD in seconds: paste HTML and get clean, GitHub-flavored Markdown back — tables included. Runs in your browser; nothing is uploaded.
Get clean Markdown to copy — runs in your browser, nothing uploaded.
Converted — share it as a page.
Publish this as a live page in one click. No account to start.
You have a chunk of HTML — a page you exported, an article from a CMS, or the markup an AI tool wrote — and you need it as Markdown for a README, a docs site, or a notes app. Doing HTML to Markdown by hand is tedious: stripping tags, rebuilding headings and lists, redoing every link and table. Paste the HTML here and you get Markdown back instantly — this is the same thing people search for as “html to md”. The conversion runs entirely in your browser, so nothing is sent to a server and there is no account or upload. Headings, lists, links, blockquotes, code blocks and tables all come across as clean GitHub-flavored Markdown you can paste straight into your repo.
Paste your HTML into the box above. A full document or a fragment both work — you do not need a complete page.
Read the Markdown that appears on the right. Tables, links, and code blocks are converted to GitHub-flavored Markdown as you type.
Copy the Markdown and drop it into your README, docs, or notes — or publish it on dochost if you want a shareable link instead.
A developer is moving an old company blog off a CMS and into a Markdown-based docs repo. Each post exists only as rendered HTML — headings, a couple of bulleted lists, inline links, and one comparison table of plan tiers. Rebuilding that by hand for forty posts would take a day. Instead they open the page source, copy the article HTML, and paste it here. The right pane fills with Markdown: the <h2> headings become ##, the list items become - bullets, the anchors become [text](url) links, and the plan table becomes a real pipe table — no hand-editing. They copy it into a .md file in the repo, skim once for anything odd, and move to the next post. Forty posts that would have been a day of tag-stripping become an afternoon of paste-and-commit.
Markdown is a smaller language than HTML, so conversion is always partly a loss — the question is which losses matter. Compared here against the thing most people try first: pasting the HTML straight into a notes app and hoping.
Headings, paragraphs, lists
Both get the basics right. This is not where conversions go wrong.
Links and images
Pasting commonly keeps the link text but drops the image, or rewrites its source to something only your machine can resolve.
Tables
Converted to GitHub-flavoured table syntax. Merged cells — colspan and rowspan — have no Markdown equivalent anywhere and get flattened.
Fenced code blocks
Code pasted as rich text usually loses its fencing and sometimes its indentation, which is the failure that quietly corrupts a snippet.
Inline CSS, classes, and layout
Markdown has no styling layer. Anything whose meaning came only from CSS — a colour that marked something urgent, a two-column grid — is gone either way.
Scripts, forms, and inputs
Dropped deliberately. Markdown has nowhere to put them, and silently keeping them as raw HTML would be worse than removing them.
“Convert HTML to MD”, “HTML page to Markdown” and “HTML to Markdown online” all end in the same Markdown. What differs is what you are starting from — pick yours.
You already have the markup — copied from somewhere, or saved as a .html file.
Paste it into the box above; a fragment works as well as a full document. For a saved file, open it in any text editor (TextEdit, Notepad, VS Code), select everything and copy. The Markdown appears as you paste, and nothing is uploaded.
The page is open in your browser and you want only its article, not the menus around it.
Right-click the article text and choose Inspect, then right-click the element that wraps the article and pick Copy → Copy outerHTML. Paste that here. You get just the content, without the navigation and footer, and it works for pages behind a login because nothing is fetched from a server.
You have the address of a public page, not its HTML.
Use the URL to Markdown converter instead: paste the address and it fetches the page and converts it in one step. Menus and footers come along, so trim them from the output.
Convert a page by URLPages that build their content with JavaScript can come back thin, because the fetch reads the HTML the server sends. The “A page open in Chrome” option does not have that problem.
The only thing you need is one HTML table as a Markdown table.
This page converts tables too, but the HTML table converter is built for exactly that job and shows the resulting pipe table on its own, which is easier to check when the table is wide.
Convert an HTML tableYes. HTML <table> markup is converted to GitHub-flavored Markdown pipe tables, with a header row and aligned columns — the same syntax GitHub and most docs tools render.
No. The conversion runs entirely in your browser. The HTML you paste never leaves your machine, there is no account, and nothing is stored on a server.
Yes — “MD” is just the file extension and shorthand for Markdown, so “html to md” and “html to markdown” mean the same conversion. This tool does both.
They are dropped. Only content elements (text, headings, lists, links, tables, code) are converted to Markdown; <script>, <style> and similar non-content tags are stripped out.
Yes, and it is one of the most common reasons people convert. Obsidian, Bear, Logseq and Notion all store notes as Markdown or something close to it, so pasting raw HTML into them gives you either escaped tags or a mess of inherited formatting. Convert first and you paste clean Markdown that keeps headings, lists, links and code blocks as real structure your notes app can index and search. Copy the page you want, paste the HTML into the box above, and copy the Markdown out — nothing is uploaded, so this works for pages behind a login too.
Los enlaces gratuitos duran 7 días con una cuenta gratuita. Con un plan de pago, cada página que publiques se queda online de forma permanente.
Ver precios