LiteralKit symbol tool
Convert English text to Wingdings symbols — or decode Wingdings back to English — across all four Microsoft variants. Every character tells you what it became.
Converted 5 of 5 · 1 newer Unicode.
Converted 5 of 5 · 1 newer Unicode.
Your text stays in this browser.
Pick a direction — Encode turns English into Wingdings symbols, Decode turns pasted symbols back into English.
Pick a variant — Wingdings 1 is the original 1990 icon font; Wingdings 2, 3, and Webdings are sibling fonts with different glyphs at the same input positions.
Read the character proof on the right. It shows what each input character became, flags newer Unicode targets, and keeps original characters that have no Unicode equivalent.
Wingdings is an icon font Microsoft licensed in 1990 from Type Solutions and shipped with Windows 3.1 in 1992. Instead of letters, the font draws small pictures at the positions where ordinary fonts put A, B, C — so typing the letter A in Wingdings renders a victory hand, typing B renders a different icon, and so on across the printable ASCII range.
The font was designed in an era when most documents never left the PC that created them. Pasting Wingdings into an email, a chat, or a web page did not carry the pictures with it — only the underlying ASCII letters, which other devices rendered with their own fonts. That quirk is the source of almost every "Wingdings looks broken" complaint today.
The Unicode Consortium eventually encoded most Wingdings glyphs as ordinary symbol characters (the bulk in Unicode 7.0, June 2014), so symbols can now travel across devices as real text. This translator uses those Unicode targets — not the original font — so what you copy is plain Unicode text.
Switch between variants in the Font row under the source box. The same input letter maps to different symbols in each font.
Each character in the proof panel is tagged with one of three tiers. The tier is a Unicode data property — it tells you when the target character was added to Unicode. It is not a platform guarantee.
When a destination device has no font that covers a code point, it draws a placeholder — typically an empty rectangle that typographers call "tofu" because the box looks like a block of bean curd. The text is still correct; the receiving device just cannot draw it. Paste a short sample into the destination you care about before relying on a symbol.
Some Wingdings symbols share their code points with emoji. For those code points, this translator appends U+FE0E (the Unicode "text presentation selector") after the symbol. U+FE0E asks the receiving platform to render the character as text rather than as a colorful emoji. Whether a destination honors that request depends on its font and rendering stack.
The output is Unicode text, but its appearance depends on the destination font and renderer. Paste a short sample into the exact document, app, or browser where it will be used. If it differs, the character proof shows the code point LiteralKit produced.
Two failure modes come up often enough that the translator calls them out inline instead of pretending nothing is wrong.
If you typed Wingdings in Microsoft Word and copied the result, what reaches the clipboard is ordinary letters — Word stored the text as ASCII and only the Word display showed pictures. Decode sees plain letters, not symbols, and tells you so. Switch to Encode to translate those letters into real Unicode symbols.
Encode expects English letters. If you paste Wingdings symbols (or any non-ASCII characters), Encode has nothing to convert and offers to switch you to Decode.
If you want to read the chart instead of typing into a box, the dedicated alphabet page lists every supported character across all four variants with the same compatibility tags. Symbols you click there copy to your clipboard.
W.D. Gaster is a hidden character from the 2015 video game Undertale, whose dialogue is rendered in Wingdings. The convention is to write Gaster dialogue in ALL CAPS because that is how the game presents it — uppercase letters are also where Wingdings 1 has its most recognizable glyphs (the zodiac signs).
To write like Gaster, type in ALL CAPS, choose Wingdings 1, and copy. The output is real Unicode text, so it survives outside Wingdings-aware contexts better than the game's original rendering — but it will not look identical to Undertale, which uses the original Wingdings font file.
There is no physical Wingdings keyboard. The realistic input paths are: (1) use this translator to produce real Unicode symbols you can paste anywhere, or (2) install the Wingdings font locally and switch your text editor to it, accepting that the result will not travel with the symbols when copied. The translator path is what we recommend.
They are four separate Microsoft fonts from 1990 and 1997. The same input letter renders as a different picture in each. The translator covers all four; pick the variant that matches the symbols you want.
It depends on your friend's device font. Symbols tagged ✓ Widely supported render on most current devices. Symbols tagged ⚠ Newer Unicode may show as empty boxes on older devices. The character proof tells you which is which before you copy.
That position in the Wingdings font has no Unicode code point (typically because the glyph is a Microsoft trademark like the Windows logo). LiteralKit keeps your original character rather than substituting a lookalike. The character proof labels this ◌ No Unicode equivalent.
Usually not directly. Word stores Wingdings text as the underlying ASCII letters and only shows pictures in its own display. What you copy is plain letters. Switch to Encode to turn those letters into real Unicode symbols that travel with the text.
The symbols this translator outputs are Unicode characters that the Unicode Consortium standardized to match the original Wingdings font glyphs. The current mapping data is generated from WG2 N4384 (2012), which cites N4363 as an earlier reference. The original font glyphs and Unicode symbols may look slightly different because they use different fonts.
No. Conversion runs locally in your browser. There is no server-side processing and no account.
That is U+FE0E, the Unicode text presentation selector. It is added only to characters on the official Unicode emoji-variation list and asks the receiving platform to render the character as text. You can keep it; it is harmless on platforms that ignore it.