When a user lands on your app's store listing, they see your screenshots before they read a single word of your description. In fact, according to industry analysis reported by Search Engine Journal's ASO guide, 60% of users won't swipe past your first two images — making your screenshot sequence the most valuable real estate in your entire app listing.
Yet mismatched dimensions, wrong file formats, or missing device variants are among the most common submission errors developers face. Apple's App Store Connect and Google Play Console each maintain distinct, device-specific requirements — and getting any one of them wrong means your screenshots either display cropped, stretched, or not at all.
This guide gives you the authoritative, complete picture of screenshot requirements for both stores in 2026, so you can submit with confidence.
By the Numbers: Why Screenshot Specifications Matter
Before diving into specs, here's the data case for getting them right:
- 60% of users stop scrolling after the first two screenshots (Search Engine Journal, ASO Guide)
- Apps with properly formatted screenshots see 25–30% higher conversion rates compared to listings with display errors or cropped images
- 5% of users read the full app description — meaning your screenshots carry the burden of explaining your app's value proposition to the overwhelming majority
- Apps with localized screenshots covering 10+ locales see an average uplift of 47% in installs in non-English-speaking markets (based on AppTweak platform analysis)
- 70% of app users discover new apps through search on the Google Play Store — making your listing's visual presentation the primary decision gate
Apple App Store Screenshot Requirements
Apple's App Store uses device-specific screenshot sets. Every app must provide screenshots for each device type on which it runs. As of 2026, the following dimensions apply in App Store Connect:
iPhone Screenshot Dimensions
| Device | Orientation | Dimensions (px) | Retina |
|---|---|---|---|
| iPhone 16 Pro Max | Portrait | 1,386 × 1,920 | @3x |
| iPhone 16 Pro | Portrait | 1,179 × 2,556 | @3x |
| iPhone 16 / 16 Plus | Portrait | 1,179 × 2,556 | @3x |
| iPhone 15 Pro Max | Portrait | 1,386 × 1,920 | @3x |
| iPhone 15 Pro / 15 | Portrait | 1,179 × 2,556 | @3x |
| iPhone SE (3rd gen) | Portrait | 750 × 1,334 | @2x |
Minimum: Apple requires at least one screenshot set. Portrait orientation is strongly recommended as the primary format.
iPad Screenshot Dimensions
| Device | Orientation | Dimensions (px) |
|---|---|---|
| iPad Pro 13" (M4) | Portrait | 2,064 × 2,748 |
| iPad Pro 11" (M4) | Portrait | 1,660 × 2,360 |
| iPad Air 11" / 10.9" | Portrait | 1,644 × 2,360 |
| iPad mini 8.3" | Portrait | 1,326 × 2,000 |
Apple Watch and Apple Vision Pro
- Apple Watch: Screenshot requirements depend on watchOS version and display size. Always verify in App Store Connect before submitting.
- Apple Vision Pro: Spatial computing apps require specific asset packs documented in Apple's visionOS Human Interface Guidelines.
Key Apple Requirements at a Glance
- File format: PNG or JPEG (PNG strongly recommended)
- Color space: sRGB (Apple uses Display P3 in some contexts but expects sRGB delivered assets)
- Maximum file size: 25 MB per screenshot
- 5.5-inch display option: Required if your app supports iPhone 5.5-inch displays (iPhone 8 Plus, X, XS, 11, 12, 13, 14 Plus models). Dimensions: 1,242 × 2,200 px (portrait)
- 6.5-inch display option: Required for all apps running on 6.5-inch iPhones (iPhone XS Max, 11 Pro Max, 12 Pro Max, 13 Pro Max, 14 Plus, 15 Plus, 16 Plus). Dimensions: 1,284 × 2,778 px (portrait)
- App preview video (optional): MP4 or MOV, H.264, 30fps max, AAC audio. 6–15 seconds for iPhone, up to 30 seconds for iPad.
- Do NOT include device frames — Apple rejects screenshots that include device hardware rendering
Pro tip from Apple's Human Interface Guidelines: Your first screenshot is your headline. Design it as a standalone brand statement — users should understand your app's core value without swiping.
Google Play Screenshot Requirements
Google Play's requirements differ from Apple's in two key ways: Google Play uses a minimum of 2 screenshots (vs. Apple's at least 1), and Google enforces a 16:9 to 9:16 aspect ratio range rather than fixed pixel dimensions.
Standard Screenshot Specifications
- Accepted formats: PNG or JPEG (lossless PNG recommended)
- Color space: sRGB
- Minimum dimensions: 320 px on the shortest side
- Maximum dimensions: 3,840 px on the longest side
- Maximum file size: 16 MB per screenshot
- Aspect ratio range: Between 1:2 and 2:1 (i.e., portrait 9:16 to landscape 16:9)
- Minimum screenshot count: 2
- Maximum screenshot count: 20 (though only 8 display in the main listing)
Required vs. Optional Screenshot Types
Google Play Console distinguishes between:
- Phone screenshots (required) — shown on phone devices and contribute to the main listing
- 7-inch tablet screenshots (optional but recommended) — shown on 7-inch Android tablets
- 10-inch tablet screenshots (optional but recommended) — shown on 10-inch Android tablets
If you don't provide tablet screenshots, Google Play may crop or downscale your phone screenshots on tablet devices — often resulting in unreadable text or cut-off UI elements.
Store Listing Experiments (A/B Testing)
Google Play Console's Store Listing Experiments feature lets you A/B test screenshots directly in the dashboard — a major advantage over Apple, which only offers Product Page Optimization tests through App Store Connect. Apps that systematically test their screenshots see conversion rate improvements ranging from 10–25% based on industry benchmarks from mobile growth platforms.
App Preview Video (Google Play)
- Format: MP4 (H.264 or VP9), WebM, or AVI
- Duration: 10 seconds minimum, 30 seconds maximum (Google recommends 15–30 seconds for best engagement)
- Dimension requirements: Same as screenshots — must fall within 1:2 to 2:1 aspect ratio
- File size: Up to 100 MB
Side-by-Side Comparison: App Store vs. Google Play
| Requirement | Apple App Store | Google Play |
|---|---|---|
| Minimum screenshots | 1 | 2 |
| Maximum screenshots | 10 per device set | 20 |
| Primary format | PNG (recommended), JPEG | PNG (recommended), JPEG |
| Color space | sRGB | sRGB |
| Maximum file size | 25 MB | 16 MB |
| Device frames allowed | No | No |
| Aspect ratio flexibility | Fixed per device | 1:2 to 2:1 range |
| Tablet-specific screenshots | Optional per device type | Optional but recommended |
| App preview video | Optional, 6–30 sec | Optional, 10–30 sec |
| A/B testing in console | Via Product Page Optimization | Native Store Listing Experiments |
| Localized screenshots | Per locale | Per locale |
Common Mistakes That Lead to Rejection or Display Errors
1. Submitting the Wrong Dimensions for Apple
The most frequent App Store rejection cause is screenshot dimensions that don't match Apple's documented specs. Even being off by a few pixels triggers rejection. Always verify your delivery dimensions against the official Apple screenshot specifications in App Store Connect, as requirements can shift slightly with new device releases.
2. Cropped Text or UI on Google Play
Because Google Play allows a range of aspect ratios, screenshots designed for a specific device may display with cropping on devices with different screen shapes. Always test your screenshots at the extremes of the acceptable ratio range: 1:2 (portrait) and 2:1 (landscape).
3. Forgetting Tablet Assets
Many developers only submit phone screenshots for Google Play. On a 10-inch tablet, cropped phone screenshots look unprofessional and can reduce conversion. Provide dedicated tablet assets whenever possible.
4. Device Frames on Apple
Apple explicitly prohibits device frames (iPhone outlines, notch renderings, etc.) in App Store screenshots. This rule has been strictly enforced since 2020. Google Play permits frames, but most top-performing apps avoid them for a cleaner, more design-forward look.
5. Wrong File Format or Oversized Files
Apple accepts JPEG at up to 25 MB; Google Play caps screenshots at 16 MB. Both require PNG for optimal quality. Always compress carefully — lossy JPEG artifacts on text or UI elements look unprofessional and can trigger review concerns.
How to Create Compliant Screenshots Efficiently
Managing screenshot sets across two platforms — each with multiple device sizes and optional tablet variants — can quickly become a production bottleneck. Tools like ScreenCraft let you design once and export to multiple officially compliant dimensions in bulk, with locale support for over 35 languages.
Key workflow optimization tips:
- Design at the highest resolution (iPhone 16 Pro Max portrait at 1,386 × 1,920) and scale down — never scale up from smaller sources
- Use vector-based design tools to maintain sharpness across all export sizes
- Export platform-specific batches rather than manually recreating each variant
- Test on real devices before submission — simulators and design previews can misrepresent how screenshots display with device status bars, rounded corners, and notch areas
Localization: A Multiplier for Install Growth
If you're targeting international markets, localized screenshots are not optional — they're a growth lever. AppTweak's analysis of localized app listings shows that apps with professionally translated and culturally adapted screenshots covering 10+ locales see an average uplift of 47% in installs in those target markets.
Both App Store Connect and Google Play Console allow you to upload locale-specific screenshot sets. Budget for at least your top 3–5 markets by install volume, and always adapt:
- Text translation (never rely on auto-translate for UI screenshots)
- Cultural context (colors, imagery, and layouts that resonate in specific regions)
- Text length (German text can be 30–40% longer than English equivalents, affecting text box sizing)
Conclusion
Screenshot requirements for iOS and Android differ in meaningful ways — not just in dimensions, but in philosophy. Apple's approach is device-prescriptive, demanding exact pixel specifications per device. Google Play takes a more flexible, ratio-based approach that requires more design judgment on your end.
Both, however, share one fundamental truth: your screenshots are your listing's sales team. With 60% of users refusing to swipe past the first two images, the cost of getting dimensions wrong isn't just a rejection email — it's lost installs, lost revenue, and lost market share.
Get the specs right. Design for conversion. Test across devices. And use the right tools to scale your screenshot production without scaling your workload.
Key Data Points Summary
| Statistic | Source |
|---|---|
| 60% of users won't swipe past the first two screenshots | Search Engine Journal ASO Guide |
| 5% of users read the full app description | Search Engine Journal ASO Guide |
| Apps with localized screenshots see ~47% install uplift in target markets | AppTweak platform analysis |
| App Store screenshot max file size: 25 MB | Apple App Store Connect Guidelines |
| Google Play screenshot max file size: 16 MB | Google Play Console |
| Apple requires at least 1 screenshot; Google Play requires at least 2 | Official platform guidelines |
| Aspect ratio range for Google Play: 1:2 to 2:1 | Google Play Console |
| iPhone 16 Pro Max portrait dimensions: 1,386 × 1,920 px @3x | Apple App Store Connect |
| A/B tested apps see 10–25% conversion rate improvements | Mobile growth platform benchmarks |