Why symbols show as boxes, and how to fix a missing glyph
A box, sometimes called tofu or the missing glyph sign, means the font has no drawing for that character. The character itself is intact. Switch to a font with wider coverage, restore or update the system fonts, or update the operating system, and the symbol appears without changing your text.
Last updated
Check your own device first
Every symbol page on this site runs a small render test in your browser. It draws the character in a serif, a sans-serif and a monospace font and compares each result with the box your system draws for a character it does not have. The verdict tells you whether your device can display that character, before you send it to anyone.
If the test says the character shows as a box on your device, the rest of this guide explains why and what to change. If it renders for you but not for the person you sent it to, the fix is on their side: their fonts, not your text.
Try it on the degree sign: run the render test for °.
Four different failures that all look like a box
| What you see | What it means | What fixes it |
|---|---|---|
| An empty rectangle, sometimes with tiny hex digits inside | Tofu, the missing glyph. The font has no drawing for this code point. | Use a font with wider coverage, or add a fallback font in your CSS font stack. |
| A rectangle with a question mark, or a diamond with a question mark | The decoder could not map the bytes to a character at all. | Fix the encoding. Serve and save the file as UTF-8. |
| Strings such as A-tilde followed by a degree sign where one character should be | Mojibake. UTF-8 bytes were decoded as a single-byte encoding. | Fix the encoding declaration, then re-save the source from a correct copy. Re-encoding the corrupted text usually does not recover it. |
| A correct symbol where you expected a coloured emoji, or the reverse | A missing or unexpected variation selector. | Append U+FE0F for the emoji presentation, or U+FE0E for the plain text presentation. |
Fixes for each operating system
The cause is almost always the same, a font without that character, but where the fix lives depends on the system. Start with the row for the device that shows the box.
| Where you see the box | Most likely cause | Fix |
|---|---|---|
| Windows | The character is newer than the installed fonts, or the font for that script is an optional feature that is not installed. | Run Windows Update. For scripts such as Japanese or Hebrew, add the matching Supplemental Fonts under Optional features in Settings. Segoe UI Symbol and Segoe UI Emoji cover most symbols. |
| macOS | A standard font was switched off or removed, or the app uses a font without the character. | Open Font Book and choose File, then Restore Standard Fonts. Check that no system font is disabled, then restart the app. |
| iPhone and iPad | The character, often a recent emoji, was added to Unicode after your iOS or iPadOS version. | Update iOS or iPadOS. Emoji and symbol support arrives with system updates; there is no separate font to install. |
| Android | The system fonts predate the character, which is common for new emoji on older phones. | Install the system updates your phone offers. If none are left, the character can still be copied and read on another device. |
| Linux | No installed font covers the character. | Install a broad font family such as Noto (on Debian and Ubuntu, the fonts-noto and fonts-noto-color-emoji packages) or DejaVu, then run fc-cache -f. |
| A web page you build | No font in your font stack has the glyph, and the system fallback on the reader's device has none either. | Add a broad fallback at the end of the font-family list, or serve a webfont that covers the characters you use. |
Boxes in PNG files and other exported images
When symbols turn into a no glyph sign in a PNG, the program that drew the image did not have a font with those characters. An image is pixels, so the box is baked in at export. Changing fonts afterwards cannot fix the file; only exporting it again can.
This happens most with tools that render text themselves instead of handing it to the system. Server-side image generators, canvas code, chart libraries and some design tools only know the fonts they are given, and they draw the missing glyph instead of searching further. A server is often a stripped-down system with very few fonts installed, which is why an image can look right on your laptop and wrong when the same code runs in production.
Fix it at the source. Choose or embed a font that covers every character in the text, make sure that font file is available where the image is rendered, and export again. For emoji, the renderer also needs a colour emoji font; a text font with the right code points still draws them in monochrome or not at all.
When ordinary letters and numbers turn into boxes
If normal letters and digits show as squares, coverage is not the problem, since every text font has them. Usually a font file is damaged, a font setting points at the wrong font, or a symbol font is being used for ordinary text.
- In a document, check the font of the affected text. A symbol font such as Wingdings or Webdings draws pictures in place of letters, and a font made for a single script may have no Latin letters at all. Set the text in an ordinary font.
- On Windows, restore the default fonts: open Control Panel, then Fonts, then Font settings, and choose Restore default font settings. Restart afterwards.
- On a Mac, open Font Book and choose File, then Restore Standard Fonts.
- If it only happens in a browser, check for an extension or a setting that forces a custom font, and try a private window, which usually runs without extensions.
- If it only happens in one program, update or reinstall that program; it may ship a damaged font of its own.
Tofu is a font problem, not a data problem
This is the reassuring part. If your text shows boxes, the characters are still correct. Copy that text into an application with better font coverage and the symbols appear. Nothing was lost.
It also means the fix belongs in your styling, not in your content. Adding a broad fallback to the end of your font stack means the browser reaches for a font that has the glyph when your preferred font does not. On Windows that is typically the built-in symbol font, on macOS the Apple symbol font, on Android the Noto family and on many Linux systems DejaVu. Naming a couple of those explicitly at the end of the stack is cheap insurance for a page full of symbols.
The variation selector problem, in plain language
Some characters have two legitimate appearances: a monochrome text form and a colourful emoji form. The heavy black heart is the clearest example. Which one you get is decided by an invisible character that can follow it, called a variation selector.
Variation selector 16, code point U+FE0F, requests the emoji presentation. Variation selector 15, U+FE0E, requests the text presentation. Many platforms default one way or the other regardless, which is why a heart pasted from one app arrives red in another and black in a third. If you need one specific appearance, append the selector explicitly and test in the destination.
The same mechanism explains vanishing characters: a variation selector on its own, separated from the character it modified by an unlucky copy, is invisible and does nothing.
Why box-drawing characters look broken even when they render
Box-drawing characters were designed to touch each other edge to edge, which only happens in a monospaced font at the exact cell width they assume. In a proportional font the same characters render fine individually but the lines do not connect, and the result looks like a rendering bug when it is really a font choice.
If you are drawing a frame or a tree in text, set the block in a monospace font and turn off any automatic character substitution. In a browser that means an explicit monospace font stack on the element.
Font fallback is a chain, not a single choice
A browser does not pick one font and give up. It walks your font stack from left to right for each individual character, and it keeps walking past the end of your stack into the system fallback list if nothing you named has a glyph. That per-character behaviour is why a paragraph can render in your chosen font while one symbol inside it quietly comes from somewhere else, at a slightly different weight and width.
It also means a page full of symbols benefits from naming a broad fallback explicitly at the end of the stack rather than leaving it to the system default, which differs by platform and by version. What you gain is not coverage, since the system fallback would have found something anyway, but predictability: you know which font drew the character, so you know why it looks the way it does.
The one place to resist that instinct is the glyph itself on a reference page. Showing a character in the reader's own system font is the honest preview, because that is what they will see after they paste it. Forcing a webfont there would make every symbol look correct on our page and tell the reader nothing about their own machine.
Encoding damage, and why re-saving rarely fixes it
Mojibake happens when bytes encoded one way are decoded another. UTF-8 stores anything outside ASCII as two or more bytes, and a decoder that assumes one byte per character renders each of those bytes as a separate character. A degree sign becomes two characters, a long dash becomes three.
The important part is what happens next. If that mangled text is then saved as UTF-8, the wrong characters are now genuinely in the file, correctly encoded. The damage has been baked in, and re-declaring the encoding afterwards does nothing, because there is no longer anything wrong with the encoding.
Sometimes the mapping is reversible with a careful decode and re-encode, but only when nothing was lost along the way, and something usually was: bytes that did not map to a character in the intermediate encoding get replaced rather than preserved. The reliable fix is to go back to a source that was never decoded incorrectly, fix the declaration there, and export again.
A short checklist when something looks wrong
- Run the render test on the symbol page to see whether your own device has a glyph for the character.
- Confirm the encoding. Serve and save as UTF-8, and declare it in the document head.
- Paste the text into a different application. If it renders there, it is a font problem, not a data problem.
- Check the code point of the character you actually have, not the one you meant to have. In Word, place the cursor after it and press Alt+X. In Sheets, use the UNICODE function.
- For emoji versus text appearance, look for a variation selector before blaming the font.
- For box drawing and ASCII layouts, set a monospace font before concluding anything else is broken.
Frequently asked questions
Why does my PNG turn symbols into a no glyph sign?
The program that rendered the image had no font containing those characters, so it drew the missing glyph and saved it as pixels. Make a font that covers the symbols available where the image is rendered, then export again; changing fonts cannot repair the existing PNG.
Why are many letters and numbers appearing as square boxes or missing-glyph symbols?
That points to a damaged or wrong font rather than a missing character, since every text font has letters and digits. Check that the text is not set in a symbol font, restore the default fonts (on Windows in Control Panel, Fonts, Font settings; on a Mac in Font Book, Restore Standard Fonts), then restart.
What is the missing glyph called?
Font designers call it the .notdef glyph: the shape a font draws for a character it does not contain, usually an empty or crossed rectangle. Users call it tofu, after its resemblance to a block of bean curd.
Does a box mean the character is broken?
No. The character is intact; the font simply has no drawing for it. Copy the text somewhere with wider font coverage and it appears.
What is the difference between tofu and mojibake?
Tofu is an empty rectangle: the right character, no glyph. Mojibake is a run of wrong characters: the bytes were decoded with the wrong encoding. Tofu is cosmetic, mojibake is data damage.
Why does the same heart look black in one app and red in another?
A variation selector, or the absence of one. U+FE0F requests the emoji presentation and U+FE0E requests the plain text one; platforms that see neither pick their own default.
Copy the characters in this guide
Related category hubs
Other guides
- Alt Codes: Full List for Windows 10 and 11
- Mac Special Characters: Every Way to Type Them
- Special Characters in Microsoft Word
- Special Characters in Google Docs
- HTML Entities: Named, Decimal and Hex
Or skip the keystrokes: open the full symbol reference and click any glyph to copy it.