iPhone Duo requires two distinct App Store screenshot sets — one for the outer display, one for the inner display — because Apple renders the product page across genuinely different dimensions and browsing contexts. Resizing existing portrait screenshots fails both conversion and Apple's own asset specifications.

Apple's first foldable iPhone isn't just a new device SKU — it's the most significant shift in App Store real estate since the iPhone X notch forced every ASO team to rebuild their screenshot templates from scratch. If your team's launch plan is "scale the existing screenshots to fit," you are already behind.

Why the iPhone Duo Changes the ASO Playbook — Not Just the Templates

Most hardware launches create a compliance task: update dimensions, re-export assets, submit. The iPhone Duo creates a strategic problem, because for the first time on iPhone, a single user holds two meaningfully different screen contexts in one device — and they switch between them fluidly, sometimes mid-session.

That has direct consequences for how the App Store renders your product page, how users browse during that critical first-impression window, and how your screenshots must do storytelling work across two completely different canvases.

The Two Display States That Define Your ASO Surface Area

Outer (Cover) Display This is the phone-as-phone state. Users browsing the App Store here are in familiar iPhone territory — portrait orientation, one-handed, likely in motion. The proportions are notably more compact than a standard iPhone screenshot (roughly 1.45:1), which means previously safe text zones may clip, and visual hierarchy that worked on a 6.7" Pro Max will feel cramped.

Inner (Unfolded) Display This is the new frontier — a significantly larger canvas closer to iPad mini territory than iPhone. Apple's specifications list both portrait and landscape as supported orientations for this display without naming a default, which means the visual contract here is still partly unsettled. Screenshots designed purely for tall portrait storytelling risk losing impact if the App Store renders this state in landscape.

The critical insight: these are not two sizes of the same experience. They are two different user mindsets, two different browsing postures, and two different visual contracts.

New Screenshot Specs: Confirmed by Apple

Apple has published official screenshot specifications for iPhone Duo in App Store Connect Help. Here is the confirmed spec framework ASO teams should build to:

Source: Apple's official screenshot specifications.

Important: Apple has not indicated a primary orientation for either display — both portrait and landscape dimensions are listed as supported for outer and inner. Any assumption about which orientation the App Store will default to for browsing is currently speculative; design flexible layouts that hold up in both until Apple's actual rendering behavior is confirmed post-launch.

The detail most teams will miss: according to Apple's own documentation, support for uploading iPhone Duo assets in App Store Connect "will be available later this year." As of publication, you cannot yet submit these screenshots even if they're production-ready. This changes the urgency calculus: the priority right now is design and production readiness, not submission. Teams with finished, on-brand assets sitting ready the moment upload opens will capture the first-mover window; teams still designing when it opens will not.

What this means for your asset pipeline:

• You will need a minimum of two distinct screenshot sets — not one set scaled to two sizes.

• Design both portrait and landscape variants for the inner display until Apple confirms which orientation the App Store renders by default.

• Monitor App Store Connect for the upload window opening. This is a discrete, trackable event — assign clear ownership for checking it, rather than assuming it will be obvious when it happens.

Visual Storytelling Across Fold States: A Framing Problem, Not a Design Problem

A note on orientation before this section: the landscape-first storytelling grammar below is the strongest working hypothesis for how the inner display will be browsed and rendered by the App Store, based on precedent from iPad split-view product pages. Apple's specifications currently list both portrait and landscape as supported dimensions without naming a default. Treat the principles below as the design direction to prototype toward — not a confirmed rendering behavior — and validate against real App Store Connect previews once upload access opens.

Here is where most ASO teams will make the expensive mistake: they will hand the new specs to a designer and ask for "the same screenshots but horizontal." This produces technically compliant assets that do zero conversion work.

The inner display changes the storytelling grammar. On a tall portrait screenshot, you lead with a hero visual at the top and read downward. On a near-square or landscape canvas, the eye moves laterally — the "hero moment" can live left-right, with enough horizontal real estate to show context (UI alongside outcome, feature alongside benefit) in a single frame rather than across a sequence.

Mostrar imagen

Three Visual Storytelling Principles for the Inner Display

1. Use the width to show cause and effect in one frame. Portrait screenshots typically show one UI state per frame. A landscape-oriented inner display frame can show the action (left panel) and the result (right panel) simultaneously. For a fintech app: input screen → portfolio outcome. For a game: character selection → gameplay moment. This is storytelling compression — more conversion signal per screenshot.

2. Anchor text to the left, spectacle to the right. Western reading patterns mean the left side of a landscape frame carries the explanatory load, and the right side carries the emotional payload. Headline copy and feature callouts belong left. Visual proof — the UI, the moment, the delight — belongs right.

3. Design for the unfolded moment, not the unfolded user. Someone who unfolds their iPhone Duo to browse the App Store is signaling intent — they've committed physical effort to open the device and are in evaluation mode, not passive browsing. Your inner display screenshots should match that energy. Go deeper, not broader.

