The Slide That Falls Apart the Moment You Hit Send
You build a clean deck. The fonts look sharp, the logo sits exactly where you put it, the chart lands on cue. You export it, email it to a client — or worse, present it from someone else's laptop — and it's a different deck entirely. Your custom font has been swapped for Times New Roman. A text box has overflowed its slide. The video on slide 12 is a black rectangle. A bullet list that filled half a slide now spills onto a second one.
You didn't change anything. So why does your PowerPoint look broken on every computer except yours?
The short answer: a `.pptx` file doesn't actually contain your presentation the way you think it does. It contains a set of *instructions* for rebuilding it — and those instructions depend on things the other computer may not have. Here's what's really going on, and the one-step fix that makes your deck look identical everywhere.
What a PPTX File Actually Stores
Like a modern Word `.docx`, a `.pptx` is really a ZIP archive — a folder of compressed XML files describing your slides, plus the images you dropped in. Rename one to `.zip`, unzip it, and you'll find the text, layout, and pictures as separate parts. (Don't do this to a deck you care about, but it's a great way to see the machinery.)
The key word is *describing*. The file says "put this text in Brandon Grotesque at 28pt here," "play this video there," "use the colors from this theme." When you open it, PowerPoint follows those instructions and reconstructs the slides live, using whatever resources are available on that machine.
That works perfectly on your computer, because your computer has everything the instructions reference. On a different one, the rebuild quietly goes wrong.
Why It Breaks on Other Computers
There are four usual suspects, and they stack:
1. The Font Isn't Installed
This is the big one. Fonts are not stored inside a `.pptx` by default — only their *names* are. If you used Montserrat, Gotham, or any font that isn't standard on Windows, and the recipient doesn't have it, PowerPoint substitutes the closest match it can find. Substitute fonts are usually wider or taller, which is exactly why text suddenly overflows its box, wraps onto new lines, and shoves your careful layout out of alignment.
2. Different PowerPoint, Different Rendering
PowerPoint on Mac, PowerPoint on Windows, the web version, Google Slides, and Keynote all interpret the same file slightly differently. Spacing, shadows, gradients, and SmartArt can shift between them. Open a Windows-built deck in Keynote and watch the transitions you spent an hour on simply vanish.
3. Linked (Not Embedded) Media
If you inserted a video or audio clip by *linking* to a file on your hard drive instead of embedding it, the deck only stores the file path. Send the `.pptx` and the media stays behind on your machine — the recipient gets a black box where your video should be.
4. Missing Templates and Theme Files
Corporate decks often rely on a custom template or theme stored locally. Open the file without it and the master slides fall back to defaults, repainting your branded layout in generic PowerPoint blue.
None of this means your file is corrupt. It means PowerPoint is rebuilding it with the wrong parts.
The Fix: Stop Sending a Recipe, Send the Finished Dish
If the recipient needs to *watch or read* your deck — not edit it — don't send PowerPoint at all. Send a PDF.
A PDF isn't a set of instructions; it's a flattened, final render. The fonts are embedded directly in the file, the images are baked in, and the layout is frozen. It looks pixel-identical on a Mac, a Windows laptop, a phone, or a printout — because there's nothing left to rebuild. Convert your deck with PowerPoint to PDF and every problem above disappears at once: no font substitution, no overflowing boxes, no missing template, no "which app are they opening this in" guessing game.
This is the right move for anything where the layout has to stay put: pitch decks sent to investors, slides attached to an email, handouts, leave-behinds, and anything going to someone who might open it on an unknown device. It's also the safest format to present *from* a shared or conference-room computer that may not have your fonts.
When PDF Isn't Enough — and What to Do Instead
PDF freezes everything, which is exactly the point — but it also means you lose animations, transitions, and embedded video. If those matter, you have options:
A Word on File Size
Decks balloon fast — a few high-resolution photos and an embedded video can push a `.pptx` past the 25MB email limit. Converting to PDF usually shrinks it, and if the result is still too big, run it through the PDF compressor to squeeze the embedded images without touching the text. A 60MB pitch deck routinely comes out under 10MB — small enough to attach anywhere. If you've got mixed document types to deal with, the general-purpose PDF converter handles them in one place.
Bottom Line
A `.pptx` file doesn't carry your presentation — it carries directions for rebuilding it, and those directions assume the other computer has your fonts, your media, your template, and the same version of PowerPoint. Change any one of those and your deck rebuilds wrong: swapped fonts, overflowing text, black video boxes, generic theme colors.
When someone just needs to *see* the deck, stop shipping the recipe. Convert it to PDF and send the finished, frozen render — embedded fonts, baked-in images, identical on every screen. Keep the editable `.pptx` for the people who actually need to change it, and reach for PDF to PowerPoint when you need to claw the slides back out. The deck you built becomes the deck they see. Which was the whole point.