HTML Entity Decode
Decode HTML entities back into readable characters instantly in your browser, using the browser's own HTML parser. Restore scraped HTML text to normal, clean up titles from an RSS feed, or fix content that was accidentally double-encoded.
Usage examples
Restoring scraped HTML text to normal
When text pulled from a webpage is full of entities like & or ", convert it back to plain characters so it's easy to read.
Cleaning up titles from an email or RSS feed
Turn HTML-entity-encoded titles or content from an RSS feed or email body back into readable plain text.
Checking what character a numeric reference represents
See exactly what character a numeric reference like € actually represents (in this case, €).
Reading an API response that double-encoded its text
If an API or CMS export stored a field with entities still baked in, such as a product name showing up as 'M&M's', paste it here to decode it back to readable text.
Comparing two blocks of text that look identical but aren't
Decode a block of text copied from a webpage before diffing it against a plain-text source, since leftover entities like or ’ can make otherwise-matching strings compare as different.
Quick reference
Named entities: punctuation & symbols
| Entity | Character | Unicode |
|---|---|---|
| & | & | U+0026 |
| < | < | U+003C |
| > | > | U+003E |
| " | " | U+0022 |
| ' | ' | U+0027 |
| | U+00A0 | U+00A0 |
| © | © | U+00A9 |
| ® | ® | U+00AE |
| ™ | ™ | U+2122 |
| — | — | U+2014 |
| – | – | U+2013 |
| … | … | U+2026 |
| ‘ | ‘ | U+2018 |
| ’ | ’ | U+2019 |
| “ | “ | U+201C |
| ” | ” | U+201D |
| • | • | U+2022 |
| † | † | U+2020 |
| ‡ | ‡ | U+2021 |
| ‰ | ‰ | U+2030 |
| € | € | U+20AC |
| £ | £ | U+00A3 |
| ¥ | ¥ | U+00A5 |
| ¢ | ¢ | U+00A2 |
| § | § | U+00A7 |
| ¶ | ¶ | U+00B6 |
| · | · | U+00B7 |
| ° | ° | U+00B0 |
| ± | ± | U+00B1 |
| × | × | U+00D7 |
| ÷ | ÷ | U+00F7 |
| « | « | U+00AB |
| » | » | U+00BB |
| ½ | ½ | U+00BD |
| ¼ | ¼ | U+00BC |
| ¾ | ¾ | U+00BE |
| ² | ² | U+00B2 |
| ³ | ³ | U+00B3 |
| µ | µ | U+00B5 |
Named entities: letters, arrows & suits
| Entity | Character | Unicode |
|---|---|---|
| á | á | U+00E1 |
| é | é | U+00E9 |
| í | í | U+00ED |
| ó | ó | U+00F3 |
| ú | ú | U+00FA |
| ñ | ñ | U+00F1 |
| ü | ü | U+00FC |
| ö | ö | U+00F6 |
| ä | ä | U+00E4 |
| ß | ß | U+00DF |
| Æ | Æ | U+00C6 |
| æ | æ | U+00E6 |
| ç | ç | U+00E7 |
| ← | ← | U+2190 |
| ↑ | ↑ | U+2191 |
| → | → | U+2192 |
| ↓ | ↓ | U+2193 |
| ♠ | ♠ | U+2660 |
| ♣ | ♣ | U+2663 |
| ♥ | ♥ | U+2665 |
| ♦ | ♦ | U+2666 |
Numeric entities
| Entity | Character | Unicode |
|---|---|---|
| ' | ' | U+0027 |
| " | " | U+0022 |
| & | & | U+0026 |
| < | < | U+003C |
| > | > | U+003E |
|   | U+00A0 | U+00A0 |
| © | © | U+00A9 |
| — | — | U+2014 |
| € | € | U+20AC |
| ' | ' | U+0027 |
| / | / | U+002F |
|   | U+00A0 | U+00A0 |
| 😀 | 😀 | U+1F600 |
Frequently asked questions
Is my text sent to a server?
No. All decoding happens entirely in your browser, and what you enter is never sent to a server.
Does it use the browser's HTML parser?
No. It doesn't rely on browser parsing features like innerHTML at all — it decodes using a hand-written lookup table plus a regex for numeric entities.
Which named entities are supported?
The basics like &, <, >, ", and ', plus around 60 commonly used named entities covering currency symbols, punctuation, arrows, and more. Any name not on the list is left as-is.
Are numeric entities supported too?
Yes — both decimal numeric entities like ' and hexadecimal ones like ' are supported.
What happens if my text contains double-encoded entities, like &amp;?
This tool performs a single decoding pass, so '&amp;' becomes '&' rather than '&'. If your text was encoded more than once, paste the output back into the input and decode it again to fully unwrap it.
What happens to text that isn't a recognized entity?
Anything that doesn't match a known named entity or a valid numeric entity pattern is left completely untouched, including stray ampersands that aren't part of an entity at all.
Can decoding ever be unsafe, like introducing an XSS risk?
Not here, since this tool only ever produces plain text output displayed as text — it never writes the result into the page as live HTML. The risk to be aware of is elsewhere: if you take decoded output and insert it into a webpage without re-encoding it first, any special characters it now contains, like < or >, could be interpreted as markup.