Why screenshots matter more than the description

Most store visitors spend less than eight seconds deciding whether to download an app. During that time, their eyes go to the icon, the rating, and the screenshots — in that order. The description gets read only if the screenshots already look promising. Getting your screenshots right is the highest-impact change you can make to your app's store listing.

Size requirements: Google Play

Google Play accepts up to eight screenshots per device type (phone, tablet, Chromebook, TV, and Wear OS). For phone screenshots:

  • Minimum: 320 pixels on the shortest side
  • Maximum: 3840 pixels on the longest side
  • Accepted formats: JPEG or 24-bit PNG (no alpha)
  • Aspect ratio: between 16:9 and 9:16 (portrait or landscape)

A safe, widely used size for portrait screenshots is 1080 × 1920 px. For landscape, 1920 × 1080 px is common.

Size requirements: Apple App Store

Apple accepts up to ten screenshots per device type (6.9-inch, 6.5-inch, 5.5-inch, iPad Pro, and so on). The required sizes depend on which device frames you are submitting for. Widely used sizes include:

  • iPhone 6.9-inch (required): 1320 × 2868 px or 2868 × 1320 px
  • iPhone 6.5-inch: 1242 × 2688 px or 2688 × 1242 px
  • iPad Pro 13-inch: 2064 × 2752 px or 2752 × 2064 px
  • Accepted formats: JPEG or PNG

If you submit screenshots for the largest required size, Apple often scales them to fit smaller devices automatically — but always check App Store Connect for the current requirements before submitting.

Sequencing: what order should screenshots go in?

The first two or three screenshots are the most visible in search results and the store listing header. Use this structure:

  1. Screenshot 1 — the hook: Show the app's primary value in one screen. This is the shot that replaces your pitch. Keep it clean and focused on one clear action or result.
  2. Screenshots 2–3 — the core features: Highlight the two or three features users are most likely to care about. Each screen should show one feature clearly.
  3. Screenshots 4–6 — supporting detail: Show secondary features, the onboarding flow, or a specific workflow that differentiates your app from alternatives.
  4. Final screenshots — social proof or summary: Ratings, awards, or a summary of key benefits can work well here if you have them.

Captions: short and benefit-focused

A short caption on each screenshot can significantly increase comprehension. Effective captions:

  • State the benefit, not the feature. "See your spending at a glance" is more useful than "Dashboard screen".
  • Keep it to one short line. On small screens, long captions get cut off. Aim for under 40 characters.
  • Use consistent typography. Matching font, size, and colour across all screenshots makes the listing look polished and intentional.
  • Place text in a safe zone. Avoid text within 100px of the top or bottom edges, where device frames or overlay elements might obscure it.

Design tips for the screenshots themselves

  • Use a consistent background. A gradient or solid brand colour behind each screenshot creates visual cohesion across the set.
  • Show real content, not placeholder data. Screens filled with "Lorem ipsum" or fake data make the app look unfinished.
  • Avoid device frames if space is tight. On phone-sized store previews, framed screenshots take up more space and make the actual UI harder to read. Frameless works well in most cases.
  • Test at small size. Zoom out on your screenshots to roughly thumbnail size (around 100 px wide) and check that the key content is still readable.
Tool tip: The App & Play Store Screenshot Maker on LightDarkTools lets you upload your screenshots, add captions, choose a gradient background, and download the full set as a ZIP — all in your browser with no upload to any server.

Exporting and submitting

  1. Export as PNG. PNG is lossless and avoids JPEG compression artefacts on text and sharp UI edges.
  2. Check file sizes. Google Play has a 8 MB limit per screenshot. Apple's limit is also 500 MB for the whole binary, but individual screenshot file sizes are not typically an issue at standard export sizes.
  3. Review on a real device before submitting. Open your screenshots on an actual phone to confirm text is readable and nothing important is clipped.
  4. Submit the full set for each device type. Google Play and Apple both let you customise screenshots per device type. If your app has a tablet or iPad layout worth showing, upload separate screenshots for those too.

A/B testing your screenshots

Google Play supports Store Listing Experiments, which let you test different screenshot sets against each other and measure which one leads to more installs. If your app has meaningful traffic, running even a simple test between two caption variants can produce actionable data. Apple's App Store does not offer native A/B testing for screenshots, but third-party tools can run pre-launch concept tests.