Quick Answer
The best app store screenshots front-load your strongest value in the first two images (most users never swipe past them), use 5-7 word benefit captions, and connect every frame into one visual story. Add social proof, localize per market, and A/B test with Apple Product Page Optimization. For sizing in 2026, Apple needs only one iPhone set — the 6.9-inch display at 1320 x 2868 px — and scales it down to every smaller iPhone automatically. Well-optimized screenshots can lift conversion by 25% or more.
Why App Store Screenshots Decide Whether You Get Installed
Your screenshots are the single biggest controllable lever on your product page. Apple and Google both render the first two or three screenshots directly in search results and the gallery preview — before anyone taps "Read More" on your description.
Industry ASO data is consistent on this: the majority of visitors decide to install or bounce based on the first impression frame alone, and most never swipe to screenshot four or five. A large share of users make the install decision without scrolling the page at all. That means your top three frames are doing nearly all the work.
The good news: screenshots are also the easiest asset to test and iterate. You don't need a new build to ship a new screenshot set. Below are nine concrete tactics, with the conversion logic behind each.
What Are the App Store Screenshot Sizes in 2026?
Before tactics, get the canvas right. Uploading the wrong resolution gets your set rejected or scaled into mush. The big shift to know: Apple no longer wants a separate screenshot set for every device. Since the 2024 simplification, you upload one iPhone set (6.9-inch) and, if you support iPad, one iPad set (13-inch) — Apple scales those down to every smaller device automatically.
| Platform / Device | Display class | Portrait resolution (px) | Status |
|---|---|---|---|
| iPhone 17 Pro Max / 16 Pro Max | 6.9" | 1320 x 2868 | Required iPhone set |
| iPhone 15 / 14 Plus (older Pro Max) | 6.7" | 1290 x 2796 | Accepted, not required |
| iPhone (legacy Plus / Max) | 6.5" | 1242 x 2688 | Accepted, not required |
| iPad Pro (13") | 13" | 2064 x 2752 | Required if you support iPad |
| Google Play (phone) | — | 1080 x 1920 recommended | Min 320px, max 3840px per side |
| Google Play feature graphic | — | 1024 x 500 | Mandatory for every Play listing |
Apple requires at least one 6.9-inch iPhone screenshot (1320 x 2868); the 6.5-inch set is only required if you skip the 6.9-inch one. Apple scales your largest set down to smaller iPhones automatically, so render your master at 6.9-inch — upscaling from a smaller size makes text fuzzy on Pro Max devices. Google Play requires a minimum of two phone screenshots plus the 1024 x 500 feature graphic. Export at native resolution, never upscaled, and hit the exact pixel count — a submission even one pixel off-spec gets rejected.
The 9 App Store Screenshot Best Practices
1. Front-load your strongest value in frames one and two
Treat screenshot one as a billboard, not a tour. Lead with the single most compelling benefit or your hero moment. Because the first two frames appear in search results, a weak opener silently kills installs before the gallery even opens. Put your best foot first — never save the payoff for frame five.
2. Write benefit captions, not feature labels
Every screenshot needs a short caption overlaid above the device. Keep it to 5-7 words and write the benefit, not the feature. "Track every workout automatically" beats "Activity dashboard." Captions that lead with an outcome consistently outperform UI labels. Use a large, bold, legible type size — captions must read at thumbnail scale.
3. Build a connected visual narrative across the set
Don't ship six unrelated rectangles. The strongest sets read as one continuous scene — a background color, gradient, or graphic element that flows from frame to frame so the gallery feels designed, not assembled. Connected, panoramic-style screenshot sets are repeatedly cited as a top driver of higher conversion because they pull the eye through the whole story.
4. Add social proof and trust signals
Numbers and credibility belong in your screenshots, not buried in the description. Surface a star rating, an award badge, a press logo, or a user count ("Trusted by 2M+ creators"). Social proof reduces perceived risk at the exact moment of decision and is one of the highest-ROI additions to an existing set.
5. Show the app, not just marketing fluff
Use real device frames around real UI. Shoppers want to see what they're actually getting. Floating, frameless marketing illustrations with no product context tend to underperform authentic in-device screenshots. Realistic frames also signal polish and platform-native quality.
6. Localize screenshots per market
Translating only your text metadata leaves conversions on the table. Captions, currency, and culturally relevant imagery should be localized per storefront. Localized screenshot sets routinely outperform a single English set in non-English markets — sometimes by double digits in conversion — because they remove friction and feel made-for-me.
7. Optimize for thumbnail legibility
Most of your impressions happen at small size in search and browse. Test every frame zoomed out to ~30%. If the caption is unreadable or the UI is noise at thumbnail scale, simplify: bigger type, fewer elements, higher contrast. Design for the thumbnail first, the full-size view second.
8. Use portrait orientation (for most apps)
Unless you're a landscape game or video tool, default to portrait. Portrait screenshots show three frames in the preview row instead of one wide landscape image, giving you more billboard space in search results and more chances to land your message.
9. A/B test with Apple Product Page Optimization (PPO)
Stop guessing. Apple's free Product Page Optimization lets you run up to three screenshot treatments against your default and reports statistically valid conversion lift. Google Play Store Listing Experiments does the same. Teams that test methodically commonly find 15-30% conversion improvements from screenshot changes alone. Test one variable at a time — caption copy, order, or background — so you know what actually moved the needle.
Ship a Connected, Store-Ready Set Without a Designer
Executing all nine tactics by hand in Figma or Photoshop is slow — exact pixel dimensions, consistent backgrounds, matching captions across six frames, then re-exporting for every device class. That's where echodesigns is built to help.
You drop your raw app artwork into a realistic device frame, add a background and a benefit caption, and arrange a connected multi-screen set that shares one visual story — the exact narrative pattern from tactic three. Then you export at the precise store resolution (1320 x 2868 for the 6.9-inch iPhone, 1080 x 1920 for Play, 4K-ready PNGs on Pro) without ever touching a layout grid.
Because the editor runs in the browser and keeps your branding consistent across the whole set, you can spin up an A/B variant for Apple PPO in minutes instead of a designer's afternoon. New to the workflow? Start with our other guides on the echodesigns blog, or just open the editor and build your first frame.
Frequently Asked Questions
How many screenshots should I upload to the App Store?
Apple allows up to 10 per device class and Google Play up to 8. But because most users only see the first two or three, prioritize quality over filling every slot. Five to eight strong, connected frames usually outperform ten weak ones. Make the first three carry your core pitch.
What size should App Store screenshots be in 2026?
Submit one 6.9-inch iPhone set at 1320 x 2868 px (portrait); Apple scales it down to smaller iPhones automatically. The older 6.7-inch (1290 x 2796) and 6.5-inch (1242 x 2688) sets are still accepted but no longer required. For iPad add 2064 x 2752 px, and for Google Play use 1080 x 1920 px plus a 1024 x 500 feature graphic.
Do screenshot captions actually improve conversions?
Yes. Short benefit-driven captions consistently lift install rates because they communicate value at thumbnail scale, where raw UI alone is unreadable. Keep captions to 5-7 words, lead with the outcome, and use large bold type. Test caption copy with Apple PPO to measure the exact lift on your listing.
Should my screenshots use device frames or be frameless?
For most apps, realistic device frames win — they show the product in context and signal native polish. Frameless marketing graphics can work as an occasional accent frame, but a fully frameless set often reads as generic. echodesigns gives you accurate, current device frames so your UI looks real.
How do I A/B test app store screenshots?
On iOS use Apple's free Product Page Optimization to run up to three treatments against your default and read statistically valid conversion lift. On Android use Google Play Store Listing Experiments. Change one variable at a time so you can attribute the result.
The Bottom Line
Your first two screenshots decide most of your installs, so front-load value, write 5-7 word benefit captions, connect the set into one story, add social proof, localize, and let Apple PPO prove what works. The tactics are simple; the bottleneck is execution. Build a consistent, store-ready, perfectly-sized set in minutes — Try echodesigns free.