iPhone Duo Screenshot Sizes: Inner, Outer & App Store Requirements

iPhone Duo screenshot dimensions and the requirement date

Apple’s screenshot reference lists separate inner and outer targets. The table below describes the complete upload image, not the screen rectangle inside a device mockup. Check the current Apple specification again when preparing the release; deadlines and accepted targets can change.

A Duo screenshot, a mockup, and a search creative are different assets

The app capture is evidence of the interface. The screenshot canvas is the store deliverable: it can contain a headline, supporting artwork, and an optional device frame. The Duo model is the presentation layer inside that canvas. Choosing it does not change the app’s actual UI or prove that the app supports both displays.

Keep product page headers and search-result artwork in another export set. Those placements introduce an app story; screenshots should demonstrate it. If a campaign needs a foldable-device visual in its header, reuse the brand direction but recompose the artwork for the header placement rather than uploading a screenshot into the wrong slot.

Prepare the source captures before styling

Start with the app state you want a prospective user to understand. For example, a planning app might show a focused route summary on the outer display and a map with a useful detail pane on the inner display—only if those are real supported interfaces. Do not stretch a narrow capture to fill the larger canvas or invent a split-view layout that the app cannot produce.

Use consistent demo data, account state, language, and feature availability across the pair. Remove private information and notifications. Keep a small capture inventory that records which display, orientation, app build, and language each source represents. This makes a future release refresh much safer than guessing from exported filenames.

• Check the actual app experience on each target display before making a marketing claim.
• Capture a complete state with readable content, not an empty loading view.
• Use content you own or have permission to display.
• Keep the unstyled captures alongside the editable design project.

Create and export the Duo set in AppLaunchFlow

Open the screenshot workflow and upload your app captures. Build the main story first, then select the Duo model and the display canvas you want to refine. The editor includes device poses and fold controls; use them to preserve a clear view of the UI. A dramatic angle is useful only when the product remains understandable.

Phone sizes can be edited independently. Untouched sizes follow the main layout, so verify the selected canvas before changing caption position, device scale, or spacing. Treat the inner and outer layouts as related designs, not identical crops. Check localized headlines separately because a line that fits one canvas can wrap awkwardly on the other.

In Download Bundle, select the required Duo sizes and inspect the exported files. The recording below shows the editor and export selection. It does not demonstrate a completed Apple review or prove that the illustrative app is a customer.

A practical Duo screenshot QA checklist

Run two reviews: one for technical acceptance and one for communication. The file can have the right dimensions and still tell the wrong story. Inspect the original export at full size, then view it as a small store thumbnail. Keep a short release checklist so the same checks happen after every design or localization change.

• Target: inner and outer files are clearly distinguished; portrait and landscape are not accidentally swapped.
• File: the complete image matches the chosen Apple target and contains no transparency.
• Accuracy: each screenshot represents the app build and the actual display experience.
• Composition: captions, device edges, and important UI are not clipped or obscured by the fold.
• Localization: translated headlines remain legible and match the UI language.
• Handoff: preview the selected files in App Store Connect and resolve any account-specific validation errors before submission.

What should you test after the new set is ready?

Treat device readiness and conversion experimentation as separate jobs. First produce an accurate, technically valid set. Then write a focused hypothesis about the first screenshot, story order, or message. If you change the device, headline, background, and feature order together, a result cannot tell you which individual decision mattered.

Do not interpret the introduction of a new display size as a guaranteed conversion improvement. Use a stable baseline and Apple’s experiment reporting where eligible. If the goal is a persistent page for a particular campaign, a custom product page may be the better tool.