App Store Screenshot Sizes Guide (2026)
Size mistakes still cause avoidable QA delays. Use this guide to keep your screenshot pipeline consistent and submission-ready.
Choose one baseline per platform
Set an iOS baseline and an Android baseline before production starts.
Generate secondary sizes from the baseline instead of building each format manually.
Baseline-first workflows reduce QA rework and prevent inconsistent layouts.
Maintain content-safe zones
Reserve breathing room near edges so headline and UI framing remain legible across device classes.
Design with vertical and horizontal crop tolerance where required.
Assume smaller previews will clip your layout: keep key claims centered and readable.
Use a final submission checklist
Verify dimensions, naming conventions, and sequencing before upload.
Store approved exports by release version for future reference and rollback.
Double-check that text remains readable on the smallest preview contexts.
Reduce operational friction
Avoid rebuilding sets from scratch. Reuse a stable visual system and update only what changed in the product story.
If your team ships weekly, your screenshot workflow must be designed for speed and consistency.
FAQ
Do iOS and Android need separate screenshot sets?
In most cases yes, because preview behavior and format expectations differ.
Where can I check dimensions quickly?
Use the Storeshots size checker resource to filter current target size presets.
Should I prioritize iPhone or iPad sizes first?
Most apps start with iPhone. If iPad is a core market for you, treat it as its own set with its own narrative and safe zones.