Apple lets you upload 10 screenshots. Stop at 6.

Every listing we see falls into one of two camps: three rushed screenshots, or all ten slots filled because the field was there. Both are guessing. Here's what the stores actually let you upload, what a visitor actually sees before they tap, and the number that isn't a guess.

What the stores actually allow

Apple's limit is 10 screenshots per device size, per localization — minimum 1. That's per display class, so iPhone and iPad each get their own set of up to 10, and if you localize your listing into five languages, that's a separate set of up to 10 for each one. Google Play is tighter: minimum 2, maximum 8 phone screenshots per listing, same per-device-type structure.

Neither number is a target. They're ceilings set for apps with genuinely complex feature sets — a project-management suite walking through six distinct workflows earns ten frames. A journaling app does not.

What actually gets seen before the tap

This is the part that changes the math. In App Store search results, only your first one to three screenshots render — the exact count depends on orientation — before someone taps into the full listing. If you've uploaded an app preview video, it plays first and can push every static screenshot out of view entirely in that preview slot. Frames four through ten only exist for people who already decided to look closer.

That reframes the whole set. Your first two or three screenshots are doing acquisition — they have to work as a standalone pitch, because for a meaningful share of viewers, that's all they get. Everything after that is doing retention: convincing someone who's already curious to finish deciding.

Where the extra slots actually pay off

Once someone opens the full listing, more screenshots aren't automatically better — but a well-sequenced set beats a short one for apps with real depth to show. The pattern that works:

Frames 1–3 (acquisition): your single strongest hook, then the two next-best differentiators, each with a short benefit headline. These need to work with zero context, because in search results they get it.

Frames 4–6 (retention): the workflow, not just the outcome. Show the app doing the thing, not just the result of the thing. This is where feature depth belongs — it's earning trust from someone already leaning yes.

Frames 7+ (optional): social proof, platform-specific features (widgets, Apple Watch companion, tablet layout), or edge-case reassurance. Skip these unless you have something concrete to put there — a filler frame this late does nothing but dilute the six good ones before it.

For most single-purpose apps, that's five to seven frames, not ten. For a genuinely broad app — several core workflows a new user needs to understand before the first session — eight to ten earns its place.

Too few is its own mistake

The restraint argument cuts both ways. Google Play requires a minimum of two phone screenshots to publish at all, and a listing sitting right at that floor reads as unfinished even when it clears the technical bar — visitors treat a thin set as a signal the app itself is thin. Apple doesn't enforce a practical minimum beyond one, but the same perception problem applies: three screenshots next to a competitor's seven, in the same search results grid, looks like the smaller, less-maintained app even if the underlying product is better.

The fix isn't "add more for the sake of it" — it's making sure your count matches what the app actually has to show. If you genuinely have three things worth saying, three well-made frames beat seven padded ones. If you have six, don't stop at three because "less is more" sounded right in the abstract.

The cost nobody accounts for: localization

Every screenshot with text on it has to be redone per locale — the "10 screenshots" number isn't ten images, it's ten images times every language you support. Teams that ship a ten-frame set in English and then localize into eight languages have just committed to producing and maintaining eighty frames, and re-touching all of them every time a headline or a screen redesigns. A tighter six-frame set localized into eight languages is forty-eight — still real work, but a set you can actually keep current.

This is the practical argument for restraint that has nothing to do with conversion theory: fewer, better frames are the set you'll actually maintain when the app changes.

Google Play's extra wrinkle

Google's 2-to-8 range is narrower, which does some of this discipline for you. But Google Play also runs Custom Store Listings and A/B experiments off the same screenshot pool, so a tight, well-labeled set of five or six gives you cleaner variants to test than a sprawling eight — you're not trying to figure out which of ten frames moved the number.

One more wrinkle: Apple's per-device-size requirement means your "one set of screenshots" is actually several. The 6.9" iPhone set, the 6.5" fallback if you skip a size, the 13" iPad set — each can carry a different frame count and even a different order, since the story that lands on a phone-sized frame doesn't always fit a tablet's wider canvas. Deciding your count once, at the largest device, and then trimming down for smaller or secondary sizes is easier than designing every size from scratch at ten frames each.

Build the right-sized set, not the maximum one

ShotCanvas renders a design once and exports pixel-exact PNGs for every required size on both stores, so trimming a set from ten frames to six — or reordering which two lead in search results — is a five-minute edit, not a re-export marathon. The free tier covers your first set.