When you submit an app to the App Store or Google Play, you need screenshots in exact pixel dimensions for each device class you support. Using the wrong size can lead to rejection in the console, automatic scaling that blurs text, or a listing that looks unprofessional next to competitors.
Why dimensions matter more than aspect ratio alone
Both stores validate width and height numerically. A screenshot that “looks” like an iPhone frame but is 50 pixels off may still fail upload checks. Design tools often export at @2x or @3x with rounding errors. The safest approach is to take your highest-quality master (or raw simulator capture) and let a purpose-built resizer output the official sizes—so every file matches Apple’s and Google’s documentation.
iOS (App Store)
Apple groups requirements by device family—for example 6.7" display, 6.5", 5.5", iPad Pro, and so on. Common iPhone sizes include 1290×2796 and 1284×2778 for modern tall phones, and 1242×2208 for the legacy 5.5" slot still used in many workflows. iPad and Mac have separate buckets. You only need sets for families your binary actually supports, but having a full standard pack ready saves time when you expand device support.
App Asset Generator includes the current standard iOS screenshot sizes so you can upload marketing art once and download every variant. Pair this with screenshots that show real UI—not only splash screens—because reviewers and users expect to see the product.
Android (Google Play)
Google Play accepts a range of screenshot dimensions for phone, 7-inch tablet, and 10-inch tablet slots. Typical phone exports are 1080×1920 or 1440×2560 in portrait; tablets need taller or wider compositions. Google publishes minimum long-edge and short-edge rules; staying inside the documented range avoids warnings in Play Console.
Because Android device diversity is huge, sharp source art matters. Start from vector or high-res PSD/PNG, then resize to each required size rather than upscaling a small phone mockup.
Practical tips for better listings
- Resolution first—export from design tools at the largest size you might need; downscale never upscales.
- Safe margins—keep titles and CTAs away from the extreme top/bottom; some devices crop or overlay system UI in previews.
- Batch workflow—upload multiple screenshots at once; App Asset Generator outputs a ZIP with every required dimension per image so your App Store Connect and Play Console sessions stay organized.
- Localization later—once your English set is correct, duplicate the same pixel pipeline for other languages.
When to refresh screenshots
Update listing images when you ship a major UI redesign, rebrand, or seasonal campaign. Stores do not require new screenshots for every tiny patch, but outdated shots erode trust. Regenerating from a single updated master keeps all device sizes in sync.