App Store Screenshot Sizes & Dimensions Guide 2026

Before a screenshot can convert anyone, it has to be the right size to be accepted at all. Getting app store screenshot dimensions right is the unglamorous foundation of your creative work — get it wrong and you face rejections, blurry images, or awkward cropping that undermines even beautiful design. This guide lays out the sizes for iOS and Android in 2026 and how to avoid the common technical mistakes.

For the requirements and submission rules, see our guide to App Store screenshot requirements; for the Android specifics, Google Play screenshot sizes.

Why exact sizes matter

It is tempting to treat dimensions as a technicality, but they have real consequences for both acceptance and quality. If your images do not match the required app store screen shot sizes, Apple may reject them outright, delaying your release. If they are scaled or cropped incorrectly, captions can be cut off and visuals distorted, quietly hurting the conversion you worked hard to design. And because you often produce localized and tested variants, getting the base dimensions right once — ideally in a template — saves compounding errors across every version. Precision here is not pedantry; it is what lets your design actually reach users as intended.

iOS screenshot dimensions

Apple defines screenshot sizes by device class, in exact pixel resolutions. The key sizes to provide are the largest iPhone displays, since Apple can use those to represent smaller devices in some cases. In practice, most teams create their screenshots at the largest required iPhone resolution and, if they support iPad, a corresponding tablet resolution. Because Apple's exact requirements evolve as new devices launch, the safest approach is to check the current specification in App Store Connect or use a generator that stays updated, rather than relying on a number you memorized last year. The principle to remember is that iOS wants specific, exact resolutions per device class — there is little flexibility, so match them precisely.

Android screenshot dimensions

Google Play takes a more flexible approach to android app store screenshot sizes. For phone screenshots, Google accepts a range — each side between 320 and 3840 pixels, with the longer side no more than twice the shorter — which gives you latitude in aspect ratio. The google play app screenshot size guidance also includes recommended dimensions that display well across devices, and separate sizing for tablets if you target them. This flexibility is convenient, but it does not mean size is unimportant: choosing a clean, high-resolution size that displays crisply and consistently still matters for how professional your listing looks. A common practical choice is to design at a high resolution within the accepted range and keep every frame the same dimensions for a consistent set.

A quick reference

While exact numbers change over time, the shape of the requirements is stable:

Treat this as the mental model, and confirm the precise current numbers in App Store Connect and Play Console before you export, since specifications update as new devices ship.

Avoiding rejections and quality issues

Most sizing problems trace back to a few habits. Designing without a template means every frame risks a slightly different size. Reusing an old specification means you may miss a change in required dimensions. Exporting at low resolution produces blurry images that look unprofessional at full size. And forgetting tablet sizes, when you support tablets, leaves gaps in your listing. The fix for all of these is to work from a current, correctly-sized template — whether hand-built or from a generator — and to export at full resolution. This turns sizing from a recurring source of errors into a solved problem you rarely think about.

A worked example

A team supporting both iPhone and iPad, on iOS and Android, wants to avoid sizing headaches. Rather than manage four sets of dimensions ad hoc, they build a master template at the largest required iPhone resolution and a second at the iPad resolution, then a consistent high-resolution size within Google Play's accepted range for Android. Every screenshot they design or localize starts from the correct template, so nothing is ever the wrong size. When Apple later updates a required resolution, they update one template rather than re-cropping dozens of images. This template-first discipline turns app store image sizes from a per-release scramble into a background non-issue, freeing their attention for the message and design that actually drive conversion.

Common sizing mistakes

The frequent errors are designing without a template and ending up with inconsistent sizes, relying on outdated specifications, exporting at low resolution, ignoring tablet sizes when relevant, and letting cropping cut off captions. Each is avoidable with a current template and a full-resolution export, and each is worth avoiding because a technically flawed image undermines even the best design.

Keeping up as device sizes change

One reason dimensions cause recurring headaches is that they are a moving target. Every time Apple launches a new iPhone or iPad with a different display, the set of required or recommended resolutions can shift, and a specification you relied on last year may be incomplete today. Android is more stable because of its flexible range, but new device form factors and Google's own recommendations still evolve. The practical defense against this churn is to avoid hardcoding numbers into your memory or your workflow and instead treat the current specification as something you confirm at export time — either in App Store Connect and Play Console directly, or through a generator that maintains up-to-date sizes. Teams that build their creatives on a template tied to current specs adapt to a device change by updating one template, while teams that produced each image ad hoc face a scramble to re-crop dozens of frames. This is a small operational discipline with an outsized payoff: it turns an annual source of last-minute stress into a routine check. As stores continue to add device classes and placements, the value of a maintainable, spec-current creative pipeline only grows, which is another reason many teams eventually hand the whole creative operation to a partner who keeps it current for them.

Let AppsLift handle your creatives end to end

Getting dimensions right is the floor, not the ceiling — designing a converting, tested, localized, correctly-sized set and ranking the keywords that bring the traffic is the full job. AppsLift handles all of it. Since 2012 we have pushed 400+ iOS and Android apps to the top of store search, pairing keyword rankings with the conversion optimization that turns impressions into installs.

Start with a free AppsLift audit: paste your app link, pick your markets, and see your real keyword positions plus the install value of the Top 3. When you want your creatives and rankings handled for you, talk to our team. Next, read our guide to App Store screenshot requirements.