HTML Entities Reference

Last reviewed on May 7, 2026

An HTML entity is a way to write a character in source code without writing the character itself. They come in three forms: named entities (©), decimal numeric entities (©), and hexadecimal numeric entities (©). All three produce the same output character.

This page is a practical reference: which named entities are worth memorizing, when to use a numeric entity instead, and how to handle the five characters that the HTML parser treats as special.

The five reserved characters

HTML reserves five characters for its own syntax. Inside the body of a page, three of them must be written as entities or the parser will misread them:

CharacterNamedNumericWhen to escape
&&&Always, except when it already starts an entity reference.
<&lt;&#60;Always in text content. Not needed in attribute values.
>&gt;&#62;Recommended for clarity, though browsers usually tolerate it.
"&quot;&#34;Inside double-quoted attribute values: title="Say &quot;hi&quot;".
'&apos;&#39;Inside single-quoted attribute values. Note: &apos; is HTML5 only.

The ampersand is the trickiest one. If you write Tom & Jerry in source, modern browsers usually display it correctly — but XML and stricter parsers will reject it. Always use &amp; when you mean an ampersand.

Whitespace and invisible characters

GlyphNamedNumericWhat it does
 &nbsp;&#160;Non-breaking space. Browsers will not break the line at this space, and will not collapse a run of them.
&ensp;&#8194;En space — one en wide.
&emsp;&#8195;Em space — one em wide.
&thinsp;&#8201;Thin space, often used between numbers and currency: 25&thinsp;€.
&zwj;&#8205;Zero-width joiner. Used to combine emoji into family or profession sequences.

The non-breaking space (&nbsp;) is the most-used named entity on the web after the reserved characters. Use it between a number and its unit, between a person's title and surname, and anywhere a line break would create an awkward read. It is also a quick way to insert visible spacing the browser will not collapse.

Punctuation entities worth memorizing

The following named entities all have a longer numeric equivalent, but the named form is shorter and reads better in source.

GlyphNamedNumericUse
©&copy;&#169;Copyright sign. See Copyright.
®&reg;&#174;Registered trademark. See Registered.
&trade;&#8482;Trademark (unregistered). See Trademark.
§&sect;&#167;Section sign. Common in legal references.
&para;&#182;Pilcrow / paragraph mark.
°&deg;&#176;Degree sign. See Degree.
&hellip;&#8230;Horizontal ellipsis. Always one character, never three periods.
&mdash;&#8212;Em dash. Aside or break in thought.
&ndash;&#8211;En dash. Number ranges and date spans.
“”&ldquo; &rdquo;&#8220; &#8221;Curly double quotes.
‘’&lsquo; &rsquo;&#8216; &#8217;Curly single quotes. The closing single is also the proper apostrophe.

For more on each, see the punctuation and special page.

Currency entities

GlyphNamedNumeric
£&pound;&#163;
¥&yen;&#165;
&euro;&#8364;
¢&cent;&#162;
¤&curren;&#164;

The dollar sign has no named entity — it's an ASCII character and you write it directly. Newer currency signs (the Indian rupee ₹, the bitcoin sign ₿) only have numeric entities. Browse the full list on the currency symbols page.

Mathematical entities

The math operators on the web have memorable named entities for the most-used ones:

GlyphNamedUse
±&plusmn;Plus or minus.
×&times;Multiplication sign.
÷&divide;Division sign (obelus).
&ne;Not equal.
≤ ≥&le; &ge;Less-than-or-equal, greater-than-or-equal.
&infin;Infinity.
&radic;Square root.
∑ ∏&sum; &prod;Summation, product (capital sigma, capital pi).
∈ ∉&isin; &notin;Element of, not element of.
∀ ∃&forall; &exist;For all, there exists.

The full math reference is on mathematical symbols.

Greek letter entities

Greek lowercase letters use the obvious names: &alpha;, &beta;, &gamma;, &delta;, &pi;, &sigma;, &mu;, &omega;, and so on. Capitals use the capitalized name: &Alpha;, &Beta;, &Pi;, &Omega;. The Greek letters page lists every one.

Heart, arrow, and other symbol entities

GlyphNamed
&hearts;
&diams;
&clubs;
&spades;
← →&larr; &rarr;
↑ ↓&uarr; &darr;
&harr;
⇐ ⇒&lArr; &rArr;
&hArr;

The four card-suit hearts and arrows are the most-used named entities outside the reserved-character set. See hearts and love and arrows for the full sets.

When to use named vs. numeric entities

Use the named form when the entity is in the short list of widely-supported names (the ones above are all safe). Named entities are easier to read in source and easier to remember.

Use a numeric entity when:

Use the literal character — just paste the symbol — when the file is encoded as UTF-8 and your editor handles it cleanly. UTF-8 is the dominant web encoding and most editors handle it correctly. The literal form reads better than the entity in source, and it's what most modern HTML examples use.

Common mistakes

  1. Forgetting the trailing semicolon. &copy is not &copy;. Most browsers tolerate the missing semicolon for a few legacy entities, but it's not portable.
  2. Capitalization. Named entities are case-sensitive. &Lambda; is the capital Greek lambda; &lambda; is the lowercase. &COPY; is not a valid entity.
  3. Double-escaping. If your CMS already converts ampersands, writing &amp;copy; outputs the literal text &copy;, not the copyright sign. Check your platform's escaping behavior.
  4. Using entities inside <script> or <style>. HTML entity parsing does not happen inside script or style blocks. Use the language's own escape: "\\u00A9" in JavaScript, "\\A9 " in CSS.
  5. Using the wrong dash. A hyphen-minus (-) is not an en dash (&ndash;) is not an em dash (&mdash;). For ranges of numbers, the en dash is correct.

If you have a code point but not the entity

The Unicode converter turns a code point into the literal character; from there you can write either the literal or the numeric entity (decimal or hex). For specific symbols, look them up by name on the home page — every symbol's page lists its decimal and HTML entity codes.