HTML Asset, Image & Markdown Extractor

The old explanation credited the wrong machinery. This tool hands your markup to the browser’s own HTML parser — DOMParser — and then simply asks it questions: every script[src], every stylesheet link, every image element. That is why malformed nesting does not derail it. The regular expression enters for one job the parser cannot do: finding URLs that are not attributes of anything, buried in the text of an inline script or inside a CSS url(...). Two different problems, two different tools — and knowing which is which is the difference between an extractor that works and one that almost works.

Most people assume a web image always lives in an `<img>` tag, but browsers also paint pictures from CSS `background-image` rules, responsive `srcset` lists, `<meta>` social-preview tags, and even arrays inside JavaScript. This tool sweeps all of those places at once. The practical takeaway: a photo you plainly see on screen may have no `<img>` tag at all — it is drawn by a stylesheet, which is why 'right-click, save image' sometimes fails.

Many 'subscribe to keep reading' walls are pure theatre. The full article is usually delivered in the page's HTML and then merely covered by an overlay or blur — the words crossed the network before you were asked to pay. Because this extractor reads the visible text straight from the parsed markup as Markdown, that content reappears intact. It is a reminder that hiding something with CSS is not the same as withholding it.