Embedding Fonts When Exporting Word to PDF

A Word PDF does not look the same on another computer unless the fonts travel with the file. Word's own export is the path that embeds fonts. The browser Word to PDF tool extracts text and sets it in Helvetica, so it is the wrong export when the typeface has to travel with the file. If the font is missing, the viewer substitutes another, and line breaks move. Turn on embedding, prefer a subset of the characters you used, export to PDF, and check the Fonts tab on a machine that does not have the typeface installed.

The contract can look right on the author's laptop. The client opens it and the headings are in Times, the body that was Calibri has shifted, and the signature block sits alone on page two. Word reported a successful export. The fonts were not in the file.

Why embedding matters

A PDF viewer paints text from:

1. Embedded font data, which matches the layout you exported
2. A local substitute, whose metrics differ
3. A missing-glyph box, when the substitute has no character for that code point

Multilingual PDF Fonts is where this fails hardest, because a substitute Latin font will not cover the script.

Word settings on Windows

1. File, Options, Save
2. Check Embed fonts in the file
3. Prefer Embed only characters used. The file stays smaller
4. Leave "Do not embed common system fonts" checked unless you accept the risk on an unusual face
5. File, Save As, PDF
6. In Options, choose ISO 19005-1 (PDF/A) if the archive requires it

Word on a Mac

Export with Save as PDF and Best for printing. Check the Fonts tab in Acrobat. The Mac labels differ. Do not assume the font was embedded because the export finished.

Third-party converters

Export a test file from the same Word path you will use in production. The browser Word to PDF tool is a different path, and it does not embed fonts. A company workflow should pick one export path and keep using it.

Licenses

Microsoft Office fonts can generally be embedded for a PDF you send to someone. A desktop font from a foundry needs an EULA check. An Adobe Fonts face that depends on an active subscription needs a look at the sync license.

A custom brand font needs an embeddable package for Office or for the web, obtained on purpose.

Bold and italic are separate files

Faux bold, which thickens the regular face in software, may not embed the way a real Font-Bold file does. Install the whole family.

What the failure looks like

| Symptom | Fix | | --- | --- | | Boxes where letters should be | Embed the font, and use a Unicode face that has the characters | | Line breaks get wider | A substitute font has different metrics | | Header or footer drifts | Export to PDF. Do not rely on a print driver | | The file is huge | Subset the embed, and compress images separately | | Form fields sit in the wrong place | Fillable vs Flat |

Check the export

1. Acrobat Properties, Fonts: every face says Embedded Subset
2. Open the PDF on a VM or a colleague's PC that does not have the Office fonts
3. Print one page. Printable PDF Margins covers the margin check
4. Open it in a mobile reader once

Compression after export

Compress PDF should not strip fonts. After an aggressive compress, open the Fonts tab again.

Student work and legal filings

Student Assignment PDF and Legal Page Numbering both assume the typeface survives the export. A substituted font is what makes the submission look unfinished.

LibreOffice on Linux

LibreOffice embeds fonts on PDF export differently from Word. Teams that export headless on Linux CI should still open the Fonts tab. The substitution list in LibreOffice options is the same class of problem as Word's.

Word Online

Word Online's PDF export may omit fonts that desktop Word would embed. For a document a client will rely on, finish the export on the desktop.

PDF/A

An archive submission may require PDF/A-1b or PDF/A-2u. Font embedding is mandatory there, and RGB may need a conversion. A validator such as veraPDF catches a font that was not embedded, before the submission is rejected.

Example: check subsets before you send a contract

1. In Word on Windows, turn on File, Options, Save, Embed fonts in the file. Also check Embed only the characters used in the document. A 4 MB font family then adds about 45 KB to the PDF.
2. Export with File, Save As, PDF, using Standard (publishing online and printing).
3. Open the PDF in Adobe Acrobat Reader. Press Ctrl+D (Cmd+D on a Mac) and open the Fonts tab.
4. Every font should say (Embedded Subset) next to its name. If a line says Actual Font: ArialMT under your brand font's name, that face had an embedding restriction and Word substituted on export.

What embedding cannot override

Even with Word set to embed fonts, a commercial desktop font whose fsType bits say "No Embedding" or "Preview & Print" may refuse to embed, or it may lock the PDF into read-only. Use an open-license family, such as a Google Font, or a standard system face, when the recipient has to annotate the file.

Word's on-screen preview is the layout on that PC. The Fonts tab on a computer that does not have the face is the check. Embedded Subset beside every name is what you want. Otherwise the other reviewer gets the Calibri drift.