Store screenshot checklist before you hit Submit in App Store Connect or Play Console

Review teams and store policies care about accurate marketing. Screenshots that promise features you have not shipped, show competitor logos, or use misleading before/after claims create rejection risk and refund churn.

Run this checklist on every release — especially when you reuse an old creative set after a UI overhaul.

Technical checks

• App Store 6.7" portraits exported at 1290 × 2796 px (PNG recommended)
• Play Store phone screenshots at 1080 × 1920 px portrait
• Google Play feature graphic at 1024 × 500 px if you use one
• No upscaled blurry captures — start from high-resolution device screenshots
• File names organized by locale and slide index for faster uploads

Message and policy checks

• Slide headlines match visible UI on the same frame
• No guaranteed ranking or income claims unless substantiated
• Age-restricted content flagged appropriately in listing metadata
• Third-party trademarks removed unless you have rights
• Pricing and trial language matches current in-app purchase rules

Story and conversion checks

1. Slide one states a user outcome, not internal feature jargon
2. At least one slide shows the primary happy-path workflow
3. Text readable at thumbnail size in search results
4. Visual style consistent across all slides and locales
5. Localized sets updated when you localize metadata

After screenshots: Android closed testing

Polished visuals get users to the install button; Google Play closed testing gets personal developer accounts toward production access. If you still need twelve opted-in testers for fourteen days, run that track in parallel on TestMyApps while screenshots are in review.