Strip HTML tags, scripts and styles from pasted markup and return clean plain text, with an option to keep paragraph and line breaks where they belong. Runs entirely in your browser — your numbers never leave this device.
| Entity | Becomes | Entity | Becomes |
|---|---|---|---|
| & | & | | (space) |
| < | < | © | © |
| > | > | ® | ® |
| " | " | … | … |
| ' / ' | ' | — / – | — / – |
Paste markup copied from a web page, an email or a CMS export, and the tool returns the plain text a reader would see. The order of operations matters and is deliberate: script and style blocks are removed whole first, because their contents (code and CSS rules) are not page text and would otherwise leak into the output as gibberish once their tags were stripped. HTML comments go at the same stage. Only then are the remaining tags removed, which leaves the text nodes behind.
With line breaks kept, the structure of the page survives in text form: <br> becomes a line break, the closing tags of paragraphs, divisions, list items, headings and other block elements become line breaks, and each list item opens with a bullet. Without that option, all whitespace collapses to single spaces and the output is one continuous block — the right form for feeding text into a word counter or a summary field. Either way, common HTML entities are decoded, so & comes back as &, © as © and a non-breaking space as a normal space; numeric entities such as © are decoded from their code point as well.
One honest limit: this is tag stripping, not rendering. Text that a page generates with JavaScript, hides in attributes, or builds from CSS will not appear, because it was never text in the markup. What you pasted is processed entirely in your browser and is never uploaded or stored — safe for unpublished pages and private exports.
Because it was not text in the markup you pasted. Content loaded by JavaScript after the page renders, text stored in attributes (alt text, titles, data attributes) and anything built by CSS do not exist as text nodes in the HTML. View-source markup gives the most complete input; for JavaScript-rendered content, copy the visible text from the rendered page instead.
The whole blocks. Script and style elements are deleted with their contents before ordinary tags are stripped — otherwise a page's CSS rules and JavaScript would survive as meaningless text once the angle brackets around them were gone. HTML comments are removed at the same stage.
When the output is for reading or further editing: paragraphs, headings and list items become separate lines and list items gain a bullet, so a copied article keeps its shape. Turn it off when the output is data — a single-line summary, an input to the Word Counter, or text destined for a spreadsheet cell — where breaks would only get in the way.
The common named ones — &, <, >, ", ', , ©, ®, …, —, – — plus any decimal numeric entity (© becomes ©) via its code point. An entity outside that set is left as written rather than guessed at, so nothing is silently altered.
Technically it is clean text; legally and editorially it is still the source's words. Stripping markup changes the format, not the ownership. Use the output for analysis, migration of your own content, quoting with attribution, or feeding your own drafts into other tools.
No. Stripping runs 100% in your browser; your markup is never sent to a server, stored or tracked.
More in Text Tools · Browse all tools