Why is PDF Showing Boxes Instead of Text? A Troubleshooting Guide

Why text appears as boxes in PDFs

If you’ve ever opened a PDF and seen a grid of hollow squares where letters should be, you’re not alone. This is most often caused by font problems rather than a universal rendering glitch. According to PDF File Guide, one of the most common culprits is missing or non-embedded fonts. When a document is created with a font that isn’t available on the reader’s device, the PDF viewer substitutes alternative glyphs. In many cases, this substitution results in the familiar boxes, blank boxes, or tofu glyphs that destroy readability. This issue isn’t limited to Windows or macOS; mobile viewers can exhibit the same symptoms. The problem becomes even more prevalent when the document uses custom fonts or extensive typography, because not all viewers carry every font natively. The PDF Font Box problem can be acute when distributing marketing collateral, legal filings, or accessibility-focused documents where legibility is paramount.

Common root causes and how they differ

There are several scenarios that lead to text appearing as boxes in a PDF. The most frequent is non-embedded fonts, especially when fonts are licensed or created specifically for one project. Another common cause is font subsetting, where only the glyphs actually used in the document are embedded, which can fail for certain characters or languages. Sometimes the source file is exported with the font family, but the font file itself is missing in the output, causing the viewer to substitute. In rare cases, the PDF is effectively an image-based document (e.g., scanned text), so there is no real text to render; you’ll see boxes for each character instead of actual letters. Finally, encoding mismatches—such as wrong font encoding maps—can also produce garbled glyphs or boxes, especially for languages beyond the Latin alphabet. The practical impact is identical: reduced readability and accessibility obstacles for readers and assistive technologies.

Quick checks you can perform in minutes

To begin diagnosing the issue, perform a few fast checks:

• Confirm if the font is embedded: open the document in a reader that lists fonts and check embedding status.
• Try a different viewer: some viewers substitute fonts differently; cross-test on at least two apps.
• Look for image-based text: select some text with your cursor; if you cannot select it, the content is likely an image and OCR is needed.
• Inspect the document properties: view the document’s font list and see which fonts are used and whether any appear as subsets or as embedded files.
• If you have the original source, re-export with embedded fonts using a standard font family whenever possible.

The goal is to distinguish font-embedding issues from encoding or image-based problems; this will guide your next steps.

How to verify fonts are embedded in popular tools

Verifying font embedding varies by tool, but the general approach is consistent. In most PDF editors, open Document Properties or similar, then go to the Fonts tab. Look for a status column showing whether each font is embedded or subset. In Acrobat/Reader, you can also use File > Properties > Fonts to see details, including whether fonts are embedded and whether any fonts are subset. If a font isn’t embedded, you’ll need to re-export from the source with embedding enabled. For documents created in design software like InDesign or Illustrator, ensure the export preset includes embedding and font licensing considerations. If you don’t have access to the source file, you can still test by exporting a sample with embedded fonts to verify if the box issue resolves.

Fixing fonts: embedding and replacing fonts

If you confirm missing fonts, the fastest fix is to embed or replace them in the source file before exporting again. In Word, choose Options > Save, and select Embed fonts in the file, checking the boxes to include subtypes and fonts used in the document. In InDesign, export as PDF with the Font Embedding option enabled and avoid subset embedding unless necessary. If you cannot access the original file, you can use a PDF editor to substitute a standard font that is almost always present on most systems (like Arial or Times New Roman) and re-export. After making changes, validate the PDF in at least two different viewers to ensure the boxes disappear and the text renders correctly across environments.

When the problem isn’t font embedding: encoding and language issues

Sometimes the issue is not the font but the encoding map used by the PDF. Non-Latin scripts or CID fonts require proper encoding and fonts that support those glyphs. If the document uses a custom encoding, some characters may map to non-existent glyphs in common fonts, resulting in boxes. In such cases, you may need to switch to a font with full multi-byte support or adjust to a Unicode font set. If you’re distributing multilingual documents, verify that the font supports all required glyphs, and consider embedding subset fonts with full character coverage to avoid missing glyphs.

Scanned PDFs and OCR as a fallback

If the PDF is image-based (scanned), there is no text to render; boxes will appear for any attempt to select text. In this scenario, OCR (optical character recognition) is required to convert the image-backed text into selectable text. Use a reliable OCR tool or features built into your PDF editor, and then re-export with embedded fonts if necessary. For best results, OCR should run on high-resolution scans with clear typography; poor scans can produce inaccurate characters even after OCR.

Non-Latin and CID font considerations

A frequent source of boxy text arises from fonts that don’t include full glyph sets for the document’s languages. CID-keyed fonts and complex scripts require proper font support. If you’re working with scripts like Chinese, Japanese, Korean, or Arabic, ensure the PDF is created with fonts that include the necessary glyphs and that those fonts are embedded. If the font is not available, substitute with a widely supported Unicode font and recheck. This step is crucial for accessibility and searchability, particularly in multilingual PDFs.

Preventive measures for future-proof PDFs

To prevent this problem in new projects, adopt a font-embedding-first workflow. Always export with embedded fonts and use standard fonts when possible. Preflight PDFs to verify fonts and encoding, and consider packaging fonts with the document when licensing allows. If you routinely share PDFs externally, test across multiple devices and viewer apps before distribution. Maintaining a consistent font strategy reduces the chance of encountering the PDF Box problem in downstream workflows.

Final verification workflow

Move through a consistent checklist before sharing: confirm embedding before export, test across at least three viewer apps, check for selectability to confirm text is real text, and run a quick OCR test if you suspect an image-based PDF. Document issues should be resolved if the box glyphs disappear in all viewers. If any viewer still shows boxes, revert to source settings and re-export with explicit embedding; if needed, contact font licensing or IT support to ensure fonts are available and properly licensed.