The App Store screenshot playbook

Your gallery is an ad, and frame one is the whole ad

The six-frame narrative

Six is the working default. Three is the minimum that functions, Google Play caps at eight per device type and Apple at ten per localisation per device class, and past about eight the marginal frame rarely earns its production cost. Each frame below answers one question the viewer is asking, in the order they ask it. One idea per frame: two features in one screenshot reads as neither.

1. 1

   Frame 1: The hook

   Answers 'what is this and why should I care'. One caption of at most two lines stating the single outcome the app delivers, plus one legible crop of the screen where that outcome appears. Not the home screen, not the dashboard, not the login: the screen that shows the result. Crop into the interface hard enough that its own type stays readable at gallery thumbnail size, which usually means showing one panel rather than one whole screen. This frame sets the visual system for the other five: background treatment, caption position, caption weight, how the device is framed, how much margin sits around everything. Build it first, approve it alone, then treat it as the template. Building all six in parallel from cold produces six galleries, not one.

2. 2

   Frame 2: The core value, shown

   Answers 'what does using it actually look like'. Frame 1 made a claim, frame 2 shows the claim being true. Use the primary workflow screen with realistic content in it: a real-looking list, a real-looking chart, plausible names and numbers. The caption here names the job, not the feature. 'Every subscription in one place' rather than 'Subscription management view'. This is the frame where empty states and placeholder data do the most damage, because the viewer is specifically looking for evidence that the app has substance.

3. 3

   Frame 3: Proof of the main action

   Answers 'how hard is this going to be'. Show the single most important action being performed, and show that it is short. A one-tap capture, a swipe that files something, a scan that resolves. If the action takes two steps, show the two steps in one frame as a small sequence rather than splitting it across two frames. The caption states the effort, not the capability: 'Log a meal in one photo' does more work than 'Photo-based food logging'. Frames 1 to 3 are the ones visible without scrolling on most layouts, so if the argument is not carried by these three, nothing later rescues it.

4. 4

   Frame 4: The differentiator

   Answers 'why this one and not the three above it in search'. Name the thing your nearest alternatives do not do, and show it. This is usually a specific capability, a constraint you respect that others do not, or a fundamentally different model of the same job. Resist the temptation to make this frame about your brand values. The viewer is comparing apps, not choosing a worldview. If you genuinely have verifiable proof to show here, such as a rating your store already displays or an award you actually hold, this is the frame for it. Never fabricate a rating, a review, a user count or a press quote: invented proof in a store listing is both a policy problem and the fastest way to lose the install after it happens.

5. 5

   Frame 5: The objection killer

   Answers 'what is going to annoy me about this'. Every category has one dominant hesitation, and it is almost always known to you from support tickets and reviews. Privacy and where the data goes. Whether it works offline. Whether it syncs to the device they actually use. Whether the free tier is real. Whether it will nag them. Pick the one objection that kills the most installs and answer it plainly in a caption, with a screen that supports the answer. This is the least glamorous frame and often the highest leverage one, because it is the only frame addressing the reason people who liked frames 1 to 4 still did not install.

6. 6

   Frame 6: The call to install

   Answers 'fine, what now'. A closing frame that restates the outcome in the shortest possible form and shows the app at its most appealing, often the single most visually pleasing screen you have. Keep the caption short and imperative in the reader's language, and do not put a fake install button in the image: the real one is already on the page and a drawn one reads as a broken control. If you have a free tier, a trial or a no-account-needed first run, this is where to say so in a single line, because the last remaining friction at this point is commitment, not comprehension.