App Store screenshot sizes and dimensions (2026 guide)

The short answer, if that is all you came for: export one iPhone set at 1320 × 2868 and, if your app runs on iPad, one set at 2064 × 2752. That covers the App Store. For Google Play, export the same designs at 1080 × 1920 or larger, staying under 3840 pixels on the long side. Everything below is the detail behind those numbers, checked against Apple and Google documentation in August 2026.

It is worth checking, because most of the size guides currently ranking are out of date. Several still present 1290 × 2796 as the single required iPhone size, one still treats the 6.7 inch display as the requirement, and at least one publishes invented per-device pixel targets for Google Play that Google has never specified.

App Store: what Apple actually requires

Apple requires one screenshot set per device family your app supports, and it generates the rest. The rules that apply to every upload:

1 to 10 screenshots per localization
PNG or JPEG only
No alpha channel and no transparency, which is the single most common cause of a rejected upload
Exact pixel dimensions from the accepted list, not approximations

iPhone sizes

Display	Portrait	Required?
6.9″	1260 × 2736, 1290 × 2796, 1320 × 2868	Yes, if the app runs on iPhone
6.5″	1284 × 2778, 1242 × 2688	Only if you skip 6.9″
6.3″	1179 × 2556, 1206 × 2622	Optional
6.1″	1170 × 2532, 1125 × 2436, 1080 × 2340	Optional
5.5″	1242 × 2208	Optional
4.7″	750 × 1334	Optional

Landscape is simply the same numbers reversed. The 6.9 inch family covers iPhone Air, iPhone 17 Pro Max, 16 Pro Max, 16 Plus, 15 Pro Max, 15 Plus and 14 Pro Max.

iPad sizes

Display	Portrait	Required?
13″	2064 × 2752, 2048 × 2732	Yes, if the app runs on iPad
12.9″	2048 × 2732	Optional
11″	1488 × 2266, 1668 × 2420, 1668 × 2388, 1640 × 2360	Optional
10.5″	1668 × 2224	Optional

Everything else Apple ships

Platform	Sizes
Mac	1280 × 800, 1440 × 900, 2560 × 1600, 2880 × 1800
Apple TV	1920 × 1080, 3840 × 2160
Apple Vision Pro	3840 × 2160
Apple Watch Ultra 3	422 × 514
Apple Watch Series 11 and 10	416 × 496
Apple Watch Series 9, 8, 7	396 × 484
Apple Watch Series 6, 5, 4, SE	368 × 448

Watch has one extra rule that catches people: you must use the same watch size consistently across every localization. Mixing a 416 × 496 English set with a 396 × 484 German set will fail.

The scaling cascade nobody publishes

Everyone writes “Apple scales down automatically.” Here is the actual chain, which is why supplying only the largest set is safe:

iPhone: 6.9″ falls back to 6.5″, then 6.1″, then 5.5″, then 4.7″, then 4″, then 3.5″
iPad: 13″ falls back to 12.9″, 11″, 10.5″ and 9.7″

Scaling is not free. A 1320 × 2868 design resampled to 750 × 1334 loses fine text. If your captions are small, ship a hand-tuned 4.7 inch set as well. If your captions are large, the cascade is fine.

Google Play: ranges, not fixed sizes

This is where most guides go wrong. Google does not specify a phone screenshot resolution. It specifies constraints, and any size satisfying them is valid.

Asset	Specification	Count
Phone screenshots	320 to 3840 px per side; long side no more than 2× the short side; PNG or JPEG, no alpha	Min 2 across device types, max 8 per type
Large screens (tablet, Chromebook)	1080 to 7680 px; 16:9 landscape or 9:16 portrait	Minimum 4
Wear OS	Min 384 × 384, 1:1, no device frames allowed	Minimum 1
Android XR	8:5 ratio, 3840 × 2400 recommended, max 8 MB each	4 to 8
Feature graphic	1024 × 500, JPEG or 24-bit PNG, no alpha	Required
App icon	512 × 512, 32-bit PNG with alpha, max 1024 KB	Required

Two things to notice. Google publishes no separate 7 inch and 10 inch tablet pixel targets; one large-screen specification covers both. And the icon is the one Google asset that requires an alpha channel, which is the exact opposite of the screenshot rule. Getting those two backwards is a common upload failure.

Side by side

Rule	App Store	Google Play
Sizing model	Exact pixel values from a fixed list	Range with a 2:1 constraint
Screenshot count	1 to 10 per localization	2 minimum, 8 maximum per device type
Transparency	Never allowed	Not allowed on screenshots, required on the icon
Auto-scaling	Yes, largest set covers smaller devices	No, upload per device type
Extra required graphic	None	Feature graphic 1024 × 500

