HTML to Markdown

Content migration usually means pulling pages out of a CMS, a wiki, or a scraped web page — all of which give you HTML — and moving them into a Markdown-based system: a docs site, a static site generator, or a knowledge base backed by Git. This tool automates that translation, converting tags like headings, lists, tables, links, and code blocks into their Markdown equivalents.

The conversion follows GitHub Flavored Markdown (GFM) conventions, so tables, strikethrough, and task-list checkboxes come out the same way they would if you'd written them by hand. Everything runs locally in your browser using an HTML parser built into the browser itself — nothing you paste or upload is ever sent anywhere.

• •Paste the innermost content you actually want — a full page including <nav>, <header>, and <footer> will convert those too, cluttering the output. Copy just the article or content region where possible.
• •ATX headings (# Heading) are the more common choice for modern Markdown files; Setext (underlined with ===) only supports heading levels 1 and 2, so deeper headings fall back to ATX automatically.
• •Review tables and nested lists after conversion — HTML has more structural flexibility than Markdown, so unusual nesting or merged cells may need small manual touch-ups.
• •If the source HTML has inline styles or class names for formatting (bold via CSS instead of <strong>), those visual cues won't carry over — Markdown only preserves semantic tags.