App Store in-app event video: 1920x1080 card, 1080x1920 page

Apple wants two videos per in-app event: a 16:9 card and a 9:16 details page. Cut both from one clip with Sume Timeline and check the sizes with video inspect.

4 min readSume
All posts

An in-app event on the App Store takes two separate videos: a 16:9 one for the event card and a 9:16 one for the event details page. With Sume you render each from the same footage with a Timeline 1.0 call, one with output set to 1920x1080 and one set to 1080x1920, both at 30 fps. Two renders of 20 seconds each cost $0.10 apiece.

What does Apple require for each video?

The numbers below come from Apple's in-app event media specifications. Apple accepts .mov, .m4v and .mp4 files, up to 500 MB, at 30 or 60 fps.

In-app event video specs from App Store Connect help, read 2026-10-03, and the matching Timeline output.
Event card videoEvent details page video
Aspect ratio16:99:16
Minimum size1920x10801080x1920
Maximum size3840x21602160x3840
Frame rate30 or 60 fps30 or 60 fps
AudioTracks without audio are supportedTracks without audio are supported
Timeline outputwidth 1920, height 1080, fps 30width 1080, height 1920, fps 30 (the default shape)

Can Sume reach Apple's maximum sizes?

No. Timeline output edges are limited to 256 to 2160, so 3840x2160 and 2160x3840 are out of reach, but the minimums Apple lists (1920x1080 and 1080x1920) are inside the limit. Apple lists a minimum and a maximum, so a file at the minimum meets the spec as written. If you need a larger frame, produce it in your editing tool instead.

How do I make both videos from one clip?

Import the source clip, then submit two renders that differ only in output and fit. A 16:9 source fills the card with cover. For the 9:16 page, cover crops the sides; use blur to keep the full frame over a blurred backdrop if the action is wide.

for SHAPE in card:1920:1080:cover page:1080:1920:blur; do
  IFS=: read NAME W H FIT <<< "$SHAPE"
  curl -s -X POST https://api.sume.com/v1/timeline-1.0/render \
    -H "Authorization: Bearer $SUME_API_KEY" \
    -H "Content-Type: application/json" \
    -H "Idempotency-Key: iae-$NAME-001" \
    -d "{\"audio\":{\"mode\":\"silence\",\"duration_seconds\":20},
         \"output\":{\"width\":$W,\"height\":$H,\"fps\":30},
         \"video\":[{\"source_url\":\"https://media.sume.com/artifacts/artf_evt/event.mp4\",
                    \"start\":0,\"duration\":20,\"fit\":\"$FIT\"}]}"
done

What does Apple say about audio?

Apple's page lists audio specs for both videos, and says tracks without audio are supported for each. For the event card video it asks for stereo, 256 kbps AAC at 44.1 or 48 kHz. For the details page video it accepts stereo PCM (16, 24 or 32 bit) or 256 kbps AAC, also at 44.1 or 48 kHz. Sume's Timeline docs do not publish the audio codec or bitrate of the rendered MP4, so do not assume it matches. If you ship sound, inspect the file and compare, and if a clip has no sound, you are inside Apple's stated rules by leaving it silent, which is also how a muted autoplay card reads.

Audio specs for in-app event videos from App Store Connect help, read 2026-10-03.
VideoChannelsCodecSample rate
Event cardStereo256 kbps AAC44.1 or 48 kHz
Event details pageStereoPCM 16/24/32 bit or 256 kbps AAC44.1 or 48 kHz

What goes in the 20 seconds?

Apple's page sets the file specs, not the story, so the content is yours. A workable plan for a game or app event is three beats: the hook in the first two seconds, the thing that is different this time (a new mode, a prize, a date), and a closing frame with the event name. Put the same beats in both renders so the card and the page tell the same story, and use two slots in the 9:16 version when the vertical crop would lose the subject. If you need text on screen, add it as cues captions after the render, since cues burn exactly what you write at the times you give.

How do I check the files before I upload?

Run each result through video inspect. It returns probe facts for the clip, including whether it has audio, so you can confirm the dimensions and the frame rate against Apple's table before you open App Store Connect. Keep the event hook in the first seconds and add any on-screen text with video captions cues; the cue text is exactly what you author.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume