HTML Symbols Reference: Arrows, Math, Currency, and More

Using symbol entities in HTML

HTML provides named entities for many common symbols. A named entity starts with an ampersand and ends with a semicolon — for example, → renders as →. When no named entity exists, you can use a numeric character reference like ₹ (decimal) or ₹ (hexadecimal).

If your document is served as UTF-8 (which it should be), you can also type or paste the symbol directly into your source code. Entity references remain useful when you want the source to stay ASCII-readable or when the character is easy to confuse with a similar-looking one.

Arrow symbols

Arrows are among the most frequently used symbols in web content, appearing in navigation links, breadcrumbs, and instructional text.

Math symbols

Mathematical operators and relations are essential for technical documentation, educational content, and anywhere you discuss quantities or comparisons.

Currency symbols

International e-commerce and financial content often require currency symbols beyond the dollar sign that sits on every keyboard.

The Indian rupee sign (₹) was added to Unicode in 2010 as U+20B9 and does not have a named HTML entity. You must use the numeric reference ₹ or paste the character directly.

Punctuation and typography

Typographic symbols help your content look polished and professional. Using the correct dash, bullet, or quotation mark makes a noticeable difference in readability.

Entity vs. UTF-8 character

Modern web pages are almost universally encoded in UTF-8, which means you can include any Unicode character directly in your HTML source. So why bother with entities at all?

• Readability — — is immediately recognizable as an em dash, whereas the literal — character could be mistaken for a hyphen in a monospaced editor.
• Safety — For the five reserved HTML characters ( &, <, >, ", ' ), entities are required to avoid breaking your markup.
• Invisible characters — Non-breaking spaces ( ) and zero-width joiners look identical to regular spaces in most editors. Entities make them explicit.

For everything else, it's a matter of team preference. Using the raw character is perfectly valid and often simpler.