Three steps. No installation, no signup.
Copy from any source — a webpage's "View Source," a CMS export, an email's HTML view, an AI assistant's output. Paste it into the box.
The converter strips out everything you don't need (styling, tracking, junk attributes) and keeps everything you do (headings, lists, tables, code, links, images).
Paste it into ChatGPT, Obsidian, Notion, your README, your static site, your notes app — anywhere that speaks Markdown.
The most common reason to convert HTML to Markdown is to clean content up — strip styling, tracking, and clutter before feeding it to an AI assistant, migrating it to a new platform, or saving it in a notes app. Pick the section that matches your case.
LLMs read Markdown more accurately than HTML — and use about 30–50% fewer tokens for the same content.
When you copy a webpage and paste it into ChatGPT or Claude, all the HTML noise (<div class="sidebar-nav">, inline styles, ad markup) burns through your context window and confuses the model. Convert it to Markdown first and you'll get cleaner summaries, faster responses, and you'll fit more content into one conversation.
Export your blog as HTML, paste each post into this converter, save the result as .md.
Now you can move to a Markdown-based system — Hugo, Jekyll, Astro, Eleventy, Notion, Obsidian — without rewriting anything by hand. The converter handles 100,000+ character documents without choking.
View the page's source HTML, paste it here, get the article body in Markdown.
Strips the navigation, footer, ads, and styling — you keep the actual content. Useful for archiving articles, building a personal knowledge base, or feeding content into an AI summarization workflow.
Most email clients let you view the HTML source of a message.
Copy that, paste here, get readable Markdown. Useful for archiving newsletters into a notes app or for processing email content programmatically.
Paste a <table> block — get back a Markdown table with column alignment preserved.
Works for tables copied from Google Docs, Excel exports, webpages, or anywhere else.
Switch to the Markdown → HTML tab to convert Markdown into HTML.
The most common use case for publishing Markdown content on a website or in an email.
Use the Table for Squarespace tab.
It's a focused workflow for adding tables to Squarespace pages, where the built-in Markdown block doesn't render them.
When converting HTML to Markdown, the tool strips out things you don't want in clean Markdown:
style="color: red") — removed by default. Toggle off if you want them preserved.<font>, <center>, and other deprecated tags — removed.<div> and <span> elements — unwrapped.What gets kept: every heading, paragraph, list, table, code block, blockquote, link, image (with alt text), and footnote.
Convert HTML → Markdown → HTML and the structure stays intact. This matters when you're migrating content: you can run a sanity check by converting back and confirming nothing important was lost. The reverse converter follows the CommonMark + GitHub-Flavored Markdown standards, so the output works with every Markdown tool you'll use afterward (GitHub, Obsidian, Notion, Hugo, Jekyll, Astro, Eleventy, you name it).
The conversion happens entirely in your browser. Nothing uploaded, nothing logged, nothing stored. Open developer tools → Network tab and watch — zero requests fire while you convert.
This matters more for HTML-to-Markdown than for almost any other tool, because the HTML you're cleaning often contains things you don't want sent to a third party: client emails, draft blog posts, internal documents, scraped article content. None of it leaves your machine.
Paste your HTML into the left panel and copy the Markdown from the right panel. That's the whole workflow — no signup, no upload.
Yes — tables are preserved with column alignment intact. A 4-column HTML table becomes a 4-column Markdown table with the same headers and alignment.
Stripped by default because Markdown has no concept of inline styles, and removing them is usually what you want when converting messy webpage HTML to clean notes. There's a toggle if you need to keep styling-as-HTML inside the Markdown output.
Yes — right-click the page, choose "View Source" (or ⌘/Ctrl + U), copy everything, paste here. For just the article body, use a browser extension like "Reader Mode" first to strip the navigation, then "View Source" on the cleaned page.
Yes — the converter runs entirely in your browser. Verify in developer tools (Network tab) that no requests fire while you convert.
Two reasons. First, LLMs parse Markdown more reliably than HTML — fewer parsing errors, better summarization. Second, Markdown is denser: the same content uses 30–50% fewer tokens, which means longer documents fit into one prompt and you get faster responses.
Yes. Export your blog as HTML (most platforms have an HTML export option), then convert each post here. The output is GitHub-Flavored Markdown that works with every modern static site generator and CMS.
Yes — paste the HTML source of an email and get readable Markdown back. Most email clients show the HTML view through "Show original" or "View source" in the message menu.
Yes — drop multiple files into the editor and download them as a single zip of .md files.
Yes — click the "Markdown → HTML" tab at the top. Same converter, opposite direction.