You spent an hour selecting the perfect fonts for your Word document. The headings are set in a clean sans-serif. The body text is a readable serif. The captions use a distinctive condensed typeface. You export to PDF, open the result, and your carefully chosen fonts have been replaced. The headings are now in Calibri. The body text is Times New Roman. The captions look nothing like what you designed. The PDF converted your font choices into generic substitutes, and the document looks like a draft instead of a finished piece.
Font fidelity during Word to PDF conversion is controlled by a single setting: font embedding. When fonts are embedded, the PDF carries a copy of every character shape used in the document. When fonts are not embedded, the PDF references the font by name and depends on the viewer's operating system to supply a matching font. If the viewer does not have the font installed, it substitutes the closest available match. This substitution is why your document looks different on someone else's computer than it did on yours.
Why Font Embedding Is Not Always Automatic
Word does not embed all fonts by default for two reasons. First, file size. Embedded fonts add the font data to the PDF, which can increase file size significantly for large font families with many character variants. A document using a full OpenType font with thousands of glyphs might add 2 to 5 MB of embedded font data to the PDF. Second, licensing restrictions. Some commercial fonts have embedding restrictions in their licenses that prevent the font data from being included in a PDF. Word respects these licensing flags and will not embed a font that its license prohibits from embedding.
You can check whether a font allows embedding by looking at its properties. In Windows, open the Fonts folder in Control Panel, right-click the font file, and select Properties. Look for the Font Embeddability field. If it says "Installable" or "Editable," the font can be embedded in a PDF without restriction. If it says "Preview/Print" or "Restricted," Word will not embed it. If it says anything else, Word may embed only a subset of the characters actually used in the document, which is usually sufficient but may cause problems if someone tries to edit the PDF text later.
How to Force Font Embedding in the Word-to-PDF Export Settings
In Microsoft Word, the font embedding setting is buried in the PDF export options. Go to File, Save As, and choose PDF from the file type dropdown. Before clicking Save, click the Options button. In the Options dialog, under the section "Include non-printing information," check the box labeled "ISO 19005-1 compliant (PDF/A)." This forces Word to embed all fonts used in the document. PDF/A compliance requires font embedding, so selecting this option guarantees that every font character is included in the output file.
There is a trade-off. PDF/A compliance also disables some interactive features like JavaScript and external hyperlinks. If your document relies on those features, do not use the PDF/A option. Instead, rely on the default font embedding behavior, which embeds TrueType and OpenType fonts when their licensing permits, and manually check that any custom fonts you purchased or downloaded are embedding-compatible before designing your document around them. A font that cannot be embedded should not be the primary typeface in a document destined for PDF distribution. Choose an embeddable alternative.
Verifying That Fonts Survived the Export
After exporting to PDF, open the file and verify the fonts. In Adobe Acrobat, go to File, Properties, and select the Fonts tab. The list shows every font referenced in the document. Next to each font name, look for the text "Embedded" or "Embedded Subset." "Embedded" means the full font is included. "Embedded Subset" means only the characters actually used in the document are included, which is usually sufficient. If a font shows neither label, it is not embedded. The PDF is referencing it by name and depending on the viewer to supply it. This is the font that will be substituted on computers that do not have it installed.
The Fonts tab also shows the encoding of each font. If a font shows a custom encoding rather than Identity-H, the font may not display correctly on all systems. Identity-H is the standard encoding for modern PDFs and indicates that the font uses standard Unicode character mapping. Custom encodings can cause characters to appear as different glyphs on different systems because the mapping between character codes and glyphs is not standardized.
In WukongPDF's PDF Export tool, the font embedding verification is built into the export preview. After uploading a Word document and converting it, the preview shows a font report listing every font in the output and its embedding status. Fonts flagged as not embedded can be addressed before finalizing the export by adjusting the conversion settings or replacing the problematic fonts in the source document.
Using Standard Fonts as a Universal Compatibility Strategy
The surest way to avoid font problems in PDFs is to use fonts that are installed on virtually every computer. The PDF base 14 fonts are guaranteed to be available in every PDF viewer: Times New Roman, Helvetica, Courier, and Symbol in their regular, bold, italic, and bold-italic variants. A document set entirely in these fonts will display identically on every device with no font embedding required. The trade-off is limited typographic variety. These are workhorse fonts, not design-forward choices, but for documents where reliable rendering matters more than visual distinction, they are the safest option available.
For documents that need more typographic personality, choose fonts from the Google Fonts library. Google Fonts are open-source and have no embedding restrictions. They can be freely embedded in any PDF. A document designed with Google Fonts like Open Sans, Lora, or Montserrat can be exported with full font embedding, guaranteeing consistent rendering while offering far more design flexibility than the base 14. The PDF Fonts you choose define the document's visual identity. Choosing embeddable fonts ensures that identity survives the journey from your computer to every recipient.
A practical troubleshooting step when a specific font refuses to embed: open the Fonts folder in Windows Control Panel or the Font Book app on Mac, find the problematic font, and check its properties. Some fonts carry a "Preview/Print" embedding flag set by the font designer. This flag tells applications that the font can be used for screen display and printing on the creator's machine, but cannot be embedded in a document for distribution. If a font has this flag and you need it in a PDF, you have three options. Contact the font foundry for a license that permits embedding, typically a commercial desktop license rather than a personal-use license. Substitute an embeddable font that is visually similar, like using Adobe Garamond Pro instead of a restricted Garamond variant. Or convert the text using that font to outlines in a vector editing program, which bakes the letter shapes into the PDF as paths rather than as text, preserving the visual appearance at the cost of making the text unsearchable and unselectable. The outline conversion path is appropriate for logos and short headings. It is not practical for body text because it makes the text inaccessible to search and screen readers.