A client once forwarded me a PDF with a single line: "Is this the final version? The chart looks weird." It was the final version. The chart wasn't weird on my end — it was crisp, vector, perfectly aligned. On theirs, the axis labels had gone soft and the gridlines looked like they'd been photocopied twice. Same file. Same export button. Different result on a different machine, because of a setting neither of us had touched in months.

That's the part people usually get wrong about PDF quality loss: they assume it happens at the export step, so they go looking for a "high quality" toggle in the export dialog and call it fixed. Sometimes that toggle exists. Sometimes the damage already happened three steps earlier, when the file was saved, and no export setting can undo it.

The compression that runs before you ever click "Export"

PowerPoint compresses images by default the moment you save a file — not when you export to PDF. Go to File → Options → Advanced and you'll find a setting called "Default resolution," usually sitting on something like 220 ppi unless someone changed it. Every picture you've pasted into the deck gets silently downsampled to that resolution on save, whether or not you ever intended to print it or blow it up on a screen. By the time you hit "Export to PDF," the low-resolution version is already the only version that exists in the file.

Keynote handles this differently — it keeps the original image data longer — but Keynote's own PDF export dialog has a quality slider that defaults to something short of "Best" on many versions, which does the same downsampling at the export stage instead of the save stage. Different mechanism, same outcome: the export dialog isn't lying to you when it says "PDF," it's just not telling you which resolution decision already happened upstream.

The fix is checking both places, not one. In PowerPoint, set Default resolution to "High fidelity" before you start pasting in screenshots and charts, not after. In Keynote, pull the export quality slider to "Best" and accept the larger file size — a report that's supposed to look sharp on a 27-inch monitor isn't the place to save two megabytes.

Vector charts that quietly become bitmaps

Here's the one that catches people who already know about image compression and think they're covered. A chart built natively in PowerPoint or Keynote — bars, pie slices, line plots drawn with the app's own chart tool — stays vector through export by default. It scales to any zoom level without a single blurred pixel. That's the behavior most people expect from every graphic in the deck.

It's not what happens to a chart that was built somewhere else and pasted in as an image, or to a diagram exported from a design tool and dropped onto the slide as a flattened PNG. Those were never vector inside the presentation to begin with, so PDF export can't magically restore edges that don't exist in the source file — it just packages up whatever resolution the pasted image already had. The trap is that both chart types look identical on the slide at 100% zoom. You can't tell which one will hold up in a printed handout until someone zooms in on the PDF and finds out the hard way.

The practical check: right-click any chart or diagram before export and see whether it offers "Edit Data" or similar native editing. If it does, it's still vector and will export cleanly. If all you get is "crop" and "compress," it's a bitmap wearing a chart's clothing, and no export setting fixes that — only rebuilding it natively does. This is one reason working from a diagram template built with native vector shapes tends to survive PDF export better than a pasted-in graphic ever will, regardless of how good the original graphic looked.

Fonts that look fine until they don't

Font embedding is the quality problem that doesn't show up on the machine where you built the deck — it shows up on everyone else's. PowerPoint can embed fonts into the PDF (and into the .pptx itself, via File → Options → Save → "Embed fonts in the file"), but that setting is off by default and most people never find it. Without it, the PDF export leans on whatever font-substitution logic the reading application has, and if the recipient doesn't have the exact typeface installed, the text reflows into a fallback font — different letter widths, different line breaks, sometimes different apparent font weight entirely.

This is a bigger risk than it sounds like precisely because the newer, more distinctive fonts that make a deck look current are also the ones least likely to be pre-installed on a stranger's laptop — the fonts that make a presentation look modern are rarely system defaults, which is exactly why they stand out in the first place. Embed them, or the PDF quietly becomes a different document depending on whose computer opens it.

The "reduce file size" checkbox that undoes everything above

You can get the resolution setting right, keep every chart vector, and embed every font — and still lose it all with one checkbox. Most PDF export dialogs, in both PowerPoint and Adobe Acrobat's "Save As," offer a file-size reduction option, usually phrased as something reassuring like "optimize for web" or "smaller file size." What it actually does is re-run image compression and sometimes font subsetting on top of everything you already set correctly, on the assumption that smaller is what you wanted.

Except when it isn't. A PDF headed to a print shop or a board packet needs the opposite priority entirely, and there's no universal right answer here — it genuinely depends on where the file is going next, which is a judgment call the export dialog can't make for you. Choose the size-reduction path for a PDF that's mainly going to be emailed and skimmed on a phone. Skip it entirely for anything that might get projected, printed, or zoomed into.

Why this keeps happening even to people who've done it a hundred times

None of these settings are hidden exactly — they're just scattered across three different menus that don't talk to each other, which is a formatting-adjacent problem more than a technical one. A GfK survey run on behalf of the software vendor empower found that formatting tasks eat up a large share of the time employees spend in PowerPoint, translating to roughly 2.6 lost hours per employee every week. Export settings are formatting's quieter cousin: nobody budgets time for them, so they default to whatever was last set, sometimes by someone who left the company two years ago.

I wouldn't recommend memorizing every menu location above. What actually holds up over time is a two-minute habit: before sending any PDF that matters, open it at 200% zoom on the sharpest element in the deck — usually a logo or a thin chart line — and look at it the way the recipient will. If a theme change has left stray manual formatting scattered across a few slides, that same override often carries the wrong image or font settings with it into the export, so it's worth catching before the PDF stage rather than after someone else does.

The client who flagged that blurry chart never asked me what setting caused it. They just wanted the fixed version. That's usually the honest measure of whether a PDF export actually worked — not whether you followed the right steps, but whether anyone downstream ever had a reason to notice you didn't.