Thirty Suits, Chess Pieces and Game Symbols
Browse 30 stored Unicode symbols or compare twelve card/chess/game-themed text patterns. The picker includes eight solid/outline suits, twelve white/black chess pieces and ten card or game entries. It is not a complete playing-card deck, chess engine, legal-move checker or chess-notation formatter.
Finding a piece, suit or card symbol
- Search symbols by collection name, literal symbol or U+ code point. Use Black Queen for one piece or Queen to compare both colors.
- Use its named Copy symbol button. Selected symbol shows the complete sequence and code points for inspection or manual copying.
- Enter Source text and compare the twelve fixed patterns. Read or select the complete readonly output, then use its named Copy button.
- Wait for clipboard confirmation. Clear text preserves symbol search; Reset restores Checkmate Strategy, blank search and empty symbol selection.
How the card and chess patterns decorate text
Source text is segmented into extended grapheme clusters before adding symbols. After styles append a cyclic symbol after each non-whitespace cluster; only those clusters advance the cycle. Between border styles insert a fixed separator between adjacent non-whitespace clusters, then frame the complete source.
Spaces, tabs and original CRLF, CR and LF remain exactly in order. The patterns keep source clusters whole and leave whitespace as typed. This preserves the source sequence, not a guarantee of identical visual alignment. Empty or whitespace-only source produces no results.
There are twelve pattern slots, with fixed palettes and ordering. Full Cards uses four stored aces, not a complete deck. Chess Mix intentionally mixes piece colors. The tool neither interprets chess positions nor verifies notation. Source is bounded to 25,000 UTF-16 units and 5,000 grapheme clusters; exact estimates cap each output at 100,000 units and all outputs at 500,000 before allocation. Errors leave the source editable.
Complete outputs for sample text
| Source | Pattern | Exact output |
|---|---|---|
AB | Card Suits | A ♠ B ♥ |
👩🏽💻B | Card Suits | 👩🏽💻 ♠ B ♥ |
A
B | Card Suits | |
AB | Card Border | ♠ A ♥ B ♦ |
AB | Full Cards | A 🂡 B 🂱 |
Glyphs, presentation and what a copy cannot prove
- Unicode text does not ensure every device has a suitable glyph.
- Shape, color, fallback and screen-reader speech vary; the copied sequence and destination-field permission are separate questions.
- A piece or suit can have text/emoji presentation behavior, so do not promise a fixed color from its label.
- Searching Queen changes which entries are visible; copied state belongs to the exact stored identity and is cleared when Search changes, and it does not follow a filtered grid index.
- If copying fails, select the complete symbol or output manually.
- A successful write is not a verified platform username or a notation check.
Searching and checking a short draft
Search Black Queen or U+265B to find the same stored piece. Search uses case-insensitive name/code-point substrings, with every query word required and outer whitespace ignored; literal symbol sequences remain unchanged. Check a short draft on the destination device, and choose a separator or frame that keeps ordinary words readable. Full Cards cycles through four stored aces, not a whole deck. An error keeps the source editable rather than shortening it. Copy confirms success only after the write completes, and source or Search changes clear pending feedback. A successful copy does not establish font appearance, destination acceptance or chess-notation validity.
Sources: Unicode chess and suit characters, Unicode text segmentation, text and emoji presentation and clipboard confirmation and errors.