An HTML to Markdown converter takes HTML markup — with all its tags, attributes, and nested elements — and outputs clean, readable Markdown. This is the reverse of Markdown-to-HTML and is essential when migrating content from websites, CMS platforms, or HTML emails into Markdown-based systems.
This guide covers common use cases, how the conversion handles different HTML elements, edge cases to watch for, and tips for getting the cleanest output.
Convert HTML to Clean Markdown
Paste any HTML and get clean Markdown output with headings, links, tables, and code blocks preserved.
Why Convert HTML to Markdown?
Markdown is cleaner, more portable, and easier to maintain than HTML. Here are the most common reasons to convert:
- CMS migration — Moving from WordPress/Drupal (HTML) to a static site generator (Hugo, Jekyll, Astro) that uses Markdown
- Documentation migration — Converting Confluence, Notion, or Google Docs exports (HTML) to Markdown for Git-based docs
- Content repurposing — Turning blog posts or web pages into README files, GitHub wikis, or Obsidian notes
- Email templates — Extracting content from HTML email templates into Markdown drafts
- Cleaning up content — Stripping out inline styles, classes, and divs to get just the text structure
Markdown files are 3-5x smaller than equivalent HTML, work natively with Git version control, and render identically across platforms — from GitHub to VS Code to any static site generator.
How HTML Elements Map to Markdown
The converter translates each HTML element to its Markdown equivalent:
| HTML | Markdown | Notes |
|---|---|---|
| <h1> to <h6> | # to ###### | Heading levels preserved |
| <strong>, <b> | **text** | Bold |
| <em>, <i> | *text* | Italic |
| <a href="..."> | [text](url) | Links with href preserved |
| <img src="..."> |  | Alt text and src preserved |
| <ul>/<ol> + <li> | - item / 1. item | Nested lists supported |
| <pre><code> | triple-backtick code triple-backtick | Code blocks with language hint |
| <code> | backtick code backtick | Inline code |
| <blockquote> | > text | Blockquotes |
| <table> | | col | col | | GFM table syntax |
| <hr> | --- | Horizontal rule |
| <br> | Two spaces + newline | Line break |
Edge Cases and Tricky Conversions
Not all HTML converts cleanly to Markdown. Watch for these situations:
Nested HTML Structures
Markdown does not support all HTML nesting. Deeply nested divs, spans with styles, and complex layouts lose their structure — the converter extracts text content and applies the closest Markdown equivalent.
Inline Styles and Classes
CSS classes, inline styles, and custom attributes are stripped during conversion since Markdown has no styling syntax. If you need colored text or custom layouts, you will need to add HTML back into the Markdown manually.
Complex Tables
HTML tables with colspan, rowspan, or nested tables do not convert cleanly to GFM (GitHub Flavored Markdown) tables, which only support simple grids. Complex tables may need manual restructuring.
Iframes and Embeds
YouTube embeds, iframes, and script tags are either removed or passed through as raw HTML (Markdown supports inline HTML). Review the output for any embedded content.
Automated conversion handles 85-90% of content correctly. Always review the output for broken links, malformed tables, and lost formatting — especially for complex pages.
WordPress to Markdown Migration Workflow
The most common large-scale use case is migrating WordPress content to a Markdown-based system. Here is a proven workflow:
- Export WordPress content — Use WordPress built-in export (Tools > Export) to get an XML file, or copy HTML from the editor
- Convert HTML to Markdown — Paste each post's HTML into the converter
- Fix images — Update image URLs from WordPress media library paths to your new hosting paths
- Add frontmatter — Add YAML frontmatter (title, date, tags) at the top of each Markdown file for your static site generator
- Review and clean — Check for shortcodes ([gallery], [caption]) that do not convert — replace with Markdown equivalents
For sites with 100+ posts, use a CLI tool like wordpress-export-to-markdown alongside this tool for spot-checking. Convert a few posts manually first to identify patterns, then batch the rest.
Cleaning HTML Before Conversion
Cleaner input HTML produces better Markdown output. Pre-process your HTML:
- Remove navigation and footer — Copy only the main content area, not the full page HTML
- Strip tracking scripts — Remove Google Analytics, Facebook Pixel, and other scripts
- Remove inline styles — Styles like color, font-size, and margin will not convert to Markdown anyway
- Fix broken HTML — Unclosed tags or mismatched elements can confuse the converter
- Simplify table structure — Replace colspan/rowspan with simple rows before converting
The less noise in your HTML, the cleaner your Markdown will be.
Conversion Tools Compared
| Tool | Type | Best For | Handles Tables |
|---|---|---|---|
| This converter (browser) | Online | Quick single-page conversion | Yes (GFM) |
| Turndown (JS library) | Library | Programmatic conversion in apps | With plugin |
| Pandoc | CLI | Batch conversion, complex docs | Yes |
| html2text (Python) | CLI | Simple text extraction | Basic |
| Copy as Markdown (browser ext) | Extension | Converting web pages on the fly | Basic |
How to Use the Tool (Step by Step)
- 1
Paste Your HTML
Copy the HTML content you want to convert and paste it into the input area.
- 2
Convert to Markdown
Click convert to transform the HTML into clean Markdown syntax.
- 3
Review the Output
Check headings, links, images, tables, and code blocks for accuracy.
- 4
Copy and Use
Copy the Markdown output into your .md file, README, or documentation system.
Frequently Asked Questions
What HTML elements are supported?+−
Headings (h1-h6), bold, italic, links, images, ordered/unordered lists, code blocks, tables, blockquotes, horizontal rules, and line breaks. Inline styles and classes are stripped.
Does it handle HTML tables?+−
Yes, simple HTML tables convert to GitHub Flavored Markdown (GFM) pipe tables. Complex tables with colspan/rowspan may need manual adjustment after conversion.
What happens to CSS classes and inline styles?+−
They are removed. Markdown has no styling syntax, so all visual formatting is stripped. Only structural elements (headings, lists, links) are preserved.
Can I convert an entire web page?+−
Yes, but it is better to copy only the main content area. Navigation, footers, sidebars, and scripts add noise to the output. Use browser DevTools to copy the article or main content div.
How do I handle images after conversion?+−
Image references are converted to . You may need to update the src URLs if moving images to a different host. Download images separately and update the paths.
Is this the reverse of Markdown to HTML?+−
Yes. Markdown to HTML converts .md files to HTML for web display. HTML to Markdown does the reverse — extracting Markdown from HTML pages. Both are lossy in edge cases.
Can I use this for WordPress migration?+−
Yes. Copy the HTML from WordPress editor (Text/Code view), paste into the converter, and save the output as .md files. Add YAML frontmatter for your static site generator.
Is this HTML to Markdown converter free and private?+−
Yes. Conversion happens entirely in your browser. No HTML content is sent to any server.
Convert HTML to Clean Markdown
Paste any HTML and get clean Markdown output with headings, links, tables, and code blocks preserved.
Open HTML to Markdown Converter ->Related Guides
Markdown to HTML Converter Guide
Convert Markdown to semantic HTML with proper heading tags, lists, tables, code blocks, and links. Includes complete Markdown syntax reference, GFM extensions, and CMS integration tips.
Code Beautifier Guide
Beautify messy code into clean, indented, readable format. Supports HTML, CSS, JavaScript, JSON, XML with configurable indentation, quotes, and style options.
JSON Formatter Guide
A complete developer reference for JSON syntax, common errors, formatting options, and how to validate JSON in any language or tool.