HTML Entity Decoder

It converts escaped sequences like &amp;, &lt; and &#233; back into the real characters they stand for, such as &, < and é, so the text reads normally instead of showing raw entity codes.

Named entities use a word, like &copy; for the copyright sign. Numeric entities use a Unicode code point written in decimal (&#169;) or hexadecimal (&#xA9;). This tool decodes all three forms in one go.

Common ones are built in, including &amp;, &lt;, &gt;, &quot;, &apos;, &nbsp;, &copy;, &reg;, &trade;, arrows-free symbols like &deg; and &times;, currency like &euro; and &pound;, and typographic marks like &ndash;, &hellip; and the curly quotes. Any named entity outside that set is left untouched, but its numeric form will still decode.

Unknown or malformed references such as &unknownxyz; are left exactly as written. Only valid named, decimal and hex entities with a closing semicolon are decoded, so surrounding text is never altered.

&nbsp; decodes to a non-breaking space (U+00A0). It looks like an ordinary space but does not wrap to the next line or collapse the way a regular space can, which is why it can appear invisible in the output.

Yes, and that is deliberate. A single pass means &amp;lt; becomes the literal text &lt;, not a less-than sign. Double-decoding would corrupt content that intentionally shows an entity, so the tool decodes each reference only once.

Yes. Hex references above the basic plane, like &#x1F600; for a grinning face, are decoded using full code point support. References that fall in the surrogate range or above the Unicode maximum are rejected and left as written.

Yes. The decoder only matches references that end in a semicolon, so a bare &amp with no semicolon is treated as ordinary text. This avoids greedily consuming words that merely start with an ampersand.

Yes. Decoding runs entirely in your browser and nothing you paste is uploaded to a server or stored, so confidential snippets stay on your machine.