iPhone Duo is here - and it's not one screenshot size, it's two

Clican — Fri, 16 Oct 2026 02:09:36 +0000

iPhone Duo ships with two displays that share an aspect ratio but not a pixel size: the outer screen is 1398 x 2034 and the inner one 2007 x 2853. App Store Connect treats them as two separate device classes - supplying one does not cover the other. So if your app runs on Duo, "a set of screenshots" quietly became "two sets of screenshots".

Here's what actually changes, and how to produce both sets without redoing your layouts twice.

What a foldable changes

The ratio is the same, so your content scales proportionally. The pixel dimensions are not, and neither is the placement: folded and unfolded screenshots go to their own slots in App Store Connect.

The practical consequence is layout, not just size. A headline that breathes on the wide inner display looks cramped once it's squeezed into the narrower outer body, and a dense layout built for the outer screen wastes half the inner one. Trying to make a single layout "fit both" is where most of the time goes.

Two canvases, one template set

The screenshot studio in my app (Store Connect Studio, macOS) now handles iPhone Duo as two first-class device classes:

iPhone Duo Folded - outer display, 1398 x 2034
iPhone Duo Unfolded - inner display, 2007 x 2853

Each is its own canvas, so copy, screenshot slots and assets are tuned independently - no forcing one layout onto two bodies. The 46 built-in template sets all carry page data for both classes, scaled proportionally from the iPhone canvas, so you open a template and export straight away.

The device frame was redrawn to match the real hardware rather than a generic rounded rectangle: the unfolded inner display has an under-display camera and no Dynamic Island, the hinge side keeps square corners, and small hinge-crease indentations sit at the middle of the left and right edges. The folded outer display has a single punch-hole camera in the top-right.

Vertical templates also carry a landscape twin that edits and exports separately. When you're done, you can push to App Store Connect from the app with your own API key - the folded and unfolded sets land in their respective placements, no uploading folder by folder in the browser.

We shipped it on our own app first

This isn't theoretical: our app AI Worksheet Cleaner has refreshed its App Store screenshots and completed iPhone Duo support. The same template set exports to both canvases, so Duo users see layouts built for the larger screen instead of a stretched iPhone layout.

The two renders below are that template on each canvas (built-in "Erase the test paper" template, placeholder screenshot slots):

Quick tips

Provide both sets if your app supports Duo. One does not substitute for the other in App Store Connect.
Don't reuse your 6.9-inch iPhone screenshots as-is. They'll be rejected - the accepted pixel list is exact.
Tune the two canvases separately. The inner display genuinely has more room; use it, and keep the outer display's message tight.
Portrait and landscape are separate uploads, so budget for both orientations.

Full walkthrough, with the exact pixel sizes and the studio workflow:
https://anaxkg.com/en/store-connect-studio/iphone-duo-screenshot-templates/

If you're shipping a foldable-friendly app, the App Store side is easy to underestimate - two more canvases, two more sets, two more chances to get the sizes wrong.

App Store screenshot sizes: what you actually have to upload

Clican — Mon, 12 Oct 2026 10:28:18 +0000

App Store Connect doesn't scale your screenshots and doesn't check proportions.
It matches your file against a list of allowed pixel sizes - if the width or
height is off by a few pixels, the upload is simply flagged invalid. A wrong
size usually means a blocked release and a fresh wait in the review queue.

Here's the size list as it actually stands, plus the three mistakes that cause
most rejections.

The sizes you have to provide

iPhone - you need at least one set for the large Dynamic Island display:

Native size	Also accepted	Notes
1320 x 2868 (portrait)	1290 x 2796, 1260 x 2736	6.9" class - this is the required set

The 6.7" class no longer exists on its own; older 1290 x 2796 shots fall into
this slot. The 6.5" size (1284 x 2778 or 1242 x 2688) is required only if you
don't supply the 6.9" set.

iPad - if your app supports iPadOS, a 13" set is required:

Native size	Also accepted
2064 x 2752	2048 x 2732 (12.9")

If the UI is identical across sizes and locales, upload only the
highest-resolution set - App Store Connect downscales it for smaller devices
automatically.

The 3 most common mistakes

Dimensions a few pixels off. Almost always the wrong device canvas, or manual cropping in a graphics tool.
A leftover alpha channel. PNGs exported from Figma, Sketch or a canvas can keep transparency data even when every pixel is opaque, and App Store Connect rejects them outright. Export as JPEG, or flatten onto a solid background.
Missing screenshots for some locales. Every region you publish should carry screenshots in its language.

Two smaller traps worth knowing: a status bar showing a real carrier, full
signal or a nearly-empty battery looks unprofessional; and screenshots that show
features not actually in the build will draw questions at review.

Exporting every size in one pass

Placing and exporting each size by hand is slow and error-prone. A screenshot
studio ships with device canvases and official colored frames, so you drop in a
UI capture and it snaps to the exact pixels.

Store Connect Studio (my app, macOS) exports at the official sizes and
includes a magnifier for pixel-level checks. Screenshots and multilingual copy
live in the same workspace, then sync in one click via your own App Store
Connect API key.

Full walkthrough: https://anaxkg.com/en/store-connect-studio/app-store-screenshot-sizes/

DEV Community: Clican