App Store Screenshot Sizes in 2026: Every Required Dimension

Screenshot dimensions are the rare part of ASO with a single correct answer — and the answer keeps moving. Since 2024 the App Store added a 6.9-inch reference class, folded the iPhone Air’s odd 1260×2736 panel into it, replaced the 12.9-inch iPad requirement with a 13-inch class, and added Watch Ultra 3 dimensions. Google, meanwhile, quietly tied featuring eligibility to a four-screenshots-at-1080px rule that most listings still fail.

This is the complete 2026 reference, checked against Apple’s current App Store Connect specifications and Google’s Play Console asset rules: what each store requires, what is optional, and what auto-scales from a single master. The App Store vs Google Play listing requirements post covers the rest of the listing.

The 2026 rules at a glance

What changed since 2024

If you last shipped screenshots a year or two ago, these are the deltas that matter:

• Late 2024: the 6.9-inch class became the iPhone reference size with the iPhone 16 Pro Max, replacing 6.7-inch as the master you design for.
• May 2024:the 13-inch iPad class (M4 iPad Pro) replaced 12.9-inch as the iPad requirement — but it still accepts 2048×2732, so old sets remain valid.
• September 2025:the iPhone Air’s 1260×2736 panel joined the 6.9-inch class, and Watch Ultra 3 added a 422×514 size.
• Ongoing:Google’s recommendation surfaces require 4+ screenshots at 1080 px in strict 16:9 or 9:16 — a quality bar, not an upload validator, so failing it fails silently.

iPhone screenshot sizes

Apple’s 2025 reshuffle made the system genuinely simple: one required class, everything else derived.

The 6.9-inch class — the only set you need

Apple’s spec sheet now accepts three portrait sizes inside the required class: 1320×2868 (iPhone 16/17 Pro Max), 1290×2796 (the former 6.7-inch size, still valid), and 1260×2736— the iPhone Air panel, which Apple buckets here despite the Air’s 6.5-inch marketing size. Landscape is the same pairs flipped. Render at 1320×2868 unless you have a reason not to: it is the largest, so it downscales cleanly everywhere.

What happens to the smaller classes

The 6.5-inch (1284×2778 / 1242×2688), 6.3-inch (1179×2556 / 1206×2622 — the regular iPhone 16 and 17), 6.1-inch, 5.5-inch, and older classes are all optional. Provide nothing and Apple scales your 6.9-inch set down the chain automatically. The only reason to upload a bespoke smaller set is overlay text you want recomposed at a different aspect ratio — and almost no indie team’s conversion data justifies that maintenance burden.

Count and order

1 to 10 per class, JPEG or PNG. Treat the first three as the whole game: they render in search results before anyone reaches your product page. The ASO playbook covers the first-screenshot pitch in depth.

iPad screenshot sizes

Required only if your app runs on iPad. The 13-inch class accepts 2064×2752 (iPad Pro M4/M5) or 2048×2732 — which is the old 12.9-inch size, so a legacy 12.9-inch set already satisfies the current requirement without re-rendering. Smaller iPad classes (11, 10.5, 9.7 inch) scale down from it.

Don’t just stretch iPhone compositions: iPad pages convert better when screenshots use the width — split views, sidebars, landscape workflows — because that is what an iPad buyer is evaluating.

App preview video sizes

Apple’s app previews have their own resolution table, and it does not match the screenshot sizes — the most common upload surprise in App Store Connect.

• iPhone (6.9-inch and 6.5-inch classes): 886×1920 portrait or 1920×886 landscape.
• iPad 13-inch class:1200×1600 portrait or 1600×1200 landscape.
• Limits: 15–30 seconds, up to 3 previews per device class, 500 MB max, H.264 or ProRes 422 HQ, 30 fps. The poster frame defaults to the 5-second mark — set it deliberately, because the poster is what renders until autoplay kicks in.
• Google Play: no video upload at all — the promo video is a public YouTube URL, 30 seconds to 2 minutes, shown behind your feature graphic.

