Your App Store Page No Longer Waits on a Build

On October 5, 2026, Apple switched on a set of new App Store creative assets for all developers in App Store Connect. The interesting part isn’t the new artwork slot — it’s that store creative now has a submission path that doesn’t involve a binary.

What actually shipped on October 5, 2026

Apple’s developer news post, Showcase your apps with new assets on the App Store, describes three things. New creative assets for “product page headers and in search result assets.” An Asset Library to “upload and organize your creative assets, screenshots, and app previews in one central place — even ahead of when you’d like to use them.” And a preview tool to see how assets “will appear on your product page and in search results before you submit them,” with support for Dark Mode, different devices and orientations.

Once approved, an asset can be used in more places than the two headline placements: the product page header, search results on the App Store and in the Apple Games app, In-App Event cards and detail pages, Custom Product Pages, Product Page Optimization treatments, and Apple Ads campaigns in the Today tab and search results.

One constraint does not appear in the news post, and it matters: creative assets “are available for iOS and iPadOS apps and games running iOS 27 or iPadOS 27 or later,” per Apple’s help page Manage your App Store assets. WWDC26 session 205 says the same.

You may read that the old, editorial-gated “Feature Banner” was renamed “Header.” That framing comes from third-party ASO commentary, not from Apple — Apple’s documentation calls the placement a “product page header” throughout and presents it as new. The verifiable point survives either way: a placement that previously required going through Apple’s editorial team is now self-serve for everyone.

Decoupled from the build, not from review

The appealing version of this story is “you can change your store creative without review.” That’s not what happened, and getting it right matters for planning.

WWDC26 session 205 describes two submission paths. You can upload assets on a version page and submit them along with the version. Or you can “submit your creative assets standalone, without updating your version.” Standalone assets are still reviewed — Apple’s help page says they’re “reviewed against your app’s latest version.” What disappears is the binary, the version entry, and the release coupling.

It also isn’t the first store surface you can change without a build. Promotional text has allowed up to 170 characters that, per Creating Your Product Page, “you can update at any time without having to submit a new version.” Product Page Optimization tests without alternate icons have long been submittable independently of a version. Ordinary screenshots, by contrast, still require a version submission even when the binary is byte-identical — a long-running source of developer-forum complaints.

So the accurate claim is narrower and still significant: this is the first visual App Store surface with a documented, pre-approvable, version-independent submission path and an App Store Connect API behind it. Promotional text was text. PPO was a workaround. This is infrastructure.

The strongest evidence that it’s a separate workstream is in the permissions. Managing assets requires the Account Holder, Admin, App Manager, or Marketing role. A designer or marketer can run this end to end without developer-level access to the account.

The specs, and the rule that will cost you a reshoot

All of these come from Apple’s creative assets specifications, retrieved October 8, 2026.

Product page header: 21:9 image at 3840 × 1646 px (.jpeg, .jpg, .png); 16:9 image at 5244 × 2950 px (.png only); video at 21:9, 3840 × 1646, 30 or 60 fps, minimum 5 seconds, maximum 30 seconds (.mov, .m4v, .mp4).

Search results asset: 3:2 image, minimum 1920 × 1280 and maximum 3840 × 2560 px; the same 16:9 5244 × 2950 PNG; video at 3:2 within the same bounds, 30 or 60 fps, 5 to 30 seconds. Because both placements accept that 16:9 PNG, Apple’s asset best practices suggests a “universal creative asset” for header and search results. Apple ships templates — Figma and Sketch provide the universal asset, Photoshop and Pixelmator provide separate header, search and universal files.

Two cross-cutting rules. “Images can’t include alpha channels or transparencies.” And on video: “Videos are muted by default in search results and can’t currently be unmuted. On your product page, videos are also muted by default, but people can unmute them. Videos loop continuously in both placements.” That “can’t currently” is Apple’s hedge, not mine.

Now the expensive one, from the best practices page: “Assets displayed on the App Store must meet a 4+ age rating, even if your app’s rating is higher and it’s intended for an older audience.” A 17+ app needs 4+ creative. Existing marketing cuts frequently won’t qualify. Also prohibited: pricing or discounts, website URLs, copyright symbols, unverified award claims, references to other platforms or marketplaces, and Apple-designated recognitions like Editor’s Choice or Apple Design Award. Games with violence “may use action imagery, but must avoid depictions of gore, graphic imagery, or weapons that are pointed directly at a person or the audience.”

Two traps worth flagging. The 5-second video minimum applies to header and search assets; In-App Event video has a 15-second minimum on the same page. And “poster frames can’t be edited after assets have been approved” — pick the poster frame before you submit, or resubmit the asset.

