App Store Screenshots That Convert: The 2026 Playbook for Indie Developers

Most users decide whether to install your app within three seconds of landing on your store listing. They don't read the description. They skim the first two screenshots. Then they either tap Get, or they bounce.

That makes your screenshots the single highest-leverage asset in your entire App Store presence. A good set can lift install conversion by 25-40% over a weak one. A great set can carry a mediocre icon and an average title. And in 2026, with store competition heavier than ever and attention spans shorter, screenshots are no longer "design polish" — they are the product page.

This guide walks through what actually works on the App Store and Google Play in 2026: the sizes you need, the messaging patterns that convert, the layout decisions that keep users scrolling, and the specific mistakes that quietly cost indie developers installs every day.

Why screenshots matter more than they did two years ago#

A few things shifted in 2024-2025 that reshaped how people find apps:

First, store search results got denser. Apple and Google both tightened listing layouts and started showing more competing apps per search. Your three screenshots are now rendered next to two or three other apps' three screenshots — and the comparison is instant and brutal.

Second, custom product pages matured. Serious indies now ship 5-10 variants of their screenshot set targeted at different acquisition channels. If you're still shipping one set for everybody, you're competing against developers shipping tailored narratives for each audience.

Third, AI-generated screenshot sets flooded the market. That's mostly bad — a lot of them look identical, stock, and lifeless. But it raised the baseline. A screenshot that would've been "fine" in 2023 now looks lazy next to a neighbor's tuned, narrative set.

The sizes you actually need in 2026#

Apple's current required base sizes are 1320 x 2868 pixels for the 6.9-inch iPhone and 2064 x 2752 pixels for the 13-inch iPad. You only need to upload at the largest required size per device family; Apple downscales automatically for older devices.

For Google Play, you need phone screenshots at minimum (1080 pixels on the short side, up to 3840 on the long side), and if you're targeting tablets or foldables, separate sets for 7-inch, 10-inch, and foldable. Play Store still rewards developers who fill out every form factor — listings with tablet screenshots tend to get better placement on tablet devices.

Vertical orientation is now the standard. Roughly 96% of top-ranking apps ship vertical screenshots. Horizontal only makes sense if your app is genuinely landscape-first (most games, some drawing apps). Even then, consider a hybrid set where the first two frames are vertical-portrait-style compositions of landscape content.

The messaging patterns that convert#

Every screenshot is answering one question: "why should I install this right now?" Most indie screenshots fail because they try to answer a different question — "what does this app do?" — which is a worse question.

The patterns that work in 2026:

Problem → solution → proof. Frame 1 names a pain the user feels. Frame 2 shows your app resolving it. Frame 3 shows social proof (testimonial, download count, award). This is the safest structure for utility and productivity apps.

Benefit-led headlines. "Plan your week in 30 seconds" beats "Calendar view." Lead with the outcome, not the feature. A headline like "Achieve your fitness goals faster" on frame one, paired with a clean shot of the core loop, does more work than a settings menu screenshot ever will.

Panoramic continuity. Design a single wide background and slice it across three or four frames. When users see a design element cut at the edge, their brain wants to see the rest — it compels horizontal swiping. This pattern is everywhere in top-ranking apps right now and it works.

One idea per frame. If you find yourself putting two headlines on a single screenshot, split it into two. Cognitive load is the enemy. Users decide in a fraction of a second, and a frame with one clear message wins over a frame with three.

Layout: what to actually put on the screen#

A working screenshot frame in 2026 has four elements: headline, device mockup (or full-bleed UI), background, and optional annotation.

The headline sits at the top, large and bold, and is readable at thumbnail size. If you can't read it on your phone from arm's length when the screenshot is shown at store-thumbnail scale, it's too small. Sans-serif, weight 600+, and high contrast against the background.

The device mockup shows your actual app UI — no abstract art, no mocked-up screens with fake data that the real app doesn't produce. Apple and Google both reject screenshots that misrepresent the in-app experience, and the rejection note is usually terse and unhelpful. Use real states from the real app.

Backgrounds should be brand-consistent across the set. A single color family, a consistent gradient, or a shared panoramic scene. Mixing background styles within a set reads as amateur and cuts perceived quality.

Annotations — arrows, magnified highlights, circled buttons — are high-leverage when used sparingly. One annotation per frame, pointing at the single thing that matters. More than one turns into visual noise.

Platform-specific differences that still matter#

Apple and Google users respond to slightly different cues, and the difference is more pronounced than it was a few years ago.

App Store users tend to respond to lifestyle imagery and emotional framing. Screenshots that show a person using the app, a scene with context, or a moment of outcome (a finished run, a completed recipe, a clean inbox) outperform pure-UI screenshots in most categories. This isn't universal — dev tools, finance, and productivity apps still do fine with pure-UI — but it's the rule for lifestyle, health, social, and entertainment.

Play Store users are feature-hungry. They want to know what the app does and see it in action. Highlighting specific features — "Smart notifications," "Offline mode," "AI-powered suggestions" — with clear UI shots tends to outperform lifestyle imagery. Play Store users are also more likely to read down the screenshot set, so frames 3-5 carry more weight than they do on iOS.

Ship different sets per platform if you can. If you can't, lean App Store on the emotional side and write extra descriptive copy in the Play Store description to compensate.

The mistakes that quietly cost installs#

A short list of things I see indie developers get wrong, in rough order of how much they cost:

1. Leading with a settings menu, profile screen, or empty state. Nobody installs an app because of its preferences panel.
2. Screenshots with text that's unreadable at thumbnail size. If users can't parse it in the search results, it doesn't exist.
3. Inconsistent typography across the set. Different headline weights, sizes, or fonts in different frames. It looks like three designers collaborated and none of them talked.
4. Fake data that looks fake. Lorem ipsum, "John Doe," obviously placeholder numbers. Use realistic sample data.
5. No annotations, or too many. One per frame, aimed at the most important thing.
6. Not localizing screenshots. If your app is translated into 10 languages, your screenshots should be too. Text-heavy screenshots in English on a Spanish store listing convert significantly worse.
7. Shipping once and never iterating. Your first set is a guess. Custom product pages let you A/B test — use them.

A practical workflow#

Here's the process that works for indie teams:

1. Write the headlines first, before you touch design. Five to seven short lines of copy, one per frame. Order them as a narrative.
2. Build a single layout template — headline position, device position, background style — and apply it to every frame.
3. Capture real app states. Use a device or simulator running realistic data, in your chosen dark/light mode, in the exact languages you'll ship.
4. Compose the frames in Figma, Sketch, or a dedicated screenshot tool. Export at the required pixel sizes.
5. Test at thumbnail scale on a real device before uploading. Re-read every headline at that scale.
6. Ship, then A/B test. Change one variable at a time — headline copy, order, background color — and let the store's analytics tell you what wins.

Conclusion#

Great screenshots are the single highest-leverage asset in your store listing, and most indie developers under-invest in them. The technical requirements are straightforward. The messaging and layout patterns are well-understood. What's missing, usually, is the time and attention to do the work deliberately.

If that time is what you don't have, Stora's screenshot generator builds conversion-oriented sets directly from your app's real UI — headlines, layouts, device mockups, and localized variants — so you can ship a tested, consistent set in an hour instead of spending a weekend fighting Figma. It's built around the patterns in this guide, which is the point: the patterns work, and the hard part is just getting them on the page.

Whether you build them by hand or generate them, ship intentional screenshots. The users scrolling through search results in 2026 are deciding faster than ever, and your first two frames are doing most of the selling.