App Store header video specs
An App Store product page header video must be 21:9 at exactly 3840 x 1646 pixels, run 5–30 seconds at 30 or 60 frames per second, and be delivered as .mp4, .mov, .m4v. It plays muted by default, viewers can unmute it, and it loops. Headers show on iOS 27 and iPadOS 27 or later.
| Placement | Type | Ratio | Size (px) | Also required |
|---|---|---|---|---|
| Product page header | Video | 21:9 | 3840 x 1646 | 30 or 60 fps · 5–30 seconds · .mp4, .mov, .m4v · muted by default, viewers can unmute · loops |
| Product page header | Image | 21:9 | 3840 x 1646 | .jpeg, .jpg or .png · no alpha / transparency |
| Product page header (universal) | Image | 16:9 | 5244 x 2950 | .png only · the one file that can also serve search results |
Updated · Checked against Apple's documentation on 2026-10-30. Apple — Creative assets specifications
What exactly does Apple require for a header video?
Apple's creative assets specifications page lists one video format for the product page header: a 21:9 frame of exactly 3840 x 1646 pixels, 30 or 60 frames per second, between 5 and 30 seconds long, in .mp4, .mov, .m4v. The same page lists a still-image header at the same size (JPEG or PNG, no alpha) and a universal 16:9 PNG at 5244 x 2950.
The header plays muted by default and loops; a viewer can turn the sound on. Design for silence first: the story has to work with no audio at all, because that is how most people will see it.
"Exactly" is literal. A file of 3840 x 1645 is not close enough — scaling a 1536 x 658 master by 2.5 gives that height, and it is a documented rejection.
Sources: Apple — Creative assets specifications · 3840 x 1645 rejection case (GitHub)
What does Apple's page not say?
The specifications page does not define a safe area, text rules or a file-size ceiling for header assets. The only 500 MB limit on that page belongs to In-App Events, not to headers. Anything you read elsewhere about a header safe zone is advice, not a rule.
The practical advice that does exist (aso.dev, paraphrasing Apple's best practices): the header and the search card crop differently, so keep the subject and any text in the middle; make text readable on a phone; no transparency; content suitable for ages 4+; and no prices, discounts, URLs or promises you cannot keep.
Sources: Apple — Creative assets specifications · aso.dev — Header and Search Results placements
Which mistakes get a header rejected?
These are the failures developers have reported in public, all of which pass a quick look and still fail upload or review:
- Off-by-one height: 3840 x 1645 instead of 3840 x 1646.
- Metadata in the file: a PNG carrying an eXIf chunk was rejected even though its size was correct. Strip metadata before upload.
- Transparency: an alpha channel fails, even when every pixel looks opaque. Export without alpha.
- Wrong frame rate or length: anything other than 30 or 60 fps, or shorter than 5 / longer than 30 seconds.
- Prices or discounts in the artwork: App Review guideline 2.3.14 rules them out for creative assets.
Sources: eXIf rejection case (GitHub) · Transparent PNG case (GitHub) · Apple — App Review Guidelines 2.3.14 (creative assets) · PPC Land — guideline 2.3.14 explained
Where does the header show, and does it replace screenshots?
The header sits at the top of the product page above your icon, and it only appears on iOS 27 and iPadOS 27 or later. It is optional and it does not replace screenshots or App Preview videos — those still do their job further down the page.
You do not need a new build. Header assets can be submitted for review on their own, and once approved they can be swapped onto the version that is already live. Account Holder, Admin, App Manager and Marketing roles can manage them. One thing is permanent: the poster frame cannot be changed after approval, so pick it deliberately.
Sources: Adapty — App Store Asset Library and creative assets (2026-10-06) · aso.dev — Header and Search Results placements
Make a header video that passes the specs
- 1Start from a 3840 x 1646 canvas — never scale a smaller master up to it.
- 2Keep the subject and any text in the middle of the frame; render 5–30 seconds at 30 or 60 fps.
- 3Export H.264 in an .mp4 or .mov container with no alpha and no extra metadata.
- 4Run the file through a spec checker before you upload it, then preview it in App Store Connect on each device and in dark mode.