The Cover Screen: Don't Neglect the First-Touch Moment

It is tempting to treat the cover display screenshots as "the old ones" and focus creative energy on the inner display. Resist this. The cover screen is where impulse discovery happens — notifications, quick searches, one-handed App Store sessions. Users may browse and install without ever unfolding the device, especially for utility and social apps.

Your cover screen screenshots need to work as a standalone conversion unit, not as a teaser for the inner display experience:

• First screenshot carries full conversion weight — assume the user sees one frame.

• Text legibility at small render sizes (App Store search grid) must be tested against the cover display's narrower ~1.45:1 proportions.

• If your app has a standout feature that works in cover screen / compact mode, lead with it here — reinforce the use case that matches the context.

ASO Readiness Checklist: iPhone Duo Launch Preparation

Use this as your team's pre-launch audit framework. Treat anything unchecked as a conversion risk, not a cosmetic gap.

Specs & Asset Production

• Inner display screenshot set designed natively at 2007 × 2853 px (not resized from standard portrait)

• Cover display screenshot set designed natively at 1398 × 2034 px — audited for narrower ~1.45:1 proportions, text and UI not clipping

• Both portrait and landscape variants prepared for the inner display, given no confirmed default orientation

• Recheck Apple's official screenshot specifications page for any updates before final asset lock

• App Preview videos reviewed for both display states — vertical video will letterbox if the inner display renders in landscape

Storytelling & Messaging

• Inner display screenshots prototyped in landscape storytelling grammar, with a portrait fallback ready

• First screenshot in each set carries standalone conversion weight

• Feature callouts audited for relevance to fold-state context (multitasking features prominently in inner display set)

• A/B test roadmap defined for post-launch — don't lock in assumptions before you have data

Technical & Submission

• Confirm App Store Connect upload access has opened before scheduling submission — Apple has stated this is a later-2026 rollout, not available at device launch

• Screenshot previews validated in TestFlight or Xcode simulator against confirmed pixel dimensions

• Localized screenshot sets flagged for update — text expansion in EU languages will hit differently on a landscape canvas

• App icon reviewed for inner display home screen rendering (larger grid context)

Analytics & Iteration

• Conversion tracking segmented by device type at launch — you need clean Duo vs. non-Duo data from day one

• Impression-to-install rate benchmarked pre-launch so post-launch deltas are meaningful

• Creative refresh cycle accelerated — expect to iterate faster than usual as user behavior patterns on the new form factor stabilize

What Happens to Teams That Treat This as a Compliance Checkbox

The App Store conversion data from the iPhone X launch is instructive. Apps that updated screenshots for the new aspect ratio but didn't redesign their storytelling saw modest conversion improvements. Apps that actually rethought their first-impression narrative for the new canvas saw outsized gains in the months following launch.

The iPhone Duo gap will be wider. The form factor difference between a cover screen and an unfolded inner display is larger than anything the iPhone line has produced before. Teams that ship resized assets will look like they didn't notice the hardware changed. Teams that rethink their visual narrative for two distinct contexts will capture conversion lift from early adopters at precisely the moment adoption curves are steepest and CPIs are most efficient.

The Mindset That Separates Readiness from Reaction

The App Store is not a filing cabinet where you deposit correctly sized images. It is a conversion environment that reflects — or fails to reflect — how your users actually experience your product.

The iPhone Duo changes the experience of finding your app before it changes the experience of using it. A user unfolding their device to browse is in a different cognitive state than a user scrolling one-handed on a cover screen. Those are different people, in different moments, making different kinds of decisions. Your screenshots need to know which person they're talking to.

The teams that will win the iPhone Duo ASO moment are not the ones with the fastest design turnaround on new specs. They are the ones who asked, before touching a single template: what does this new form factor reveal about how our users want to engage with our app — and have we ever actually shown them that in the App Store?

Resize is a response. Rethink is a strategy.

FAQ

What are the confirmed screenshot dimensions for iPhone Duo? Per Apple's official specifications: 1398 × 2034 px (portrait) or 2034 × 1398 px (landscape) for the outer display, and 2007 × 2853 px (portrait) or 2853 × 2007 px (landscape) for the inner display. Both orientations are listed as supported for each display, with no confirmed default.

Can I upload iPhone Duo screenshots to App Store Connect right now? No. Apple's documentation states that upload support for this device "will be available later this year" — meaning it isn't live at device announcement. Use this window to design and finalize assets so you're ready the moment uploads open.

Should our inner display screenshots be portrait or landscape? Unconfirmed by Apple. Both orientations are technically supported. The strongest working hypothesis, based on iPad split-view precedent, favors landscape storytelling — but prepare a portrait fallback and validate against real App Store Connect previews once upload access opens.

Preparing your App Store assets for iPhone Duo? Appvertiser AI helps ASO and growth teams move from spec compliance to genuine conversion strategy — production-ready screenshot sets, display-state storytelling, and a testing roadmap built for launch day. See how our ASO growth services can get your Duo assets launch-ready →