Wingdings Font

Charles Bigelow and Kris Holmes designed the predecessors of Wingdings in 1990–1991 as Lucida Icons, Arrows and Stars. Microsoft reorganized and released the symbol families under the Wingdings name in 1992.

The official family entry provides the source account and the listed edition’s information. A broader family name may cover other releases; keep the exact version clear when comparing files or documenting a project.

Use a short character sample to inspect installed glyphs, not to infer a universal letter-to-symbol translation. If the message must carry semantic symbols across apps, use appropriate Unicode characters instead of depending on a particular dingbat font.

Use representative wording: include names, punctuation, numbers and any script you need. A family name alone does not establish that a particular installed edition contains every required character or typographic feature.

No substitute with matching script coverage or glyph mappings is asserted here. Use the official family information to investigate the exact characters and edition your workflow needs.

For broader context, read the related typography guide. When comparing other fonts, use the same sample and check shaping, punctuation and output size in your final application.

The local preview asks the browser to load a named face already on your device. If that cannot happen, the preview is unavailable; it does not silently present an alternative as Wingdings. The control shows only the installed default face and does not expose every weight, optical design or OpenType feature.

Use the official family entry to investigate available editions, supplied products and acquisition routes. This site does not provide Wingdings font files or promise a free redistribution license. Copying ordinary text does not carry a font into another app. Read typeface versus font and font file types when preparing an editable handoff.

Choose a compatible single-face TTF or OTF file you already have in the chart above. The tool reads that file locally, lists entries from a supported character map and lets you search, resize the preview and copy a labeled code. It does not obtain or identify an original Wingdings file for you. A browser may reject a file it cannot render; use the installed-font workflow below in that case.

The chart distinguishes Unicode code points from a legacy Windows symbol mapping. Microsoft’s OpenType reference explains that symbol mappings can use font-specific positions in the Private Use Area without being Unicode encodings. The viewer’s default glyph ID is a separate file reference, not a number to paste indiscriminately into another application. Unencoded alternates and ligatures are outside this chart’s scope.

In Word, use Insert > Symbol > More Symbols and choose the installed family. Check Character code and the adjacent From field: Microsoft distinguishes Unicode (hex) from Symbol (decimal). Match the font and code system before repeating a mark. For a worksheet, keep a plain-language label beside an unfamiliar symbol; a decorative tick is not automatically an interactive checkbox. The separate Webdings chart guide concerns another family with its own mappings.