App Store Screenshot Sizes 2026: The Complete iPhone, iPad, and Google Play Dimensions Chart

Why screenshot dimensions still trip people up in 2026

Every year, a new device launches, Apple or Google quietly updates a spec page, and thousands of app listings end up with screenshots that are stretched, cropped oddly, or rejected outright at submission. Screenshot dimensions feel like they should be a solved problem by now, but they aren't: display sizes keep changing (this year's round of Pro Max and foldable devices being the latest example), and both stores handle "which sizes are actually required" differently enough that even experienced developers get it wrong.

This is meant to be a working reference, not a one-time read. Bookmark it, but also build a habit of checking App Store Connect and Google Play Console directly before a submission, since exact required display classes shift when new hardware ships.

App Store Connect: current iPhone screenshot sizes

Apple organizes screenshots by "display size class" rather than by device name, and it only requires you to upload for one or two of the largest classes in each device family. Once you upload the largest size, App Store Connect can scale it down to cover smaller, compatible devices automatically, so you don't need a unique image for every iPhone that has ever shipped.

The display classes you'll typically see in App Store Connect today:

• 6.9 inch / 6.7 inch class (current and recent Pro Max and Plus models): roughly 1290 x 2796 px portrait, or the equivalent 1320 x 2868 px on the newest Pro Max hardware, depending on which generation Apple has most recently added
• 6.5 inch class (older Max-size iPhones still in the install base): 1242 x 2688 px portrait
• 6.1 inch class (standard-size iPhones): 1179 x 2556 px portrait
• 5.5 inch class (legacy Plus-size iPhones some users still run): 1242 x 2208 px portrait

Landscape orientation simply flips the width and height values. You can upload up to 10 screenshots per display class, but realistically the first three are what most users see before they either keep scrolling or tap install, so treat those first three like a mini landing page.

Because Apple periodically adds a new top-tier size class when it releases a larger flagship phone, the safest approach is to design your master screenshot at the highest resolution currently listed in App Store Connect for your target devices, then let Apple's scaling handle the rest, and re-check that master size every time Apple ships new hardware.

iPad screenshot requirements

If your app supports iPad at all, iPad-specific screenshots are not optional; Apple treats iPad as a separate device class from iPhone entirely, and a listing with only iPhone screenshots will fail review for an app with iPad support enabled. The commonly required iPad classes are:

• 12.9 inch (iPad Pro): 2048 x 2732 px portrait
• 11 inch: 1668 x 2388 px portrait
• 10.5 inch: 1668 x 2224 px portrait
• 9.7 inch (standard iPad): 1536 x 2048 px portrait

As with iPhone, you generally only need to supply the largest class you're targeting and let Apple scale down, but always confirm the current minimum requirement in App Store Connect at submission time, since Apple has changed which classes are mandatory more than once in recent years.

Google Play screenshot and feature graphic specs

Google Play is more forgiving on exact pixel counts and instead works within ranges, which is both easier and easier to get subtly wrong:

• Phone screenshots: any dimension between 320 px and 3,840 px per side, with 1080 x 1920 px (portrait) being the practical sweet spot most developers use. You need a minimum of 2 screenshots and can upload up to 8.
• Tablet screenshots (7 inch and 10 inch): same 9:16 or 16:9 aspect ratio guidance, sized between 1,080 px and 7,680 px per side. Google now recommends at least 4 tablet screenshots if you want your listing considered for tablet-specific featuring.
• Feature graphic: a fixed 1,024 x 500 px banner, no alpha transparency allowed. This one is mandatory for every listing regardless of category, and it's the image most developers forget about until the upload form rejects an empty field.

Google's aspect-ratio flexibility is convenient, but it also means a screenshot that looks fine in your local preview can appear differently cropped once Google Play resizes it across phone, tablet, and Play Store web listing surfaces. Always preview on an actual device or the Play Console's own preview tool before publishing, not just in a design file.

Common mistakes that get screenshots rejected or stretched

A few patterns show up again and again in submission rejections and support forums:

Uploading a single image size and assuming both stores will scale it identically. They don't; Apple's scaling logic and Google's range-based system behave differently, and an image built for one store's aspect ratio often gets awkwardly cropped on the other.

Designing screenshots with critical text or UI elements too close to the edge. Both stores' preview thumbnails crop more aggressively than the full-size image, so headline text and key visuals should stay well inside a safe margin, not flush against the border.

Mixing orientation without checking device support. A landscape-only screenshot set on a phone listing where most traffic is portrait-first mobile browsing will underperform even if it's technically compliant.

Forgetting to update screenshots after a UI redesign. Stale screenshots showing an old interface are one of the most common causes of negative first-week reviews, since new users immediately notice the app doesn't match what they were shown.

Keeping every size in sync without redoing the work manually

The tedious part of all this isn't knowing the dimensions, it's producing and maintaining correctly sized, on-brand screenshots across every required class, for every locale, every time you ship a redesign or a new device size gets added. Doing that by hand in a design tool for four iPhone classes, four iPad classes, and two Google Play formats multiplies fast, especially if you're also localizing into multiple languages.

This is the exact problem WhixFrame's Screenshot Studio is built to solve: you design your screenshot templates once, and it generates every required App Store and Google Play size automatically, keeping text, backgrounds, and device frames consistent across the full set instead of manually resizing and re-exporting each variant. It's worth a look if you're currently maintaining these sizes by hand in Figma or Photoshop and re-exporting on every update.

Quick reference checklist

Before your next submission, confirm you have current, correctly sized assets for: the largest required iPhone display class, at least one legacy iPhone class if your minimum OS support goes back far enough to need it, iPad screenshots if iPad support is enabled, Google Play phone screenshots within the accepted pixel range, at least 4 tablet screenshots if you want tablet featuring eligibility, and a compliant 1,024 x 500 px feature graphic for Google Play. Check both consoles' current specification pages directly before uploading, since these numbers shift whenever new hardware ships, and a five-minute check beats a rejected build.