Turning Web Content Back into Plain, Portable Text
HTML is what browsers render; Markdown is what humans comfortably write and edit. Converting HTML to Markdown strips away the markup ceremony — tags, attributes, wrapper divs — and keeps the meaning: headings stay headings (<h2> → ##), links keep their text and URL ([text](url)), lists stay lists, code blocks stay code blocks. What you get is content that's readable as-is, diffable in version control, and editable in any text editor without hunting through angle brackets.
The conversion is intentionally opinionated: presentational clutter — inline styles, class attributes, layout tables, tracking spans — has no Markdown equivalent and gets dropped. That's the feature, not a bug: the output is the clean editorial core of the page.
Who Reaches for This Conversion
- Writers migrating platforms: moving posts out of WordPress or an old CMS into a Markdown-based system — Ghost, Hugo, Jekyll, Astro, or a docs site. Paste each post's HTML, get clean Markdown for the new repo.
- Developers writing documentation: converting rendered docs, wiki pages, or knowledge-base articles into Markdown for a git-tracked docs folder, where changes get code review like everything else.
- Note-takers: clipping article content into Obsidian, Notion, or Logseq, whose native format is Markdown — the conversion preserves structure that plain copy-paste flattens.
- Newsletter and README authors: repurposing existing web copy into Markdown-first tools without manually rebuilding headings, links, and lists.
The opposite direction — publishing Markdown drafts as web-ready markup — is covered by our Markdown to HTML converter; together they form a round-trip between the writing format and the publishing format.
Getting Clean Results from Messy Pages
Real-world HTML — especially from CMS editors and word processors "Save as HTML" — is full of nested spans, empty paragraphs, and styling debris. For best results, convert the article portion rather than a whole page: copy from the browser's reading mode, or grab just the content container's HTML via DevTools (right-click the article → Inspect → Copy outer HTML). Complex HTML tables convert to Markdown tables only when they're simple grids; tables using rowspan/colspan have no Markdown equivalent and may need manual cleanup. Images convert to  references — the files themselves stay wherever they're hosted, so download any images you need to own.
More Questions Answered
Is the HTML I paste sent anywhere?
No — conversion runs entirely in your browser, so internal wikis and unpublished drafts are safe to paste.
Which Markdown dialect does the output use?
GitHub-Flavored Markdown — the de facto standard that Obsidian, Notion, Hugo, and virtually every modern tool accepts, including tables and fenced code blocks.
Why did some formatting disappear?
Anything purely visual — colors, fonts, column layouts, floated boxes — has no Markdown representation and is dropped by design. If a piece of structure vanished (a heading demoted to plain text, say), the source probably styled a <div> to look like a heading instead of using a real <h2>.
Can I convert an entire website at once?
This tool converts one page's HTML at a time. For bulk migrations, convert a few pages here to verify the output style, then script the rest with a library like Turndown using the same settings.
Do links and images keep working?
URLs are preserved exactly. Relative links (/about) stay relative, so they'll only resolve once the Markdown is published on the same site — convert them to absolute URLs if the content is moving domains.