Plan an App Store preview as a separate deliverable

Open the current app record and identify the device category, orientation and localisation you intend to supply. Read Apple’s preview-specification table for that slot. Do not select dimensions from a different app’s old release folder or from a general social-video preset.

Apple currently describes previews as optional, with up to three per supported device size and language. The ordinary app-preview slot is not the same deliverable as a review demonstration or a Header/Search Results marketing asset. Verify each destination independently.

For an illustrative translation app, the sequence could show selecting two languages, starting an allowed sample phrase and displaying the translated result. Keep the source data fictional and make the visible result understandable without a long spoken introduction.

Prepare a clean account and repeatable starting state. Record actual app behaviour rather than presenting a simulated interface as device evidence. If a feature depends on subscription, permissions or a download, decide how to show that honestly within the sequence.

Rehearse once and record a slightly longer source take, including the opening state and completed result. Avoid moving a presenter bubble across essential controls. A general tutorial’s face camera or decorative frame may be unnecessary for this destination.

Keep an original recording and identify the device, operating system, app build and interface language. These notes help distinguish outdated visuals from a current release. This guide does not claim a recorder automatically meets every Apple composition or content rule.

The checked Apple table specifies 15–30 seconds, a 500 MB maximum and a maximum 30 fps for this app-preview format. It lists H.264 in supported movie containers and a separate ProRes option, with audio requirements. Read the complete current table for the selected export, not just these headline limits.

Inspect dimensions, duration, encoding and audio in the final file. Do not infer H.264 merely from an .mp4 suffix. A source recording may need an editor export before it meets the chosen upload specification.

Upload to the intended language and device slot, allow Apple’s processing to complete, then play the processed preview. Check the poster frame, start, end, legibility and localisation. A completed file transfer is not the same as a playable processed asset.

Preserve the accepted export and its source notes in the project’s managed storage. If a language has no dedicated video, inspect Apple’s documented fallback behaviour rather than assuming the product page will show nothing. Keep store metadata aligned with the actual app build.