TEXT & WRITING

Strip HTML Tags

Remove HTML from a page or snippet and keep the readable text: scripts and styles dropped, entities decoded, blocks as line breaks, links kept on request.

Plain text with the document’s line structure (or on one line), the number of tags removed, elements dropped and entities decoded — parsed, not regex-stripped, and nothing fetched.

Example: A page with a <head>, a <style> and a <script> becomes "Hi & bye" and "Para bold link (https://x.y)." followed by "- one" / "- two"; table cells come out tab-separated and <pre> keeps its spacing.

v0.1.0 · last reviewed 21 September 2026
Loading the workspace…
BUILT TO BE UNDERSTOOD

Parsed,
not regex-stripped.

Why a parser, what is dropped, and how the text keeps its shape.

Parser

The HTML goes through the same forgiving in-house parser as the HTML → Markdown page. That matters for the cases a "<…>" regex gets wrong: script and style contents, comments, attributes containing a >, unclosed tags. Nothing is fetched or executed.

What is dropped

script, style, head, title, meta, link, noscript, template, svg, iframe and object go with their contents. Everything else contributes its text. Entities — named (&, é) and numeric (’) — are decoded to characters.

Shape

Block elements (p, div, headings, lists, blockquote, table rows …) become line breaks and list items can carry a "- " marker; table cells are tab-separated; <pre> keeps its whitespace; runs of blank lines collapse to one. Links can keep their target as "text (url)" and images their alt text. Nothing leaves the browser; the same four anonymous usage counts as the rest of the site apply.

SOURCES

  • In-house forgiving HTML parser shared with HTML → Markdown: script, style, head, svg, iframe, template dropped with contents; p, div, headings, li, tr, br → line breaks; entities decoded

Last reviewed 21 September 2026. How results are checked: How we verify.