Word to PDFWhy Your Font Changes When You Convert Word to PDF
Your font changed because the PDF doesn't contain it. A PDF only draws a typeface if a copy is embedded inside the file, or if the font happens to be installed on the machine opening it — when neither is true, the viewer silently substitutes something of similar width. The fix in Word is one checkbox plus using Export rather than Print, and a handful of fonts can never be embedded at all.
How a PDF decides which font to draw
A PDF is not a picture of your document. It stores text along with instructions about which typeface to draw it in, and the viewer resolves that typeface the moment you open the file. There are exactly three outcomes: the font is embedded in the PDF and gets used; it is not embedded but is installed on the reader's machine and gets used; or neither is true, and the viewer picks the closest face it has and redraws your text in that.
Only fourteen fonts are guaranteed by the PDF standard — variants of Helvetica, Times, Courier, Symbol and ZapfDingbats. Everything else, Calibri and Aptos and Arial and Times New Roman included, has to travel inside the file.
That is why this is so easy to miss. You open the PDF on the machine that made it, Calibri is installed there, and it looks perfect. The recipient opens it on a Mac, a phone or a Chromebook with no Calibri, and the substitution happens on their screen, not yours.
Embed the fonts in the Word file
Two different problems get blamed on the same thing. If the .docx itself already looks wrong when someone else opens it in Word, then every PDF made from it will be wrong too, and the fix belongs in the document.
On Windows: File > Options > Save, scroll to Preserve fidelity when sharing this document, and check Embed fonts in the file. On a Mac the same setting is under Word > Settings > Save. The dropdown just above it decides whether the setting applies to the open document or to All New Documents.
Two sub-checkboxes appear underneath, and both defaults work against you:
- Embed only the characters used in the document keeps the file small by embedding a partial font. Anyone who edits the file and types a character you never used gets a substitute for that character. Leave it unchecked for anything that will be edited.
- Do not embed common system fonts is the one that bites hardest, because "common" means common on a Windows PC running Word. Calibri and Aptos are unremarkable there and completely absent on a Mac without Office, on ChromeOS, on Linux, on Android and in Google Docs. If the file will leave the Windows-and-Office world, uncheck it.
Export embeds fonts; Microsoft Print to PDF doesn't
If the Word file looks right and only the PDF is wrong, the export route is the culprit.
File > Export > Create PDF/XPS Document > Create PDF/XPS hands the job to Word's own PDF writer, which can see the document's font resources and writes them into the PDF. It writes subsets, so "Embedded Subset" in a reader's font list is normal and fine. Leave Optimize for on Standard (publishing online and printing) — Minimum size compresses images rather than fonts, but there is no reason to take the quality hit. File > Save As with PDF chosen in the file-type list runs the same writer.
File > Print with Microsoft Print to PDF selected is a different mechanism: a generic Windows print driver receiving a page stream. It exposes no font settings at all — there is no dialog to open — and it is a recurring source of substituted, clipped and overlapping text, with Aptos the current favorite complaint. Use Export instead.
This warning is Windows-specific. On a Mac, File > Print > PDF > Save as PDF goes through macOS's own PDF engine, which embeds fonts, so that route is safe.
Fonts that cannot be embedded, and what to use instead
Embedding is a permission, not a preference. Every TrueType and OpenType font carries an fsType flag set by its foundry with one of four values: Installable, Editable, Print/Preview, or Restricted — no embedding at all. Word and Acrobat both honor it, so a Restricted font gets substituted no matter which boxes you tick.
Format matters too. Microsoft's own guidance is to use OpenType (.otf) or TrueType (.ttf) and avoid PostScript fonts (.pfb, .pfm), which Word cannot embed. OpenType comes in two flavors — TrueType outlines and PostScript/CFF outlines — and the CFF kind frequently fails to embed from Word. That flavor is common on macOS, which is why Mac users run into this more.
When a font won't embed, reach for a metrically compatible replacement, which has identical character widths so nothing reflows:
- Calibri → Carlito
- Cambria → Caladea
- Arial or Helvetica → Arimo
- Times New Roman → Tinos
- Courier New → Cousine
All five are open-licensed, freely embeddable, and ship with LibreOffice and ChromeOS. Aptos, the Microsoft 365 default since 2024, has no widely available metric twin and is missing from Office 2021, Office 2019, LibreOffice and Google Docs — embed it, or set the document in something older. For a licensed corporate face flagged Restricted, the only legitimate fix is a document-embedding license from the foundry.
A substituted font changes your page count
Substitution is not only cosmetic. A typeface defines the advance width of every character, so a different face makes every line a slightly different length. Lines break in new places, a paragraph gains a line, a heading set to keep with next slides onto the following page, and a two-page document arrives as three.
The knock-on effects are the ones that cause arguments: table rows re-wrap and change height, a table of contents keeps the page numbers it had when you last updated it, and cross-references point at the wrong page. If your PDF gained pages or shifted blocks, see why layout shifts when converting Word to PDF and blank pages in the PDF.
This is the entire point of metric compatibility. Carlito's letters are not Calibri's letters, but the widths match exactly, so the same document breaks its lines in the same places either way.
What our converter does, and when to use Word instead
Plain disclosure: the Word to PDF converter on this site typesets with DejaVu Sans and embeds it. It does not reproduce your typeface. Calibri, Aptos, Garamond and a licensed corporate face all come out as DejaVu Sans — right sizes, weights, colors, indents and lists, wrong letterforms.
When the exact typeface matters — a brand template, a filing with a required font, a typeset manuscript, anything a designer will look at — use File > Export > Create PDF/XPS in Word. That is the right tool, and we would rather say so here than have you discover it after sending the file.
What the trade-off buys is predictability. The font is always embedded, so the PDF is self-contained and renders identically everywhere, with no substitution step left to go wrong. DejaVu Sans covers Latin, Cyrillic and Greek, so Polish, Czech, Turkish, Ukrainian, Russian and Greek text — and every accented name — survives intact instead of turning into boxes, which is exactly what a partially embedded font produces. Chinese, Japanese, Korean, Thai and Devanagari are not covered, and the tool raises an explicit error rather than handing you a page of empty rectangles. It all runs in your browser, with nothing uploaded, and works without Office installed.
Check what a finished PDF actually embedded
Don't guess. Open the PDF and go to File > Properties (Ctrl+D on Windows, Cmd+D on a Mac), then click the Fonts tab. Acrobat Reader lists every font the file references.
Read it like this. A font marked Embedded or Embedded Subset travels with the file and is safe anywhere. A font with no such label is being supplied by your machine and will be substituted on someone else's. And if a name in that list isn't one you chose — Helvetica or Arial where you set Calibri — the substitution already happened during export, and you need to fix the export, not the reader.
The cheapest real-world test is to open the PDF on your phone. It has essentially none of your desktop fonts installed, so whatever still looks right there is genuinely embedded.