Nobody Told Me PowerPoint Fonts Were a Thing. Then I Was Replacing Them at 11pm.

I was finishing a client deck. Late. The kind of late where you have already convinced yourself it is done three times. I opened the file in PowerPoint to do a final check before sending it, and the headline font was wrong. Not slightly off. Completely wrong. A clean, modern geometric typeface had turned into something that looked like a default office memo from 2003.

I had built the deck in Canva. I exported it as a PPTX. I sent it to a client whose machine did not have the font installed. PowerPoint looked at the file, could not find the font, and silently replaced it with something it did have. No warning. No prompt. Just gone.

That was the night I learned that font rendering is a thing. And that when you are working across multiple platforms, it is one of the most quietly destructive problems you will face.

Why PowerPoint Font Substitution Happens (And Why It Is Silent)

Tools like Canva and Gamma are browser-based. They live on the web and they use web fonts, which are fonts served from the cloud when you are viewing something in a browser. When you export a presentation from one of these tools as a PPTX file, the font references travel with the file. But the actual font files do not, unless the tool specifically embeds them, and many do not by default.

PowerPoint is a local application. When it opens that PPTX file, it looks for the fonts on the machine it is running on. If the font is not installed there, it substitutes. It does not ask. It does not warn you when opening. It just picks something from what is available, and the logic it uses to make that choice is not always what you would choose yourself.

The problem gets worse the more tools touch the file. Canva to PPTX. PPTX to a client on Windows when you designed it on a Mac. Windows to a projector in a conference room running an older version of PowerPoint. Every handoff is a potential substitution event. By the time someone is clicking through slides in a room full of stakeholders, the deck can look like a completely different document than the one you built.

Why This Keeps Getting Worse as Our Workflows Get Better

Here is the irony. The tools that make us faster, the AI-assisted design platforms, the rapid deck builders, the browser-based creative suites, are also the tools most likely to introduce this problem. They are optimized for speed and visual output on screen. They are not always optimized for what happens after you hit export.

In a traditional workflow where everything starts and ends in PowerPoint, this is rarely an issue. But when your deck starts in Gamma, gets refined in Canva, gets exported to PPTX, and then gets opened on three different machines before it reaches a client, you have introduced multiple points where fonts can break that most people do not even know to look for.

This is not a knock on those tools. It is a reality of working across platforms, and it is one that the industry is only beginning to talk about honestly.

How to Stop PowerPoint Font Substitution Before It Happens

One quick caveat before we get into it: if both you and your client are on Microsoft 365 with a live internet connection, cloud fonts can auto-resolve some substitution events in the background. That is genuinely useful, but it is a dependency you cannot always control, especially for offline viewing, projectors, or anyone on an older version of Office. So the habits below still matter.

A few things that have saved me since that late night:

• If the final stop is PowerPoint, start in PowerPoint. I use Gamma and Canva for rapid concepting and client review. But if I know the deliverable needs to live in PPTX long-term, I either build natively or I plan a rebuild phase that accounts for font translation.

• Embed fonts when you export. On Windows: File > Options > Save. On Mac: PowerPoint > Preferences > Save. Note that font embedding on Mac was only added in 2021, so if you or your client is on an older version, it will not be available. It adds file size, but it protects your design from substitution on other machines. If you are sending a final deck to a client, this should always be on.

• Stick to system fonts for anything that will move around. Fonts like Arial, Helvetica, Georgia, and Times New Roman are installed on virtually every machine regardless of operating system or whether Office is present. If a deck needs to be opened reliably across different environments, using one of these in your final version eliminates the substitution risk entirely.

• Always open the PPTX export on a fresh machine before sending it. Not the machine you built it on, which likely has the font installed. A different machine, ideally one that does not have your creative tools. That is the machine that shows you what the client will see.

The Bigger Point

We are in a moment where the tools available to create faster, more polished work are genuinely remarkable. I use them every day and I believe in them. But speed without awareness of the handoff creates its own category of problems. Problems that used to happen in print shops now happen quietly, in the background, on someone else's screen.

Font rendering is a small thing until it is not. Until it is 11pm and you are looking at a deck that no longer looks like yours.

That is what this series is about. The things nobody tells you until you are already in the room when they go wrong.

This is Part 1 of Warning Lights, a Signal series on what happens to your work when it passes through Microsoft as the final stop.

Coming up: Color shift. Why your deck looks perfect on screen and prints muddy. Why RGB and CMYK are not the same thing and why it matters more than people think.