Previews must be captured from the running app, not motion design — Apple rejects montage-style trailers under guideline 2.3.3 the same way it rejects fabricated screenshots.

Google Play screenshot sizes

Play gives you a range instead of fixed sizes, then layers a stricter quality bar on top for promotion.

Phone screenshots — the baseline rules

• Count: 2 minimum, 8 maximum.
• Dimensions: every side between 320 and 3,840 pixels.
• Aspect ratio:the long side can’t exceed twice the short side (2:1).
• Format: JPEG or 24-bit PNG, no alpha.

The featuring rule most listings miss

To be eligible for recommendation surfaces — featuring, editorial collections, the large screenshot-led cards — Google wants at least 4 screenshots at 1080 px or higher, in 16:9 (1920×1080 minimum) or 9:16 (1080×1920 minimum). A two-screenshot listing is valid but invisible to Play’s merchandising. Render portrait masters at 1080×1920 or above and you clear both the baseline and the featuring bar at once.

Tablets and the feature graphic

7-inch and 10-inch tablet sets follow the same dimensional rules, up to 8 each. They’re optional but feed large-screen search and Chromebook surfaces. The 1024×500 feature graphicremains mandatory; keep it free of device frames and call-to-action text, both of which Google’s metadata policy rejects.

Apple Watch, tvOS, visionOS, Mac

Each applies only if you ship that platform; all take 1–10 images.

Apple Watch

• Ultra 3:422×514
• Ultra 2 / Ultra:410×502
• Series 11 / 10:416×496
• Series 9 / 8 / 7:396×484
• SE and Series 6 and earlier:368×448

Upload the largest size your app supports and keep the same size across every localization — App Store Connect enforces consistency there.

Apple TV and Vision Pro

tvOS takes 1920×1080 or 3840×2160, landscape only. visionOS takes 3840×2160 — and flat phone-style mockups read as low-effort there; show the spatial UI.

Mac App Store

16:10 only: 1280×800, 1440×900, 2560×1600, or 2880×1800. Use a Retina size; 1280 masters look soft on every modern Mac.

Rules reviewers enforce beyond the pixels

Passing the upload validator is not the same as passing review. The screenshot rejections that actually happen:

• Screenshots must show the shipped app. Concept art, outdated UI, or features the build doesn’t have get flagged under Apple guideline 2.3.3 and Play’s Deceptive Behavior policy — the most common screenshot rejection on both stores.
• No other store’s branding.A “Get it on Google Play” badge inside an iOS screenshot is an instant metadata rejection, and vice versa.
• No visible transparency on Apple. PNGs with alpha can pass upload, but screenshots that render with transparent regions draw a 2.3.3 flag — flatten everything onto a solid background.
• No competitor trademarks in overlays. Same IP rules as the text fields — the rejection reasons index has the real-world examples.
• Feature graphic restrictions are stricter. Device mockups and CTA text are banned in Play’s 1024×500 graphic even though they’re fine inside phone screenshots.
• Localize the overlays.English captions on a Japanese listing won’t get you rejected, but they crater conversion and signal neglect — pair screenshot localization with the 14-language localization workflow.

A production pipeline for screenshots

1. Render two masters.One 1320×2868 portrait set for Apple, one 1080×1920-or-larger 9:16 set for Play’s featuring bar. Add a 2064×2752 iPad master if you ship iPad.
2. Keep overlays on a separate layer. UI renders change every release; localized caption layers change per market. Separating them means re-exporting, not redesigning.
3. Let a tool fan out the sizes.Push My App’s Screenshot Resizer exports every store size from one master with correct aspect handling — the icon resizer does the same for icons.
4. Re-render on UI changes, not on a schedule. Stale screenshots are the fastest way to earn a 2.3.3 flag — make the render step part of the release checklist, or use the 9-minute pre-submission checklist which includes it.

Frequently asked questions