HTML Entities for Symbols: Named, Decimal, and Hex

What Are HTML Entities?

An HTML entity is a text sequence that represents a character in HTML source code. Entities exist for two reasons: to safely insert reserved characters that would otherwise be interpreted as HTML markup, and to insert special characters that may be difficult to type or that might not survive copy-paste across different encodings.

Every HTML entity starts with an ampersand (&) and ends with a semicolon (;). Between them, you specify the character using one of three formats:

• Named entity — A human-readable name: © renders as ©
• Decimal entity — The Unicode codepoint in base 10: © renders as ©
• Hexadecimal entity — The Unicode codepoint in base 16, prefixed with x: © renders as ©

All three produce the same result in the browser. The difference is convenience: named entities are easier to read in source code, while numeric entities (decimal and hex) work for any Unicode character — even those without a named entity.

Using HTML Entities in Practice

Here are common patterns for using entities in real HTML markup:

Inline Text

Insert entities directly in your HTML content, just like regular text:

<p>Copyright &copy; 2025 Acme Corp. All rights reserved.</p>
<p>Temperature: 72&deg;F</p>
<p>Price: &euro;49.99</p>

Escaping Reserved Characters

When displaying code or technical content, escape characters that HTML would otherwise interpret as markup:

<p>Use &lt;strong&gt; for bold text.</p>
<p>The URL parameter separator is &amp;.</p>

Attribute Values

Entities work inside HTML attributes too. This is especially important for quotes inside attribute values:

<img alt="Photo &copy; John Doe" src="photo.jpg">
<input placeholder="Search &hellip;">

Non-Breaking Spaces

Use   to prevent a line break between two words, which is useful for names, units, and numbers:

<p>100&nbsp;km</p>
<p>Dr.&nbsp;Smith</p>

For CSS-based symbol insertion using pseudo-elements, see Using Symbols in CSS with the Content Property. For JavaScript string handling, read Unicode in JavaScript.

Do You Still Need HTML Entities in UTF-8?

With UTF-8 as the dominant web encoding, you can type most symbols directly in your HTML source. A copyright sign © or an em dash — can appear as literal characters in a UTF-8 document. So when do you still need entities?

• Always for reserved characters — <, >, &, and " in attributes must be escaped regardless of encoding.
• When your toolchain isn't UTF-8 safe — Some build tools, email templating systems, or legacy CMSes may corrupt non-ASCII characters. Entities survive any ASCII-compatible pipeline.
• For readability in source code — — is immediately recognizable; the literal character — is ambiguous (is it an em dash, en dash, or hyphen?). Named entities make intent explicit during code review.
• For characters you can't type — Hex entities let you insert any Unicode character without needing a special keyboard layout or input method.

In modern UTF-8 web development, entities are optional for most characters but remain essential for reserved characters and valuable for clarity. Understanding all three formats gives you flexibility regardless of the situation.

Finding Any HTML Entity on Symbolwise

Symbolwise eliminates the need to memorize or look up entity codes. Here's the workflow:

1. Search — Type a name like "copyright" or a codepoint like "U+00A9" in the search bar.
2. Select the HTML format — On the symbol card, click HTML to copy the entity to your clipboard.
3. View full details — Click the symbol to see its detail page, which shows the named entity (if available), decimal entity, and hex entity side by side, along with UTF-8 bytes, CSS escape, JavaScript escape, and URL encoding.

This works for any of the 150,000+ characters in the Unicode standard — not just the ~250 that have named entities. Whether you need © for a copyright notice or 😀 for a grinning face emoji, the HTML entity is always one search away.

For a broader guide to finding and copying symbols in all six formats, see How to Find and Copy Any Unicode Symbol. To understand the Unicode standard that HTML entities reference, start with What Is Unicode?

Troubleshooting HTML Entities

If an entity isn't rendering correctly, check these common issues:

• Missing semicolon — Entities must end with ;. Writing &copy without the semicolon may work in some browsers but is technically invalid and can cause parsing errors.
• Wrong encoding declaration — Ensure your HTML document declares UTF-8 encoding with <meta charset="UTF-8"> in the <head>. Without this, browsers may misinterpret multi-byte characters.
• Double-encoding — If you see © rendered as literal text instead of ©, the entity was encoded twice. This often happens when a CMS or template engine escapes content that already contains entities.
• Font support — The entity is correct but the character displays as a box or blank. This means the user's font doesn't include a glyph for that codepoint. See why symbols show as boxes or question marks for solutions.

When in doubt, use the browser's developer tools to inspect the rendered element. The Elements panel will show the actual character — if the entity resolved correctly, you'll see the symbol rather than the entity text.