Export store screenshots for all sizes and locales

Create organized PNG screenshot packages for iOS, Google Play and Chrome Web Store, including multiple sizes, locales and Fastlane folders.

3 min readProduct-verified 20 August 2026By the Screenhance team

Need another answer?

Turn one reviewed store project into a predictable, upload-ready ZIP structure.

01

Run the export preflight

  1. 1Choose the platform and confirm the current preview size.
  2. 2Select the device sizes you actually plan to submit.
  3. 3Choose the current locale only or every enabled locale, depending on the release.
  4. 4Resolve missing-translation warnings and inspect the most constrained language or size.
  5. 5For iOS automation, enable Fastlane folder structure when you want App Store Connect locale codes such as en-US and zh-Hans.
  6. 6Review the total image count, then start the ZIP export and keep the panel open until download completes.
02

Understand the downloaded package

Store screenshots export as opaque PNG files to avoid alpha-channel rejection. Multi-size and multi-locale exports are grouped into folders so you can identify each output. Fastlane mode follows the locale-folder convention expected by fastlane deliver.

  • Open several files from different folders rather than checking only the first image.
  • Confirm filenames, dimensions, slide order and locale before uploading.
  • Keep the ZIP as a release artifact so the exact submitted set can be recovered later.
03

If one or more screenshots are skipped

The export continues when it can and reports slides that could not render. A common cause is remote media that blocks cross-origin canvas access. Re-upload the affected screenshot or asset directly from a local file, confirm it appears in the editor, and export again.

Was this guide missing something?

Tell us what you were trying to do and which step stopped you. That helps us improve both the product and this guide.

Send guide feedback