For the App Store, the one iPhone size you must upload is the Dynamic Island medium display: 1206 x 2622 or 1179 x 2556 pixels in portrait, and 1 to 10 screenshots per size, as JPEG or PNG with no transparency, according to Apple's screenshot specifications.
If your app runs on iPad, you also need a 13-inch set at 2064 x 2752 or 2048 x 2732. Google Play is looser: any JPEG or 24-bit PNG between 320 and 3,840 pixels on each side, with at least two screenshots and a 1024 x 500 feature graphic, per Google's preview asset rules.
Below are the full size tables, how many screenshots to upload and in what order, where to get templates, and what real tests suggest about the first two frames.
All specs were checked against Apple's and Google's documentation as of November 2026.
iPhone and iPad screenshot sizes
Apple groups iPhones by display type, not by model name.
You upload one set per group, and App Store Connect scales your largest required set down to fit smaller devices.
Apple's rule: if your interface looks the same across sizes, "you only need to provide screenshots for the highest required resolution."
| Display group | Portrait sizes (pixels) | Example devices | Status |
|---|---|---|---|
| iPhone, Dynamic Island, medium | 1206 x 2622 or 1179 x 2556 | iPhone 18 Pro, 17, 17 Pro, 16, 15, 14 Pro | Required |
| iPhone, Dynamic Island, large | 1320 x 2868, 1290 x 2796 or 1260 x 2736 | iPhone Air, 18/17/16 Pro Max, 16 Plus, 15 Plus | Optional |
| iPhone, Face ID, large | 1284 x 2778 or 1242 x 2688 | iPhone 14 Plus, 13 Pro Max, 11, XR | Optional (scaled) |
| iPhone, Face ID, medium | 1170 x 2532, 1125 x 2436 or 1080 x 2340 | iPhone 17e, 16e, 14, 13, 12, X | Optional (scaled) |
| iPhone, Home button, large | 1242 x 2208 | iPhone 8 Plus, 7 Plus, 6S Plus | Optional (scaled) |
| iPhone, Home button, medium | 750 x 1334 | Older home-button iPhones | Optional (scaled) |
| iPhone Duo | 1398 x 2034 (outer) and 2007 x 2853 (inner) | iPhone Duo | Required from April 2027 for apps on the iOS 27.1 SDK or later |
| iPad 13-inch | 2064 x 2752 or 2048 x 2732 | iPad Pro (M5, M4), iPad Air (M4, M3, M2) | Required if the app supports iPadOS |
| iPad 11-inch | 1668 x 2420, 1668 x 2388, 1640 x 2360 or 1488 x 2266 | iPad Air, iPad (A16), iPad mini | Optional (scaled) |
Landscape versions use the same numbers flipped, so 2622 x 1206 is the landscape version of the required iPhone size.
Pick one orientation per set and stay with it.
The rules that trip people up
- No alpha channel. A PNG exported with transparency gets rejected. Flatten it or export as JPEG.
- Exact pixels. Apple only accepts the listed sizes. 1080 x 1920, a common design canvas, is not on the iPhone list.
- Medium is the required set now. Apple's page lists the Dynamic Island medium display as the one required iPhone size. If you also want sharp images on Pro Max, Plus and Air phones, upload a large set at 1320 x 2868.
- iPhone Duo is coming. Apple says Duo screenshots will be required starting in April 2027 for apps built with the iOS 27.1 SDK or later, and listings that include them get an "optimized for iPhone Duo" badge.
Mac, Apple TV, Vision Pro and Watch
If you ship on other Apple platforms, each needs its own set.
Apple's current specs: Mac at 16:10 (1280 x 800, 1440 x 900, 2560 x 1600 or 2880 x 1800), Apple TV at 1920 x 1080 or 3840 x 2160, Vision Pro at 3840 x 2160, and Apple Watch at sizes from 312 x 390 up to 422 x 514 for the newest Ultra models.
Watch screenshots must use the same size across all localizations.
Google Play screenshot sizes and the feature graphic
Google doesn't list fixed device sizes. Instead it sets a range and a ratio limit. These are the current Play Console requirements:
| Asset | Requirement |
|---|---|
| Phone screenshots | JPEG or 24-bit PNG, no alpha; each side 320 to 3,840 px; the long side no more than twice the short side; up to 8 per device type |
| Minimum to publish | 2 screenshots across device types |
| Recommended for promotion | Apps: at least 4 screenshots at 1080 px or more, 9:16 portrait (1080 x 1920 minimum) or 16:9 landscape (1920 x 1080 minimum). Games: at least 3 |
| Tablets and Chromebooks | At least 4 screenshots, 1,080 to 7,680 px, 16:9 or 9:16 |
| Wear OS | 1:1, at least 384 x 384, app interface only, no device frames or extra text |
| Android TV | At least 1 TV screenshot to publish |
| Feature graphic | 1024 x 500, JPEG or 24-bit PNG, no alpha; required to publish |
| App icon | 512 x 512, 32-bit PNG with alpha, 1,024 KB max |
A 1080 x 1920 portrait canvas is the safe default for Play phone screenshots.
It meets the promotion recommendation and stays inside the 2:1 ratio limit.
Feature graphic and content rules
The feature graphic shows up in several places on Google Play, including as the cover image for your preview video.
Google advises against prominent branding that repeats your icon, so treat it as a banner that sets the mood rather than a second logo.
Google also limits what goes on screenshots. Taglines should take up no more than 20% of the image, and you can't use wording about Google Play rankings, accolades or awards.
Apple's equivalent is App Review Guideline 2.3.3: screenshots "should show the app in use, and not merely the title art, login page, or splash screen."
Guideline 2.3.7 adds that screenshots shouldn't include prices or terms.
How many screenshots to upload, and in what order
Use every slot you can fill well: up to 10 on the App Store and up to 8 per device type on Google Play.
The order matters far more than the count, because most people never scroll past the first few.
On the App Store, the first one to three screenshots appear in search results when you don't have an app preview, depending on orientation.
Apple's advice is to make those "highlight the essence of your app" and to focus each later screenshot on one main benefit.
Google notes that screenshots may show in search and on the homepage, not just on your listing.
An order that works for most subscription apps:
- Frame 1: the core outcome. The result a user gets, shown on a real screen, with a caption of five to seven words.
- Frame 2: proof or the main differentiator. A rating, a well-known feature, or the thing competitors don't do.
- Frame 3: the first-session experience. What the user sees right after install, so the listing matches the onboarding.
- Frames 4 to 8: one feature each. Ordered by how often users mention them in reviews.
- Last frames: secondary features, integrations or dark mode. Apple suggests including one dark mode screenshot if your app supports it.
Portrait is the default for most apps because three portrait screenshots fit in an App Store search result.
Landscape fits games and video apps, but it usually means only one frame shows in search.
If you have an app preview, it takes the first slot, so plan the video and the first screenshot together. Our preview video guide covers that trade-off.
Screenshot templates and tools
You don't need to design from scratch. Three common routes:
- Apple Design Resources. Apple publishes product bezels for current iPhone, iPad, Mac and Watch models in Photoshop and PNG, plus an iOS and iPadOS UI kit for Figma. If you use bezels in marketing, Apple asks you to follow its marketing guidelines.
- Figma or Sketch templates. Set up frames at the exact pixel sizes above (for example 1206 x 2622 for iPhone and 1080 x 1920 for Play), then export each frame. One master file per language keeps localization manageable.
- Screenshot generators. Browser tools handle device frames, captions and exports for every required size at once. We compare them in our screenshot generator roundup.
Whatever you use, export a test set and upload it to App Store Connect or Play Console before you finish the whole batch.
Rejections for wrong pixel sizes or a hidden alpha channel are much cheaper to catch on frame one.
What tests say about the first two screenshots
An honest note first: LiftArchive doesn't yet have an app store screenshot test with published numbers.
Most store tests run in Apple's product page optimization or Google Play experiments and never get shared.
We collect them on our store listing tests page as they appear.
What we do have are in-app tests of the same idea: show people the product and its result before you ask them to commit. They point in one direction.
- Unchaind tested a paywall that previews its premium features and saw over +50% conversion and +64% estimated ARPU (vendor-reported, from a Superwall case study).
- Clear 30 moved from 20% to 30% conversion (+50%) after switching to a paywall that previews the program. This was a before-and-after change, not a split test.
- FitnessAI reported about +80% revenue after adding video to its paywall, also a before-and-after change.
- PepTalk, working with Kovalee, tested a 10-second video preview before the paywall. Variant B beat variant A clearly, and both trended above control.
Localization is the other lever. Photoroom saw +50% upsell screen conversion from localized paywalls, and Daily Horoscope reported +183% trial start rate from paywalls localized by country (a bundled change, vendor-reported).
If translated screens convert that much better inside the app, translated screenshot captions are worth testing in your largest non-English markets.
KovaleeEcommerce product galleries are the closest web match to a screenshot carousel, and there the first image is also tested often.
In one test, moving the second product photo into first position raised revenue per visitor from £3.32 to £3.60. In another, a new first product image lifted conversion by 10.26%.
The lesson carries over: the lead frame is worth testing before anything else in the set.
How to test your own first frames
- Write two versions of frame 1 that differ in one thing: the outcome shown, the caption, or the screen.
- Run them in product page optimization on iOS or a store listing experiment on Play. For ad traffic, custom product pages let you match frame 1 to each campaign.
- Judge on installs, and if you can, on trial starts afterward. A screenshot that overpromises can win on installs and lose on paid conversion.
- Once frame 1 is settled, test frame 2. More ideas are in our screenshot element guide and the wider ASO guide.