HTML Entity Lookup & Converter

Search and browse all HTML entities by name, number, or character with copy-to-clipboard.

Tested tool guide Tested browser tools Checked August 16, 2026

What HTML Entity Lookup & Converter does, with a checked example

HTML lets you write any character as a text-safe reference: a named form like €, a decimal form like €, or a hex form like €. This tool searches the full set of 2,231 named character references from the WHATWG HTML standard, accepts all three spellings as well as a pasted character, and shows the decoded character, its Unicode code point, and every equivalent entity form, each copyable in one click. What users trip over: names are case-sensitive and the semicolon is required. © resolves, &COPY; does not, and  is the euro sign, not a control character.

Worked example

A concrete input and expected output from the current implementation.

Input

&#128;

Expected output

Decodes to the euro sign, U+20AC. The tool also lists the equivalent forms: &euro;, &#8364;, and &#x20AC;, each ready to copy.

HTML numeric references to code points 128-159, the C1 control range, are remapped by the parsing rules to their Windows-1252 equivalents, so 128 becomes the euro sign, the same character the named form € produces. A plain Unicode lookup of 128 would have returned a control character.

How the result is produced

Search and matching

Each query is checked against the WHATWG table of 2,231 named character references, so a name search must be exact and case-sensitive: © is defined, &COPY; is not, and a name that fails to match is exactly what browsers render as literal text. Numeric queries accept both decimal (€) and hexadecimal (€) forms, and a pasted character is matched back to every reference that produces it.

Code point remapping

Decoding follows the HTML parsing rules, not raw Unicode. Numeric references to code points 128-159 are remapped to the Windows-1252 characters HTML expects, which is why  yields the euro sign and  yields an em dash. References to surrogates, values above U+10FFFF, U+000D, or noncharacters are replaced with U+FFFD, the replacement character.

Good uses

Writing an HTML email or template when you need a character your keyboard cannot type, or one that would break the markup: < to display code,   where a browser would collapse a raw space.
A scraped page or exported file arrived as a run of &#nnn; numbers and you want to know what text they actually represent before reworking the markup.
Moving text through an encoding you do not control, such as an ASCII-only system, where the entity form like ö survives while the raw character would be corrupted.

Limits and checks

Names are case-sensitive. © is valid; &COPY; and &Amp; are not in the table, and browsers pass a misspelled name through as literal text, so verify the canonical spelling rather than assuming an uppercase variant exists.
The semicolon is required. Browsers still decode a small legacy set of HTML4-era references like &amp without it, and decode semicolon-less numeric references with a parse error, but only the semicolon form is valid everywhere, including XML.
Numeric references to 128-159 never produce the control characters those code points mean in Unicode; they decode as Windows-1252 punctuation such as the euro sign, en dash, and em dash. A result like  showing a euro sign is correct behavior, not a bug.

Common questions

Is there a named entity for every character?

No. HTML defines 2,231 named references covering a few thousand characters, a small fraction of Unicode. Characters without a name, including most emoji, can still be written as numeric references such as 😀 for the grinning face, and the lookup resolves them the same way.

Why does  show a euro sign instead of a control character?

HTML deliberately remaps numeric references in the 128-159 range to the Windows-1252 characters that existed before Unicode took over that space, so 128 decodes to the euro sign and 151 to an em dash. This mirrors what every browser does; showing the control character instead would be wrong.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.