Test the delivered version on the playback system
A presentation can look correct on the author's computer and still fail after transfer because it depends on a local video, an unavailable font, an online resource or software features missing from the show system. A file can also open correctly while the wrong output or audio device is selected. The useful preflight covers both the content package and its actual playback route.
Give the technical team a test version early, then deliver one clearly identified final version. Agree who approves visual changes and who may replace the show copy. “Final” in a filename is not enough when several people continue editing separate copies.
Match the symptom to the next check
| Symptom | What to investigate | What confirms the fix |
|---|---|---|
| Slides open but a film is missing | A linked file, missing media or an unsupported encoding | Play the film from the transferred presentation on the show computer |
| Text wraps or symbols change | Font availability, embedding permissions and application differences | Compare important slides against an approved visual reference |
| Video plays without sound | File soundtrack, mute settings, output selection and the audio chain | Listen through the event sound destination |
| The audience sees notes or a desktop | Display assignment and presentation mode | Run the real slide show through the audience output |
| An online element remains blank | Network access, login, permissions or service dependencies | Test the agreed account and connection, plus the fallback |
| A film stalls or loses smooth motion | Actual file encoding and playback workload | Play the complete demanding segment through the final configuration |
Package media and fonts deliberately
Microsoft recommends MP4 with H.264 video and AAC audio for PowerPoint. That is a useful starting point for a PowerPoint delivery, not a universal export requirement for all playback systems. A filename ending in .mp4 alone does not describe every encoding setting. Ask the receiving technician for the accepted specification and test a representative file.
Microsoft's compatibility guidance also addresses linked media. Where its optimisation tool is used, work on a copy and review the result: Microsoft notes that embedded subtitles and alternate audio tracks can be removed during optimisation. A film that now plays but has lost required captions is not a completed fix.
Font embedding can help preserve appearance, but Microsoft explains that font permissions and application support affect what can be embedded. Confirm the actual show copy, including accented characters, figures and last-minute text edits. Do not assume that a successful title slide proves every font in the deck is available.
Hypothetical example: the launch film disappears
A speaker sends a presentation that worked on their office laptop. During rehearsal, slide 12 shows a missing-video message. In this hypothetical case, the deck refers to a film stored in the speaker's local project folder, and only the presentation file was transferred.
The author supplies the missing film and prepares an agreed package with the media correctly included or otherwise handled by the chosen playback workflow. The team copies that package to the show computer and plays slide 12 from the slide show, checking its start, sound and return to the next slide. They also store an agreed standalone copy of the film for the fallback procedure.
Afterwards, a revised deck changes the order of slides. That version needs a renewed cue check: the operator's note “film on slide 12” is no longer dependable. File compatibility and programme accuracy must both be checked.
Run the rehearsal in the right order
Confirm the show computer, operating system, application and delivery specification with the technical team.
Transfer the complete package to the intended local storage, then reopen the delivered copy rather than the author's original.
Check slide layout, important characters, every media item, animations and required captions.
Run the audience output and sound path; verify notes, presenter view and remote control behaviour separately.
Test the longest or most demanding media segment and the transitions into and out of it.
Record the approved version and rehearse the agreed fallback.
Make the fallback usable
A PDF can preserve static slide appearance but does not reproduce a native presentation's animations, live demonstrations or ordinary embedded-video workflow. Decide which content can use a PDF fallback and provide essential films separately where appropriate. A cloud link is not an offline copy; verify files are actually available when the intended fallback requires local playback.
Label the approved package with a version and date, and keep a short cue list with media names and starting instructions. Ask the operator to confirm receipt and testing. These steps make a spare file useful when it is needed, rather than another ambiguous attachment.
Discuss the delivery package with technical support and confirm the playback computer before speakers finish their files. The best deadline leaves time to correct problems and test the corrected version.
Further reading
Microsoft provides guidance on supported media formats, playback compatibility and font embedding. Check the instructions for the application version used at the event.