App store screenshots are the highest-leverage pixels you’ll ever ship. Your first screenshot appears right in the search results, next to your icon and rating, and a big share of users decide to install or scroll past without ever opening your listing. This guide covers the 2026 specs for both stores, why the first three screenshots carry almost all the weight, and how to design a set that actually converts.
The short version
- Tap-to-install averages 33.4% on iOS and 27.7% on Google Play in 2026. Above 30% is strong. Below 15% means your visuals are leaking installs.
- Your first screenshot shows in search results before anyone taps your listing. It’s doing sales work whether you designed it for that or not.
- iOS shows your first 3 screenshots above the fold, right next to the install button. Google Play surfaces more text, so your screenshots fight for attention differently there.
- The specs are incompatible: 1320 × 2868 px for iOS, 1080 × 1920 px for Google Play. You always export two sets.
- Caption first, UI second. A screenshot without a benefit caption is just a picture of your app.
Your screenshots are your landing page
Most developers treat screenshots as proof the app exists. Open the app, capture five screens, upload, done.
That’s backwards. On both stores, screenshots occupy more screen space than every other listing element combined. Your description gets truncated behind a “read more” tap. Your feature list never gets read. Your screenshots get seen by everyone who finds you.
The numbers back this up. Tap-to-install sits around 33.4% on iOS and 27.7% on Google Play on average. The gap between a mediocre listing and a strong one is routinely 10 or more percentage points, and screenshots are the biggest lever in that gap. Same app, same traffic, double the installs.
If your listing converts below 15%, don’t buy more traffic. Fix the creative first. It’s the same logic we walked through in why most indie apps fail after launch: acquisition can’t fix a conversion problem.
The specs, so you don’t get rejected
The two stores share a goal and almost nothing else. Here’s what each one wants in 2026.
Spec App Store (iOS) Google Play Phone size 1320 × 2868 px (6.9-inch) 1080 × 1920 px typical Size rules Fixed per device class Sides 320 to 3840 px, ratio max 2:1 How many 1 to 10 2 to 8 per device type Tablet set iPad: 2064 × 2752 px, separate 7-inch and 10-inch, separate Format PNG or JPEG, RGB, no alpha, max 10 MB PNG or JPEG, RGB, no alpha, max 8 MB Visible without scrolling First 3 screenshots Varies, text competes earlier
The practical takeaway: you can’t reuse the same files across stores. Apple’s required iPhone dimensions fall outside Google Play’s accepted aspect ratio. Design once at a common safe layout, then export two sets. That’s exactly the workflow ReachFront Studio automates, one design, both stores’ exports.
The first three screenshots do all the work
On iOS, your first three screenshots sit above the fold next to the install button. Most visitors never swipe past them. On top of that, your first screenshot appears in search results as a thumbnail, which means plenty of installs happen from people who saw exactly one screenshot and your star rating.
So the order isn’t cosmetic. It’s your pitch sequence:
- Screenshot 1: the outcome. Not your login screen. Not your settings. The single result your app delivers, stated in a caption a stranger understands in two seconds.
- Screenshot 2: the differentiator. The thing competitors can’t claim. If you have social proof (ratings, users, press), this is where it earns its keep.
- Screenshot 3: the depth. The feature that makes people who almost installed commit.
Screenshots 4 through 10 are for the researchers, the people comparing three apps in tabs. They matter, but they’re the dessert, not the meal.
How to design screenshots that convert
Step 1: Write the captions before you open a design tool
Each screenshot gets one benefit statement, 6 words or fewer, readable at thumbnail size. If the caption doesn’t survive being shrunk to a search result, rewrite it. The captions in sequence should read like a pitch even if nobody looks at the UI underneath.
Step 2: Show real UI, framed, not raw
Raw screen captures convert worse than composed shots: a device frame, a short caption above, brand color behind. But keep the UI real. Stores reject misleading imagery, and users can tell a mockup that oversells.
Step 3: Design for the thumbnail first
Check every screenshot at 30% size. That’s how it appears in search results, where a large share of install decisions happen. Text under 60 px tall on your 1320 × 2868 canvas is invisible where it matters most.
Step 4: Keep one visual system across the set
One background family, one caption position, one device angle. A set that looks like one designer made it in one sitting reads as a professional app. Five styles in five screenshots reads as a side project.
Step 5: Export per store, then actually test
Export the iOS set and the Play set separately, then use each store’s testing tool: Product Page Optimization on iOS, Store Listing Experiments on Google Play. Screenshot tests routinely move conversion more than any metadata change. One test at a time, two weeks minimum, or the data is noise.
Where developers get it wrong
- Leading with the login screen. The most common first screenshot in every category, and the worst possible pitch.
- No captions. A naked UI screenshot asks the user to figure out the benefit themselves. They won’t.
- Designing at full size only. Looks great in Figma, unreadable as a search thumbnail.
- Reusing one export for both stores. Either it gets rejected or it gets letterboxed into looking broken.
- Set-and-forget. Your screenshots compete against every new app in your category. A set from 2024 is losing to sets designed last month.
Common questions
1. What size should app store screenshots be in 2026?
For iOS: 1320 × 2868 px for the 6.9-inch iPhone, and Apple propagates them to smaller sizes. If you support iPad, add a 2064 × 2752 px set. For Google Play: 1080 × 1920 px is the standard, with each side between 320 and 3840 px and the aspect ratio capped at 2:1.
2. How many screenshots should I upload?
Use most of your allowance: up to 10 on iOS, up to 8 on Google Play, minimum 2 on Play to publish. But spend 80% of your design effort on the first 3, because that’s what most users see.
3. Which screenshot matters most?
The first one. It appears in search results next to your icon and rating, before anyone opens your listing. Treat it as your single best pitch, not an introduction.
4. Can I use the same screenshots for the App Store and Google Play?
No. Apple’s required 1320 × 2868 dimensions fall outside Google Play’s 2:1 maximum aspect ratio. Design one layout, export two sets.
5. Should screenshots have text captions?
Yes. A short benefit caption, 6 words or fewer, above the device frame. Captioned, composed screenshots consistently outperform raw UI captures in store listing tests.
6. Portrait or landscape?
Portrait, unless you’re a game or video app that genuinely lives in landscape. Portrait shows 3 screenshots per screen width on iOS; a landscape first screenshot takes the whole row and cuts your above-the-fold pitch from 3 messages to 1.
7. What’s a good tap-to-install rate?
The 2026 averages are 33.4% on iOS and 27.7% on Google Play. Above 30% is strong for most categories. Below 15% almost always means a creative problem, and screenshots are the first place to look. Check where you stand with the free ReachFront ASO Score check.
8. How often should I update screenshots?
Run a store listing test whenever you ship a major feature, rebrand, or see conversion drop, and review the set at least every 6 months. Screenshot tests are free on both stores and routinely beat metadata tweaks for impact.
Start with the first one
You don’t need 10 perfect screenshots this week. You need one: a first screenshot with a real caption, showing a real outcome, readable at thumbnail size. That single file is in front of every person who ever searches your keywords.
Design it, ship it, test it against your current one. Then do the next two.
And if you’d rather not fight export sizes and device frames by hand, ReachFront Studio generates store-ready screenshot sets for both stores from one design. Run your listing through the free ASO score check first and see how much room you’ve got.