A practical guide to Apple's current size classes, an editable screenshot workflow, localization review, and the checks to run before uploading to App Store Connect.
Loved by 3,000+ creators
App Store screenshots are the product images attached to an app listing. Apple accepts from one to ten files per supported device size and localization, using exact pixel dimensions. A useful set shows the current product clearly, explains the important differences, and stays readable at listing size.
Choose the part of the workflow you need now: design, localization, size checking, testing, or the separate Google Play set.
Build and export an editable iPhone and iPad screenshot set.
Localize one design into 16 locales.
Resolve Apple's “dimensions are wrong” rejection error.
Prepare creative variants for Apple and Google store experiments.
Prepare a separate screenshot set for Google Play.
iOS-specific screenshot sets and frames.
Apple validates screenshots against an exact list. The upload slots that apply depend on the devices supported by the submitted app, so confirm them in App Store Connect before export.
| Device | Portrait size |
|---|---|
| iPhone 6.9" (17 Pro Max) | 1320 × 2868 px |
| iPhone 6.9" class | 1290 × 2796 px |
| iPhone Air 6.9" | 1260 × 2736 px |
| iPad 13" (M4) | 2064 × 2752 px |
Verify the current list in Apple's screenshot specification. For a readable device table, landscape pairs, and the dimension-error workflow, see App Store Screenshot Dimensions 2026 →
There is no universal winning number or sequence. Start with the question a prospective user needs answered first, then show the real interface that supports that answer. Later images can cover important workflows, meaningful differences, or device-specific experiences. Stop when the set becomes repetitive.
Prefer specific captions over generic screen labels, and keep typography, colour, and framing consistent enough for the images to read as one set. Device frames are optional. Test meaningful alternatives through Apple's Product Page Optimization rather than treating a fixed formula as fact. The supporting guide explains how to design and test an App Store screenshot set.
A localized set should match the language and experience available in that storefront. Reusing one editable layout saves work, but every locale still needs a human review for meaning, line breaks, cultural context, layout direction, and any region-specific UI. The App Store screenshot translator does exactly that across 16 locales; the localization guide covers a practical, review-led workflow.
When App Store Connect reports a dimension error, identify the failed file and compare it with the current accepted pixel pairs for that upload slot. Also confirm that screenshots reflect the submitted product and comply with Apple's current review and metadata rules. The fix wrong dimensions tool checks and re-exports files for the selected size.
Go deeper on any part of the App Store screenshot workflow.
Apple lists several exact pixel pairs for each display class. Current 6.9-inch portrait pairs include 1260×2736, 1290×2796, and 1320×2868; current 13-inch iPad pairs include 2048×2732 and 2064×2752. Check the slot in App Store Connect and Apple's current specification before export.
Apple allows from one to ten screenshots per supported device size and localization. Use the number needed to explain the product clearly, put the most important message early, and review the final sequence at listing size.
Use localized screenshots when the product and listing are localized for that audience. Translation alone is not enough: review line breaks, cultural context, layout direction, and any region-specific UI or claims before upload.
Start with the error shown in App Store Connect. For a dimension error, identify the failed file and re-export it at an exact accepted pixel pair. Also keep every screenshot truthful to the submitted build and review Apple's current upload guidance.
The same visual system can be reused, but Apple and Google have different file rules and listing contexts. Derive each set from one editable design, then inspect the platform-specific outputs separately.
Continue preparing the same App Store, Google Play, or Chrome listing.
Promo tiles, marquee, and screenshots
Start creatingCreate iOS and Android store visuals
Start creatingAndroid-ready Google Play visuals
Start creatingiOS-specific screenshot sets
Start creatingValidate screenshots before App Store Connect rejects them
Start creatingCheck screenshots against Google Play's accepted range
Start creatingPick a template, replace the sample screens, review each selected size and locale, then upload the finished files in App Store Connect.
%2FOlivia%20Rhye.webp&w=64&q=75){kind=small}
%2FPhoenix%20Baker.webp&w=64&q=75){kind=small}
%2FLana%20Steiner.webp&w=64&q=75){kind=small}
%2FDemi%20Wilkinson.webp&w=64&q=75){kind=small}
%2FDrew%20Cano.webp&w=64&q=75){kind=small}