Journal · Guide · 6 min

App Store screenshot sizes that still get accepted in 2026

By Ziyarex ·

"The dimensions of one or more screenshots are wrong."

That's the whole error. It doesn't say which screenshot, or which dimension, or what it wanted instead. If you've shipped to the App Store you've seen it, usually at the worst possible moment.

Here are the numbers. These are cross-checked against what this studio actually has live (ueue's iPhone screenshots are 1242 × 2688, Slate's Mac screenshots are 2560 × 1600) and they're the same set our screenshot resizer targets.

App Store: iPhone

DisplayPixelsStatus
6.9″1290 × 2796required
6.9″ (alt)1320 × 2868also accepted
6.5″1242 × 2688still accepted
6.1″1179 × 2556accepted
5.5″1242 × 2208legacy

The important simplification: Apple now derives the smaller sizes from your largest ones. Supply a complete 6.9″ set and you're done: you don't have to produce four separate size families any more, which is the single biggest time saving available in this whole process.

Both portrait and landscape are fine; just don't mix orientations within one set.

App Store: iPad

DisplayPixelsStatus
13″2064 × 2752required for iPad apps
12.9″2048 × 2732accepted
11″1668 × 2388accepted

If your app ships on iPad at all, you need a real iPad set. Uploading upscaled iPhone shots is allowed by the validator and immediately obvious to anyone reading the listing.

App Store: Mac

PixelsNote
2560 × 1600the one we ship
2880 × 1800accepted
1440 × 900accepted
1280 × 800the size in-app-purchase review images want

Mac screenshots are 16:10 and must not include the desktop background outside the window unless you want it there, Apple accepts either, but a full-bleed 2560 × 1600 canvas with the window composited on a designed background looks dramatically better than a raw window grab.

App Store: Watch and TV

DevicePixels
Apple Watch 46 mm416 × 496
Apple Watch 45 mm396 × 484
Apple TV1920 × 1080

Google Play

Play is far more forgiving, it takes a ratio range instead of fixed pixels, but it has its own hard requirements.

AssetPixelsRules
Phone1080 × 19202 to 8 required
7″ tablet1200 × 1920required if you claim tablet support
10″ tablet1600 × 2560required if you claim tablet support
Feature graphic1024 × 500required, no transparency

Each side must be between 320 and 3840 px, and the aspect ratio can't exceed 16:9 in either direction. The feature graphic's no-alpha rule is a genuine rejection reason and catches people who export a PNG straight out of a design tool with a transparent artboard.

The workflow that stops this being annoying

Design once, at the largest size. Build your 6.9″ iPhone frames (1290 × 2796) and your 13″ iPad frames (2064 × 2752). Everything else is a resize.

Resize, don't re-export. Going back to the design file per size is how a screenshot set takes three hours. A resizer that fits your source into each canvas (padding rather than cropping, so nothing important is lost) turns it into one step.

Check the first two. On both stores, the first two screenshots are what appear in search results, and a large share of people never swipe past them. Whatever your best argument is, it goes in slot one.

Put words on them. A raw UI screenshot assumes the reader already understands your app. A screenshot with a five-word caption above the frame explains it to someone who's never heard of you, which is everyone in a search result.

Keep the sources. You will redo these at the next OS design refresh. A layered file beats regenerating from scratch.

The tool

Our screenshot resizer has every size on this page built in, including the Play feature graphic with its alpha stripped automatically. Drop in your source images, pick the targets, get a zip. It runs in the browser and nothing is uploaded.

Related: every app icon size, and what screenshots have to do now that discovery has moved.