Black diamond suit (♦) is Unicode U+2666 in the Miscellaneous Symbols block. It is the filled diamonds suit used in card games and suit notation. HTML provides the named entities ♦ and ♦.
Remember
Character ♦
Unicode U+2666
Hex entity ♦
Decimal ♦
Named entity ♦ (also ♦)
CSS escape \2666
Not the same ♢ U+2662 (white) · ❖ U+2756 (dingbat)
All of these produce the same glyph: ♦. Prefer ♦ in hand-written HTML; type ♦ in UTF-8 when you can; use numeric or CSS forms for generated content.
Black diamond suit using Hex Code: ♦
Black diamond suit using HTML Code: ♦
Black diamond suit using Named Entity: ♦
Black diamond suit using CSS Entity: ♦
Typed directly: ♦
How It Works
1. Hex:U+2666 → ♦ in HTML. The browser turns it into ♦.
2. Decimal: same code point as 9830 → ♦. Same result as hex.
3. Named:♦ (or ♦) is the standard HTML name for U+2666 — clear in source.
4. CSS: use \2666 in content (not an HTML entity). #point::after appends that ♦ after the paragraph text.
5. Typed ♦: fine in UTF-8 source. All five lines show the same glyph.
Pitfalls & Tips
Common mistakes when working with black diamond suit (♦).
Screen readers may not announce the suit clearly. Pair the glyph with visible or visually hidden text.
Fonts
Match suit fonts
Use the same font stack for ♣ ♦ ♥ ♠ so suit glyphs look consistent.
CSS vs HTML
Do not mix escapes
\2666 belongs in CSS. ♦ / ♦ belong in HTML.
Semicolon
End references
Always finish with ; — write ♦, not &diams.
Compatibility
Browser Support
Black diamond suit (U+2666) and its entity forms (♦, ♦, ♦, ♦, CSS \\2666) are supported in all mainstream browsers. Glyph quality depends on font support for Miscellaneous Symbols.
✓ Universal support
Black Diamond Suit (♦)
Type ♦, or encode with named, hex, decimal, or CSS escape — same glyph 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
U+2666 / entitiesFull support
Bottom line: Prefer ♦ or a typed ♦ for normal text. Use numeric forms when generating markup, and \\2666 only inside CSS content.
Remember
Key Takeaways
Unicode: black diamond suit is U+2666 (decimal 9830).
HTML: prefer ♦ (or ♦ / ♦).
CSS: use \2666 inside content for generated icons.
Use ♦ (hex), ♦ (decimal), ♦ or ♦ (named), or the CSS escape \2666 in the content property. All render ♦. You can also paste ♦ directly if your file is UTF-8.
U+2666 (hex 2666, decimal 9830). Unicode names it BLACK DIAMOND SUIT. It belongs to the Miscellaneous Symbols block in the playing-card suit range.
Yes. ♦ and ♦ both map to U+2666. Prefer ♦ in hand-written HTML; numeric forms are useful in generated markup.
♦ (U+2666) is the filled black diamond suit. ♢ (U+2662) is white diamond suit. ❖ (U+2756) is a dingbat diamond with a white X — not a card suit.
HTML entities (♦, ♦, or ♦) go in markup. The CSS escape \2666 is used in stylesheets (usually in the content property of ::before/::after). Both render ♦.
Use ♦ for card games, Bridge notation, suit labels, and UI that needs the diamonds suit. Pair the glyph with the word Diamonds when accessibility matters.
🤔
Did you know?
Black diamond suit is Unicode U+2666 (decimal 9830) in the Miscellaneous Symbols block — official name BLACK DIAMOND SUIT. HTML’s named references are ♦ and ♦. It is not white diamond suit (U+2662 ♢) or black diamond minus white X (U+2756 ❖).