If you copy a diamond-shaped mark from a PDF, a diagram, or a character picker, the picture alone may not tell you what you copied. ◇ and ◊ can be especially troublesome: one is called WHITE DIAMOND, the other LOZENGE, yet a font can draw them so similarly that the names are more helpful than the outlines.
◆ is easier to separate at first glance because it is filled, but even that shape has nearby Unicode relatives. The useful question is not simply “Does this look like a diamond?” but “Which diamond-shaped character is actually in the text?”
The Names Are More Reliable Than the Outline
| Character | Unicode name | Code point | Basic appearance |
|---|---|---|---|
| ◇ | WHITE DIAMOND | U+25C7 | Outlined diamond |
| ◊ | LOZENGE | U+25CA | Outlined lozenge |
| ◆ | BLACK DIAMOND | U+25C6 | Filled diamond |
Unicode places all three in the Geometric Shapes block. In these names, white marks the open form and black the filled form; the actual on-screen color can be changed by ordinary styling. The same naming convention appears across many geometric symbols.
A black diamond can therefore appear red, blue, or green when the surrounding text is styled that way. Its code point remains U+25C6.
Why ◇ and ◊ Can Be Almost Impossible to Separate by Eye
People often expect a lozenge to be narrower or more elongated than a diamond. Some typefaces do draw ◊ that way. Others do not. Unicode does not give you a dependable width ratio that can be measured from a screenshot and used as an identification test.
The Unicode core specification explicitly says that U+25CA LOZENGE should be distinguished from U+25C7 WHITE DIAMOND and U+2662 WHITE DIAMOND SUIT. It describes U+25CA as a typographical symbol seen in PostScript and the Macintosh character set, and it points out another character sometimes called a lozenge: ⌑ U+2311 SQUARE LOZENGE. Even the everyday name “lozenge,” then, is not enough to identify a code point.
Changing fonts may make the difference easier to see, but it cannot settle the identity of the original text. The stored character stays the same even when the glyph changes shape.
◆ Is Clearer, but It Is Not the Only Filled Diamond
◆ U+25C6 BLACK DIAMOND is the familiar filled form in this group. Unicode also includes size-specific relatives such as ⬥ BLACK MEDIUM DIAMOND and ⬩ BLACK SMALL DIAMOND. Those sizes have their own code points; they are not produced by simply shrinking U+25C6.
In mathematics, size can be part of the notation rather than decoration; Unicode explicitly allows for semantic distinctions among differently sized simple shapes. Replacing every diamond-shaped character with the most familiar one can therefore erase information from the source.
Outside technical notation, authors may use different sizes only for visual hierarchy. The code point still matters if the text needs to survive copying, searching, or exact comparison.
Card-Suit Diamonds Belong to a Different Family
♢ U+2662 WHITE DIAMOND SUIT and ♦ U+2666 BLACK DIAMOND SUIT are playing-card symbols. At small sizes a card-suit diamond may be visually indistinguishable from a geometric one, even though copying the text reveals a different code point.
A poker hand or suit selector gives you a strong clue that a card-suit character is intended. A flowchart, map key, legend, or diagram is more likely to use a general geometric symbol. That is still only a clue: designers sometimes choose a symbol for appearance rather than for the meaning suggested by its Unicode name.
In editable text, the character value settles that ambiguity immediately. The artwork around the symbol is useful context, but it cannot turn a card-suit diamond into a geometric one.
Equations Bring Their Own Diamond-Shaped Symbols
Mathematics adds another common lookalike: ⋄ U+22C4 DIAMOND OPERATOR. It is an operator, not a decorative version of U+25C7. Unicode also encodes shapes such as ⟡ WHITE CONCAVE-SIDED DIAMOND.
In an equation, that semantic difference is more important than a slight change in width or line weight. Replacing an operator with a geometric marker because the two happen to look alike can change the encoded notation even when a reader barely notices the visual change.
When a diamond-shaped mark sits among variables and operators, read the expression before deciding that it is merely a geometric diamond.
When All You Have Is a Screenshot
A filled shape at least narrows the field, but an outlined one may be ◇, ◊, ♢, or another related symbol. Context can make one candidate more plausible, yet fonts and custom icons prevent a screenshot from proving the exact code point.
With live text, identification is straightforward. With an image alone, it is better to describe what is visible—an outlined diamond-shaped mark, for example—than to attach a Unicode name that the pixels cannot prove.
Character data removes the guesswork: U+25C7 is ◇, U+25CA is ◊, and U+25C6 is ◆. The awkward cases are the flattened ones—a tiny mark in a scan, screenshot, or PDF where no text value is exposed.