HTML currency entities are character references for money symbols — dollar, cent, pound, euro, yen, generic currency, and regional marks such as rupee, ruble, won, and baht.
Remember
Named (common) $ ¢ £ ¤ ¥ €
Numeric ₹ (₹) · ₽ (₽) · ₩ (₩) · ฿ (฿)
CSS escape \24 · \A2 · \A3 · \A4 · \A5 · \20AC
Prefer UTF-8 type the glyph when the whole toolchain is Unicode-safe
Prefer named forms when HTML defines them; use hex or decimal when there is no short name. For the generic placeholder alone, see Currency Sign (¤).
Reference
Quick Reference
Search by symbol, Unicode, hex, decimal, or entity name.
1. Named:$, ¢, £, €, ¥, and ¤ are HTML named references for common currency glyphs.
2. Numeric: rupee and ruble use hex forms ₹ and ₽ because HTML5 has no short named entity for them.
3. CSS:\20AC in content injects the euro (U+20AC). Escapes belong in stylesheets, not as HTML entities.
4. Same glyph: named, hex, decimal, CSS, and typed UTF-8 all resolve to the same Unicode character when the code point matches.
Pitfalls & Tips
Common mistakes when working with currency entities.
Named
Prefer names when available
€ and £ are clearer than numeric forms. Use the table for symbols without a short HTML5 name.
Yen
¥ ≠ always JPY
U+00A5 is shared by yen and yuan. Add ISO codes (JPY / CNY) when the legal tender matters.
Locale
Glyph ≠ formatting
Entities only supply the symbol. Separators, decimals, and symbol placement follow locale rules.
A11y
Pair with clear currency text
For critical amounts, include an ISO 4217 code or visible label so assistive tech conveys both amount and currency.
CSS vs HTML
Do not mix escapes
\20AC belongs in CSS. € / € belong in HTML.
Semicolon
End references
Always finish with ; — write € and ₹, not bare forms.
Compatibility
Browser Support
Named and numeric currency character references work in all mainstream browsers with UTF-8 documents. Visible glyphs depend on font coverage for less common marks.
✓ Universal support
HTML Currency Entities
Encode with named, hex, decimal, CSS escape, or type the character — same code point everywhere encoding is supported.
100%Browser coverage
Google ChromeSupported
Yes
Microsoft EdgeSupported
Yes
Mozilla FirefoxSupported
Yes
Apple SafariSupported
Yes
OperaSupported
Yes
Internet ExplorerAll versions
Yes
Currency entitiesFull support
Bottom line: Prefer named entities when listed. Use numeric forms for rupee, ruble, won, and baht. Use CSS escapes only inside content.
Numeric: rupee ₹, ruble ₽, won ₩, baht ฿.
CSS: use escapes such as \20AC inside content for generated text.
Watch out: glyph ≠ locale formatting; pair with ISO codes when precision matters.
One line: named when available → numeric from the table → CSS escape only in content.
Frequently Asked Questions
Use named references such as € and $, or numeric forms like € / €. All valid forms for one code point render the same character.
$, ¢, £, ¤, ¥, and € cover many Western layouts. Use hex/decimal from the Quick Reference table for rupee, ruble, won, and baht.
When you want ASCII-safe source, generated markup, or explicit documentation of the code point. UTF-8 paste is fine when your editor, server, and headers all agree on Unicode.
HTML entities go in markup. CSS uses backslash hex in content on ::before/::after (for example \20AC for euro). Pick HTML for body text and CSS when the design injects the glyph.
Use ₹ (₹) and ₽ (₽), or decimal ₹ and ₽. There is no standard short named entity for these in HTML5.
U+00A5 is shared by yen and yuan in Unicode. Prefer ISO 4217 codes (JPY, CNY) or clear labels when the legal tender matters.
🤔
Did you know?
Common Western currencies have short HTML5 names — $, ¢, £, ¤, ¥, €. Symbols such as Indian rupee (₹ / U+20B9) and Russian ruble (₽ / U+20BD) use numeric references. Entities supply the glyph; locale rules still control separators and placement.
