Skip to content

Your screenshot release checklist

Review device coverage, current app content, screenshot dimensions, image formats and the final exported files before updating your store listing.

By Skir · Updated October 1, 2026 · Suggest a correction

Quick answer

What should you check before publishing app screenshots?

Review the actual exported files for the correct app build, truthful headlines, readable text, image order and intended locale. Verify dimensions, format, alpha, screenshot count and required device coverage against the store slot. Open every image and inspect the store upload preview, then record the approved files and any unresolved release issues.

Store reference: Apple screenshot specifications; Google Play preview asset requirements.

Fresh Groceries: existing screenshot template from the Skir catalog
Fresh Groceries. Review the headline, shopping interface and delivery wording separately on every board of this grocery sequence. Sample artwork, badges and claims need review before publishing. Edit Fresh Groceries

Free screenshot release checklist

Copy this resource into your release notes, or download the editable Markdown version. No account needed.

Download screenshot release checklist

App: __________ Version: __________ Store: __________ Locale: __________

Reviewer: __________ Review date: __________ Export location: __________

Product truth

  • [ ] Every app capture matches the version intended for release.
  • [ ] Each headline describes a feature the app actually supports.
  • [ ] Sample reviews, ratings, awards and outcome claims have been removed or substantiated.
  • [ ] Personal information and confidential test data are absent.
  • [ ] Sample artwork has been replaced or reviewed for intended use.

Sequence and readability

  • [ ] The opening image demonstrates the main task rather than leaving it to the reader to infer.
  • [ ] Each following image adds a distinct feature, step or useful result.
  • [ ] Text is readable in a small preview and is not clipped at full size.
  • [ ] Device frames do not obscure essential interface details.
  • [ ] Colors, typography, terminology and screenshot order are consistent.

File and device checks

Compare the intended slot with Apple's screenshot specifications or Google Play's preview asset requirements. Check the current store reference again when you upload.

  • [ ] The intended store and upload slot have been recorded.
  • [ ] Actual exported dimensions match that slot's current requirements.
  • [ ] File format and alpha/transparency checks have been completed.
  • [ ] Required device coverage has been checked against the store's reference.
  • [ ] Phone screenshots, feature graphics and other asset types have not been confused.
  • [ ] The number of images matches the intended listing or placement requirements, not just an editor's free allowance.

Localization and handoff

  • [ ] Captures, headlines, dates, numbers and currency belong to the intended locale.
  • [ ] A reviewer has checked translated meaning and text overflow.
  • [ ] Every exported file has been opened; the ZIP download alone is not treated as approval.
  • [ ] Upload previews show the expected locale, order and crops.
  • [ ] The approved export and any unresolved issues are attached to the release record.

Unresolved item: __________ Owner: __________ Recheck date: __________

Next action: run files through the Skir checker. To change the artwork, choose an editable catalog template. An optional paid plan may be needed to export beyond the first three screenshots.