Your App Store screenshots are the most viewed piece of marketing your app will ever have. Every time someone taps your app in search results, they see your screenshots before they read a single word of your description. Most users decide whether to download in under 7 seconds.
This guide covers everything a mobile app founder needs: the exact dimensions for every device and platform, the design principles that lift conversion by 20–35%, and a practical workflow for creating on-brand screenshots without a design team.
App Store Screenshot Dimensions: Quick Reference (2026)
For iPhone, upload screenshots at 1320×2868 pixels (6.9-inch display, iPhone 16 Pro Max) — Apple will automatically scale them for smaller devices. For Google Play, use 1080×1920 pixels for phones. Maximum file size is 10 MB for iOS (PNG preferred) and 8 MB for Google Play. You can upload up to 10 screenshots per device type on iOS and up to 8 on Google Play.
iOS App Store
| Device | Required Size | Notes |
|---|---|---|
| iPhone 6.9" (16 Pro Max) | 1320×2868 px | Required minimum — upload this |
| iPhone 6.7" (15 Pro Max/Plus) | 1290×2796 px | Optional — Apple scales from 6.9" |
| iPad 13" (Pro) | 2064×2752 px | Required if app supports iPad |
| iPad 11" | 1668×2388 px | Optional — scales from 13" |
iOS file requirements: PNG (preferred) or JPEG · Max 10 MB per file · Up to 10 screenshots per device · Vertical orientation used by 96% of top apps
Google Play
| Device | Recommended Size | Notes |
|---|---|---|
| Phone | 1080×1920 px | Minimum; aspect ratio must not exceed 2:1 |
| 7-inch tablet | 1200×1920 px | |
| 10-inch tablet | 1600×2560 px |
Google Play file requirements: JPEG or 24-bit PNG (no alpha) · Max 8 MB per file · Up to 8 screenshots per device type
Can I use the same screenshots for both stores?
Not directly — the required dimensions differ (iOS 1320×2868 vs Google Play 1080×1920). However, if you design at 1320×2868 with safe margins, you can crop or export a second version at 1080×1920 with minimal rework. The aspect ratio is close enough that the visual design survives the resize in most cases.
Why Screenshots Are Your Highest-ROI Marketing Asset
Most app founders underinvest in screenshots relative to their impact. Here's the math:
The average user spends about 7 seconds on an App Store product page. In search results, they see only your app icon and the first two screenshots before they decide to tap through — or move on. The first three screenshots visible after tapping account for the majority of conversion decisions.
Research across thousands of app store experiments shows that optimizing your screenshot set — better captions, clearer value proposition, stronger visual design — lifts install conversion by 20–35%. For comparison, improving your keyword targeting typically moves conversion by 5–15%. Screenshots are the higher-leverage optimization.
This is also why it matters to update screenshots regularly. An app that has shipped significant product changes but kept its original screenshots is showing users a version of itself that no longer exists — and missing the conversion lift of showing the improved product.
Screenshots are not documentation. They are your primary sales page.
The 5 Rules of a High-Converting Screenshot Sequence
These principles apply to both App Store and Google Play, across any app category.
Rule 1: Lead with outcome, not feature. "Save 2 hours every week" converts better than "Calendar integration." "Fall asleep faster" converts better than "Sleep tracking." Users care about what your app helps them achieve — the feature is evidence of that, not the selling point. Every caption should answer: what does the user get?
Rule 2: Tell a narrative arc. Your 5–8 screenshots should tell a story. Screenshot 1 is the hook. Screenshots 2–4 are the proof. Screenshots 5–8 are supporting evidence and depth for users who are close to converting. Don't treat each screenshot as a standalone — each one should make the next one more compelling.
Rule 3: Show real UI with realistic data. Apple requires screenshots to accurately represent actual app UI. Beyond compliance, realistic data converts significantly better than empty interfaces. A calendar app showing a filled week converts better than one with a blank screen. A finance app showing sample transactions converts better than empty charts. Users are imagining themselves using the app — help them visualize it with real-looking content.
Rule 4: Keep captions short and benefit-driven. 5–8 words is the optimal caption length for app store screenshots. They need to be readable as a tiny thumbnail in search results. Test your captions at 50% zoom — if you can't read it easily, it's too small or too long.
Rule 5: Maintain visual brand consistency across all screenshots. Your 8 screenshots should look like they came from one brand — same background color family, same font and weight, same logo placement, same corner radius treatment on device frames. Visual inconsistency across a screenshot set signals low quality to users subconsciously, even if they can't articulate why. This is the most commonly neglected rule.
What to Put in Each Screenshot Slot
Most guides tell you to "put your best screenshots first." Here's a more specific slot-by-slot framework:
Screenshot 1 — The Hook Job: make someone stop scrolling. This is your billboard. Use your clearest value proposition as the caption. Show the most recognizable or impressive screen in your app. This screenshot appears as a thumbnail in search results — it needs to work at tiny size. Avoid: welcome screens, login screens, settings menus.
Screenshots 2–3 — Primary Features Job: prove the value proposition from Screenshot 1. Show the two or three screens that are most central to why someone would download your app. Each gets a benefit caption that extends the story from Screenshot 1.
Screenshots 4–5 — Social Proof or Secondary Features Job: address objections and add depth. If you have user testimonials, star rating highlights, or press mentions, Screenshot 4 is a good place for a social proof graphic. Alternatively, show secondary features that serve users who are already interested but need more convincing.
Screenshots 6–8 — Advanced Features or Specificity Job: close the sale for users who are deep in evaluation mode. These screenshots are seen by users who are genuinely considering downloading — they have time to explore. Show more detailed features, edge cases handled, or platform-specific capabilities.
Brand Consistency Across All Your Screenshots
This is the gap most template tools don't solve well, and the one that matters most at scale.
When you use a screenshot generator like AppLaunchpad or AppScreens, you configure the brand manually: enter your hex color code, upload your logo file, select a font. This works for the first session. Over time, your brand evolves — you adjust your primary color, update your logo, change your heading font. The templates you saved no longer match your actual product. Your screenshots look slightly off from your app's real UI and from your other marketing materials.
This divergence is subtle but consistently impacts conversion. A user who sees your ad on Instagram (in your current brand), then lands on your App Store page (showing your old brand from 6 months ago) experiences a small moment of visual dissonance that erodes trust.
The reliable fix is to generate screenshots from a tool that reads your current brand from your live website rather than a manually configured template. Framiq extracts your actual CSS hex values, loaded fonts, and logo directly from your URL — so your screenshots automatically match your live site and your other marketing assets (OG images, social posts, ad creatives) without any manual synchronization.
This is especially useful for B2C founders who are iterating frequently. As covered in our B2C app marketing assets guide, the ongoing nature of consumer app marketing makes brand drift a recurring problem, not a one-time setup issue.
Creating App Store Screenshots Without a Designer
You have three practical options, ranging from most manual to most automated:
AppLaunchpad (free tier available) Template-based generator with 1000+ layouts. You select a template, enter your brand colors manually, upload your screenshots, add captions, and export at the required dimensions. Good for founders who want control over every visual detail. Works for both iOS and Google Play formats.
AppScreens / AppScreen Studio Similar to AppLaunchpad but with different template aesthetics. AppScreen Studio offers a fully free tier. Both handle the dimension requirements for iOS and Google Play correctly. Same manual brand configuration process.
Framiq (brand-aware, multi-asset) Framiq generates device mockups using your brand identity extracted automatically from your URL — your real colors, fonts, and logo. Upload a product screenshot, confirm your URL, and Framiq generates a branded device mockup at the correct dimensions. The advantage is consistency: the same brand that appears in your Framiq-generated OG images and social posts appears in your App Store screenshots, because they're all drawn from the same URL-based brand extraction.
Practical workflow (no designer):
- Capture clean screenshots of each screen you want to feature from your actual device or simulator
- In Framiq, upload each screenshot and point it at your URL
- Generate device mockups with brand overlay and captions for each slot
- Export at 1320×2868 (iOS) and 1080×1920 (Google Play)
- Upload to App Store Connect and Google Play Console
- After launch, run Product Page Optimization (iOS) or Store Listing Experiments (Android) to test variants
For your Product Hunt launch, the same Framiq session that generates your App Store screenshots can produce your Product Hunt gallery images, OG image, and social announcement posts — making the full visual asset suite consistent across every platform where you launch.
Frequently Asked Questions
What size should App Store screenshots be?
For iPhone, upload screenshots at 1320×2868 pixels (6.9-inch display). This is the required minimum for iOS as of 2026, and Apple will automatically scale to smaller devices. For Google Play, use 1080×1920 pixels for phone screenshots. iOS files should be PNG (preferred) or JPEG under 10 MB. Google Play requires JPEG or 24-bit PNG (no alpha) under 8 MB.
How many screenshots should I upload to the App Store?
iOS allows up to 10 screenshots per device type; Google Play allows up to 8. In practice, 5–8 is standard for most apps. The first two screenshots are most critical — they're visible in search result thumbnails without tapping through. Upload enough to tell your full feature story without padding with low-quality screens just to reach the maximum.
Do App Store screenshots need to be vertical?
Not technically — Apple and Google both allow landscape screenshots. However, 96% of top-performing apps use vertical (portrait) orientation because most users browse the store in portrait mode. Vertical screenshots take up more visual space in the browse view. Unless your app is specifically landscape-first (games, video players), use vertical.
What is the difference between iOS and Google Play screenshot requirements?
The main differences are dimensions (iOS requires 1320×2868 for iPhone 6.9"; Google Play requires 1080×1920 for phones), file size limits (10 MB for iOS, 8 MB for Google Play), and alpha channel support (Google Play does not allow alpha/transparency in PNG files). Both require actual in-app UI — neither allows screenshots that misrepresent the app experience.
Can I use the same screenshots for both the App Store and Google Play?
Not directly, due to dimension differences. However, if you design at 1320×2868 with safe margins, you can export a cropped/resized version at 1080×1920 for Google Play with minimal visual rework. Tools like Framiq, AppLaunchpad, and AppScreens support exporting the same design to both required dimensions simultaneously.