App Store Screenshots: Sizes, Layouts and Copy
App Store screenshots that convert: current iOS and Google Play sizes, the first-three rule, layout patterns, caption formulas and a checklist for your set.

This guide is for founders, indie developers and marketers preparing App Store and Google Play screenshots, whether for a first launch or a redesign of a set that is not converting. You will get the current required sizes, how screenshots appear in search and on product pages, layout patterns that work, caption formulas, and a checklist to review your set before upload.
TL;DR: Your first three screenshots do most of the work, because they are what people see in search results. Lead with the core benefit, use one short caption per screenshot, show the real app large and legible, and follow the order of a user's motivation, not your feature list. Upload the 6.9-inch iPhone size for Apple and at least four 1080 px screenshots for Google Play, then A/B test.
Why app store screenshots matter
On both stores, most people decide whether to install from the listing without reading the description. Screenshots are the largest, most visual element and show up directly in search results, so they act as your ad, your demo and your pitch in a few seconds of scrolling.
The goal of a screenshot set is not to document every feature. It is to answer three questions quickly: what is this, is it for me, and why is it better than the alternatives I can also see on this screen?
Current screenshot sizes and limits
Store requirements change, so confirm in App Store Connect and Play Console before exporting. As of this writing:
Apple App Store
| Item | Requirement |
|---|---|
| Number | Up to 10 screenshots per device size and language |
| iPhone 6.9-inch (required for iPhone apps) | 1320 × 2868 px or 1290 × 2796 px portrait |
| iPhone 6.5-inch (accepted alternative) | 1284 × 2778 px or 1242 × 2688 px portrait |
| iPad 13-inch (required if your app runs on iPad) | 2064 × 2752 px or 2048 × 2732 px portrait |
| Smaller sizes | Scaled automatically from the largest size you provide |
| Format | PNG or JPEG, no transparency |
| App previews | Up to 3 videos, 15 to 30 seconds each |
Google Play
| Item | Requirement |
|---|---|
| Number | 2 to 8 screenshots per device type |
| Dimensions | 320 px to 3840 px per side; the long side cannot exceed twice the short side |
| Recommended | At least 4 screenshots at 1080 px or more on the short side, which also makes apps eligible for more store placements |
| Feature graphic | 1024 × 500 px, shown at the top of the listing and in some placements |
| Promo video | YouTube link |
Our App Store screenshot sizes reference keeps every device size in one table.
How screenshots appear to users
Understanding placement changes how you design.
- •App Store search results show the first three portrait screenshots side by side (or the first landscape one). If your app preview video is first, it plays in that slot.
- •App Store product page shows screenshots in a horizontal scroll; the first two or three are visible without swiping.
- •Google Play listing shows a horizontal row of screenshots below the install button; search results show less, so the icon and title carry more weight.
The practical consequence: screenshots 1 to 3 must sell the app on their own. Screenshots 4 and later are for people who are already interested.
Plan the story before designing
Write the set as a sequence of benefits, ordered by what matters most to a new user.
- •Screenshot 1, the promise: the core benefit and the hero screen. "Split bills with friends in seconds."
- •Screenshot 2, the main proof: the feature that delivers the promise.
- •Screenshot 3, the differentiator: why you instead of the competitor next to you in search.
- •Screenshots 4–6, depth: secondary features, integrations, customization.
- •Final screenshot, trust or breadth: awards, privacy, platforms, or "and much more."
Look at your competitors' listings first. If every app in your category leads with a dashboard, leading with the outcome (a finished, beautiful result) will stand out. Our ASO screenshot teardowns break down real sets frame by frame.
Layout patterns that work
| Pattern | What it looks like | Good for |
|---|---|---|
| Caption + device | Short headline at top, phone frame below | Most apps; clear and easy to localize |
| Full-bleed UI | App screen fills the frame, caption overlaid | Visually rich apps: photo, maps, games |
| Panorama | One continuous background spanning several screenshots | Creating flow and encouraging swipes |
| Zoomed detail | A cropped, enlarged part of the UI | Showing small but important features |
| Lifestyle context | UI shown with illustrated or photographic context | Fitness, travel, food |
| Comparison | Before and after, or "with vs without" | Editing, productivity, finance apps |
Tips that apply to all patterns:
- •Make the UI large. Remember that screenshots appear small in search results. Tiny phone frames with tiny text read as gray noise.
- •Use real content, not lorem ipsum. Real names, prices and photos make the app believable.
- •Hide the clutter. Clean status bar (full battery, strong signal, a neat time), no debug labels, no notifications.
- •Keep one visual system. Same caption position, type and background family across the set.
- •Match light or dark to the app's default experience.
You can create device frames with the phone mockup generator and build complete sets with the App Store screenshot generator.
Writing captions that convert
Captions do the selling. Keep them short enough to read at thumbnail size.
Caption rules
- •Two to six words for the main line; an optional short subline.
- •Lead with a benefit or outcome, not a feature name. "Never miss a bill" beats "Smart notification system."
- •Use the user's words, the same terms they search.
- •One idea per screenshot.
- •Large type: bold, high contrast, readable at the size shown in search.
Caption formulas
| Formula | Example |
|---|---|
| Verb + outcome | "Plan meals in minutes" |
| Problem solved | "No more forgotten workouts" |
| Number + benefit | "500+ guided meditations" (only if true) |
| Social proof | "Loved by runners in 40 countries" (only if true) |
| Comparison | "Your whole budget on one screen" |
| Feature as benefit | "Offline maps, no signal needed" |
Avoid claims you cannot support, such as "#1 app" or award badges you did not win. Both stores have rules against misleading metadata.
Platform differences to respect
- •Show the right device. iPhone frames for the App Store, Android frames (or frameless UI) for Google Play. Apple's guidelines require screenshots to show the app in use, and Google Play policy prohibits misleading content, so do not show another platform's UI.
- •Do not reuse iOS UI on Google Play. If your Android app follows Material 3, show it.
- •Feature graphic: Google Play's 1024 × 500 banner needs its own design, and important content should stay away from the edges because it can be cropped or overlaid.
The UI in your screenshots should be the real app. If you are still building, design the hero screens first; our guides on making an iPhone app and making an Android app cover the listing requirements around them.
Localization
If your app supports several languages, localize screenshots, not just the description. At minimum translate captions; ideally show localized UI too. Watch for text expansion: German and French captions often run noticeably longer than English, so design captions with room to grow or allow two lines.
Test and iterate
Both stores let you test:
- •Apple Product Page Optimization runs A/B tests of icons, screenshots and previews against your default page.
- •Apple Custom Product Pages let you create alternative pages with different screenshots for specific ad campaigns or audiences.
- •Google Play store listing experiments test graphics and text variants.
Test one big variable at a time, such as the first screenshot's message or the overall style, and let tests run long enough to reach significance in the console.
Worked example: a budgeting app
- •"See where your money goes" with the spending breakdown dashboard.
- •"Set budgets that stick" with category budgets and progress bars.
- •"Bills reminded before they're due" with the upcoming bills screen and a reminder notification.
- •"All your accounts in one place" with the accounts list.
- •"Private by design" with security settings and a lock icon.
- •"Works on iPhone, iPad and Apple Watch" with the device family.
Screenshots 1 to 3 cover what it is, how it helps and why it is different. You can generate a first draft of the in-app screens for a set like this in floow and drop them into the frames.
App store screenshots checklist
- • Correct sizes for every required device and store
- • Screenshots 1 to 3 sell the app on their own
- • One benefit per screenshot, captions of 2 to 6 words
- • Captions readable at search-result size
- • Real app UI, real content, clean status bar
- • Consistent caption style and background system
- • Platform-correct devices and UI for each store
- • No unverifiable claims or fake badges
- • Google Play feature graphic designed separately
- • Localized captions for each supported language
- • A/B test planned for the first screenshot
FAQ
What size should App Store screenshots be?
For iPhone apps, Apple requires the 6.9-inch size, 1320 × 2868 px or 1290 × 2796 px in portrait, or accepts the 6.5-inch size; smaller sizes are scaled automatically. iPad apps also need 13-inch iPad screenshots. Check App Store Connect for the current list before exporting.
How many screenshots should I upload?
Apple allows up to 10 and Google Play up to 8 per device type. Use enough to tell your story, usually five to eight, but put the effort into the first three because they appear in search results.
Can I use the same screenshots for iOS and Android?
You can reuse the captions and story, but show platform-appropriate UI and device frames. Android users should see your Android app, and both stores discourage showing a different platform.
Should I use device frames in screenshots?
Frames help people recognize the image as a phone app and give structure, but they shrink the UI. Many successful sets use frameless or cropped UI to keep content large. Test both if you are unsure.
Do app preview videos help?
They can, especially for apps whose value is motion or interaction, like games or editing tools. On the App Store a preview in the first slot autoplays in search results, so its first seconds must be as clear as a screenshot.
Design it with floow
Generate the in-app screens for your store set in floow, then frame them for each store. Paste this prompt to start:
Design the 3 hero screens for App Store screenshots of an iOS budgeting app: a spending breakdown dashboard with a donut chart and categories, a budgets screen with progress bars, and an upcoming bills list with a reminder banner. Clean, realistic data, light mode, large legible numbers.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Guides22 November 2026Mobile App Accessibility: Designer and Founder ChecklistMobile app accessibility made practical: contrast, touch targets, Dynamic Type, VoiceOver and TalkBack labels, motion and a full pre-launch checklist.By floow.design
Roundups22 November 2026ScreensDesign Alternatives: 9 Places for Real App ScreensScreensDesign alternatives compared: Mobbin, Page Flows, Refero and more, with what each library is best for and how to turn references into your own screens.By floow.design
Insights21 November 2026Music App Design: Player, Library and DiscoveryMusic app design guide: home and discovery, search, library, mini player, now playing, queue and offline, plus lock screen, car and widget surfaces, with.By floow.design