When you share a Microsoft Word document that uses bespoke, commercial, or third-party fonts with clients or colleagues, Word on their computer may automatically substitute a generic system font—such as Calibri or Arial—if the original typeface is not installed on their operating system. This font substitution frequently breaks line wraps, causes table text to spill over margins, and alters the carefully curated design of your report or resume. To ensure that your document renders with complete visual fidelity on any recipient’s computer, you can embed TrueType and OpenType fonts directly into the Word file.
Font Embedding Requirements and Licence Constraints
Before embedding fonts into a Word document, consider the following technical specifications and licensing parameters:
- Font Format: Word supports embedding for TrueType (
.ttf) and OpenType (.otf) font files. Older PostScript Type 1 fonts cannot be embedded. - Embedding Licences: Digital typefaces contain built-in metadata flags defined by the font foundry that govern embedding rights. Word adheres strictly to these DRM flags:
- Installable: The font can be embedded and permanently installed on the recipient’s computer.
- Editable: The recipient can view the document and edit its contents using the embedded font.
- Preview / Print: The recipient can view and print the document in the embedded font, but opening it for editing will prompt a font substitution.
- Restricted (No Embedding): Word will display an error message and refuse to save the document if embedding is attempted for this font.
- Operating System Support: Full font embedding controls are natively supported in Microsoft Word for Windows. Word for Mac supports opening and viewing documents with embedded fonts, but creating and saving documents with embedded fonts has historical limitations on macOS.
How to Enable Font Embedding in Microsoft Word (Windows)
Font embedding is configured per document within Word’s advanced application options:
- Open your document in Microsoft Word on Windows.
- Click the File tab in the top-left corner of the Ribbon, then select Options at the bottom of the navigation bar.
- In the Word Options dialogue box, click Save in the left-hand menu.
- Scroll down to the bottom section labelled Preserve fidelity when sharing this document.
- Ensure the dropdown menu displays your current document rather than “All New Documents”.
- Tick the checkbox for Embed fonts in the file.
Optimising Embedded Font File Size
Embedding every glyph, symbol, and weight of an elaborate typographic family can substantially increase your Word document’s file size. To minimise file bloat, Word provides two granular sub-options under the embedding setting:
- Embed only the characters used in the document (best for reducing file size): When enabled, Word embeds only the specific letters, numbers, and symbols that actually appear in your text. This reduces the added file size from several megabytes down to a few kilobytes. However, if the recipient edits the file and types characters that were not previously present, those new characters will fall back to a default system font.
- Do not embed common system fonts: Ticking this box ensures that standard fonts present on virtually all Windows installations (such as Times New Roman, Arial, Georgia, and Segoe UI) are excluded from embedding, saving significant storage space.
For documents that recipients only need to read or print—such as contracts, brochures, or portfolios—tick both sub-options for the leanest possible file size. If recipients need to edit and expand the document extensively, leave Embed only the characters used in the document unticked.
Verifying Font Embedding Success
To confirm that your custom fonts have embedded properly before dispatching the document:
- Click OK in the Word Options dialogue to apply the changes.
- Save the document (Ctrl + S).
- If Word encounters a font whose foundry licence prohibits embedding, a warning dialogue will identify the restricted typeface. You must either substitute that font with an embedding-compliant alternative or export the document as a high-resolution PDF instead.
- Inspect the saved file properties in Windows File Explorer: a modest increase in file size confirms that the font data has been successfully packaged into the
.docxcontainer.