PowerPoint to PDF — preserve animations and fonts

Why PowerPoint → PDF is mostly lossless

PowerPoint files (.pptx) are defined by the ISO/IEC 29500 Office Open XML standard — every slide is a typed composition of placeholders, shapes, images, charts and embedded media.¹ A PDF page, defined by ISO 32000-1, is a flat content stream of glyph positions and graphics operators.² Going from the rich structure of a slide to the flat canvas of a PDF page is a simplification — you can always represent richer structure on a simpler canvas. That is why this direction is much easier than the reverse: the converter "prints" each slide onto the PDF page exactly as PowerPoint would render it on screen, and almost everything visual survives intact.

The two things that genuinely cannot survive are dynamic — animations and transitions — and one thing depends on licensing — embedded fonts. The rest is mechanical.

What survives the export, and what does not

Handling animations in a static PDF

PDF has no native animation primitive — by design, the format is print-faithful and page-bound. There are three reasonable strategies when an animated deck needs to travel as a PDF:

1. Accept the static version. The most common path. The animation played a role on the live stage; the PDF carries the slide content. Most decks read fine without their animations.
2. Export each build step as a separate PDF page. PowerPoint's "Print" dialog offers this under the slides-per-page section as "Slide builds"; LibreOffice Impress exposes it as "Export each frame of the animation"; the ScoutMyTool tool offers a "build-by-build" option. A bullet list that animates in one item at a time becomes a sequence of pages, each adding one bullet — the reader sees the animation in stepped form by flipping pages.
3. Distribute as a video. For animation-heavy decks where the motion is essential (training materials, product demos), the right answer is "File → Export → Create a video" in PowerPoint and distribute as MP4. The PDF then becomes a still-image companion rather than the primary medium.

Font embedding — the one thing most decks get wrong

Custom fonts in a PowerPoint deck only survive the PDF export if the font's licence allows embedding. The licensing flag is set by the foundry that issued the font, and the PDF export honours it. The four possible states:

• Installable — the font can be embedded and even extracted from the PDF for installation on another machine. Most open-source fonts (Inter, Roboto, Open Sans) are this.
• Editable — the font can be embedded for viewing and editing of the PDF, but not extracted for re-distribution.
• Print and preview — the font can be embedded for viewing only; the PDF cannot be edited and re-saved with the font intact.
• Restricted licence (no embedding) — the font cannot be embedded at all; the PDF substitutes a system font on the reader's machine.

Check before sending: in PowerPoint, File → Options → Save → "Embed fonts in the file" forces a full or subset embed and warns when a font refuses. On macOS / Linux, otfinfo -i <font.ttf> reports the licensing flag. For corporate decks that travel to outside audiences, use fonts in the Installable or Editable category — substitution is the cause of nearly every "deck looks different on their machine" support ticket.

Five export paths compared

For desktop users with PowerPoint installed, the built-in export is the right default and supports every option discussed above. For users without PowerPoint or with sensitive material, ScoutMyTool's browser-based path keeps the file on the local machine. LibreOffice Impress is the cleanest free-and-open-source desktop alternative, particularly for the per-frame animation export.

Exporting via ScoutMyTool — five steps

1. Open the tool. Go to scoutmytool.com/pdf/pptx-to-pdf. The page loads as static HTML and the conversion runs entirely in your browser tab — the .pptx is read locally with JSZip and each slide is rendered to a canvas.
2. Drop in the .pptx file. The tool accepts up to a few hundred megabytes of source file. Larger decks can be split first.
3. Pick options. Include speaker notes (off by default), include comments, choose handout layout (1 / 2 / 4 / 6 / 9 slides per page), and pick PDF page size (Letter or A4).
4. Click Convert. The tool walks each slide, rasterises or vector- renders the content, and assembles the PDF using pdf-lib. The result downloads as a standard PDF 1.7 file that opens in every viewer.
5. (Optional) Compress before emailing. If the deck is image-heavy, run the result through Compress PDF to bring it under your recipient's email cap, or password-protect it before sending.

Related ScoutMyTool tools and articles

