COVID-19 UPDATE 
Important Notice:Beware of scams using ASOWorld's name for part-time recruitment or ASO earning app activities. ASOWorld is not hiring any part-time staff. Trust only official information posted by ASOWorld.
TL;DR
Apple's App Store Connect reference lists iPhone Duo as its own entry with two sizes:
| Item | iPhone Duo |
|---|---|
| Outer display | 1398 × 2034 (portrait), 2034 × 1398 (landscape) |
| Inner display | 2007 × 2853 (portrait), 2853 × 2007 (landscape) |
| Quantity and format | 1 to 10 per device size; .jpeg, .jpg or .png; no alpha channel or transparency |
| Requirement | Starting April 2027, for any app using the iOS 27.1 SDK or later |
Not yet. Today the iPhone set Apple requires is still the one for the Dynamic Island devices (the 6.9" class is the usual choice), and Duo screenshots are an addition to it. From April 2027, Apple's note says Duo screenshots become required for apps built with the iOS 27.1 SDK or later. Press coverage describes the rule as applying to both new apps and updates to existing apps, so plan against Apple's SDK-based wording.
💡 Expert Tip: Don't wait for April 2027
A native Duo set takes design, localization and review time. Starting now lets you test it in PPO and CPPs well before the deadline, and gives you a polished set the day Apple opens uploads.
Apple's general display-scaling rule says that if your interface is consistent across devices and localizations, you can provide only the highest required resolution and App Store Connect scales it down. Apple has not documented what iPhone Duo users see before you supply Duo screenshots, so don't plan around a guess. Make sure your 6.9" set is strong either way.
For baseline rules on slot count, in-app-only imagery and per-locale screenshots, see ASOWorld's guide on how to optimize iOS app screenshots for the Apple App Store. It predates Duo, so use it for the fundamentals.
Apple lists the same accepted preview resolutions for Duo as for other modern iPhones: 886 × 1920 (portrait) or 1920 × 886 (landscape).
Press reports describe the displays as 5.4 inches outside and 7.6 inches inside. Aspect ratio matters more for layout than diagonal size:
| Canvas | Height ÷ width |
|---|---|
| iPhone 6.9" (1320 × 2868) | ≈ 2.17 |
| Duo outer (1398 × 2034) | ≈ 1.45 |
| Duo inner (2007 × 2853) | ≈ 1.42 |
| 13" iPad (2064 × 2752) | ≈ 1.33 |
Both Duo canvases sit much closer to an iPad than to any tall phone. That drives the creative differences below.
Apple's guidance says the system presents navigation bars, toolbars and tab bars vertically on the side of the display when the device is closed. Capture outer-display frames from the real build so this layout appears exactly as users will see it.
On the inner display, the folding region and the front camera can divide or cover content. Don't stage your hero element across the fold, and check each pose Apple describes (open, partially folded, rotated) before you pick a capture.
💡 Expert Tip: The inner set sells, the outer set is about speed
Duo buyers want proof that your app uses the extra space, so lead the inner set with a layout that only exists unfolded. Lead the outer set with an action people can complete without opening the phone.
Both orientations are accepted for both displays. Which orientation the store favors by default is not documented, so design a portrait set first. Add landscape for genuinely landscape-first apps (games, video, creative tools) and for inner-display split layouts, then validate in App Store Connect previews before you lock assets.
xcrun simctl status_bar) and load realistic demo data.💡 Expert Tip: Capture, don't stretch
Shoot from the real build at Duo resolution, then add captions. Stretching a 6.9" screenshot is the fastest way to look careless and to invite accuracy questions in review.
Search results and many browse surfaces show only the first few screenshots (for portrait apps, typically up to three) before a user opens your page. Those frames do two jobs:
Whether Duo's search cards use the outer set, the inner set or a fixed fallback is not publicly documented.
💡 Expert Tip: Put your best message in frames 1–3 of both sets
Keep the core promise identical and change only the layout. That protects you whichever set the store surfaces.
ASOWorld's guide to optimizing app screenshots, icons and videos explains why visual assets are the first thing users see in search and is a useful companion for the fundamentals.
Not Sure Where to Begin?
Skip the guesswork — launch your first campaign with ASOWorld in 3 steps.
An app preview is optional, but it leads the media row and can show motion and flow that static frames can't.
💡 Expert Tip: Check where your preview lands
Duo screenshots are much squarer than the accepted 886 × 1920 preview frame. Verify how the preview renders once uploads are available, and don't assume it keeps the lead slot.
The default poster frame is 5 seconds in, and you can choose another. Open on the outcome, not a logo.
A video doesn't always help, because it can push your screenshots down the page. Let PPO decide.
PPO tests your default product page. One test runs at a time, with up to three treatments, for up to 90 days. PPO does not test Custom Product Pages.
| Step | Action |
|---|---|
| 1. Baseline | Record 4+ weeks of impressions, page views and downloads first |
| 2. Hypothesis | One sentence: "Showing X in frame 1 raises page-view-to-download rate" |
| 3. One variable | Change order, caption or hero screen, never all three |
| 4. Run | Cover at least two full weekly cycles (our recommendation, not an Apple rule) |
| 5. Decide | Apply the winner only if it wins on the metric you chose in advance |
| 6. Log | Record every test so no one repeats it |
💡 Expert Tip: Priority test order for Duo
(1) Frame order, (2) benefit-led vs. feature-led captions, (3) UI-heavy vs. lifestyle-led frames, (4) with vs. without a preview.
Each CPP is an alternate version of your listing with its own screenshots, previews and promotional text.
| Intent | Page angle | Traffic source |
|---|---|---|
| Generic discovery | Default page (PPO-tested) | Browse, brand search |
| Task-specific search | Lead with the matching feature | Keyword-linked CPP |
| Paid acquisition | Match the ad promise | Apple Ads, social ads |
| Multitasking / productivity | Lead with the inner-display workspace | Targeted ads, partner links |
| Re-engagement | Lead with what's new | Email, owned channels |
Group your keywords by user intent before you create pages. ASOWorld's free ASO tools can help with keyword research and competitor analysis to feed that grouping.
💡 Expert Tip: Use Apple's universal link, not a shortener
Extra redirects can break attribution and the intended page match.
A translated caption over an English interface looks careless and weakens your "accurate metadata" case in review.
Rank locales by revenue and download share, not by locale count. For previews, Apple notes that if no preview exists for a language, the next best available language is shown, so know which of your locales rely on that fallback.
💡 Expert Tip: Pair CPPs with local keyword intent
A strong English CPP is not automatically a strong Japanese one. Rebuild the angle per market.
If you lack in-house capacity for multi-market creative and keyword work, ASOWorld's ASO Service covers title, subtitle and description optimization with keyword research.
Build the funnel from App Store Connect analytics. Apple has also expanded per-CPP reporting, with 100+ new metrics reported in 2025.
| Stage | Metric | Working formula (our definitions) |
|---|---|---|
| Visibility | Impressions | From App Store Connect |
| Interest | Product page views | From App Store Connect |
| Tap-through | Impression → page view | Page views ÷ impressions |
| Conversion | Page view → download (CVR) | Downloads ÷ page views |
| End-to-end | Impression → download | Downloads ÷ impressions |
Apple's own "conversion rate" definition may differ from these working formulas, so state which one you use in every report.
Track ratings, day-1 retention and refund rate. A page that converts more but attracts poor-fit users hurts you later.
💡 Expert Tip: Duo may not appear as its own segment
Apple hasn't documented a Duo device breakdown. If none appears, compare pre- and post-launch periods, use dedicated CPPs as proxies, and state that limitation in your report.
Guideline 2.3 (Accurate Metadata) is the core rule: your metadata, including screenshots and previews, must accurately reflect the app's core experience and be kept up to date with new versions.
💡 Expert Tip: Never depict an inner-display feature you haven't shipped
If a layout isn't in the build, it can't be in the screenshot. Concept art doesn't belong in submitted assets.
The guidelines were last updated June 8, 2026. Re-check the current text before you publish.
No. Today they are optional. Apple's specification page says screenshots become required from April 2027 for apps using the iOS 27.1 SDK or later. Your 6.9" iPhone set remains the baseline.
Not as of October 5. Apple says upload support will arrive "later this year." The sizes are published, so you can design and export now and upload when the slot appears in your account.
Not well. A 6.9" screenshot is about 2.17 times taller than wide, while the Duo inner display is about 1.42. Scaling one into the other letterboxes or crops it. Native Duo frames are safer for conversion.
Apple lists two sizes. If your UI is identical on both, one set may work, but you lose the chance to tell a different story per screen.
Use the iPhone Duo simulator in the latest Xcode. Build with the current SDK so the app uses the full screen, then open, close and rotate the simulated device to capture each display from one session.
Apple hasn't published Duo-specific PPO behavior. Check the test configuration screen once Duo slots open in your account.
Say so honestly. Show what the app genuinely does on the larger screen and nothing more.
Get a good start for your app optimization with practical ASO guideline！
Want to get the latest Guides & Insights from ASOWorld?
Related posts
