Why does my text look like Wingdings symbols?

Wingdings is a font in which every keyboard key draws a different picture, so the document still contains normal letters, digits, and punctuation that just happen to be displayed as hands, arrows, or stars.

Can I read Wingdings from a screenshot?

Not automatically. This translator only works on the documented Wingdings 1 key map, so it cannot identify a glyph inside an image. Use it on the original typed symbols, or compare the picture to a Wingdings alphabet chart by hand.

Does the translator work on Wingdings 2, Wingdings 3, or Webdings?

No. Those are separate fonts with their own key maps and are outside this tool's scope. The translator covers Wingdings 1 only.

Are my messages uploaded to a server?

No. Conversion happens entirely in your browser and nothing is sent to a server or stored. You can disconnect from the internet after the page loads and the translator will still work.

How to Read Wingdings Symbols in Any App

Reading Wingdings comes down to one rule: Wingdings is a font, not a code, so every symbol you see is just the key you typed drawn as a picture. That means a document full of hands, arrows, and skulls really only contains ordinary letters, digits, and punctuation — the Wingdings font is what renders them as icons. To read a Wingdings message, you do not need to memorize the alphabet or learn a new language; you need a reliable map from each Wingdings glyph back to the key that produced it. Once you have that map, decoding is as simple as looking up each symbol and writing down the matching letter. In practice, the fastest way to do this is to paste the symbols into a translator that uses the official Unicode encoding of the Wingdings 1 key map, which guarantees a one-to-one match with no ambiguity. This article explains what Wingdings actually is, why it becomes unreadable outside Microsoft Office, and exactly how to turn any Wingdings 1 message back into readable text in any application.

What Wingdings Actually Is

Wingdings is a symbol font shipped with Microsoft Windows and Microsoft Office. It was designed in 1990 by Kris Holmes and Charles Bigelow as a quick way to insert pictograms into documents before standardized icon sets existed. Each of the 26 uppercase letters, 26 lowercase letters, 10 digits, and a wide range of punctuation marks on a standard keyboard is mapped to a specific hand-drawn glyph: A becomes a hand pointing up, B becomes a balloon, C becomes a hat, and so on. The full set of glyphs and their key positions is documented in Microsoft's Wingdings reference, which lists every printable key alongside the symbol it draws.

Because Wingdings is a font rather than a character encoding, the underlying text in your document does not change. If you select a paragraph and switch the font from Wingdings back to Arial, the letters, digits, and spaces reappear exactly as you typed them. This is the central insight for anyone learning how to read Wingdings: there is nothing to crack or decode in the cryptographic sense. The letters are always there — the font just hides them behind a symbol.

Wingdings was followed by Wingdings 2 and Wingdings 3, which provide additional glyphs using the same key positions, and by Webdings, a separate Microsoft font with its own map. Each of these four fonts uses the same keyboard keys but assigns a different picture to each one, which is why Wingdings 2 messages do not look like Wingdings 1 messages and why they cannot be read with the same map. The translator covered in this article focuses on Wingdings 1, which is the most widely used of the family.

Why Wingdings Stops Being Readable Outside Word

The trick with Wingdings is that it only works while the font is installed. Open a Wingdings document on a machine that has the font, and every glyph renders correctly. Copy that same document into a chat app, an email, a social network, or a phone that lacks Wingdings, and the document either falls back to a generic font or shows the Unicode Private Use Area characters that the source machine quietly inserted as a substitute.

The substitution is what causes the mystery. A passage that read as "hello" in Word can land in your inbox as a row of pictograms because the receiving app replaced the missing Wingdings glyphs with placeholder symbols from the Unicode private-use range. Those placeholder symbols are still tied to the same key positions, so a translator that knows the official Unicode mapping of Wingdings 1 can usually read them back to text without the original font being installed anywhere on the reader's machine. For a focused walkthrough of the same workflow, see the guide on converting Wingdings to text without the font.

This gap is what the Wingdings Translator is built for. It maps every printable key in the Wingdings 1 chart — the full A-Z, a-z, 0-9, and punctuation range — to the standard Unicode symbol that represents the same glyph, so the result can be pasted and read in any Unicode-aware application without installing a single font.

Read Wingdings Online in Three Steps

The translator lives in your browser and uses the documented Unicode mapping of the Wingdings 1 key set. There are no uploads, no signups, and no fonts to install on your machine. To read a Wingdings message, follow these three steps:

