App Store Screenshot Sizes at a Glance
If you're searching for app store screenshot sizes, you've probably got a screenshot open in one window and App Store Connect or the Google Play Console open in another, trying to work out why the export won't upload. Here's the short version: Apple and Google each set their own pixel requirements, those requirements are grouped by device display size rather than by every individual model, and you need fewer uploads than the full device list makes it look.
| Platform | What you upload | Varies by |
|---|---|---|
| iPhone | Screenshots sized to Apple's iPhone display classes | Display size class, not individual model |
| iPad | Screenshots sized to Apple's iPad display classes | Display size class, not generation |
| Mac, Apple TV, Apple Watch | Each platform has its own required resolution | Platform |
| Google Play — phone | Screenshots within Google's accepted pixel range and aspect ratio | Aspect ratio limits |
| Google Play — tablet | A separate size range from phone screenshots | Tablet display size |
| Google Play — feature graphic | One fixed-size graphic for your store listing | Same size for every app |
Apple and Google both update these numbers themselves, and both have changed them before when new devices shipped — most recently around the iPhone 16 lineup. A pixel number printed in a blog post can be out of date within months. So this guide explains how the sizing logic works; for the exact current pixel dimensions for every device and both stores, use our screenshot size reference — that's what it's built for.
iPhone Screenshot Sizes
Apple doesn't ask you to upload a screenshot for every iPhone model it has ever sold. App Store Connect groups iPhones into a handful of display size classes, and you upload one screenshot set per class. Several iPhone models usually share the same class, so a single export covers all of them — you don't need a unique shot for, say, every storage or colour variant, or even for every model name released in a given year.
When Apple adds a new display size, as it has with recent iPhone lineups including the iPhone 16, it can add a new class to the list, and the current list moves. Rather than freeze a set of numbers here that will be wrong by next year's device launch, check our screenshot size reference for the current iPhone classes and their pixel dimensions.
iPad Screenshot Sizes
iPad follows the same logic as iPhone. Apple defines display size classes for iPad instead of requiring a screenshot per model, and most iPad generations fall into one of a small number of classes. If you support iPad, you're exporting per class, not per generation.
The exact dimensions for each current iPad class are in our screenshot size reference, alongside the iPhone classes, so you can check both platforms in one place instead of two separate tables.
Google Play Screenshot Sizes
Google Play's requirements are structured differently from Apple's. Instead of named display classes, the Google Play Console defines an accepted pixel range and aspect ratio for phone screenshots, a separate range for tablet screenshots, and one fixed-size feature graphic that sits on your store listing page regardless of device.
For the Android-specific breakdown, see our guide to Android app store screenshot sizes. To see Apple's and Google's current numbers side by side, screenshot sizes covers both.
What Happens If Your Screenshot Is the Wrong Size
Both App Store Connect and the Google Play Console validate screenshots against their accepted dimensions before your listing can go live — if a file falls outside what's currently accepted, you won't be able to publish it as-is. Exactly how each platform handles that (a hard rejection versus a prompt to resize) can change as Apple and Google update their own submission tools, so if you need the precise current behavior, each platform's own submission guidance is the place to confirm it.
What doesn't change is the practical fix: export your screenshots directly at the sizes each class or platform calls for, rather than resizing a finished design afterward and hoping it scales cleanly. Stretching or cropping an export to fit after the fact is where text gets clipped and mockups end up off-centre — a problem you avoid entirely by building at the right dimensions from the start.
Do You Need a Different Screenshot for Every Device?
No, and this is the part most explainers skip. Apple requires screenshots per display size class, not per iPhone or iPad model — a single correctly-sized export covers every device that shares that class, which is usually most of the current lineup. Google Play works on a similar principle: one phone screenshot set sized to its accepted range, and a separate tablet set if you support tablets.
What you don't get is one universal size that covers iPhone, iPad, and every Android screen at once. Apple and Google each set their own specs, and within each platform the classes differ by device type. The practical minimum is one set per display class, per platform you support — fewer uploads than the device list suggests, but not down to a single image for everything.
How to Create Screenshots in the Right Sizes Fast
Once you know which sizes you need, the fastest path is generating them directly in those dimensions rather than designing once and resizing six different ways afterward. AppShots takes raw iOS and Android screenshots and turns them into store-ready marketing screenshots — device mockups, headlines, feature callouts, backgrounds — exported directly to the sizes each store expects, without needing Photoshop, Figma, or a designer on hand.
For the design side of this — what actually makes a screenshot worth looking at once it's the right size — see how to make good app store screenshots. The app screenshot generator covers the tool end to end, and pricing is there for when you're ready to set it up. For the wider picture on App Store screenshots beyond sizing — strategy, layout, ordering — see App Store screenshots.
FAQ
What size are App Store screenshots in 2026? It depends on which iPhone or iPad display class, or which Google Play asset, you're exporting for — Apple and Google each set and periodically update their own numbers. Screenshot sizes has the current pixel dimensions for every class on both platforms.
Can I use one image for all iPhones? Within a display size class, yes — Apple groups models by display size rather than requiring a unique screenshot per model name, so one correctly-sized export covers every iPhone that shares that class.
Do iOS and Android need different screenshot sizes? Yes. Apple and Google set their requirements independently, with different structures — Apple's organized by display size class, Google Play's by accepted pixel range and aspect ratio, plus a separate feature graphic Apple doesn't require.
What's the fastest way to get every required size without resizing by hand? Generate screenshots directly at the required dimensions instead of designing once and resizing afterward. See the app screenshot generator for how that works in practice.
