Both stores
bothApp Store and Google Play sizes in one package.
- AppStore/iPhone-6.9 — 1290 × 2796
- AppStore/iPad-13 — 2064 × 2752
- PlayStore/Phone — 1080 × 1920
Use it when: A simultaneous iOS and Android release. The usual choice.
Export & packaging
One ZIP, already sorted the way you upload
Fifty files across three device families and five languages is not a design problem, it is a filing problem. The export handles the filing: correct dimensions, flattened RGB, folders that match the console slots.
Generate and exportPackage structure
screenshots.zip
├── AppStore/
│ ├── iPhone-6.9/
│ │ ├── English_US/ 01.png … 05.png
│ │ ├── German/ 01.png … 05.png
│ │ └── Japanese/ 01.png … 05.png
│ └── iPad-13/
│ └── English_US/ 01.png … 05.png
└── PlayStore/
└── Phone/
├── English_US/ 01.png … 05.png
└── German/ 01.png … 05.pngFour export presets
The preset decides which sizes get produced and how the ZIP is laid out. Switching preset and re-exporting the same project costs nothing.
Apple App Store
appstore6.9" iPhone and 13" iPad Pro sizes required by App Store Connect.
- AppStore/iPhone-6.9 — 1290 × 2796
- AppStore/iPad-13 — 2064 × 2752
Use it when: iOS-only apps, or an App Store update that does not touch the Play listing.
Google Play
playstorePhone and tablet sizes required by Play Console.
- PlayStore/Phone — 1080 × 1920
- PlayStore/Tablet — 1600 × 2560
Use it when: Android-only apps, or a Play-specific experiment variant.
Original resolution
originalExactly as generated, no resizing.
- Flat, one file per mockup
Use it when: Landing pages, decks, press kits and ad creative, where store dimensions do not apply.
Four things the export does so you do not have to
01
Uploading is where the time actually goes
Generating five screenshots is fast. Renaming, resizing and sorting fifty files across three device families and five languages is what turns a release into an afternoon. The folder structure is the feature.
02
Exact dimensions, not "close enough"
App Store Connect validates pixel dimensions strictly and rejects a mismatch outright. Every file in the package leaves at the size its target slot expects, so nothing bounces at upload.
03
Flattened before it is zipped
Alpha channels are the most common silent failure — the PNG looks right locally and is rejected on upload. Exports are flattened to RGB on a solid background first.
04
Export a selection, not everything
Select the frames you want and only those are packaged. Useful for shipping a single replacement screenshot without regenerating the gallery around it.
Export questions
How do I export all my screenshots at once?+
Open a project, choose an export preset, and download. Every mockup in the project is resized to the preset's targets and packaged into one ZIP, split by store, device family and language. If you have frames selected, only those are included.
What is inside the ZIP?+
PNG files at store dimensions, in nested folders named for the store, the device family and the locale — for example AppStore/iPhone-6.9/German/. The structure mirrors the order you upload in, so each folder maps to one slot in the console.
Can I export a single screenshot?+
Yes. "Save PNG" downloads the currently selected mockup on its own at its generated resolution, which is what you want for a quick share or a landing-page hero.
Does exporting cost credits?+
No. Credits are spent when a screenshot is rendered. Exporting, re-exporting, and switching presets are all free, so you can package the same set for both stores without paying twice.
Why does the export resize rather than crop?+
Because cropping loses headline text. The image model renders at a fixed set of aspect ratios, none of which is exactly 1290 × 2796, so the export scales to fill the target instead. Every pixel of the artwork survives and no letterbox bars are baked into a file bound for a store listing.