Store screenshots and preview assets: the actual requirements on both stores
Apple's required screenshot sizes depend on the devices your app supports - one iPhone size, plus a 13-inch iPad size only if your app runs on iPadOS - with display scaling covering the rest; iPhone Duo shots become mandatory in April 2027 for apps built on the iOS 27.1 SDK. Play gates its best surfaces behind a 1080px bar plus icon, feature graphic and an 80-character description with a banned-word list.
Store listing artwork is the rare task that is both purely mechanical and easy to fail. The requirements live on two long reference pages - Apple's screenshot specifications and Play's preview-assets guide - and they disagree with each other in ways that matter: different minimums, different scaling behavior, different words you are banned from using. This is the distilled version, with the page numbers that decide whether a submission goes through.
Apple: two required sizes carry the whole catalog
App Store Connect asks for one to ten screenshots per device size, in JPEG or PNG, with no alpha channels or transparencies. Only two sizes are truly required: at least one screenshot for iPhone with Dynamic Island (medium display), and at least one for the 13-inch iPad if your app supports iPadOS. Everything else is optional because of display scaling: if your interface is consistent across sizes, you upload the highest required resolution and App Store Connect scales it down for every smaller device class automatically. You only upload per-size or per-localization artwork when you want it to differ.
The accepted pixel dimensions are enumerated per device class - for example 1290 x 2796 among the large-display Dynamic Island sizes and 2064 x 2752 or 2048 x 2732 for the 13-inch iPad class - and each older class falls back to scaled versions of a newer one if you skip it. Mac apps need a 16:10 shot (1280 x 800 up to 2880 x 1800), Apple TV 1920 x 1080 or 3840 x 2160, Vision Pro 3840 x 2160, and Watch apps pick one size from a per-series list and must use it consistently across all localizations.
The new line: iPhone Duo
Apple's foldable gets its own row on the specifications page: 1398 x 2034 pixels for the outer display and 2007 x 2853 for the inner display. Duo screenshots are optional today, but from April 2027 they become required for any app built with the iOS 27.1 SDK or later - the same mechanism Apple uses for every screenshot migration, where the new size quietly turns from nice-to-have into submission blocker. Submitting Duo screenshots also adds a "made for iPhone Duo" badge to your product page, which is the cheapest featuring signal Apple currently offers.
Google Play: fewer sizes, more rules
Play's minimum to publish a store listing is just two screenshots across your supported device types, JPEG or 24-bit PNG without alpha, between 320px and 3840px on each dimension, with the long side at most twice the short side. You can add up to eight per device type - phones, 7- and 10-inch tablets, Chromebooks, TV, Wear OS, Automotive and XR - and several types have their own tables: Chromebooks and tablets want at least four screenshots between 1080 and 7680px in 16:9 or 9:16; Wear OS demands a 1:1 shot of at least 384 x 384 showing only the interface, with no device frames or added text; XR wants four to eight shots at 8:5, ideally 3840 x 2400; Automotive asks for two portrait (800 x 1280) and two landscape (1024 x 768) taken on the generic system image, never a specific car maker's UI.
The number that actually decides visibility is not the minimum - it is the recommendation bar. To be eligible for Play's large-format recommendation surfaces, apps need at least four screenshots at 1080px or better (1920 x 1080 landscape or 1080 x 1920 portrait), and games need at least three showing real gameplay. Play also requires three non-screenshot assets to publish at all: a 512 x 512 32-bit PNG app icon with alpha (1MB max), a 1024 x 500 feature graphic without alpha, and an 80-character short description.
The word list that gets listings rejected
Play's metadata rules reach into your artwork and copy with a specific banned vocabulary: nothing that suggests ranking, price, testimonials or accolades - "Best," "#1," "Top," "New," "Free," "Discount," "Sale," "Million Downloads" - and no calls to action like "download now" or "try now." Short descriptions may not contain emojis, repeated punctuation or special symbols, and capitalization for emphasis is out. Apple's enforcement is less enumerated on the specs page - it defers to the App Review Guidelines - but the practical rule is identical: show the app, not the marketing department. Play additionally asks for alt text on every graphic asset, 140 characters or fewer, describing the content rather than saying "image of."
A working asset checklist
- Apple: shoot once at the highest required iPhone and 13-inch iPad resolutions; add per-size art only where the UI genuinely differs. Plan Duo shots before April 2027 if you will build on the iOS 27.1 SDK.
- Play: meet the recommendation bar, not the floor - four 1080px+ screenshots (three for games, real gameplay), plus icon, feature graphic and short description.
- Both: no alpha, no device frames where prohibited, no ranking or price language anywhere, real in-app footage only.
- Keep a size matrix in the repo. The tables change with hardware cycles; the teams that ship fast keep one checked-in sheet mapping device class to pixels, regenerated from the source pages each quarter.
The honest summary
Apple wants two good screenshots and will scale them everywhere, with a foldable deadline arriving in April 2027. Google wants more assets, more formats and compliance with a banned-word list, and gates its best promotional surfaces behind a 1080px recommendation bar. Neither is hard; both punish guessing. Build the matrix once, automate the exports, and the mechanical part of your listing stops being a launch-week surprise.
Sources
- App Store Connect Help: Screenshot specifications
- Play Console Help: Add preview assets to showcase your app
Prepared with AI assistance and reviewed before publication. Pixel dimensions, minimums, the iPhone Duo timeline and metadata wording rules are drawn from the two source pages above, checked on 19 November 2026.