App Store screenshot sizes (2026 reference)

App Store Connect accepts screenshots only at a fixed list of pixel sizes per device class, and you need at least one screenshot for the required iPhone class (and for iPad 13-inch if your app runs on iPad). Upload at the largest size your app supports and App Store Connect scales it down for the smaller classes, unless you choose to upload sizes tailored to each one.

Checked against Apple's screenshot specifications on 2026-11-03. Apple changes this list when new devices ship, so check the page before you produce a new set.

The general rules

From Apple's specification page:

• Count: at least one screenshot, and up to 10 screenshots per device size.
• Formats: .jpeg, .jpg or .png.
• Transparency: images can't include alpha channels or transparencies. Export a flat image with an opaque background.
• Content: screenshots must follow the App Store Review Guidelines.
• Colour: the specification page does not state a colour profile requirement.

Which sizes are required

Apple's page lists two required display sizes to submit an app:

• iPhone: at least one screenshot for iPhone with Dynamic Island (medium display).
• iPad, if your app supports iPadOS: at least one screenshot for the iPad 13-inch display.

Mac, Apple TV, Apple Vision Pro and Apple Watch screenshots are each marked "Required" for apps on that platform.

The device rows add a second statement for iPhone: the iPhone with Face ID (large display) row is marked "Required if app runs on iPhone and screenshots for iPhone with Dynamic Island (large display) aren't provided". That row adds a condition the summary at the top does not list. The safe reading is to provide both Dynamic Island classes, large and medium, at their accepted sizes.

Scaling

If your interface looks the same across device sizes and localizations, Apple says you only need screenshots for the highest required resolution, and App Store Connect scales them down for smaller sizes. Each class below names the class whose screenshots are scaled in when you provide none. You can still upload screenshots tailored to each device size and localization.

iPhone

Apple groups iPhones by display type, not by diagonal size. Each class accepts any one of its listed sizes; the page does not tie each size to a single model.

On iPhone Duo, Apple's page says that starting in April 2027 screenshots will be required for any app using the iOS 27.1 SDK or later, and that submitting iPhone Duo screenshots shows a badge on your product page saying the app is optimized for iPhone Duo.

Apple still lists two older classes, with separate sizes with and without the status bar:

These figures are transcribed as Apple lists them, including the landscape values without status bar.

iPad

In practice, one set at a 13-inch size covers every iPad class through scaling.

Mac, Apple TV, Apple Vision Pro and Apple Watch

For Apple Watch, Apple asks you to use the same screenshot size consistently across all localizations of the app.

Google Play's listing graphics

Google Play uses ranges and ratios rather than a fixed list. Checked against Google's Add preview assets to showcase your app on 2026-11-03.

Google's page gives a 3840 px maximum in the general screenshot rules and a range up to 7,680 px for large screens; it does not reconcile the two. Staying at or below 3840 px on the long side satisfies both.

Producing a set without surprises

A few habits save a rejected upload or a blurry listing:

• Match an accepted size exactly. Apple lists exact pixel sizes, not ranges. Capture on a device or simulator in the class and check the pixel size of each file before uploading.
• Design at the largest size and export down. Text and fine lines stay sharp when an image is reduced, not when it is enlarged.
• Flatten before export. A PNG export can keep a transparent background, and Apple's rule is that images can't include alpha channels or transparencies.
• Keep one orientation per set where you can. A row that switches between portrait and landscape is harder to read while swiping.
• Write down what you uploaded and when. The date of a screenshot change is what lets you read the numbers around it later.

Example (a fictional app)

A developer ships a recipe app for iPhone and iPad, portrait only, with the same layout everywhere. They capture five screens on a large Dynamic Island iPhone simulator at 1320 × 2868 and on a medium one at 1206 × 2622, and five on a 13-inch iPad at 2064 × 2752. They export PNGs with no transparency and upload them in the English localization. App Store Connect scales them for the older iPhone and iPad classes. For a German localization, they upload the same layouts with translated captions at the same sizes.

When they later rework the first screenshot, they record the date, so the periods before and after can be compared on App Store Connect's conversion rate rather than judged by eye.

Where this shows up in Indevaro

Indevaro does not produce, resize or upload screenshots; you do that in App Store Connect or Play Console. What it can do is show App Store Connect's daily product page views and downloads, so you can look at the weeks before and after a screenshot change. It does not tell you whether the screenshots were the reason for any difference. For testing screenshots properly, the stores' own tools split traffic for you: product page optimization on the App Store and store listing experiments on Google Play. What is ASO covers how screenshots fit the rest of the listing.