• PPTX to PDF — the primary tool referenced.
• PDF to PPTX — the reverse direction.
• Handout from slides — multiple slides per page.
• Compress PDF — shrink the exported deck before emailing.
• Protect PDF — password-protect the exported deck.
• Add Page Numbers — paginate a long deck for review.
• PDF to PowerPoint converter — sister article on the reverse direction.
• Adobe Acrobat free alternatives — broader Acrobat-replacement piece.
• How to send large PDFs over email — when the exported deck is too big to attach.

Frequently asked questions

Can a PDF actually play animations from my PowerPoint deck?

No, not in the conventional sense. The PDF specification (ISO 32000-1) does not include a slide-animation primitive — page content is static once rendered. There is one workaround: export each "build step" of an animated slide as a separate PDF page, so the reader can flip through pages and see the animation play in stepped form. PowerPoint, LibreOffice Impress, and Adobe Acrobat plug-ins all expose this option under names like "create one PDF page per build" or "export animation frames". For rich interactive PDFs, the PDF/A-3 and Rich Media Annotation features in newer PDF specs can carry embedded media, but viewer support is uneven enough that almost no professional workflow relies on them.

Will my fonts look right on the recipient's computer?

They will if the export embeds them properly. PowerPoint's default export subsets and embeds all standard fonts (Calibri, Arial, Times New Roman, Segoe UI). Custom or licensed fonts only embed if the font's licence permits PDF embedding — many commercial fonts do, but some restricted-license fonts do not, in which case the PDF substitutes a similar system font on the reader's machine. The fix for a font that refuses to embed: check the font's licence (otfinfo -i on macOS/Linux, or any font-info tool on Windows reports the embedding flag), and if the flag is "no embedding", switch to a different font with permissive licensing.

Should I include speaker notes in the exported PDF?

Depends on the audience. For a deck you are sharing publicly or for download, exclude speaker notes — they were written for you, not the reader. For a deck you are sending to colleagues who could not attend the meeting, include them — the notes are often what makes the slides actually make sense. Both PowerPoint and LibreOffice expose "include speaker notes" as a checkbox in the export options. ScoutMyTool's PPTX to PDF tool exposes the same toggle.

Will hyperlinks (URLs, email links, slide references) still work in the PDF?

Yes. The PDF specification supports both external link annotations (pointing to a URL or mailto: address) and internal link annotations (pointing to a specific page within the PDF). Every reasonable PowerPoint-to-PDF export preserves these. Click-to-jump behaviour works in Adobe Reader, Apple Preview, Chrome, Edge, Firefox, and almost every PDF viewer. The one edge case: links that target a PowerPoint object (like "go to next slide if clicked") generally convert to "go to next page", which behaves the same in PDF.

Why does the exported PDF look slightly different from the on-screen deck?

Three common reasons. First, font substitution if a non-embeddable font was used — the substitute renders at a slightly different metric. Second, image compression — many exporters re-encode images as JPEG at 220 DPI or lower by default; visible mainly on photos with fine detail. Third, the slide aspect ratio versus PDF page size — a 16:9 slide exported at A4 will have whitespace top and bottom; export at "custom slide size" to match the destination PDF format if this matters.

Is my deck uploaded anywhere when I use a free online tool?

Only if the tool is server-based. Smallpdf, iLovePDF, and Adobe online converters upload the .pptx to their servers, run LibreOffice or a proprietary engine there, and stream back the PDF. ScoutMyTool's PPTX to PDF tool runs entirely in your browser tab — the .pptx is read locally using JSZip (PPTX is a ZIP archive of XML), each slide is rendered to canvas in the browser, and the PDF is built client-side with pdf-lib. For confidential decks (pricing, roadmap, M&A material), the client-side path is the only one that genuinely keeps the file off third-party infrastructure.

How do I get a "handout" version with multiple slides per page?

PowerPoint has this built-in: File → Print → choose "Handouts" (2, 3, 4, 6, or 9 slides per page) → "Save as PDF" instead of printing. For the same operation outside PowerPoint, ScoutMyTool has a PDF handout-from-slides tool that takes an already-exported single-slide-per-page PDF and re-tiles it into 2, 4, 6, or 9 per page. Handouts are good for printed audience copies but bad for on-screen reading — make the choice based on the medium.