
Use Keynote HTML when the recipient must experience builds and animations in a browser. Use PDF when they need a static review document, with separate build-stage pages if necessary. The best choice depends on what the photo pitch communicates through time, not which filename is easiest to attach.
Key Takeaways
- Keynote HTML export includes animations and builds.
- PDF provides pages rather than a live presentation sequence.
- Test the recipient's real opening workflow before delivery.
Identify the information carried by motion
Apple's Keynote export guide documents HTML output opened through index.html and says animations and builds are exported. Its PDF option represents slides as pages and can print each build stage separately.
Imagine a pitch comparing a portrait's original lighting with a proposed treatment. If the reveal itself explains the idea, a single final PDF page may hide that comparison. If the reviewer simply needs to approve a crop and caption, static pages may be more convenient.
Prepare the appropriate artifact
For HTML, keep the complete exported material together and test the index.html entry point as delivered. Do not assume that attaching one entry file includes every resource it needs. Confirm how the recipient is allowed to open local or hosted HTML within their organization.
For PDF, decide whether to include each build stage, presenter notes, skipped slides and comments. A staged proof can preserve a sequence as stills without pretending it has live animation. The notes-page handoff guide helps separate review commentary from slide artwork.
Make timing expectations explicit
HTML is not a substitute for a narrated movie when the client needs a fixed audiovisual timeline. Discuss the intended playback mode separately. The recorded-timing guide illustrates how timing choices can alter a presentation's meaning.
Do not infer that a PDF carries sound because it came from a slideshow. The slideshow PDF guide is another useful comparison, with different application-specific behavior.
Check the content without motion too
A reveal should not be the only way to identify what changed. Use a visible label or concise explanation so the reviewer knows which version is original and which is proposed. Apple's image-description documentation helps with image meaning, but it does not certify an exported HTML presentation's accessibility.
An acceptance test could ask a reviewer to open the delivered artifact on the intended device, identify both versions, understand the approval question and reach the final contact slide. For PDF, check the required states as pages. For HTML, check the builds and transitions that carry the argument.
This is a decision workflow with a hypothetical pitch. Browser behavior, organizational restrictions and assistive-technology support still require verification for the actual export.
Name a fallback delivery format in the handoff note if the client cannot open local HTML within their organization.
Related tasks
- Why Does My PowerPoint Advance Without a Click After Rehearsal?
- Why Did My PowerPoint PDF Export Include Speaker Notes Instead of Full Slides?
- Why Does My Lightroom PDF Slideshow Lose Its Music and Timing?
Sources and scope
- Export to PowerPoint or another file format in Keynote on Mac: Static page proof versus animation-carrying HTML; test the actual recipient workflow.
Documentation-based guidance; proposed playback and export checks have not been run on a sample presentation.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.