You create a document in Word that uses special characters, accented letters, or non-Latin glyphs. On your screen, every character looks correct. When you export the document to PDF, some glyphs appear different or become missing. This mismatch between on-screen display and PDF output often happens because of font embedding rules, font substitution, and rendering engine differences. This article explains why Word renders specific glyphs differently during PDF export compared to display and shows you how to prevent the problem.
Key Takeaways: Why Glyphs Change in PDF Export
- File > Options > Save > Embed fonts in the file: Forces Word to include font data so the PDF renderer uses the original glyphs.
- Font substitution by the PDF engine: Word uses its own text engine for display; the PDF engine (e.g., Microsoft Print to PDF) may substitute missing or unlicensed fonts with a fallback.
- OpenType vs TrueType glyph encoding: Some advanced OpenType features (ligatures, stylistic sets) are lost during PDF generation if the target font is not fully embedded.
Why Word and the PDF Engine Use Different Glyph Rendering
Word displays text using its own layout engine, which reads the font file directly from your system. When you export to PDF, the process is handled by a separate component — usually the Microsoft Print to PDF driver, the Save As PDF feature, or a third-party PDF add-in. Each component has a different approach to handling font data.
The core issue is font availability. Word can display a glyph because the font is installed on your computer. The PDF engine, however, must either embed the font into the PDF file or substitute it with another font. If the font license forbids embedding, the PDF engine replaces the font with a fallback. That fallback often lacks the specific glyph you used, resulting in a different character or a blank box.
A second factor is glyph mapping. OpenType fonts can contain multiple glyphs for the same character — for example, stylistic alternates or ligatures. Word may display the default glyph, while the PDF engine, during conversion, applies a different substitution rule. This mismatch is most common with fonts that include advanced typographic features like contextual alternates or swashes.
Font Embedding Restrictions
Fonts are licensed either as installable (can be embedded), editable (can be embedded for editing), print/preview (can be embedded for viewing only), or restricted (cannot be embedded). When you use a restricted font, the PDF engine cannot include the font data. It must substitute the entire font with a system fallback like Times New Roman or Arial. That fallback font will not contain your original glyphs.
PDF Generation Method Differences
The built-in File > Export > Create PDF/XPS command uses a different engine than File > Print > Microsoft Print to PDF. The Export method typically embeds fonts more aggressively than the Print method. However, both methods rely on the font’s embedding permissions. If the font is marked as print/preview only, the Export method may still embed a subset for on-screen viewing, while the Print method may not embed anything at all.
Steps to Ensure Glyphs Are Rendered Correctly in PDF Export
Method 1: Embed Fonts in the Word File
- Open File > Options > Save
In the Word Options dialog, locate the section labeled Preserve fidelity when sharing this document. - Check the checkbox for Embed fonts in the file
Select Embed fonts in the file. For most documents, leave Do not embed common system fonts unchecked to ensure all glyphs are included. - Save and close the document
Close the Options dialog and save your document. The font data is now stored inside the .docx file. - Export to PDF using File > Export > Create PDF/XPS
Use the Export method rather than Print. Click Options in the PDF export dialog and confirm that ISO 19005-1 compliant (PDF/A) is unchecked. PDF/A mode can strip fonts that are not fully licensed for archival embedding.
Method 2: Use a Font Without Embedding Restrictions
- Identify the font you are currently using
Select a glyph that renders incorrectly in the PDF. Note the font name from the Home tab Font group. - Check the font embedding license
Right-click the font file in C:\Windows\Fonts and choose Properties. On the Details tab, look for Font embeddability. If it says Restricted or Print/Preview, consider switching to a font with Installable or Editable embedding. - Replace the font in the document
Select all text (Ctrl+A) and change the font to one with unrestricted embedding, such as Calibri, Arial, or Times New Roman. If you must keep the original font for branding, purchase a license that allows embedding.
Method 3: Convert Glyphs to Images
- Insert the glyph as a picture instead of text
Type the glyph in a separate application (like Character Map or a graphics editor). Take a screenshot or save the glyph as a transparent PNG. - Insert the image into Word
Use Insert > Pictures to place the glyph image at the correct size. Anchor it to the text line using the In Line with Text wrapping style. - Export to PDF
The glyph is now a raster image and will not change regardless of font embedding.
If Glyphs Still Differ After the Main Fix
Word Shows a Glyph but the PDF Shows a Blank Box
A blank box or a question mark indicates that the PDF engine could not find any glyph for that character code in the substituted font. Verify that the font is embedded by opening the PDF in Adobe Acrobat Reader and going to File > Properties > Fonts. If the font is listed as embedded subset, the glyph should be present. If it says no embedding, repeat Method 1 and ensure the font license allows embedding.
PDF Shows a Different Glyph Altogether
A glyph that changes to a different character — for example, a fi ligature turning into two separate letters — usually results from OpenType feature loss. Word applies OpenType features during display, but the PDF generator may not carry them over. To force basic glyphs, select the text and go to Font > Advanced > OpenType Features and set Ligatures to None. Then re-export the PDF.
Glyph Looks Correct in One PDF Viewer but Not Another
PDF viewers have their own font fallback logic. Adobe Acrobat Reader uses its own font pack for missing glyphs, while a browser PDF viewer uses system fonts. If the glyph is correct in Acrobat but wrong in Chrome, the font is partially embedded. Use File > Options > Save and check Embed fonts in the file. Also uncheck Do not embed common system fonts to include every character.
Word Display vs PDF Export: Glyph Rendering Comparison
| Item | Word Display | PDF Export |
|---|---|---|
| Font engine | DirectWrite (Windows 10/11) or GDI (older versions) | Microsoft Print PDF driver or Save As PDF module |
| Font availability | Always uses the installed font | Uses embedded font or substitutes with a fallback |
| OpenType features | Applies ligatures, alternates, and stylistic sets | Often strips advanced OpenType features unless the font is fully embedded |
| Embedding license check | Not performed | Honors font embedding permissions; may refuse to embed restricted fonts |
| Rendering resolution | Screen resolution (96-192 DPI) | Vector resolution (can be very high) |
| Substitution behavior | No substitution for installed fonts | Replaces missing or unembedable fonts with system fallback |
The difference in rendering engines is the primary reason glyphs change. Word uses DirectWrite, which has full access to the font file and its OpenType tables. The PDF generator uses a separate code path that may not read all OpenType tables or may skip glyphs that are not part of the basic character set.
To summarize the comparison: Word display gives you the full fidelity of the font because it reads the font directly from your hard drive. PDF export is constrained by font embedding licenses, OpenType feature support, and the fallback logic of the PDF engine. When you need pixel-perfect glyphs in PDF, embed the font with unrestricted licensing and disable advanced OpenType features that the PDF engine may not preserve.
You can now diagnose and fix glyph rendering differences between Word display and PDF export by embedding fonts, switching to an installable font, or converting glyphs to images. Next time you create a document with special characters, set File > Options > Save > Embed fonts in the file before exporting. For documents that require exact glyph reproduction, test the PDF in multiple viewers and use a font such as Calibri or Arial that has no embedding restrictions.