Skip to content
Primio Docs

Creating App Store Screenshots

Screenshots are the single biggest factor in whether someone downloads your app. They’re the first thing users see on your store listing, and most people decide to download — or keep scrolling — based on the first two or three.

Size requirements

Section titled “Size requirements”
DeviceSize (px)Required?
iPhone 6.9” (Pro Max)1320 × 2868Yes — covers all iPhones
iPad 13”2064 × 2752Required if your app supports iPad

You need 2–10 screenshots per device size. Apple displays up to 10 on your listing. All images must be PNG or JPEG (no transparency). Apple auto-scales these for smaller device sizes.

Capturing screenshots

Section titled “Capturing screenshots”

Three options, from best to quickest:

From a real device (best quality)

Build an APK via Android Builds, install it on your phone, and use the device’s built-in screenshot tool (usually Power + Volume Down on Android, Side Button + Volume Up on iPhone). For iOS, test via TestFlight and screenshot on your iPhone. Real-device screenshots look the most authentic.

From your Web Hosting URL on your phone (good balance)

Publish your app via Web Hosting (free), open the URL on your phone, and take a screenshot. This gives you real mobile screenshots at the correct resolution without building an APK or IPA.

From the Primio web preview (quickest — and now store-ready)

Take screenshots directly from the preview panel using the camera button and Save to disk. Primio captures at the device’s native resolution (3× for phones, 2× for iPad), producing images that match App Store and Google Play size requirements out of the box. Select iPhone 16 Pro Max for the required iOS screenshot size, or iPad Air 13” for iPad. No resizing or post-processing needed.

Structuring your screenshot set

Section titled “Structuring your screenshot set”

Plan your 5–8 screenshots as a visual story. Each one should answer: “Why should I download this?”

  1. Hero screenshot — Your app’s main screen showing the core value proposition. This is the most important screenshot. It should instantly communicate what the app does.

  2. Key feature #1 — The most compelling feature in action. Show it being used, not just a static screen.

  3. Key feature #2 — Second most important feature or capability.

  4. Differentiation — What makes your app unique or better than alternatives. A feature competitors don’t have, a cleaner design, or a simpler workflow.

  5. Social proof or results — Show outcomes, achievements, statistics, or anything that demonstrates value delivered to users.

Adding text overlays

Section titled “Adding text overlays”

Screenshots with short, benefit-focused captions convert significantly better than raw screenshots. A caption tells the user why the screen matters.

Format: A short headline above or below each screenshot explaining the benefit — not the feature.

Good (benefit)Bad (feature)
“Track your progress effortlessly""Analytics dashboard"
"Never forget a workout""Push notification settings"
"Plan meals in under a minute""Recipe input form”

Keep captions to 5–8 words. One idea per screenshot. Use a large, readable font — many users browse on small screens.

Section titled “Recommended tools”
  • Canva (canva.com) — Search “App Store Screenshot” for free templates. Select iPhone (9:16) or iPad (4:3) presets. Drag in your screenshots, add text overlays, export as PNG. Easiest option for most people.
  • Screenshots Pro (screenshots.pro) — Purpose-built for app store screenshots. Device frames, backgrounds, batch export to all required sizes.
  • Figma — More control for designers. Free tier available. Many community templates for app store assets.

All three tools let you add device frames (a phone mockup around your screenshot), which looks more polished than a raw screenshot.

Google Play feature graphic

Section titled “Google Play feature graphic”

Google Play requires a 1024 × 500px feature graphic — a banner image shown at the top of your listing and in promotional placements.

Keep it simple:

  • Your app name in large text
  • A one-line tagline or value proposition
  • A small preview of the app (optional)
  • A clean background that matches your app’s color scheme

Create one in Canva — search for “Google Play Feature Graphic” for templates.

Common mistakes

Section titled “Common mistakes”
  • Wrong dimensions — Will be rejected by the store or displayed stretched/cropped
  • Unreadable text — Captions too small, too much text, or low contrast against the background
  • Placeholder content visible — “Lorem ipsum,” test data, or obviously fake content in screenshots
  • Cluttered layouts — Too much information per screenshot; each one should focus on a single idea
  • No text overlays — Raw screenshots without context consistently underperform screenshots with captions
  • Inconsistent style — Different fonts, colors, or layouts across screenshots looks unprofessional. Pick a template and use it for all screenshots.

Screenshot localization

Section titled “Screenshot localization”

If you plan to launch in multiple countries, consider localizing your screenshots. This means:

  • Translating text overlays into the local language
  • Using culturally relevant content in the screenshots
  • Adjusting the store listing language to match

Localized screenshots can dramatically improve conversion in non-English markets. Start with your top 2–3 target markets.

Next steps

Section titled “Next steps”