Presentation transfer

How it works

A deck that embeds a 200 MB video becomes a large-file transfer. A deck that links the video breaks on the recipient's machine. Fonts that are not embedded substitute. Transfer the package you tested on a clean machine. Hash it. Playing the slides is the acceptance test after the hash.

A 480 MB keynote with an embedded reel bounces from mail. A link upload finishes. The client opens it without the font and the titles reflow. The bytes matched. The font was not in the file. They resend a PDF export for the room and keep the editable file for the studio.

How it differs

A presentation transfer is not a screen share. Screen share does not leave a file. The transfer does.

Exporting to PDF at send time drops builds and transitions. Do that on purpose, not as a silent gateway conversion.

Two versions named Final.pptx in one folder: the later download overwrites. Put the date in the name.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For presentation transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive presentation transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.