HTML Entities Reference

Searchable reference for 65+ HTML character entities. Click any row to copy, inspect detailed escape codes, hex, and decimal values.

Search HTML Entities

Copy Action Mode

Entity Catalog (66 shown)

Char	Named entity	Numeric	Description
&	&	&	Used to start HTML entities
<	<	<	HTML tag delimiter
>	>	>	HTML tag delimiter
"	"	"	Double quote
'	'	'	Single quote / apostrophe
			Prevents line break between words
			Optional hyphenation point
—	—	—	Long dash
–	–	–	Medium dash
…	…	…	Three dots
©	©	©	Copyright symbol
®	®	®	Registered trademark
™	™	™	Trademark symbol
€	€	€	Euro currency
£	£	£	British pound sterling
¥	¥	¥	Japanese yen / Chinese yuan
¢	¢	¢	US cent
¤	¤	¤	Generic currency sign
•	•	•	Bullet point
·	·	·	Middle dot / interpunct
°	°	°	Degree sign
±	±	±	Plus or minus
×	×	×	Multiplication sign
÷	÷	÷	Division sign
¹	¹	¹	Superscript 1
²	²	²	Superscript 2 (squared)
³	³	³	Superscript 3 (cubed)
¼	¼	¼	1/4
½	½	½	1/2
¾	¾	¾	3/4
‘	‘	‘	Left single quotation mark
’	’	’	Right single quotation mark
“	“	“	Left double quotation mark
”	”	”	Right double quotation mark
«	«	«	Left-pointing double angle quotation mark
»	»	»	Right-pointing double angle quotation mark
§	§	§	Section sign
¶	¶	¶	Pilcrow / paragraph mark
†	&dagger;	†	Dagger
‡	&Dagger;	‡	Double dagger
✓	&check;	✓	Check mark
✗	&cross;	✗	Ballot X
∞	∞	∞	Infinity symbol
′	′	′	Prime (feet / minutes)
″	″	″	Double prime (inches / seconds)
←	←	←	Leftwards arrow
↑	↑	↑	Upwards arrow
→	→	→	Rightwards arrow
↓	↓	↓	Downwards arrow
↔	↔	↔	Left right arrow
∑	∑	∑	Summation / sigma
√	√	√	Radical / square root
≈	≈	≈	Almost equal to
≠	≠	≠	Not equal to
≤	≤	≤	Less than or equal to
≥	≥	≥	Greater than or equal to
µ	µ	µ	Micro sign
´	´	´	Acute accent
¯	¯	¯	Macron / overline
¸	¸	¸	Cedilla
à	à	à	à
é	é	é	é
ñ	ñ	ñ	ñ
ü	ü	ü	ü
¡	¡	¡	¡ (Spanish)
¿	¿	¿	¿ (Spanish)

Row Inspector Card

&AmpersandUsed to start HTML entities

Code & Escape Reference

Named Entity

Hex Entity

Dec Entity

CSS Escape

\0026

JS/JSON Escape

\u0026

Hex Value

0x26

Decimal Value

When to use HTML entities

HTML entities are needed when you want to display characters that have special meaning in HTML (<, >, &) or characters not easily typed on a keyboard. Named entities like © are more readable; numeric entities like © work in any HTML version. Modern UTF-8 documents can use most characters directly, but entities remain the safest option in HTML attributes and wherever encoding is uncertain. For encoding and decoding, try HTML Entity Encoder / Decoder.

Built and maintained by Meet Shah · Last updated 1 August 2026

What this tool is used for

Finding the entity for a character you cannot type.
Checking whether a named entity exists or only a numeric one.
Copying a character in named, numeric or raw form.
Confirming an entity's spelling before using it.
Finding the entity for a character that must be escaped.

Frequently Asked Questions

Which characters must always be escaped?: `&`, `<` and `>` in text, plus quotes inside attribute values. The ampersand first — escaping it after the others double-escapes everything, which is the single most common bug in hand-written escaping.
What is the difference between named and numeric entities?: Named entities such as `&` are readable but only exist for a defined set; numeric ones such as `&` work for any code point. Numeric is the safer choice for anything unusual.
Do I still need entities for accented characters?: No, not with a UTF-8 document. Writing `é` directly is clearer and shorter; entities for accents are a legacy of pages served in ASCII-only encodings.
What is a non-breaking space actually for?: Preventing a line break between two things that belong together — a number and its unit, a name and its initial. Using several in a row to create indentation is a misuse that breaks on narrow screens.
Why does my ampersand break the page?: Because a bare `&` followed by letters and a semicolon parses as an entity, so `?a=1&copy=2` silently becomes `©`. Query strings in HTML must have their ampersands escaped.

Common errors and gotchas

Using `'`, which is not in older HTML and where the numeric form is safer.
Escaping every non-ASCII character, which bloats markup unnecessarily on a UTF-8 page.
Forgetting the trailing semicolon, which some parsers tolerate and others do not.
Escaping only `<` and `>` inside an attribute, where quotes and ampersands matter too.
Treating entity escaping as XSS protection, which is context-dependent.