Why Your PowerPoint Fonts Changed on Another Computer (and the Permanent Fix)

By the Kinsy team · Published 25 July 2026

The deck was perfect when you saved it. Then it went to a client, a colleague, or the boardroom PC — and came back wearing a different typeface, with headlines wrapped onto new lines and text spilling out of its boxes. Nothing is corrupted and nobody touched your slides. Here is what actually happened, and the setting that stops it happening again.

Why did my PowerPoint fonts change on another computer?

Because the font you designed with isn't installed on that computer and wasn't embedded in the file, so PowerPoint silently substituted the closest font it had. A .pptx file doesn't normally carry fonts — it carries font names. When the file opens, PowerPoint looks each name up in the machine's installed fonts, and if a name isn't there it swaps in a stand-in: usually Calibri, Arial, or Aptos, Microsoft's default typeface since early 2024. There is no error dialog and no obvious warning. The slides simply render in the wrong type.

The substitution is also temporary, which is what makes it so confusing to debug. The text is still tagged with the original font name inside the file, so when the deck comes back to your machine it looks correct again. "It works on my computer" is literally true — the file only breaks on machines missing the font, which is to say, on most machines that aren't yours.

One missing font reflows the entire deck

Font substitution sounds cosmetic. It isn't, because no two typefaces measure text the same way. Character widths, x-height, and line spacing all differ between the font you chose and the font PowerPoint substituted — so every paragraph gets re-measured, and the layout your deck was built on quietly dissolves. A title that fitted on one line wraps onto two and pushes everything below it. A bullet that filled its box now overflows it, or triggers autofit and shrinks the text. Two columns that lined up drift apart. None of this is flagged anywhere; the deck just looks subtly — or unsubtly — wrong, and the person presenting it usually finds out live.

The permanent fix: embed the fonts in the file

PowerPoint can package the actual font data inside the .pptx, so any machine that opens the file has the typeface whether it is installed or not. It is one checkbox, and it is off by default. Here is the full routine:

1. Open the deck on the machine where it looks right. Embedding copies fonts from the computer doing the saving, so do this where the correct fonts are installed.
2. Find the embedding setting. On Windows: File → Options → Save, then look for the "Preserve fidelity when sharing this presentation" section. On a Mac: the PowerPoint menu → Preferences → Save.
3. Tick "Embed fonts in the file". This is the whole fix — the two radio buttons beneath it just decide how much font data travels.
4. Choose how much to embed. "Embed all characters" is the safe choice if anyone else will edit the deck — they can type new text in your typeface. "Embed only the characters used in the presentation" keeps the file smaller, but recipients who edit may see substitutes on any character you didn't happen to use.
5. Save — as .pptx. The font data is written into the file at save time, not when you tick the box. Avoid saving back to the legacy .ppt format, which can drop embedded fonts on the way through.
6. Verify on a machine that doesn't have the font. Open the file somewhere your design fonts were never installed and compare line breaks against the original. If nothing moved, the embedding worked.

If you've received a deck that is already substituted, there are two rescues. The clean one: install the original font, then reopen the file — the text is still tagged with the right name, so it snaps back. The pragmatic one: use Replace Fonts (Home → Replace → Replace Fonts on Windows; Edit → Find → Replace Fonts on a Mac) to swap the missing typeface for one every machine has, then fix the layout once, deliberately, instead of letting PowerPoint improvise.

The gotchas

Mac embedding is newer than you'd think

For years PowerPoint for Mac simply couldn't embed fonts. Support arrived with PowerPoint 2019 (version 16.17) and Microsoft 365; anything older on a Mac will neither embed fonts nor reliably honour the ones embedded elsewhere — it substitutes as if they weren't there. Two font formats are also unembeddable on any platform: old Adobe PostScript Type 1 faces and Apple Advanced Typography fonts. If your brand typeface is one of those, convert it or change it.

Some fonts refuse to be embedded

Every font file carries an embedding permission set by its foundry, and PowerPoint obeys it. A licence-restricted font is quietly skipped at save time — at best you get a terse notice that "some of your fonts can't be saved with the presentation", at worst nothing at all, and the deck still breaks on the next machine. Microsoft's own fonts are all embeddable, as are the Microsoft 365 cloud fonts, which have a second advantage: on any machine running Microsoft 365 they download automatically when the file opens. Fonts bought from independent foundries are the ones to check before you build a 40-slide deck on them.

PowerPoint for the web doesn't play along

You can't switch embedding on from PowerPoint in a browser — it's a desktop-only setting on both platforms. Worse, the web app renders with its own limited font set, so a deck with correctly embedded fonts can still display with substitutes in the browser while the underlying file remains intact. Judge fidelity in desktop PowerPoint, not in a tab.

Embedding costs file size

"Embed all characters" for a full family — regular, bold, italic, bold italic — can add several megabytes per typeface. For a deck that travels by email, that's usually a price worth paying; for a deck with four display fonts, it's a reason to use fewer fonts, which was probably good advice anyway.

Habits that keep your fonts yours

Menu paths and behaviour checked against Microsoft's documentation and current desktop builds, July 2026 — Microsoft does move these settings occasionally.

Why AI presentation tools make this worse

Most AI deck generators are web apps, and they design the way web apps do — with web fonts served by the browser. Those typefaces are often lovely and almost never installed on anyone's PowerPoint machine. When such a tool exports a .pptx, it typically writes the font name into the file and stops there — so every recipient, everywhere, opens the substituted version. The deck you approved on screen never existed as a file. This isn't a rare edge case; it's one of the two big export failure modes we refereed in Gamma vs Canva, where geometry survives but the typography silently doesn't.

So if an AI tool is making your decks, demand three things before trusting it with anything that leaves your laptop: the export embeds its fonts, so the type survives on any machine; the preview matches the downloaded file to the line break; and every text element stays editable rather than arriving as a picture. Disclosure: we build Kinsy, an AI presentation maker, so we're biased — but those three are exactly what Kinsy guarantees, and each one can be tested from the outside in minutes. The full test method is in our guide to the anatomy of a broken PowerPoint export, and if you're comparing tools on this axis, start with what an AI presentation maker with genuinely editable .pptx output should promise.

Keep reading

• Why every AI deck tool breaks on export (and how Kinsy doesn't)
• AI presentation makers that export truly editable PowerPoint files
• Gamma vs Canva for presentations: an honest comparison