HTML to Markdown
Convert HTML pages or snippets into clean Markdown (.md). Scripts and unnecessary markup are stripped, leaving readable Markdown for docs, README files or
Drop your HTML file here
or click to browse files
Convert an HTML page or a snippet into clean Markdown: headings, links, emphasis, lists, tables and code are mapped to their Markdown equivalents, while scripts, styles and layout wrappers are stripped out.
The everyday use is turning documentation, a blog post or a CMS export into Markdown you can commit to a repository or paste into Obsidian, Notion or a static site generator. What you get is readable text with the structure preserved, not HTML with the tags filed off.
How to convert HTML to Markdown
Paste HTML or choose a .html file
Convert it
Copy the Markdown or download the .md file
FAQ
What happens to scripts and styles?
They are removed, along with navigation and layout wrappers that carry no content. Inline styles do not survive because Markdown has no concept of them.
Are tables converted?
Yes, simple tables become Markdown pipe tables. Merged cells and nested tables have no Markdown equivalent and are simplified - check those by hand.
Are images kept?
Image tags become Markdown image syntax pointing at the original URL. The files themselves are not downloaded.
How do I convert a live web page?
Open the page, view the source or use "Copy outer HTML" from the developer tools, then paste it here. Fetching a URL directly is not supported because of cross-origin restrictions.
Will the output look identical to the original page?
No. Markdown is a text format: layout, colours, multi-column designs and custom components are lost by design. Expect to tidy up complex pages.
Is my HTML uploaded?
No, conversion runs locally in your browser.
At a glance
| Input | HTML |
|---|---|
| Multiple files | No |
| Where it runs | In your browser - files are never uploaded |
| Works offline | Yes — once the page has loaded |
| Price | Free, no sign-up, no watermark |
What survives a conversion
Structure usually survives, formatting often does not. Headings, paragraphs, lists, links, bold and italics convert cleanly between Markdown, HTML, Word and PDF. What tends to break is anything relying on styling rather than structure: CSS classes and custom colours disappear, complex nested tables collapse into unreadable ones, embedded HTML may be stripped for safety, and images either stay as links or get downloaded depending on the tool. Footnotes and math usually need explicit support. If the result matters, convert a sample first - a document with a table, a code block, a link and an image will reveal almost every problem you are going to hit.
Using the result in the real world
Where the converted file goes next decides which format you should produce. Pasting into a CMS or a help centre usually means HTML, because those systems store and re-render markup. Sending a contract, an invoice or anything someone will sign means PDF, because the layout is fixed and the file cannot be edited by accident. Editing later means Word, since that is what people will actually open it in. Feeding a script or a static site generator means keeping it as Markdown. Converting to the wrong target is the most common reason a document "looks wrong" afterwards - the content is intact, but the destination was never going to preserve that particular formatting.