How to embed fonts in PowerPoint, and why your deck still breaks

A .pptx does not, by default, contain the fonts it uses. It contains their names. When the file opens, PowerPoint looks for a font by that name on that machine, and if it is not installed, it picks a substitute and carries on without asking.

That substitution is rarely a like-for-like swap. The replacement font has different character widths, so a headline that fitted on one line now wraps onto two, a bullet that ended neatly now overflows its placeholder, and vertical rhythm shifts down the slide. This is why "the fonts changed" and "the layout broke" are usually the same event described twice.

Embedding stores a copy of each font inside the .pptx, so the recipient's machine does not need it installed. The setting lives in a slightly odd place, under application options rather than under the file, but it applies to the presentation you currently have open.

1. 1

   Windows: File, then Options

   In the Options dialog, choose Save from the left-hand list.

2. 2

   Find "Preserve fidelity when sharing this presentation"

   It is near the bottom. The dropdown beside it names the presentation the setting applies to, which is the clue that this is per-file.

3. 3

   Tick "Embed fonts in the file"

   Then choose between the two options underneath, which are covered in the next section. They are not equivalent.

4. 4

   Save, and check the file size

   The jump tells you roughly how much font data went in. A few hundred kilobytes is normal for a Latin font. Tens of megabytes means you embedded something very large, usually a CJK family.

5. 5

   Mac: PowerPoint, then Preferences, then Save

   The equivalent checkbox is there. Font embedding on macOS arrived much later than on Windows, so on older Mac builds the option may be absent entirely, and the fix is to update rather than to hunt for it.

Sources: [1] [2]

This is the choice that decides whether your deck survives being edited by someone else, and it is presented as though it were only about file size.

The rule that follows: subset when the deck is finished and going out to be viewed, embed everything when the deck is going out to be worked on. A proposal template that account managers fill in with client names should always embed all characters, because every client name is new text.

Sources: [1] [5]

This message is not a corruption warning and not something to work around. It means one of two things, and Microsoft states both.

1. The font is a type PowerPoint cannot embed at all, such as Adobe PostScript Type 1 or an Apple Advanced Typography font. The advice is to use a different font.
2. The font is a perfectly normal TrueType or OpenType font, but its creator did not grant permission to embed it. Microsoft's wording is blunt: this situation cannot be changed for that font.

The second case surprises people because they own a licence for the font. The permission being refused is not your commercial licence, it is a flag stored inside the font file itself.

Every OpenType font carries an OS/2 table, and inside it a field called fsType that encodes what applications may do with the font when embedding it in a document. The values are defined in the OpenType specification.

So a font set to Restricted refuses outright, and a font set to Preview and Print may embed while leaving the recipient unable to edit. If a deck opens looking correct but the text refuses to be changed, that flag is a likely explanation.

Sources: [3] [4]

This is the part that is almost never mentioned, and it is why people who did everything right still get a call saying the deck looks wrong.

PowerPoint for the web

The browser version renders with fonts available to the browser. Embedded font data in the file does not get installed into the recipient's browser, so a deck opened from a share link can substitute even though the same file opens correctly in the desktop app.

Google Slides

Importing a .pptx into Google Slides does not carry embedded fonts across. Slides maps what it can onto its own font library, which is largely Google Fonts, and substitutes the rest. If your audience opens decks in Slides, embedding buys you nothing and choosing a Google Font buys you everything.

Older PowerPoint file formats

Saving down to the legacy .ppt format changes what can be embedded. If a deck must go to someone on very old software, test it rather than assuming.

The practical consequence is that embedding is a desktop guarantee, not a universal one. A deck that has to look identical everywhere needs a second line of defence.

• Pick a typeface that exists in the destination. If the deck will live in Google Slides, use a Google Font. If it will be opened by strangers on unknown machines, a widely installed family is worth more than a distinctive one.
• Set the fonts at the theme level, so a substitution stays consistent instead of varying slide by slide.
• Export a PDF alongside the .pptx for anyone who only needs to read it. A PDF embeds its fonts as part of the format and will not substitute.
• Test on a machine that has never had your brand font installed. This is the only test that actually proves anything.

Sources: [6] [1]

Microsoft lists embedded fonts alongside images as a main driver of presentation file size, and for some fonts the effect is dramatic. A Latin text family embedded in full might add a few hundred kilobytes. A CJK family covering thousands of glyphs can add tens of megabytes, per font, per weight.

The awkward case is a deck that uses four weights of a family for typographic reasons. Embedding all characters of all four multiplies the cost, and each weight is a separate font file inside the archive.

• Going out to be read, in a Latin script: subset it. Small file, no editing expected.
• Going out to be edited: embed all characters and accept the size.
• Using a CJK or otherwise very large font: subset, and warn recipients not to retype text.
• Deck already too large: fonts are rarely the biggest offender. Compress the images first.

Sources: [5]