App Store & Play Store Screenshot Sizes: 2026 Requirements Guide

Google Play requires at least 2 and at most 8 phone screenshots. The size rule is flexible: each side must be between 320 and 3840 pixels, and the longer side can be at most 2x the shorter side (a 2:1 aspect-ratio cap). Files must be JPEG or 24-bit PNG without transparency (no alpha channel). Google's current documentation states no official file-size limit for phone screenshots; keeping files compressed (well under a few MB) is still good practice for upload and page-load speed — the 8 MB cap that appears in older documentation is no longer part of the current official spec.

In practice most developers use 1080x1920 (9:16) for portrait apps and 1920x1080 (16:9) for landscape games. That is no accident: to be eligible for promotional placements outside search (featuring, collections), Google expects phone screenshots with at least 1080 px resolution, a 16:9 or 9:16 ratio, and at least 4 screenshots (at least 3 for games). A compliant set that falls short of these thresholds will not be rejected — it just lowers your chances of being featured.

7-inch and 10-inch tablet screenshots fall under Google's 'large screens' category together with Chromebook, and follow a different rule than phones: each side must be between 1,080 and 7,680 pixels, and the ratio is fixed — 16:9 for landscape, 9:16 for portrait (not the flexible 2:1 cap that applies to phones). Adding them is optional but recommended if your app supports tablets; Google recommends at least 4 images, with the same 8-image upper limit as other screenshot types. The store listing also has a feature graphic slot (1024x500 px) that Google requires you to provide, which doubles as the cover image if you add a promo video.

On Apple's side the rules are strict: screenshots must match exact pixel dimensions per device class. The reference class for iPhone is the 6.9-inch display (iPhone 17 Pro Max / 16 Pro Max): 1320x2868, 1290x2796, or 1260x2736 in portrait, 2868x1320, 2796x1290, or 2736x1260 in landscape. If your app runs on iPhone this set is required; Apple automatically scales these images down to the other iPhone sizes.

The 6.5-inch class (1284x2778 or 1242x2688; landscape 2778x1284 / 2688x1242) only becomes required if you did not provide the 6.9-inch set. Apps that support iPad must additionally provide the 13-inch iPad set: the current size is 2064x2752 (landscape 2752x2064), and the legacy 12.9-inch size of 2048x2732 (landscape 2732x2048) is still accepted. Apple's official classification has no separate "6.7-inch" display class — whichever of the 6.9-inch or 6.5-inch sets above matches your device is the real answer for that search term; App Store Connect names its classes 6.9, 6.5, 6.3, and 6.1 inches.

You can upload between 1 and 10 images per device class. The format must be JPEG or PNG, without transparency, in the RGB color space. If the dimensions do not match exactly, App Store Connect rejects the file at upload time — the most common stumbling block for developers used to Play Console's flexible range.

The most frequent technical error is wrong dimensions: on the App Store, an image that does not match pixel-for-pixel fails immediately; on Play, images exceeding the 2:1 ratio (for example a very tall full-page scroll capture) are rejected. Second place goes to PNGs with an alpha channel — an image exported from a design tool with a "transparent background" is not accepted by either store.

On the content side, Apple requires screenshots to reflect actual app usage. Sets made purely of marketing imagery with no visible app UI can trigger a metadata rejection in App Review. Using the wrong platform frame (an iOS screenshot inside an Android phone frame, or vice versa) is another known rejection reason.

Stretched, blurry, or forcibly rescaled images may not be rejected outright, but they degrade your listing quality. Pricing and promo claims ("50% off", "best app ever") and competitor brand names can also run afoul of both stores' metadata policies; keeping on-image text focused on describing features is the safest route.

The first 2-3 screenshots matter far more than the rest of the set: they are what users see in search results and on the store card, and most of the install decision happens there. Lead with your strongest feature — never open with an onboarding or settings screen.

A raw screenshot is rarely enough on its own. Overlaying a short 4-6 word caption above or below the screen (e.g. "Auto-categorize your spending") keeps the message readable even at thumbnail size. Use high contrast, keep the same typography and background language across all images; swiped left to right, the set should tell a single story.

Device frames are allowed but come at a cost: the frame shrinks the area left for your actual UI. Google recommends full-bleed, frameless captures with a clean status bar for Play images. If you use caption overlays, localizing screenshots per language measurably improves conversion; both stores let you upload a separate set for each language.

1. Capture raw screens on the highest-resolution target: the 6.9-inch iPhone simulator and 13-inch iPad for iOS, a 1080p-or-better device or emulator for Android. Upscaling loses quality; downscaling is always safe.

2. Build a single template: background, caption typography, and screen placement should be identical across images. Reserve the captions of the first two images for your clearest value proposition.

3. Export at each store's own sizes: 1080x1920 (or 16:9 landscape) for Play, exact per-class dimensions for the App Store (6.9-inch: 1320x2868 or 1260x2736; 13-inch iPad: 2064x2752). Remember to strip the alpha channel on export.

4. Validate before uploading: pixel dimensions, ratio, format, and transparency. App Store Connect surfaces errors instantly; Play Console silently accepts some issues and only shows a quality warning later, so a pre-flight check saves time on both stores.

If you want to run this whole flow in the browser, Vibeloy Screenshot Studio validates your raw captures against each device class, applies your caption and background from a single template, and exports at the exact sizes both stores accept.