Google Play screenshots, every device class in one pass

The Play Store screenshot rulebook, in one preset

Google Play Console's screenshot specification is the operational layer of every Android app listing. The phone screenshot — the most-uploaded slot — accepts 16:9 landscape or 9:16 portrait at a 320-px short-side floor and 3840-px long-side ceiling, with 2 minimum and 8 maximum per device class. The 7-inch tablet slot uses the same 320-px floor; the 10-inch tablet floor jumps to 1080 px on the short side because tablet displays are denser, with a 7680-px ceiling on the long side. Wear OS screenshots are 1:1 square at 384 px minimum. Android TV needs a 1280×720 TV-specific feature graphic. The general feature graphic (the wide banner above the listing) is 1024×500 px regardless of device class, and the app icon is 512×512 px PNG with alpha. JPEG and 24-bit PNG without alpha are accepted on screenshots; the alpha channel is reserved for the icon. Play Console rejects 4:3 / 1:1 / 21:9 phone screenshots at upload because the listing display surface is built around 16:9 / 9:16 only.

The rules that move Play Store screenshot review are mostly about accurate representation and locale alignment. Misleading content — a screenshot showing a feature, in-app activity, or content that is not in the shipping binary — is the highest-friction rejection reason in Play Store review, and the policy team is empirically strict about it. iPhone device frames, iOS Settings UI, Apple App Store badges, and comparative screenshots showing a competitor app all get rejected on a Play Store listing because they suggest cross-platform misrepresentation. Caption text must be in the storefront language for each locale — English captions on the JP / KR / ZH-TW stores get rejected as locale-misaligned, and right-to-left layouts (Arabic, Hebrew) require chrome-layer flip. Pricing and promo overlays are restricted; 'Free' and 'No ads' claims are reviewed against the actual binary, and '50% off' promo overlays trigger a marketing-policy review. Adult or sexual content is forbidden on the storefront screenshots even when the app itself is rated 18+. The preset's chrome-layer separation keeps the in-simulator capture independent of the caption and frame, so locale-aligned localisation, RTL flips, and per-version caption edits don't require full re-renders.

Why a complete screenshot set drives more Play Store installs

Google Play's funnel is short — search or category browse to listing card to install — and the listing card decides most installs. The first 2-3 screenshots show on the card without scrolling, and they carry the highest install-conversion weight. Apps that ship the full 8 screenshots × 3 device classes outperform apps with the minimum 2 phone screenshots, because the broader set lets prospects evaluate whether the app actually fits their device — the same dynamic that drives Play Store's tablet-experience and Wear OS visibility surfaces. Localisation matters disproportionately on the storefronts where in-language captions are the floor for trust signals — Japan, Korea, Taiwan, and the right-to-left markets in particular. Apps that skip localised captions on those storefronts quietly cap their install ceiling at the English-tolerant subset of the local audience. Running the full screenshot set through the preset before the next Play Console upload — every device class, every locale, complete chrome layering — is the cheapest install-volume lift available without changing the binary itself.