Home / ASO guides / App Store screenshot templates: what to use and avoid

App Store screenshot templates: what to use and avoid

Quick answer: A good App Store screenshot template gives you the right canvas sizes, a device frame or frameless layout, and a caption area that stays readable as a thumbnail. Use one for structure, then change the layout so your app doesn't look like the hundreds of others using the same template.

How to build a reusable screenshot template

Follow these steps in order. Each one is something we do on client work.

  1. Set up frames at accepted sizes. 1320 × 2868 px for iPhone 6.9-inch; 2064 × 2752 px for iPad.
  2. Create a caption style. One heading size, one weight, consistent margins.
  3. Make a device or frameless layout. Pick one and use it for all screens.
  4. Use components for screens. Swap captures without breaking layout.
  5. Add localization slots. Leave room for longer languages.
  6. Export in batches. Name files by device and order.

App Store screenshot template: key rules and context

What a template must have

Layouts that work

  1. Benefit caption + one screen.
  2. Panoramic set where the background continues across screenshots.
  3. Before/after for utilities.
  4. Social proof only if real and allowed; no invented ratings.

Where to get one. Build in Figma or Canva, or try a screenshot generator.

Avoid. Tiny captions, feature lists, five similar screens, and device frames that shrink the UI.

Worked example (hypothetical)

This example is illustrative. The app is made up, and so are any numbers in it.

Suppose Wanderly, a travel app, builds a Figma template with six frames. German captions run about 30% longer in our hypothetical draft, so the template uses auto-layout text boxes and a two-line limit.

Common mistakes

  • Fixed-width text boxes. Break with translation.
  • Wrong frame sizes. Uploads fail.
  • Mixing styles. Inconsistent set.
  • No file naming. Uploads get out of order.

Screenshot specs we design to

Both stores publish exact requirements. These are the ones that matter most for a phone-first app.

Store / deviceSize or ruleCount
App Store, iPhone 6.9-inch1320 × 2868, 1290 × 2796 or 1260 × 2736 px (portrait)1–10 per device size
App Store, iPad 13-inch2064 × 2752 or 2048 × 2732 px (portrait)1–10 per device size
App Store, format.jpeg,.jpg or.png—
Google Play, phoneJPEG or 24-bit PNG, 320–3,840 px, long side no more than 2× the short sideMinimum 2 to publish, up to 8 per device type
Google Play, Chromebook / tablet1,080–7,680 px, 16:9 or 9:16Minimum 4 recommended

How we measure the result

For App Store screenshot template, success is measured on conversion, not looks. Screenshots mainly change conversion: the share of people who see your page or search result and then install. We wait until the console shows a confident result before calling a winner.

Checklist

Copy this list into your release notes or ticket and tick each item off before you ship.

  • Frames at accepted sizes
  • Caption style
  • One layout
  • Components for captures
  • Localization room
  • Named exports
FAQ

Questions

Are free templates OK?

Yes, if sized correctly and customised.

Should I use device frames?

Optional; frameless gives more space to UI.

Same template for both stores?

Yes, export separately.

How many screenshots?

5–8 is common; use what tells the story.

Can you design them?
Can I use the same template for Google Play?

Yes, with an export that fits Play's rules: 320–3,840 px and a long side no more than twice the short side.

Ready when you are

Fix your listing this week.

One fixed price, delivered as copy and files you paste yourself. No calls, no account access.

$99 one-timeDelivered in 2–3 business days2 revisionsNo login needed
Questions? Email us
Rank higher. More installs.Want your app ranked and more installs?
Get HireASO