Your app does something genuinely useful. Users love it once they try it. But your product page converts at 18% while your competitor hits 42%. The difference is almost always screenshots.
App Store screenshots are the most influential element on your product page. Apple gives you 10 slots maximum. Most users only see the first 3.
Getting specs wrong means rejection. Getting design wrong means invisibility.
Why screenshots decide your conversion rate
70% of App Store visitors never scroll past the first impression. They see your icon, your first three screenshots, and your star rating. That's the entire pitch. If those screenshots look generic or confusing, they bounce.
Apple's own data shows that optimized screenshots lift conversion rates by 25-35%. That's the gap between 1,000 daily installs and 1,350 daily installs from the same traffic. Over a year, that compounds into tens of thousands of additional users at zero acquisition cost.
Higher conversion rates also signal quality to the algorithm. Apple surfaces apps that convert well more frequently in editorial features and category rankings.
Technical requirements Apple enforces
Apple rejects screenshots that miss their specifications. Every pixel dimension, file format, and display size must match exactly. Getting this wrong adds 3-7 days to your release cycle while you resubmit.
File format and general rules
All screenshots must be PNG or JPEG. RGB color space only. No alpha transparency. You can upload 1 to 10 screenshots per localization.
Each must match Apple's accepted resolutions exactly. No scaling, no rounding.
Required screenshot sizes by device
Apple requires screenshots for specific display sizes. Missing a required size triggers a validation error in App Store Connect.
| Display Size | Device Example | Portrait (px) | Landscape (px) | Required |
|---|---|---|---|---|
| 6.7" Super Retina | iPhone 16 Pro Max | 1320 x 2868 | 2868 x 1320 | Yes (if supporting) |
| 6.5" Super Retina | iPhone 11 Pro Max | 1284 x 2778 | 2778 x 1284 | Yes |
| 5.5" Retina | iPhone 8 Plus | 1242 x 2208 | 2208 x 1242 | Yes |
| 12.9" Retina (3rd gen+) | iPad Pro 12.9" | 2048 x 2732 | 2732 x 2048 | Yes (if iPad supported) |
| 12.9" Retina (2nd gen) | iPad Pro 12.9" (2017) | 2048 x 2732 | 2732 x 2048 | Yes (if iPad supported) |
| 11" Retina | iPad Pro 11" | 1668 x 2388 | 2388 x 1668 | Optional |
| 10.5" Retina | iPad Air (3rd gen) | 1668 x 2224 | 2224 x 1668 | Optional |
| 9.7" Retina | iPad (6th gen) | 1536 x 2048 | 2048 x 1536 | Optional |
The 6.5" display screenshots can be used as a fallback for the 6.7" size. Apple auto-scales them. But native 6.7" screenshots look sharper on newer devices and signal attention to detail.
iPad screenshot specifics
If your app runs on iPad, you must provide 12.9" iPad Pro screenshots. Apple won't let you submit without them. Many developers skip iPad screenshots entirely and miss a massive audience. iPad users have 3x higher lifetime value than iPhone-only users in most subscription categories.
The first three screenshots matter most
Apple displays your first three screenshots in search results and category pages. These three images are your storefront window. Everything else requires a tap.
Users spend 7 seconds on average before deciding. Those three frames must communicate your core value fast.
Screenshot one: your hero shot
The first screenshot carries 60% of the conversion weight. It should show your app's most compelling feature in action. Not a splash screen. Not a logo.
Show an actual use case that resonates with your target user's pain point.
Pair the screen with a short text overlay. Seven words maximum. State the benefit, not the feature. "Track expenses in 3 seconds" beats "Expense tracking app" every time.
Screenshots two and three: support the story
Screenshot two reinforces the first with a complementary feature. Screenshot three addresses the biggest objection your users have. Together, these three frames tell a complete story. A user who never scrolls should still understand what your app does and why it matters.
Design patterns that convert
Raw device screenshots convert poorly. They look like documentation, not marketing. The top-performing apps in every category use designed screenshot frames with strategic overlays.
Text overlays that work
Keep text overlays to 3-7 words per screenshot. Users scan, they don't read. Large bold fonts at 60-80pt equivalent work best on mobile. Position text in the top 30% of the frame where eyes land first.
Use your brand font if it's legible at small sizes. Avoid thin or decorative typefaces. The text must be readable as a 375px-wide thumbnail in search results, not just at full resolution.
Device frames and backgrounds
Placing your screenshot inside a device frame adds context. Users immediately recognize they're looking at an app. Gradient or solid backgrounds keep visual focus on the content.
Avoid busy patterns. The best apps use 1-2 brand colors as background across all 10 screenshots.
Panoramic and continuous layouts
Apple allows screenshots that span across multiple frames. A panoramic layout flowing across 2-3 screenshots creates visual intrigue and lifts scroll-through rates by 15-20%. Use this sparingly. Your first three screenshots must still work individually in search results.
Feature callouts and UI highlights
Draw attention to specific UI elements with subtle arrows or glow effects. This guides the eye to the feature your text describes. One callout per screenshot keeps things focused.
Localized screenshots multiply conversions
Translating your screenshot text overlays into local languages drives 25-40% higher conversion rates in non-English markets. This isn't a guess. It's backed by aggregate data across thousands of apps.
A Japanese user searching for a fitness tracker sees your screenshots. If the text overlays are in English, they scroll past. If the text reads "3秒で運動を記録" they stop and look. That single difference in perceived relevance changes everything.
The math behind localized screenshots
Say you get 500 daily product page views in Germany. Your English-only screenshots convert at 22%. That's 110 installs per day.
Localized German screenshots push conversion to 30%. That's 150 installs per day. An extra 40 daily compounds to 14,600 additional installs per year.
Now multiply that across Japan, France, Brazil, South Korea, and Spain. Localized screenshots across 10 markets can double your global install volume without a single dollar in ad spend. A solid app localization strategy makes this systematic rather than ad hoc.
What to localize in screenshots
Translate all text overlays into the target language. Update in-app content to match the locale. Show local currency, local date formats, and culturally relevant content. A recipe app should show local cuisine, not translated labels over American dishes.
Localizer Mate handles the metadata side. Grid Mate generates localized screenshot variants across every device size and language combination. Ten screenshots across 8 sizes and 35 languages means 2,800 individual images. That's not a weekend project.
App Preview videos
Apple lets you add up to 3 App Preview videos per localization. Each video plays automatically (muted) on the product page. Videos appear before your screenshots, making them the true first impression when present.
Video specifications
App Preview videos must be 15-30 seconds long. They use the same resolution as the corresponding device screenshot size. H.264 codec, 30fps minimum. Audio is optional but plays when unmuted.
Videos must show actual app footage. Apple rejects stock footage and live-action content. Screen recordings with minimal overlays work best.
Should you use App Preview videos?
Videos lift conversion by 15-25% when done well. But a bad video hurts more than no video. Apps with strong visual workflows benefit most.
Text-heavy apps often convert better with static screenshots alone. Test in your primary market first before rolling out globally.
Common screenshot mistakes that kill conversions
Some patterns consistently underperform. Avoiding these saves you testing cycles.
- Using raw screenshots with no design: Unframed device screenshots look amateur next to designed competitors.
- Leading with a settings screen: Nobody downloads an app because the settings look nice.
- Too much text per screenshot: More than 7 words per overlay and readability collapses at thumbnail size.
- Inconsistent visual style: Mixing colors, fonts, and frame styles across 10 screenshots creates visual chaos.
- Ignoring iPad entirely: Missing iPad screenshots means missing high-value tablet users.
- Same screenshots for every locale: English overlays in the Japanese App Store signal you don't care about that market.
A practical screenshot workflow
Here's the process that works for teams shipping across multiple markets.
- Define your 10-screenshot narrative arc: hero shot, key features, social proof, closing CTA.
- Design one master template per screenshot at 6.7" resolution with text overlay and device frame.
- Export variants for every required device size: 6.7", 6.5", 5.5", and iPad 12.9".
- Localize text overlays and in-app content for each target market.
- Generate all size and language combinations programmatically.
- Upload to App Store Connect per localization.
Grid Mate collapses steps 3-6 into a single automated pipeline. Design your master templates once and generate every variant across all sizes and localizations.
No Figma export marathons. No manual resizing. No uploading 2,800 images one by one.
Measuring screenshot performance
App Store Connect provides conversion data segmented by source. Compare your conversion rate before and after screenshot changes. Keep everything else constant for 2-3 weeks to isolate the variable.
Apple's product page optimization lets you A/B test up to three screenshot treatments. Use it. Opinions about "looks better" are worthless next to download data. Run tests at least 7 days to account for weekday versus weekend patterns.
Track conversion per localization to spot weak markets. A 15% rate in South Korea against a 32% global average means your Korean screenshots need work. Fix the weakest markets first.
Screenshots are a growth lever, not a chore
Most developers treat screenshots as a box to check during submission. Upload some device captures, fill the required slots, move on. That mindset leaves 20-40% of potential installs on the table.
The apps that dominate their categories treat screenshots as core ASO strategy. They design with intent, localize across markets, test with data, and iterate every cycle. The specs are strict, but the right pipeline makes screenshot creation routine instead of painful.
Get the first three screenshots right. Localize them. Measure the results. Everything else follows.