Home/Guides

Practical store screenshot playbooks

App Store & Google Play Screenshot Guides

Straightforward guides for making store screenshots that are clear, readable, and accepted by App Store Connect and Google Play Console.

Updated June 6, 2026

App Store Screenshot Rejected for Wrong Size: How to Fix It

Fix App Store Connect screenshot wrong-size rejections: check image dimensions, match Apple's accepted iPhone or iPad slots, and export the exact size in ScreenKit.

  • Check the file's exact pixel width and height
  • Compare the file with Apple's accepted App Store screenshot sizes
  • Choose the correct iPhone or iPad display slot

Updated May 29, 2026

App Store Screenshot Best Practices

A practical 2026 guide to App Store screenshot best practices: first-three screenshot strategy, copy, device sizes, localization, and export checks.

  • The first screenshot explains the main user outcome
  • Screenshots 1-3 tell a sequence, not 3 repeated claims
  • Every headline is readable at thumbnail size

Updated May 29, 2026

How to Make App Store Screenshots Without Figma

A step-by-step workflow for making App Store screenshots without opening Figma: plan the story, import screens, add copy, and export store-ready sizes.

  • Capture real screens from the app
  • Choose 4-6 screens that tell a complete story
  • Write one short headline per screenshot

Updated May 29, 2026

Google Play Screenshot Best Practices

Practical Google Play screenshot best practices for Android apps: phone screenshots, tablet assets, feature graphic alignment, copy, and localization.

  • Start with a strong phone screenshot set
  • Use 1080x1920 portrait unless the app is landscape-first
  • Make app UI large enough to inspect

Updated May 29, 2026

7 App Store Screenshot Mistakes That Cost Installs

Common App Store screenshot mistakes indie developers make: unreadable copy, weak first screenshots, wrong sizes, fake UI, and skipped localization.

  • Replace login and empty states with useful product states
  • Rewrite feature labels as user outcomes
  • Increase app UI size until it is readable