Wingdings in Google Docs: Every Way to Do It (2026)

You want the symbols — a check mark here, a smiley there — inside a Google Doc. The catch: Docs does not ship the Wingdings font. The good news: three fully working methods get you identical results, and this guide ranks them from fastest to most flexible.

Why There Is No Wingdings Font Button

Wingdings is a Microsoft font licensed with Windows and Office; Google Docs bundles its own type library and does not include it — the same reason your Android keyboard has never offered it. But here is the fact that unlocks everything: the symbols themselves long ago received Unicode code points. The check mark, the smiley, the airplane — each exists as a genuine character that renders on any platform, no font required. That is the entire strategy below: work with the characters, skip the font. (Curious which glyph maps to which key? The full chart and the font history guide have you covered.)

Method 1 — Copy and Paste (30 Seconds, Best for Most People)

Open our tap-to-copy wall, click any symbol, and it is on your clipboard — paste into your doc, done. This works for check marks, smiley faces, arrows, all twenty-eight of the most-used glyphs. For whole phrases, the English-to-Wingdings converter outputs the full string with one Copy button. Pasted symbols behave like normal text in Docs: they bold, recolor, resize and travel intact into Slides, Gmail and comments.

Method 2 — Insert > Special Characters (Built Into Docs)

1. In your doc, click Insert > Special characters.
2. Search by keyword — try "check", "ballot" or "dingbat".
3. Click the glyph; it inserts at your cursor.

The picker's search is hit-or-miss with symbol names (it knows "check mark" but not always the Wingdings-style variant you want), which is why we rank it second. Where it shines is browsing: the dingbat categories are a rabbit hole of decorative characters you did not know you had. Power tip — draw the symbol into the search box's sketch pad and Docs will try to recognize it.

Method 3 — Char Codes for Keyboard Purists

Every dingbat has a hex code you can type anywhere, Docs included: type the code, press Enter… no — Google Docs does not convert Alt codes like Windows does. The codes still matter as reference (our keyboard guide lists them for Word users), but inside Docs the honest answer is methods one and two. This is exactly why we built the tool pages: browser-native, zero-install, and the output is the same Unicode either way.

Real Examples You Can Paste Right Now

Pro examples, one per workflow: a teacher marking essays pastes ✓ next to finished rubric lines; a project manager builds a status column of ☑/◻ toggles; a student decorates a title with a row of ✈ ♪ ☾ — all identical to what Word users achieve with the real font, all rendered from plain characters. More ready-cut combinations live on the check mark page and the Halloween kit.

One Modern Gotcha: The Emoji Takeover

Paste certain symbols into the Docs mobile app and they may render as colorful emojis — the cartoon bomb instead of the classic black glyph. Nothing is broken: phones choose an alternate face for characters that have both. For the strict monochrome look, copy from our no-emoji mode, which appends an invisible variation selector that locks text-style rendering. The decoder accepts either form, so replies decode cleanly regardless of which face your correspondent's device picked.

Collaboration Notes

• Fonts do not travel — a collaborator with Word who applies the real Wingdings font is fine locally, but exporting to Docs converts glyphs back to letters. Unicode characters survive every hop; font-styled text does not. When in doubt, convert once with our translator and paste the characters.
• Accessibility — screen readers announce most dingbats poorly. Pair important symbols with real words ("Done ✓" not "✓" alone); your blind collaborators will thank you, and the doc reads better in every export.
• Search — Docs searches symbol characters literally, so a check-mark row is findable, but keyword-based search ("done") will not match it. Another reason to keep the word next to the glyph.

Quick Reference Card

Everything above also applies to Google Slides, Sheets cells, Gmail signatures and Google Forms — same characters, same paste behavior. The alphabet tables and the full chart are your permanent references; bookmark the copy wall for daily use.

Beyond Docs: The Same Tricks in Slides, Sheets and Gmail

Everything above carries into the rest of Google's suite, with a few per-app notes worth knowing. Slides: symbols make superb decorative bullets — paste one into the bullet-character field of a list style and every line inherits it; a ✓ bullet on a closing-agenda slide reads instantly in a classroom or standup. Sheets: build a status column of ☑/◻ toggles, then filter by exact character to count completed rows — the formula =COUNTIF(A:A,"☑") counts your done items, a trick project trackers have used for years. Conditional formatting can even recolor cells containing a chosen glyph, turning a plain spreadsheet into a glanceable kanban. Gmail signatures: a short symbol row (music note, star, airplane) under your name survives every client and renders identically in Outlook and Apple Mail, because the characters are plain Unicode — unlike an image logo that some clients block by default. Forms: spice up section headers with single decorative glyphs; respondents see them on every device without you touching a single font setting.

Troubleshooting: Four Complaints We Hear

• "It pastes as a box/tofu." The target font lacks the glyph — switch that text run to a default like Arial or Docs' native font; Unicode coverage in mainstream system fonts is near-universal for the classic dingbats.
• "It turned into an emoji." Mobile Docs picking the colorful face — copy from no-emoji mode instead, which ships the variation selector that forces the monochrome glyph.
• "My collaborator sees letters." They applied a Wingdings-lookalike font to plain text on their end (a Word habit). Re-send the actual characters from the translator; characters travel, fonts do not.
• "Special-character search finds nothing." Docs' keyword index is quirky about dingbat names; search "ballot" or "dingbats", or just use the copy wall — it is always one click and never depends on Google's search vocabulary.

Why This Whole Approach Beats Installing Fonts

Font-based workflows fail at every boundary: different operating systems, missing licenses, mobile apps, exports, collaborators. The Unicode approach has none of those failure modes — characters are the documents' own substance, viewable forever by anyone, searchable, accessible-adjacent, and free. It is the same bet this entire site is built on, and the same reason a checker-pasting teacher in a school Chromebook district has exactly the same experience as a designer on a tricked-out workstation. Portability is the feature; the font was only ever the delivery mechanism.

Frequently Asked Questions