
This guide concerns Keynote on Mac using a nearby iPhone or iPad to scan through Continuity. Apple documents that, on that route, only the first item appears in the presentation when several are scanned. It is not a claim about every scanning app or ordinary multi-page file import. If a multi-page reference scan seems incomplete, verify the inserted object before assuming all pages became separate slide images.
Key Takeaways
- A multi-item scan does not guarantee multiple visible Keynote images.
- Inventory the required reference pages.
- Use a verified import or assembly route for the complete set.
Confirm what was inserted
The Keynote image guide explicitly notes the first-item behavior for multiple scans. Inspect the presentation and the source scan separately. Do not tell a client that their second page was lost permanently merely because it is absent from the slide.
For this documented route, open the destination slide on Mac and use the media toolbar control to choose Scan Documents beneath the nearby device name. Check the official Continuity requirements for the devices in use. Identify which scanning workflow and source artifact you actually have. The guide's statement does not establish a universal recovery path or the storage location of every scan, so use the device's current interface rather than inventing a hidden-page command.
Inventory the reference material
For a hypothetical location brief, the required scans might be a room sketch, a lighting diagram and a permissions note. List those three content items and mark which are visible in Keynote. A count of three inserted objects is not enough if one page was inserted repeatedly.
Give each reference a clear title or ID. The identifiable proof guide explains why stable references make later feedback more reliable.
Assemble a complete review deliberately
If the workflow provides separate image files, add the required items individually through the documented image insertion route. If it produces a multi-page document, decide whether the recipient needs that document as an accompanying reference instead of trying to imply that one placed image represents it all.
The PDF portfolio versus sequential document guide helps distinguish a collection from a linear review file. The correct choice depends on the recipient's task and tools.
Do not replace an unverified multi-page reference with screenshots that omit important detail or make text unreadable.
Check the final handoff
Inspect each required reference at the intended reading size. Confirm that page titles, diagram labels and necessary permission text are readable. Distinguish visible page numbers from physical order if reviewers will discuss specific pages.
If exporting the presentation, use Apple's export documentation and check the actual PDF or image set. Correct source insertion does not prove correct export scope.
Acceptance means every required reference is present or explicitly supplied alongside the pitch, with an understandable order and clear IDs. This guide describes documented insertion behavior and a proposed completeness check, not a tested scanning session or a promise that all scanning applications behave identically.
For an archival or legal reference, retain the supplied original separately and avoid cropping out contextual information merely to make it fit a presentation slide.
Related tasks
- Why Does My PDF Portfolio Show Only a Cover in a Browser?
- Why Does PDF Page 1 Appear as Page 5 in the Viewer?
- Make a Lightroom Contact Sheet That Clients Can Identify
Sources and scope
- Add an image in Keynote on Mac: Multi-item scan insertion shows the first item; this is not a multi-page gallery import.
Documentation-based guidance; proposed editing 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.