If you are preparing an App Store listing, screenshot dimensions are one of the easiest details to get wrong.
You can have excellent app screenshots, persuasive copy, and a strong product — but an upload can still fail if the image dimensions do not match an accepted device size. Even when Apple accepts a scaled image, the result may crop important UI or make your screenshot text look too small.
The good news is that you do not need to create a different design for every iPhone model. You need the right source dimensions, a clear screenshot sequence, and a layout that remains readable when Apple scales it across devices.
This guide covers the current App Store screenshot sizes, the practical dimensions to use, how many screenshots to upload, and how to design them for App Store conversion.
Quick answer: the main App Store screenshot sizes
For most iPhone apps, start with an accepted screenshot size for the 6.9-inch display group:
| Orientation | Accepted screenshot size |
|---|---|
| Portrait | 1320 × 2868 px |
| Landscape | 2868 × 1320 px |
Apple also lists 1260 × 2736 px and 1290 × 2796 px as accepted 6.9-inch portrait sizes for specific device groups. Use the size that matches the device screenshot you are exporting, rather than stretching an image to an arbitrary resolution.
For iPad apps, the 13-inch display group is required when the app runs on iPad. Accepted portrait sizes include 2064 × 2752 px and 2048 × 2732 px, depending on the device group.
Apple’s specifications change as new devices are introduced. Before exporting final assets, check the official App Store Connect screenshot specifications.
Current iPhone screenshot dimensions
The following are the main iPhone screenshot groups you are likely to use for a current listing.
| Display group | Portrait sizes | Landscape sizes | Practical use |
|---|---|---|---|
| 6.9-inch | 1260 × 2736, 1290 × 2796, or 1320 × 2868 px | 2736 × 1260, 2796 × 1290, or 2868 × 1320 px | Primary group for current large iPhones |
| 6.5-inch | 1284 × 2778 or 1242 × 2688 px | 2778 × 1284 or 2688 × 1242 px | Older large iPhone models |
| 6.3-inch | 1179 × 2556 or 1206 × 2622 px | 2556 × 1179 or 2622 × 1206 px | Current standard and Pro models |
| 6.1-inch | 1170 × 2532, 1125 × 2436, or 1080 × 2340 px | 2532 × 1170, 2436 × 1125, or 2340 × 1080 px | Smaller current and older iPhones |
| 5.5-inch | 1242 × 2208 px | 2208 × 1242 px | Older Plus models |
The 6.9-inch group is the most important starting point for a new iPhone listing. If you do not provide screenshots for a required display group, App Store Connect may use scaled screenshots from another accepted group. Scaling is convenient, but it is not always ideal for text-heavy screenshot designs.
Current iPad screenshot dimensions
If your app supports iPad, you need a separate iPad screenshot set. Do not place an iPhone screenshot inside an iPad frame and assume the listing is complete.
| Display group | Portrait sizes | Landscape sizes |
|---|---|---|
| 13-inch | 2064 × 2752 or 2048 × 2732 px | 2752 × 2064 or 2732 × 2048 px |
| 11-inch | 1488 × 2266, 1668 × 2420, 1668 × 2388, or 1640 × 2360 px | 2266 × 1488, 2420 × 1668, 2388 × 1668, or 2360 × 1640 px |
| 10.5-inch | 1668 × 2224 px | 2224 × 1668 px |
| 9.7-inch | 1536 × 2048 or 768 × 1024 px | 2048 × 1536 or 1024 × 768 px |
The exact size depends on the iPad model your screenshot represents. Apple’s reference table maps each size to compatible devices, including newer iPad Pro, iPad Air, iPad, and iPad mini models.
How many screenshots should you upload?
App Store Connect allows up to 10 screenshots for each device size and localization. That does not mean every app should upload 10.
A strong set usually needs five to eight screenshots:
- The core promise of the app
- The primary user outcome
- The most important workflow
- A differentiating feature
- Proof, personalization, or a high-value secondary feature
- Additional features for users who keep scrolling
The first screenshot deserves the most attention. Apple says the first one to three screenshots can appear in search results when an app preview is not available. That means users may decide whether to open your product page based on a small, quickly scanned sequence — not your full listing.
Do not use the first five screenshots as a feature inventory. Make them read like a short sales argument:
Problem → outcome → how it works → why this app → supporting proof.
Screenshot dimensions are not screenshot strategy
Correct dimensions only make an asset uploadable. They do not make it persuasive.
The design question is not “What does this screen do?” It is “What does the user get from using this app?”
Compare these two headlines:
- “Dashboard”
- “See your entire week at a glance”
The first labels an interface. The second explains a benefit. App Store screenshots should help a prospective user understand the benefit before they understand every control on the screen.
Use one message per screenshot
Each screenshot should have one main idea. If a screenshot contains three headlines, six feature callouts, and a paragraph of supporting text, the user will probably read none of it.
Use a short headline, one supporting line if needed, and a focused product image. Keep the most important words large enough to read on a phone without zooming.
Design for the smallest realistic display
Create at the highest required resolution, but test the design at smaller sizes. Text that looks comfortable on a 6.9-inch source can become difficult to read when scaled down.
This is especially important for localized screenshots. German, French, Spanish, and Japanese copy may occupy a different amount of space than the English version. A design that works in English may wrap badly or force a smaller font in another locale.
Keep the app UI visible
Marketing text should frame the product, not hide it. Users want to see what the app looks like before downloading it. Show the relevant screen at a useful scale and remove unnecessary interface noise where possible.
For a productivity app, that might mean showing the completed weekly plan rather than a settings screen. For a finance app, it might mean showing a clear spending insight rather than a login page.
Portrait or landscape screenshots?
Portrait screenshots are usually the safest default for iPhone apps because they match the way most people browse App Store listings. They also make a vertical sequence easy to scan.
Landscape screenshots make sense when the app’s main experience is landscape-first, such as a game, video editor, drawing app, or certain productivity tools. Do not rotate a portrait interface into landscape just to create a different-looking asset.
Choose the orientation that best demonstrates the product in actual use, then keep the sequence consistent. A sudden switch between portrait and landscape can make the listing feel less coherent unless the orientation change is part of the product experience.
Screenshot text and App Store localization
Screenshot text is not a substitute for App Store keyword metadata. Apple does not use text embedded inside screenshot images as the same kind of searchable keyword signal as the app title, subtitle, or keyword field.
Screenshots still matter because they influence conversion. If a user searches in German and lands on a listing with German metadata but English screenshot headlines, the page can feel unfinished. That mismatch can reduce trust and downloads.
When localizing screenshots:
- Translate the headline, not just the interface labels.
- Rewrite copy when a literal translation sounds unnatural.
- Allow extra room for longer German and French phrases.
- Check line breaks in Japanese and Korean rather than forcing Latin-style wrapping.
- Keep the benefit consistent across every locale.
- Review screenshots on an actual device-sized preview before submission.
Localizing screenshots is one part of a complete listing. The title, subtitle, keyword field, description, and screenshot messaging should all support the same local search intent. See the App Store Localization Checklist for the full pre-submission workflow and App Store Optimization Localization for the broader international strategy.
Common App Store screenshot mistakes
Using the wrong device dimensions
Exporting a screenshot at a random phone resolution is one of the fastest ways to create upload problems. Start with an accepted Apple size and keep the original export files organized by device group.
Treating screenshots as documentation
Screenshots should sell the outcome, not document every button. Users do not need a complete product manual before installing an app.
Making the first screenshot too generic
“The simple way to manage your tasks” is vague. Make the first frame specific to the user and result: “Plan your day in under one minute” is easier to understand.
Shrinking text to fit every language
Do not solve translation overflow by making the type tiny. Rewrite the headline, adjust the layout, or create a locale-specific design variation.
Reusing the same sequence in every market
A feature that matters in the US may not be the strongest opening message in Japan, Germany, or Brazil. Keep the product truth consistent, but adapt the order and wording to local expectations.
Ignoring the preview in search results
Open the App Store listing on a real device and inspect the first screenshots as a user would see them. The design may look perfect on a desktop artboard but lose its message in the smaller search-result view.
App Store screenshot checklist
Before uploading, check each item:
- The source file uses an accepted Apple dimension.
- The correct device group is selected.
- The app UI is clear and large enough to understand.
- The first screenshot communicates one strong benefit.
- The first three screenshots work as a sequence.
- Each additional screenshot has one primary message.
- Screenshot text is readable on a phone.
- Screenshot copy is localized for every target market.
- Longer translations have room to breathe.
- The sequence is consistent in orientation and visual style.
- The screenshots match the current version of the app.
- The final listing has been reviewed inside App Store Connect.
The practical takeaway
For most iPhone apps, begin with an accepted 6.9-inch screenshot size, design a focused five-to-eight-image sequence, and test the result at smaller display sizes. If your app runs on iPad, prepare a separate 13-inch screenshot set as well.
The technical requirement gets your screenshots accepted. The message, order, readability, and localization determine whether those screenshots turn listing visits into downloads.
If you are localizing an app for multiple countries, screenshot copy should be planned alongside local keyword research and metadata — not added as a final translation task. LocalizeRank researches the market, builds localized metadata, and adapts screenshot text for each target locale. See how App Store localization works.