Choose Text to symbols or Symbols to text. Pick "Symbols to text" if you are trying to read a Wingdings message, or "Text to symbols" if you want to write one in portable Unicode.
Type or paste your text, or the Unicode symbols to decode. Symbols to text accepts any string made up of the official Unicode equivalents of the Wingdings 1 glyphs.
Review anything left unchanged, then copy the result. The translator lists any character it could not map — for example accented letters, non-Latin scripts, or unrelated emoji — so you always know exactly what was and was not converted.

Because the mapping is based on the official Unicode encoding of Wingdings 1, encoding and decoding are exact inverses: anything the translator encodes can be decoded back to the original text without ambiguity. Spaces and line breaks are preserved exactly where you put them, and those gaps often provide the strongest clues about word boundaries when you are staring at a row of pictograms.

Open the Wingdings Translator to try it on your own message, or keep reading for the specific cases that come up most often.

Reading Wingdings in Word, PowerPoint, and Google Docs

If you can open the source file in Microsoft Word or PowerPoint, reading Wingdings is almost embarrassingly simple. The font is shipped with Office, so every glyph is already drawn correctly on screen. Select the passage you want to read (Ctrl+A selects the whole document), then change the font from Wingdings back to Arial, Times New Roman, or your normal body font using the font dropdown on the Home tab. The letters, digits, and punctuation reappear instantly because they were never replaced — only their display style was. To confirm, you can also press Ctrl+Shift+F to open the font box and type "Wingdings" back in to watch the symbols reappear.

Google Docs handles Wingdings the same way for documents created in Google itself. Open the file, select the Wingdings text, and use the font menu to switch to Arial. If the document was uploaded as a .docx and the original Wingdings formatting is preserved, Google will display the symbols through its own font substitution and the same trick of switching the font back to a standard face works just as well.

LibreOffice Writer and OpenOffice Writer include Wingdings in their standard installations, so the same select-and-change-font workflow applies there too. The catch is that if you are on a machine without any of these applications — for example a school Chromebook, a phone, or a borrowed laptop — the font may not be installed at all and the select-and-switch trick is not available. In that case the browser-based translator is the most reliable fallback.

Reading Wingdings From Screenshots and Chat Messages

The translator works on text, not on images, so the source you have matters. The three cases readers run into most often are:

A chat or email message made up of Unicode symbols. This is the easy case: copy the symbols straight into the translator's Symbols to text box and read the result. If your message was once plain text that got re-encoded when the Wingdings font was missing, the symbols you see are the official Unicode equivalents and the translator will read them back exactly.
A screenshot of a Wingdings document. The translator cannot identify a glyph inside a picture, but you can still decode it manually by comparing the symbol to a Wingdings alphabet chart, such as the printable chart at textformatting.com. Match each visible symbol to its key, write down the letters, and you have the original text.
A live document where the font is still applied. If you can open the file in Word, PowerPoint, or any editor that has Wingdings installed, simply select the passage and switch the font back to your normal body font as described in the previous section.

For chat messages and emails specifically, copying the raw symbol string is always preferable to taking a screenshot, because screenshots drop the underlying Unicode characters that the translator needs. Most messaging apps and email clients let you long-press or right-click to copy selected text; if the symbols appear in a selectable form, copy them directly rather than capturing the screen.

What Wingdings Will and Won't Decode

The translator is deliberately narrow so its results are exact rather than approximate. Knowing what is and is not in scope avoids surprises.

Font	Covered by this translator	Notes
Wingdings 1	Yes	Full keyboard map — A-Z, a-z, 0-9, and punctuation — is encoded to Unicode symbols and back
Wingdings 2	No	Separate Microsoft font with its own key map, not decoded here
Wingdings 3	No	Separate Microsoft font with its own key map, not decoded here
Webdings	No	Different Microsoft font with a different map
Custom or unknown dingbat fonts	No	Unknown glyphs are listed as unchanged rather than guessed at

Characters outside the Wingdings 1 key map — accented letters, Greek or Cyrillic, CJK, or unrelated emoji — pass through the translator unchanged and are listed in the unchanged section so you can see exactly what was and was not converted. The Unicode symbols the translator outputs are the official equivalents of the Wingdings glyphs, but their final appearance still depends on the fonts installed on the receiving device, so a small number may display as empty boxes on older systems. To preview the genuine article, the encoder also renders your original text using the real Wingdings font where it is installed, and you can reproduce the same look anywhere by typing the text in Word or PowerPoint and setting the font to Wingdings.