Browse this Wingdings alphabet across Wingdings 1, 2, 3, and Webdings, then copy individual supported Unicode symbols from the chart. Compatibility is tagged per character because the original font glyphs and modern Unicode rendering are not guaranteed to look identical everywhere.
Wingdings alphabet chart
✓ Widely supported⚠ Newer Unicode◌ No Unicode equivalent
Each row in this Wingdings alphabet is one input character. The Symbol column shows what that input becomes in the active variant. Compatibility uses the legend marks above the table, because paste results still depend on the destination font.
✓Widely supported. Target code point encoded before Unicode 7.0; broad font coverage.
⚠Newer Unicode. Target code point added in Unicode 7.0 or later; some devices may lack the glyph.
◌No Unicode equivalent. Variant has a glyph here but Unicode has no target. We show the original input character; the row is not copyable.
All baseline mappings come from WG2 N4384, which records the Unicode unification of each Wingdings glyph and cites N4363 as an earlier reference. We do not ship approximate look-alikes.
Switch variant tabs to compare this Wingdings alphabet. The same input character maps to different Unicode targets in each font; some input positions exist in only a subset of variants.
Wingdings 1 covers input positions 0x21–0xFE plus 0xFF (the Windows logo position, not encoded in Unicode).
Wingdings 2 covers 0x21–0xF9. Letters tend to become ornamental dingbats (interrobangs, leaves, quilts).
Wingdings 3 covers 0x21–0xF0. Most letters become arrows of various weights and directions.
Webdings covers 0x21–0xFF. The 1997 picture-icon font; many letters become hand gestures, buildings, or vehicles.
Characters with no Unicode equivalent
The ◌ rows in this Wingdings alphabet are inputs where the active variant has a glyph but Unicode has no encoding. The most well-known case is Wingdings 1 position 0xFF, the Windows logo, which was excluded from Unicode for trademark reasons. LiteralKit preserves the original input character rather than substituting a lookalike.
Click any ✓ or ⚠ symbol in this Wingdings alphabet to copy it. A green confirmation shows the symbol you copied.
◌ rows are not copyable — the variant has no Unicode target for that input. The translator page preserves your original character in the same situation.
Some symbols include an invisible U+FE0E character that asks the receiving platform to render as text. It is harmless to keep.
If a destination shows an empty box (tofu), the device lacks a font for that code point. Try a destination with appropriate font support, and verify a short sample where the symbol will be used.
Frequently asked questions
Why don't all four variants show the same number of rows?
Each variant covers a different range of input positions. Wingdings 2 stops at position 0xF9, Wingdings 3 stops at 0xF0, while Wingdings 1 and Webdings extend to 0xFE and 0xFF. Rows only appear where the active variant has a glyph.
Can I copy multiple symbols at once?
Not from this Wingdings alphabet chart. The chart copies one symbol per click. To translate a string of characters at once, use the Wingdings translator page.
What do ✓, ⚠, and ◌ mean?
✓ Widely supported: Unicode encoded this character before version 7.0. ⚠ Newer Unicode: encoded in 7.0 or later, may lack glyphs on older devices. ◌ No Unicode equivalent: the variant has a glyph but Unicode has no target — the row is not copyable.
Are these the original Wingdings font glyphs?
No. These are the Unicode characters that the Unicode Consortium standardized to match the original Wingdings glyphs (per WG2 N4384, which cites N4363 as an earlier reference). They render using whatever symbol font your device ships; on a system with the original Wingdings font installed, they may look slightly different.
Why does my paste show the wrong symbol?
The symbol you copied is correct Unicode text. If the destination shows something different, its font is substituting a different glyph for that code point. Try pasting into a different app or a major browser.