Fixing the errors App Store Connect gives you

Four messages account for nearly every failed screenshot upload:

“The dimensions of one or more screenshots are wrong” usually means an export that is a pixel or two off. Design tools round when a canvas is scaled. Set the artboard to the exact target and export at 1×.
An alpha channel error means your PNG has transparency. Flatten it against a solid background before export.
A device-family mismatch means you uploaded a valid size into the wrong slot, for example a 6.5 inch export into the 6.9 inch slot.
An inconsistent watch size across localizations, as described above.

Generating the full set without a design sprint

The arithmetic is what makes this painful. Two device families, five screenshots each, ten languages is 100 image exports, all at exact dimensions, all needing translated captions. Doing that by hand in a design tool once is tedious; doing it every release is unsustainable.

A screenshot generator solves it by separating the design from the export. You build one composition, a background, a device frame, your app capture and a headline, then the tool renders it at each store size and each language. AppBoard includes a free browser-based screenshot editor that does exactly this: device mockups for iPhone, iPad, Android and Watch, gradient and mesh backgrounds, text and shape layers, one-click templates, panorama layouts that slice one wide image into consecutive store frames, and PNG export at the exact dimensions above. It runs entirely on your device, needs no account, and there is nothing to install.

Whatever tool you use, the checklist is the same. Design at the largest size. Keep captions large enough to survive scaling. Flatten before export. Keep one source file per language rather than one per language per device.

Per-locale sets are where the work really is

Screenshot sets are per localization on both stores. If your captions are baked into the images, and they almost always are, then every language you add multiplies your export count. Upload English captions to a Japanese listing and Japanese users see English captions.

This is the operational cost people underestimate when they decide to launch in twelve markets. We covered how to pick which markets are actually worth that cost in our guide to app store localization.

Sizes are the easy half

Getting the pixels right stops your upload from bouncing. It does not make anyone install your app. The order of the frames and the message on the first two do that, and most viewers never scroll past frame two, so that is where the entire conversion decision happens. We wrote about ordering and captioning in app screenshots that convert, which is the companion piece to this one.

Frequently asked questions

What size should App Store screenshots be in 2026?

Apple accepts three sizes for the 6.9 inch iPhone display: 1260 by 2736, 1290 by 2796, and 1320 by 2868 pixels in portrait. Supplying one 6.9 inch set is enough for every smaller iPhone, because Apple scales your screenshots down through 6.5, 6.3, 6.1, 5.5, 4.7, 4 and 3.5 inch displays automatically.

Do I need a different screenshot for every iPhone size?

No. You need one 6.9 inch iPhone set if your app runs on iPhone, and one 13 inch iPad set if it runs on iPad. Every other display size is optional and is generated by Apple scaling the largest set you provided.

What size are Google Play screenshots?

Google does not publish fixed pixel targets. It publishes a range: each screenshot must be between 320 and 3840 pixels on any side, and the longer side cannot be more than twice the shorter side. Google recommends at least 1080 pixels of resolution with a 16:9 or 9:16 aspect ratio. Anything quoting an exact Google phone or tablet size such as 1200 by 1920 is repeating a number Google never published.

How many screenshots can I upload to each store?

You can upload 1 to 10 screenshots per localization on the App Store. Google Play requires a minimum of 2 screenshots across different device types and allows a maximum of 8 per device type, with a minimum of 4 for large screens such as tablets and Chromebooks.

Why does App Store Connect say the dimensions of one or more screenshots are wrong?

The most common causes are an alpha channel, which Apple rejects outright, an off-by-a-few-pixels export from a design tool, or an image scaled to a size Apple does not list for that display family. Export at one of Apple's exact listed sizes, flatten the image so it has no transparency, and save as PNG or JPEG.

Can I use the same screenshots for the App Store and Google Play?

Not identically. Apple requires exact pixel dimensions with no alpha channel, and Google accepts a range with a 2:1 constraint. A 1320 by 2868 Apple export happens to satisfy Google's range, so one design can serve both, but the files themselves still need separate exports because Apple rejects transparency and Google requires a different asset set including a 1024 by 500 feature graphic.

Can I update screenshots without releasing a new app version?

Yes on both stores. Screenshots are metadata, not part of the binary, so you can replace them without shipping a new build. On the App Store, changes to a live version's screenshots go through review; on Google Play they publish through the store listing update flow.

These specifications change whenever Apple ships a new display size. This page was verified in August 2026 against Apple's App Store Connect screenshot specifications and Google Play's graphic asset requirements. If you are checking it much later than that, verify the 6.9 inch numbers before a release.