TL;DR: App Store listings need at least one screenshot, but the smallest useful set is the one that shows the app in use, explains the main benefit, and makes the listing understandable at a glance.
The minimum App Store screenshot count
App Store listings need at least one screenshot. In practice, though, the exact set you upload depends on the device sizes and storefront requirements you are targeting. For the current screenshot rules and review guidance, see App Store screenshot guidelines and App Store screenshot sizes.
Why the minimum is not the practical target
One screenshot may satisfy a bare minimum in theory, but a useful listing usually needs enough images to show the app in use, the key value, and the primary workflow. That lines up with Apple’s guidance that screenshots should show the app in use, not just a title card with ambitions.
If you want a broader framing for this kind of launch decision, how to announce a new feature to existing users is useful because it shows the same idea from a messaging angle, keep the promise clear and concrete.
Worked example: deciding the smallest useful set
Say you are launching a budgeting app with this one-line description, “Track spending without spreadsheet chaos.”
The first screenshot should support that main promise, maybe showing the dashboard with categories and the balance at a glance. The second should show the core workflow, such as adding a transaction or reviewing a budget category. The third should resolve a likely hesitation, like how the app handles syncing, privacy, or a simple monthly summary.
That is the point where “minimum” and “effective” stop being the same thing. One image can exist. Three images can explain.
What to check before you publish
Before you start optimizing for the smallest possible count, check the basics that actually matter:
- Each screenshot is legible on the device it is meant for.
- Each screenshot shows the product in use.
- Each screenshot matches the one-line description.
- The set supports the decision a shopper is trying to make on the product page.
If you are still shaping the product message, how to evaluate a new software tool before your team adopts it can help you think about the app in terms of the job it is meant to do, which is basically the same sanity check screenshots need to pass.
If you want the shortest acceptable set, use this rule
Use the smallest number of screenshots that still proves the app works, communicates the main benefit, and avoids an incomplete-looking listing. If you cannot do that with one image, add the next most important one.
That is the whole trick. Not glamorous, but neither is debugging why your listing looks like a skeleton in a blazer.
FAQ
Can an App Store listing work with only one screenshot?
It can meet a minimum in some contexts, but it usually under-explains the product, so most teams should add screenshots until the listing is understandable at a glance.
Should screenshots repeat the one-line description?
No, they should expand it by showing the app in use and making the promise concrete.