The App Store screenshot resizer that turns one master into every size
Stop resizing screenshots for each iPhone and iPad by hand. Upload the cleanest capture once, label the device slot it belongs to, and keep a versioned asset set for every release — icons generated from a single master, store headers and feature graphics validated against the rules that get listings rejected.
- iPhone 6.9, 6.7 & 6.1-inch
- iPad 12.9, 11 & 10.9-inch
- Google Play device classes
The sizes the stores ask for, checked against the files you upload
Apple and Google publish fixed requirements per asset kind, and a file that satisfies one is usually rejected by the other. These rules are enforced from the file's own header at upload time, so a bad submission is caught before it ever reaches review.
Every iPhone and iPad screenshot size
Upload the largest usable shot once, label which slot it fills, and keep the set for each App Store submission straight without a folder-per-device mess.
Google Play device classes
Play Console validates phone, 7-inch tablet and 10-inch tablet lists separately. Screenshots are stored per class, so a phone shot is never a silent substitute for a tablet one.
All app icons from one master
Give the generator one square 1024px master and get the seven sizes the stores, browsers and home screens ask for by name, each named after its slot.
Store header, exact
Google's header is exactly 1024 × 500 — any other aspect ratio gets cropped. The upload rules check the file, so the mismatch is caught before you submit.
App preview sizes
iPhone Duo previews are 1920 × 886 or 886 × 1920 pixels. The same size rule applies as for stills: wrong dimensions, rejected.
Versioned, release-ready sets
Assets are versioned per app and travel with the release. The screenshots reviewers see in 2.4.0 are the ones 2.4.0 ships — not last quarter's set.
The pixel sizes behind the store listing
These are the requirements the upload rules encode. Nothing here is invented — it is the flat list of dimensions a submission has to satisfy, and the platform checks each file against it.
| Asset | Rule | Accepted dimensions |
|---|---|---|
| App icon | Square, at least 1024 × 1024, no alpha channel | 1024px master (stores) → 512 (Play), 192 PWA, 180 touch, 48 / 32 / 16 favicons |
| iPhone Duo screenshot | One of four exact sizes | 2034 × 1398, 1398 × 2034, 2853 × 2007, 2007 × 2853 |
| Screenshots | At least 320 × 320; Play classes validated separately | Phone, 7″ tablet, 10″ tablet — one ordered set per class |
| Feature graphic | Exactly 1024 × 500 | Any other aspect ratio gets cropped by Google |
| Store header | Exactly 5244 × 2950 or 3840 × 1646 | No round edges, no transparency |
| App preview | iPhone Duo video, one of two exact sizes | 1920 × 886 or 886 × 1920 |
Four steps from simulator to submitted
- 01
Upload once
Drop in the largest, cleanest shot you have — the one from your latest simulator run, with the device frame trimmed off.
- 02
Label the slot
Say which device the screenshot is for (phone, 7-inch tablet, 10-inch tablet or iPhone Duo) and what it shows. The slot, not the file, is what gets submitted.
- 03
Generate the icons
One square master becomes the App Store icon, the Play icon, the PWA icon, the Apple touch icon and the favicons — with the master never saved at all.
- 04
Ship the set
Every asset is versioned against the app, so the store listing and the release you are about to review agree. Update art once, and the diff is visible instantly.
Resizing gets a capture to its exact target dimensions — it does not manufacture a UI the device never rendered. A stretched phone screenshot is still a phone screenshot. Capture each device family, then let the tool handle every size in it.
Screenshot resizing, answered honestly
Can I resize a single screenshot to every App Store size?
Within one device family, yes: submit the largest clean capture, and Apple downscales it for the rest of the iPhone line. The one honest exception is a different device type. Stretching an iPhone 6.1-inch portrait to an iPad layout fakes a design the device never rendered, which reviewers over state — so keep separate captures for iPhone and iPad, and use resizing to get each capture to its exact target dimensions.
Do I still need Fastlane Snapshot if I use this?
Not for sizing, but you may still want it for capturing. Fastlane Snapshot runs your UI tests to produce fresh frames on simulators; it does not resize them, label the slots, or track versions. The common setup is Snapshot for the capture step and a management tool like Releaseyour.App for everything after: resize or convert, validate the store rules, and keep versioned sets for both stores in one place.
How do I organize screenshots for multiple languages?
Keep one set of artwork per language and per release. Labels describe what a screenshot shows, which only makes sense once the language is part of the record. Because the slots (not the files) are what get submitted, a localization review can see exactly which image ships to which storefront without digging through a dozen folders.
How do I keep screenshots in sync with each app version?
Version the assets the same way you version the app. When screenshots are tracked per release, the set that goes out with 2.4.0 is the set that was submitted with 2.4.0 — a bad screenshot or a stale one is caught in the diff instead of in the review queue hours later.
Can I manage App Store and Google Play assets in one place?
Yes — that is the point of the platform. An app record holds its Apple and Play assets side by side: screenshots per Play device class and iPhone Duo sizes, the feature graphic, the store header and the icon master, all versioned against the same releases.
Will resizing fix a screenshot that was captured at the wrong resolution?
Only up to a point. Upscaling a small file breeds soft edges, and no filter can invent detail that was never captured. Resizing handles scale, cropping and the exact store dimensions; it does not manufacture a sharper image or a better layout.
One master. Every size. Both stores.
Start with one app and a 1024px icon. The rest of the release is arranged around that record.
Guides: resizing App Store screenshots · Fastlane Snapshot alternatives