
Keynote can export each stage of a slide's builds as a separate PDF page. If your PDF has more pages than the presentation has slides, inspect Print each stage of builds before deleting pages. Presenter notes, skipped slides and comments are separate inclusion choices that also deserve review.
Key Takeaways
- A slide with several build stages can produce several PDF pages.
- Decide whether the reviewer needs the sequence or only the final state.
- Match the exported proof against a content inventory.
Inspect the PDF export choices
Choose File > Export To > PDF. In Apple's export guide, each slide normally becomes a PDF page, while Print each stage of builds outputs build stages separately and in presentation order.
Keynote remembers its last export settings. Do not assume that a setting used for a previous rehearsal is still suitable for a client proof. Review the notes, skipped-slide and comment options at the same time.
Choose a review purpose
Suppose a slide first shows an unedited portrait, then an annotation and finally an approved crop. A sequence proof may need all three states. A final-layout approval may need only the completed view. State which review you are requesting so the recipient does not treat an intermediate state as a separate design proposal.
Do not manually delete pages until you understand the source setting. Deleting the wrong state could remove a required instruction while leaving the page count looking reasonable.
The hidden-slide scope guide covers a related inclusion issue in another application. Its commands differ, but the principle is useful: source visibility and delivery scope are not interchangeable.
Verify images and context
Check every intended slide against the output. If notes are included, confirm that they are meant for the recipient. The notes-page handoff guide explains why internal commentary can be a separate deliverable.
For image-dependent instructions, retain meaningful descriptions. Apple's image guide describes adding image descriptions, and the export documentation states those descriptions are exported automatically to PDF. This does not prove that every reading sequence or description is useful.
Approve the actual page sequence
A concrete acceptance rule could be: twelve approved slides, final state only, no skipped draft slide, no internal notes, and the final contact page present. For a build-sequence proof, name the expected states instead of forcing the output to match the slide count.
Distinguish PDF page labels from physical page order when discussing specific pages with the reviewer. Keep the approved PDF filename in the delivery record.
This is a documented explanation with a hypothetical slide. It does not claim that build stages are the only cause of extra pages or that a specific exported presentation was inspected.
Keep the source slide number in the review note so extra build pages remain traceable to their original slide.
Related tasks
- Why Does My PDF Include a Slide Hidden in PowerPoint?
- Why Did My PowerPoint PDF Export Include Speaker Notes Instead of Full Slides?
- Why Does PDF Page 1 Appear as Page 5 in the Viewer?
Sources and scope
- Export to PowerPoint or another file format in Keynote on Mac: Each-stage-of-builds PDF export option.
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.