App Store Screenshot Sizes: The Only 2026 Guide You Need
The only 2026 guide to App Store screenshot sizes you need — exact iPhone and iPad dimensions, how many you need, and the easy way to export them all.
I got a build rejected once over a wrong screenshot size — a single set uploaded a few pixels off the spec — and lost most of a launch day to a re-export and another review round. So I did what any mildly annoyed developer does: I made the one App Store screenshot sizes chart I actually trust, checked it against Apple's requirements, and stopped guessing. This is that chart, plus the context around it, so you never eat a rejection over App Store screenshot dimensions again.
Bookmark this one. It's the reference I keep open every time I ship.
What size should App Store screenshots be in 2026?
The short answer: App Store screenshots must match the exact pixel dimensions Apple defines for each device display size, in either portrait or landscape, uploaded as PNG or JPEG with no transparency (RGB, flattened). The dimensions are tied to display sizes — measured in inches — not to individual phone models, which is what keeps the list manageable even as new devices ship.
Here's the part that saves the most time, and I'll repeat it later because it matters most: you generally only need to provide the largest display size in each family. Apple can scale your largest iPhone and iPad screenshots down to cover the smaller sizes, so you don't have to hand-produce every device class. Provide the big ones cleanly and you're covered.
iPhone screenshot sizes
For iPhone, the two display sizes that carry current submissions are the 6.9-inch display (the largest, used by recent Pro Max / Plus-class devices) and the 6.5-inch display. If you provide the 6.9" set, it covers the modern lineup; the 6.5" slot exists for older large-display devices. Smaller displays inherit from these.
| Display | Orientation | Aspect | Required? | Pixel size |
|---|---|---|---|---|
| iPhone 6.9" | Portrait | ~19.5:9 | Yes (primary) | Exact pixels from the converter |
| iPhone 6.9" | Landscape | ~9:19.5 | Optional | Exact pixels from the converter |
| iPhone 6.5" | Portrait | ~19.5:9 | Yes (or inherit from 6.9") | Exact pixels from the converter |
| iPhone 6.5" | Landscape | ~9:19.5 | Optional | Exact pixels from the converter |
A note on the pixel column: rather than print numbers here that could drift the next time Apple updates a display class — and get you rejected on my say-so — I let the tool emit them. Our free Screenshot Size Converter outputs the exact current pixel dimensions for every iPhone display size, portrait and landscape, from a single master image. That way the number you upload is always the number Apple wants today, not the number that was right last year.
iPad screenshot sizes
iPad is simpler than it used to be. The one that matters now is the 13-inch iPad display — the largest — which covers the current iPad Pro class and scales down to smaller iPads. As with iPhone, provide the biggest size well and let Apple handle the rest.
| Display | Orientation | Aspect | Required? | Pixel size |
|---|---|---|---|---|
| iPad 13" | Portrait | ~4:3 | Yes (primary) | Exact pixels from the converter |
| iPad 13" | Landscape | ~3:4 | Optional | Exact pixels from the converter |
iPad screenshots are near-square compared to the tall iPhone frames, which is exactly why a layout that looks perfect on iPhone often needs its text and imagery re-flowed for iPad — the headline that fit a 19.5:9 frame has nowhere to go in a 4:3 one. Plan for that re-flow rather than stretching an iPhone design and hoping.
The Screenshot Size Converter handles the iPad 13" pixel output too, so you're pulling iPhone and iPad exports from the same place.
How many screenshots do you need?
Two numbers to hold onto:
- Per display size: the App Store accepts up to 10 screenshots and requires at least 1. In practice, three to five well-sequenced screenshots do the heavy lifting — the first two are what most people actually see in search results, so front-load your strongest message.
- How many sizes: thanks to the "largest size covers the rest" rule, you realistically produce one iPhone set (6.9") and one iPad set (13") if you support both platforms. That's the whole point of this guide — the matrix looks intimidating, but the required surface area is small.
Don't forget the icon, which travels with the same submission: your App Store icon has its own exact requirement, and if you're generating platform icon sizes from one source, the free App Icon Resizer spits out every required icon dimension so the icon half of the upload is as painless as the screenshots.
The "you only need the largest" tip (in full)
Because it's the single most useful thing here: design once at the largest display size in each family, and let smaller sizes inherit. One clean iPhone 6.9" master and one iPad 13" master is a complete, uploadable set for most apps. You do not need to hand-craft 6.5", 5.5", or smaller iPad frames — Apple scales your largest assets down.
The catch is that "largest" still has to be exactly right to the pixel, in the correct orientation, as a flattened PNG or JPEG. That precision is where rejections come from, and it's precisely the part worth automating.
The easy way (skip the manual exports)
Here's what I do now instead of maintaining a spreadsheet of dimensions and a folder of export presets:
- Design my best iPhone 6.9" and iPad 13" screenshots once.
- Drop each master into the Screenshot Size Converter and let it produce every required App Store size at the exact current pixels — no manual number-checking, no rejected build over a stray dimension.
- Run my icon through the App Icon Resizer so the icon sizes come out of the same one-source, one-click flow.
That's it. The reference chart above tells you what the App Store wants; the tools make sure the files you upload actually are that, down to the pixel. The rejection I lost a launch day to simply can't happen when the dimensions aren't something I'm typing by hand anymore.
If your real pain isn't the sizes but the building — the resize-reflow-export-localize grind around each layout — that's a different (and bigger) time sink. I wrote about escaping it in the faster way to build App Store screenshots than Figma.
Reverze turns App Store creative production from a multi-day design workflow into minutes — paste a URL, rebuild your screenshots, generate new directions, and export production-ready assets. Explore the free tools or start in the app.