Your screenshot release checklist

Use this checklist on the final exported files for each release and locale. A design that looks correct inside the editor can still be exported at the wrong size or with an unwanted alpha channel.

App and story

• Every shown feature exists in the version you are releasing.
• Example content contains no private account data, credentials or real customer information.
• Headlines describe visible benefits without unsupported rankings or promises.
• The first image is understandable at a small listing size, and later images add useful information.
• You have permission to use the screenshots, artwork and fonts.

Device, language and layout

• Select the required device classes and verify the app really supports them.
• Use current Apple dimensions or Google Play requirements.
• Check each locale’s app UI and captions together; review long text, line breaks and right-to-left reading order.
• Keep device frames proportional. Make sure critical UI and captions remain visible.
• Confirm the screenshot order and set count in the actual store console.

Final export

• Inspect every delivered file, not only the first one in the set.
• Measure actual pixel dimensions and decode the real format.
• Remove PNG alpha channels where required; recheck the exported file.
• Open the ZIP and check its contents before uploading.
• Review the upload preview and any console warnings, then retain the editable source for your next release.

A file check cannot confirm licensing, feature accuracy, store approval or conversion impact. Those remain separate review steps.

Source: Apple screenshot specifications. Checked September 10, 2026. Store guidance can change; confirm the upload slot in your console before submitting.

Source: Google Play preview asset requirements. Checked September 10, 2026. Store guidance can change; confirm the upload slot in your console before submitting.