Key points:
- One screenshot set often doesn’t carry over cleanly to a different device size, since the shapes don’t match.
- Skipping a size can leave that part of your listing empty, stretched, or filled with a fallback that looks unplanned.
- Screenshot size rules differ by store and by device, so check each store’s current specs directly.
- Treat screenshots as a job done per size, not a single upload, to avoid a gap most teams miss until someone on a different device sees it.
One set of screenshots feels like it should be enough. Whether it actually covers every device your app runs on is a separate, checkable question.
Why one set doesn’t cover every size on its own
Different device sizes often have real differences in shape, not just pixel count. A screenshot built for one size can look stretched, cut off oddly, or just too small once forced into a shape it wasn’t made for. Stores generally expect, sometimes require, a separate set for each size for exactly that reason. One set rarely carries over cleanly to all of them.
| What tends to happen | |
|---|---|
| A set made for each size | A clean, right-shaped image on every device |
| One set used everywhere | Stretching, cropping, or a gap on sizes it wasn’t made for |
Why this gap is easy to miss
A team checking their listing on their own main device sees a clean set of screenshots and figures the job is done. The gap only shows up on a size nobody on the team happened to check, so it can sit there unnoticed for a long time until someone looks at the listing from a different device’s point of view.
Real-world scenario: A team uploaded a polished set of screenshots sized for their most common device and assumed that one set would cover the whole listing. Checking how it actually looked on a less common device size, they found a stretched, slightly off version of the same images. Clearly not planned, to anyone looking at it. Uploading a second, properly sized set for that device fixed the spot instead of leaving it looking like a mistake.
Why checking the current rules matters
Exact size rules, and which devices need their own set, differ by store and shift as device lineups change. Going by last year’s rules, or assuming one store’s rules apply to the other, risks a real gap. Checking each store’s current screenshot specs directly, instead of working from memory or an old list, is the safer way to confirm every size is actually covered.
What to actually do about it
- Check your listing on more than just your main device size. A clean look on one device doesn’t tell you every size is covered.
- Upload a set made for each size instead of relying on one set everywhere. One set rarely carries over cleanly to a different shape.
- Check each store’s current screenshot rules before assuming you’re covered. Rules differ by store and change over time.
- Treat this as an ongoing check, not a one-time task. A gap on a less common device size can sit unseen until someone looks for it on purpose.
AppRankr’s ASO Inspector checks your real listing signals, a useful habit alongside confirming your screenshots actually cover every device you support.