Technology & formats
Your beautiful type is one borrowed laptop from Calibri.
Most slide files don't carry your fonts — they just name them. Open the file where that font isn't installed and the computer quietly picks a stand-in, with different letter widths, and your careful layout rearranges itself.
5 min read
Jul 2026
Every claim sourced · 3 references
You spent an hour getting the type just right: the headline weight, the tracking, the way the subtitle sat under it. Then you present from the client's PC and the whole thing looks subtly generic — because it is now generic. The machine didn't have your font, so it used one it did.
✕ The myth
"The font is saved inside my file."
I used it in the deck, so it must travel with the deck.
✓ The reality
Usually the file just names the font.
Unless you deliberately embed it — and the font permits embedding, and it opens in a compatible app — the other computer supplies its own font or a substitute.1
When the named font is missing, Windows consults a font-substitution table to pick a replacement; with no mapping, the app falls back to a theme default — frequently Calibri.1 Because the substitute's letters are different widths, your line breaks shift, text overruns its box, and vertical spacing drifts. Nothing is "broken" in a way that throws an error — it just quietly stops being your design.
Why "just embed the font" isn't a clean fix
Embedding exists, but it's fenced. It's opt-in, and not every font is embeddable — type designers can flag a font as non-embeddable, and PowerPoint will honour that.2 Embedding also historically behaved differently across Windows and macOS, so a deck that embeds cleanly on one can still substitute on the other. You can make embedding work — choosing "embed all characters," staying on compatible Windows PowerPoint, using embeddable fonts — but that's a checklist to remember under pressure, not a guarantee.
Substitution
A missing font is mapped to a replacement via the OS table, or falls back to the theme font.
1
Not all
Fonts carry an embeddability flag; some refuse to travel inside the file.
2
Widths
Different letter metrics = shifted line breaks and reflowed layout, not just a different look.
⚖ The honest bit — you don't have to abandon custom fonts
Two reliable paths, depending on what you need.
If you must keep editing in the room, embedding can work — do it deliberately (embed all characters, verify on the target OS), or design with genuinely universal fonts so there's nothing to substitute. If you just need it to look right when shown, export to PDF, which bakes the fonts in. The mistake isn't using a beautiful typeface; it's assuming it will follow your .pptx onto a stranger's machine by default. It won't.
Where SyncBy!App fits
SyncBy shows a PDF or images, so whatever type you designed arrives on the screen exactly as drawn — the fonts are already inside the file, nothing to install on the receiving device, nothing to substitute. If your workflow needs live editing with custom fonts, that's a "keep embedding and test it" situation; for showing a finished deck faithfully, a PDF over SyncBy simply removes the question.
TL;DR
- Slide files usually name fonts rather than carry them; a missing font gets substituted.1
- Substitutes have different letter widths, so your layout reflows — silently.1
- Embedding is opt-in and limited: not every font is embeddable, and it varies by OS.2
- Reliable fixes: embed deliberately and test, use universal fonts, or export to PDF.