Apple states that creative assets are reviewed against App Review Guidelines 2.3.3 and 2.3.4. Guideline 2.3.3 governs screenshots and demands that they “show your app in use,” while creative assets are explicitly brand material sitting outside screenshots and previews. How strictly reviewers apply 2.3.3 to a brand header isn’t established yet. The feature is days old.

Static or video? There is no performance data yet

Any vendor publishing conversion lift numbers for product page headers in October 2026 is extrapolating. The placement has existed publicly for three days as of this writing. Decide on cost and constraints instead.

Video is more expensive and carries more obligations. Apple’s guidance: “Lead with your value proposition or most compelling feature… Avoid quick cuts and fast-moving visuals.” It must loop without “visible jumps or breaks.” It must work muted: “your creative must work silently first… treat [sound] as brand texture rather than information delivery.” And its poster frame locks on approval.

Static is cheaper, trivially localizable, and can reuse the universal 16:9 canvas across both placements.

If you do cut video, produce it to spec rather than letting an export preset decide:

# Product page header video: 21:9, 3840x1646, 30 fps, 5-30s, no audio.
ffmpeg -i master.mov \
  -t 12 \
  -vf "scale=3840:1646:force_original_aspect_ratio=increase,crop=3840:1646,fps=30" \
  -c:v libx264 -profile:v high -pix_fmt yuv420p \
  -movflags +faststart -an \
  header-21x9.mp4

The crop after an increase scale is what keeps you from letterboxing inside a 21:9 frame. -an is deliberate for the search placement. Then check what the viewer sees before playback starts:

ffmpeg -i header-21x9.mp4 -vframes 1 -q:v 2 poster-check.jpg

One open question: the preview tool supports Dark Mode, but no Apple documentation mentions uploading separate light and dark variants. As of October 8, 2026, treat it as one asset that must survive both appearances — and remember you can’t lean on a transparent background, because alpha isn’t allowed. Confirm in the console before you plan around it.

Almost nobody can see it yet

Because headers require iOS 27 or iPadOS 27, the size of the audience is the whole story right now. iOS 27 shipped September 14, 2026, with iOS 27.0.1 following on September 28.

Adoption estimates are contested, and the two named sources disagree sharply. TelemetryDeck, updated October 1, 2026, puts iOS 27 at 16.27%, iOS 26 at 74.58% and iOS 18 at 7.09% — and discloses that its dataset skews toward American and European apps and independent developers. StatCounter puts iOS 27 at 2.41% worldwide for September 2026, 2.02% in the US; it derives figures from web traffic, which lags device telemetry. Neither is Apple.

Don’t average them. The honest reading is that somewhere between roughly 84% and 98% of the installed base cannot see a header as of early October 2026. iOS adoption historically climbs quickly over a quarter, but putting a number on that curve would be a guess.

That argues for sequencing, not for skipping. Build the asset pipeline now while the stakes are low, and let the audience arrive into creative that’s already been iterated on.

One more thing to not imply: Apple makes no statement that creative assets affect search ranking. It does say ratings and reviews influence search ranking. It says nothing of the kind about assets.

What to do this month

Audit what exists. List the assets you already have per localization, and mark which could pass a 4+ review unchanged. For anything above 4+, assume new creative, not a re-crop.

Pick the canvas before the concept. If one universal 16:9 asset at 5244 × 2950 can carry both placements, that halves the production and localization work. Decide that first, because it constrains composition — Apple asks you to “design key elements with a safe area in mind” and keep “focal point artwork… within the center of your composition to prevent any unwanted clipping.”

Pre-approve seasonal creative early. Apple’s example is submitting “creative assets for approval today to use in a future seasonal campaign, then immediately use them once you’re ready.” Apple publishes no turnaround time for standalone asset review — that silence is exactly why you queue holiday creative weeks out rather than days.

Hand the workstream to whoever owns the brand. The Marketing role is sufficient. If store creative currently routes through an engineer, it no longer has to.

Put the one hard deadline in the calendar. Per App Store Connect release notes dated October 5, 2026: “Starting April 2027, any apps or games submitted will need to include screenshots for iPhone Duo.” iPhone Duo launched alongside iOS 27 on September 14, 2026, and both the preview tool and Apple’s templates already support it. Every other item here is discretionary. That one has a clock.

If you’re building on current tooling while you do this, Xcode 27 is the stable release as of October 8, 2026 — Swift 6.4 compiler, iOS 27 SDK, macOS Tahoe 26.6 or later, deployment targets back to iOS 17. Xcode 27.1 was at release candidate and 27.2 at beta 2, so check Apple’s Xcode versions page before pinning a CI image.