HTML Entity Table
Search common HTML entities by symbol, name or numeric code.
Overview
The HTML Entity Table is a searchable index of named character references (©, —, ) alongside their decimal (©) and hexadecimal (©) numeric equivalents and the rendered glyph. Filter by symbol, name, or code point to find the right entity quickly.
Useful when learning how to encode a copyright symbol in HTML or how to write a non-breaking space entity. Reach for it when authoring static HTML, building email templates that must avoid raw Unicode, or auditing third-party content for unsafe characters.
How it works
HTML5 defines roughly 2,200 named character references derived from the HTML5 named-character-references list maintained by WHATWG. Browsers also accept any Unicode code point as a numeric entity (decimal &#NNN; or hexadecimal &#xNNNN;). For most modern use cases, only a small subset matters — the entities for characters that cannot appear literally in HTML (<, >, &, ", ') plus typography helpers (em dash, ellipsis, curly quotes) and a few symbols (copyright, registered, trademark, non-breaking space).
The table filters across name, glyph, and numeric code so you can look up an entity from any of the three angles.
Examples
- Search
dash→ returns—(—),–(–),−(−). - Search
&→ returns&and explains why a literal&is unsafe in HTML. - Search
160→ returns (non-breaking space), code point 160 / 0xA0. - Search
quot→ returns",“,”,‘,’.
FAQ
Do I need entities for non-ASCII characters?
Not for general content if your document is UTF-8 encoded — write them literally. Entities still matter for HTML-significant characters (<, &) and for environments that may strip non-ASCII (older email clients, certain CMS exports).
Named vs numeric entities?
Named entities (©) are more readable. Numeric entities (©) are universally supported even in fragments where the doctype is unclear (e.g. XML imports).
Why does matter?
It prevents the browser from breaking a line between two words. Useful for "Mr. Smith" or "100 km" where the line break would look wrong.
Are HTML entities the same as URL encoding?
No. URL encoding uses %XX percent-escapes (e.g. %20 for space). HTML entities are for HTML context only.