App Store In-App Event guide

In-App Event assets

Prepare a coordinated pair: a landscape Event Card for discovery and a portrait Event Details asset for the deeper event page. The two placements have different shapes and should be recomposed rather than cropped from one generic banner.

By AppListingLab · against Apple's In-App Event media specifications.

Image sizes for Card and Details

Swipe the table to see every size.

App Store In-App Event image requirements
PlacementOrientationAspectResolutionFormatsMax size
Event CardLandscape16:91920×1080 to 3840×2160 pxJPG, JPEG, PNG500 MB
Event Details PagePortrait9:161080×1920 to 2160×3840 pxJPG, JPEG, PNG500 MB

Video uses the same placement shapes

Event Card video remains 16:9 landscape and Event Details video remains 9:16 portrait. Apple accepts MOV, M4V, and MP4, with the same resolution ranges as the corresponding images.

Duration

15–30 seconds

Frame rate

30 fps or 60 fps

Maximum file size

500 MB

Silent tracks are supported. When audio is present, Apple documents stereo AAC at 256 kbps and 44.1/48 kHz for Event Card video. Event Details video can also use PCM under Apple's documented bit-depth rules.

Treat one event as one visual direction with two compositions

  1. 01

    Design the Card for discovery

    Use the wider 16:9 composition for the first encounter with the event. Keep the event identity readable without assuming the viewer has opened the detail page.

  2. 02

    Recompose the Details asset

    The 9:16 detail placement has much more vertical space. Move subjects and copy intentionally instead of center-cropping the Card.

  3. 03

    Keep the pair recognizable

    Carry over color, illustration, typography, and message so the transition from Card to Details feels like the same event.

  4. 04

    Review every localization

    Visible event copy can expand significantly in another language. Treat Card and Details as two localized layouts, not one translated image.

AppListingLab does not yet expose an In-App Event editor

The current customer product does not create, schedule, or publish In-App Events. The planned image-first workflow will create the Event Card and Event Details pair from the same App profile and event context, then validate/export both placements.

Provider event creation, Asset Library upload, scheduling, and review submission stay blocked until their current App Store Connect API contracts are verified. This page is a preparation guide, not a claim that the workflow is already released.