Sizing guide
App Store screenshot sizes for iPhone & iPad
This page is built for teams searching for the current App Store screenshot sizes they need to plan exports, QA, and final submission. As of April 12, 2026, Apple accepts multiple screenshot dimensions across current iPhone and iPad classes, so the goal is not just knowing the numbers, but knowing which classes matter first.
The iPhone sizes most teams care about first
Apple supports several accepted iPhone screenshot dimensions. In practice, most modern teams start with the largest currently accepted iPhone classes because Apple can scale certain approved assets to smaller classes when you do not provide them directly.
6.9-inch class
Current accepted portrait sizes
- • `1260 × 2736`
- • `1290 × 2796`
- • `1320 × 2868`
These are the large modern iPhone classes Apple lists for current Pro Max, Plus, and Air-era devices.
6.5-inch fallback class
Common accepted portrait sizes
- • `1284 × 2778`
- • `1242 × 2688`
Apple notes this class is required if 6.9-inch screenshots are not provided for iPhone apps.
Current iPad screenshot sizes
If your app runs on iPad, Apple requires iPad screenshots. The largest class is the safest starting point because it covers the current iPad Pro and iPad Air families and sets the composition standard for the rest of the iPad set.
13-inch iPad class
Accepted portrait sizes: `2064 × 2752` and `2048 × 2732`.
11-inch iPad class
Accepted portrait sizes include `1488 × 2266`, `1668 × 2420`, `1668 × 2388`, and `1640 × 2360`.
Workflow note
Design iPad separately, not as an afterthought
iPad screenshots usually need their own rhythm, spacing, and copy hierarchy. A direct upscale from iPhone often leaves too much negative space or awkward text balance.
- • Treat iPad as a parallel composition, not just a resize target.
- • Re-check headline line breaks after moving to larger canvases.
- • Keep the first frames aligned with the same product story as iPhone.
How teams use this sizing guide in production
1. Lock the required classes
Decide which iPhone and iPad classes you will export directly before anyone starts visual QA.
2. Build the master compositions
Create one iPhone master and one iPad master so copy hierarchy holds up cleanly on both families.
3. Export and verify at the end
Re-check accepted dimensions in App Store Connect before shipping because Apple’s accepted classes evolve over time.
Want the full workflow instead of managing sizes manually? Use the App Store screenshot generator and pair it with our template library.
App Store screenshot sizes FAQ
What App Store screenshot sizes should I export first?
For most iOS teams, the highest-priority exports are the approved large iPhone classes and the required iPad class when the app runs on iPad. PerfectDeck helps teams generate those sizes first so the same design system can scale across the rest of the submission set.
Do I need separate screenshot sets for iPhone and iPad?
If your app runs on both iPhone and iPad, you should plan for both device families. The iPad requirements are distinct from iPhone, and the layout usually needs its own composition rather than a direct resize.
How often do App Store screenshot specs change?
Apple updates supported device classes over time, especially when new hardware sizes ship. Teams should verify accepted dimensions in App Store Connect before every major submission or seasonal screenshot refresh.