App Screenshot Best Practices in 2026: A Three-Second Guide for Indie Developers

Good screenshots do one job: they tell a stranger what your app does, and why they should care, in about three seconds. That means leading with your strongest benefit in the first screenshot, writing captions you can read at thumbnail size, uploading the exact pixel sizes each store wants (1260×2736 for the current required iPhone size, 1080px+ for Google Play), and putting your best two or three images first — because on the App Store, that's all most people will ever see. Here's how to get each of those right without hiring a designer.

Why screenshots matter more than almost anything else on your listing

Your store listing has a lot of parts — icon, title, subtitle, description, reviews — but screenshots take up most of the screen, and they're what people actually look at. In an audit of 70+ app product pages, SplitMetrics found that 56% of apps had screenshots that didn't clearly communicate what the app does — the single most common conversion mistake they saw. The same research puts users' attention span at around 8 seconds, with almost half of visitors leaving the product page within 3 seconds.

Three seconds. Nobody is pinch-zooming your fourth screenshot to admire your settings screen. Storemaven's guidance, as summarized by Asodesk, says the same thing from the other direction: your product page should explain what the app does in no more than 3 seconds.

The practical conclusion for a solo dev: spend your design time on screenshots 1–3 and treat the rest as bonus material.

Get the technical specs right first

Nothing kills momentum like App Store Connect rejecting your uploads at 11pm. Here's what the stores currently require.

App Store (iOS)

Apple's official screenshot specifications allow 1 to 10 screenshots per localization, in JPEG or PNG, with no transparency or alpha channel.

The one size that matters most: the 6.9-inch display (iPhone Air, 16 Pro Max, 15 Pro Max and friends) at 1260×2736 portrait. It's the required size for iPhone apps — every smaller size can auto-scale from your larger uploads if you don't provide it. If your app runs on iPad, you'll also need the 13-inch size at 2064×2752.

In practice, that means an indie can ship with exactly two sets of screenshots — one 6.9" set and one 13" set — and let Apple scale the rest. Pixel-perfect sets for every device are a nice-to-have, not a launch requirement.

Google Play

Google's preview asset guidelines ask for a minimum of 2 screenshots to publish, and allow up to 8 per device type (phone, tablet, Chromebook, and so on). Files must be JPEG or 24-bit PNG (no alpha), between 320px and 3840px on each side, and the longest side can't be more than twice the shortest.

One detail worth knowing: to be eligible for featuring and certain promotional placements, Google wants at least four screenshots at 1080px resolution or higher, in 16:9 or 9:16. Even if featuring feels like a distant dream, uploading four 1080×1920 screenshots costs you nothing extra and keeps the door open.

The first screenshot carries the whole listing

On the App Store, Apple's product page documentation notes that your first 1–3 screenshots appear directly in search results when there's no app preview video. Most people who ever see your screenshots will see them there — on a search results page, at thumbnail size, without ever tapping through to your listing.

So the first screenshot has to work alone. A reliable pattern:

Screenshot 1: your core benefit, stated in plain words, over your best screen. Not your login page. Not a welcome screen. The moment your app delivers its value.

Screenshot 2: your second-strongest feature, or the same feature from the doing-it angle rather than the result angle.

Screenshot 3: whatever answers the biggest objection — pricing clarity, privacy, offline mode, sync. The thing people ask about in your reviews.

SplitMetrics' audit backs the ordering: the first 1–3 screenshots get the highest number of views, which makes them the most important ones. Everything after slot three is for the small minority who scroll.

Captions: short, big, and about them

The same SplitMetrics audit found 40% of apps had caption text that was hard to read — too small, too long, or too low-contrast — and 37% had overcrowded designs. These are the cheapest problems to fix.

A few rules that hold up:

• One idea per screenshot. If a caption has the word "and" in it, it's probably two screenshots.
• Write benefits, not features. "Never lose a receipt" beats "OCR document scanning."
• Test readability at thumbnail size. Shrink your screenshot to the size it'll appear in search results. If you can't read the caption, neither can anyone else.
• Real UI, not mockups of things your app doesn't do. Both stores require screenshots to reflect the actual experience, and users can tell.

If your app supports dark mode, Apple recommends including at least one screenshot showing it — an easy way to signal polish.

Should you add an app preview video?

Maybe — but test it. Data collected by Asodesk shows video can lift conversion meaningfully — SplitMetrics reports around a 16% lift in engagement and conversion, while Storemaven has seen 20–35% — but the same guide notes videos have also decreased conversion in some tests. A boring or confusing video is worse than no video.

For most indie apps, the sane order of operations is: nail the first three screenshots, ship, and only invest in a 15–30 second preview once the static listing is converting. Apple allows up to three app previews of up to 30 seconds each; they autoplay muted, so the first few seconds have to work without sound.

Test instead of guessing

Apple's built-in Product Page Optimization lets you run up to three alternate versions of your screenshots against your current set, with results in App Analytics. It's free, native, and criminally underused by small developers. Google Play offers the equivalent with store listing experiments. If you change your screenshots, change them as an experiment — otherwise you'll never know whether the redesign helped or the seasonality did.

(That's the same discipline we apply at Kintsu, an ASO toolkit for indie developers currently in private beta — measure before and after, always.)

A one-evening checklist

1. Export your 6.9" iPhone set at 1260×2736 (and 13" iPad at 2064×2752 if applicable); for Play, at least four at 1080×1920.
2. Put your core benefit in screenshot 1, in words a stranger understands.
3. Cut every caption to 5–7 words. One idea each.
4. Shrink everything to thumbnail size and re-read.
5. Add a dark mode shot if you support it.
6. Set up a Product Page Optimization test before you swap anything live.

None of this needs a design agency. It needs an evening, a free template, and the willingness to look at your listing the way a stranger does: for three seconds, deciding.

FAQ

How many screenshots should I upload? Use every slot you're given if you can — up to 10 on the App Store, up to 8 per device type on Google Play — but front-load ruthlessly. The first three do almost all the work; the rest are for the rare deep-scroller.

What's the single most important App Store screenshot size in 2026? The 6.9-inch iPhone size: 1260×2736 pixels (portrait). It's the required size per Apple's specifications, and smaller sizes auto-scale from it if you don't upload them separately.

Portrait or landscape? Portrait, unless your app is genuinely used in landscape (games, video). Portrait screenshots show 2–3 at once in App Store search results, giving you more surface area to make your case.

Do I need different screenshots for the App Store and Google Play? The design can be the same, but export them separately: the pixel dimensions, file rules, and slot counts differ, and Play's featuring eligibility asks for at least four screenshots at 1080px+.