Questions About This Tool
Why use a parser instead of find and replace?
Because HTML nests arbitrarily deep and real markup is full of unclosed tags. Browsers have a specified recovery algorithm for that, and DOMParser is it. Using the real parser means malformed input converts the way it displays, which no pattern can promise.
Is it safe to paste HTML from a site I do not control?
Yes. Parsing with the text/html type builds an inert document: scripts do not execute, event handlers do not fire, and images and stylesheets in the markup are never fetched. The tags become data, not behavior.
Where did my divs and classes go?
Markdown has no equivalent, so layout containers are unwrapped — their contents are kept and the container is dropped. Elements that are not prose at all, like script and style, are removed entirely and named in the summary.
Why are there backslashes in my output?
They escape characters that would otherwise become Markdown syntax. Without them, a sentence containing asterisks would render as emphasis when the Markdown is converted back. The escaping is kept narrow so the output stays editable.
Can I convert back and forth without losing anything?
Only for the constructs Markdown can express. Headings, lists, links and code survive a round trip; layout divs, styling and merged table cells do not. It is a migration aid rather than a lossless channel.
Does it handle tables?
Yes, into GitHub pipe syntax, with pipes inside cells escaped. Merged cells cannot survive, because Markdown tables have no colspan or rowspan.