Guide

App Store screenshot sizes overview

Jul 19, 2026 Understand App Store screenshot device sizes, required display families, and how to organize screenshot groups by locale and order in Helm.

App Store screenshots are sized per device display family. Upload the wrong pixels and ASC rejects the asset, or Apple derives a softer version from another size. This overview explains how to think about sizes, what to prioritize, and how Helm screenshot groups keep devices, locales, and order under control. For the upload workflow itself, see upload App Store screenshots.

Think in families, not one magic resolution

Apple organizes screenshot requirements around the devices your app supports. Exact pixel dimensions change as new displays ship, so treat any printed size chart as a starting point and confirm the current slots in App Store Connect or Helm for your version.

Typical families:

iPhone: required sizes for the phone displays you support; often you must supply the largest required iPhone size for your app
iPad: required if you support iPad
Mac: required for Mac apps
Apple TV / visionOS: when those platforms apply

If you only upload one iPhone size, Apple may derive others. Dedicated assets almost always look sharper for ASO and featuring reviews.

Required vs derived

Required means you must provide assets for that slot before the version is complete.

Derived means Apple can generate a size from another upload. Derived images save time. They can also crop captions awkwardly if your safe area was designed for a different aspect ratio.

Practical rule: hand-craft the sizes that matter for your traffic (usually the newest required iPhone size, plus iPad if that is a real market for you). Derive the long tail when quality stays acceptable.

Design constraints that survive resizing

Keep captions inside a safe area that survives taller and shorter crops
Avoid critical UI under status bars and home indicators
Export without unexpected alpha channels when the storefront rejects them
Match UI language to the locale you upload into
Make the first three frames carry the story; most people never swipe far

Pair screenshot planning with app preview videos when motion helps, and with listing localization when markets differ.

Organize source files before you touch ASC

Use a boring, sortable naming scheme:

en-US_iphone67_01_hero.png en-US_iphone67_02_share.png de-DE_ipad13_01_hero.png

Include locale, device family, and order. Future Magic upload and human teammates both benefit. Store masters in version control or a shared drive tagged by app version so 2.3 screenshots do not leak into 2.4 by accident.

Screenshot groups in Helm

In Helm, screenshots are grouped by device with guidance so captures match what App Store Connect expects. You can:

Upload and reorder images per group
Inspect assets in a large Mac preview window
Use Magic upload to place files by filename and dimensions into the right size, locale, and order
Bulk download or delete assets for a version
Add app previews, including poster frames, on Mac

iOS includes lighter screenshot support for on-the-go fixes. The full editor lives on macOS. CLI upload and organization are available via helm-asc when automation is part of your pipeline.

Per-locale strategy without drowning

You do not need every size in every language on day one. Prioritize:

Primary storefront language, required iPhone size
Top revenue or growth locales
iPad or Mac if those platforms drive installs
Remaining locales with shared layouts and translated captions

Reuse composition layouts from your design system, or start from /templates/ when you want shared examples, so each locale is a caption pass, not a full redesign.

Checklist

Confirmed current required sizes for this app version
Source files named by locale, device, order
Safe areas verified on the sizes you hand-craft
Alpha issues removed where needed
Groups complete in Helm or ASC for priority locales
First three frames tell a coherent story