Skip to content
Back to home
ResearchLast verified: May 5, 2026

App Store & Google Play Screenshot Size Reference 2026

Every screenshot slot Apple and Google currently accept, with the exact pixel dimensions, aspect ratios, file formats, and file-size ceilings each store enforces in 2026. Verified against the official Apple and Google developer documentation on the date below.

Eric Isensee
Eric IsenseeFounder · Last updated May 5, 2026

Why does the exact screenshot size still matter in 2026?

Apple and Google still enforce strict, slot-based screenshot uploads. Both stores accept a fixed set of canonical sizes per device class and reject anything that does not match. Apple is the stricter of the two: App Store Connect rejects any image whose pixel dimensions deviate by even a single pixel from the accepted list. Google Play is more flexible at the upload layer but still gates promotional placement on well-formatted assets.

The sizes also drift. Each year Apple ships new iPhone and iPad models, each year a new display-class size becomes the canonical one, and each year teams that did not update their templates ship slightly stretched screenshots. The table below is the version we trust for releases shipping between May and December 2026.

What screenshot sizes does the App Store require in 2026?

App Store Connect requires the canonical 6.7-inch iPhone and 12.9-inch iPad slots; everything else is optional but recommended for pixel-perfect control. Apple downscales the canonical sizes to fill missing slots, but downscaled assets often have soft text that hurts conversion.

SlotPixelsAspectFormatMax fileRequiredNotes
iPhone 6.9" / 6.7" (Display Class 1)1290 × 279619.5:9JPEG or PNG (no alpha)30 MBRequiredCanonical iPhone size. App Store Connect downscales this to fill smaller iPhone slots when device-specific assets are not provided.
iPhone 6.5" (legacy class)1242 × 268819.5:9JPEG or PNG (no alpha)30 MBOptionalOptional drop-in for older 6.5-inch hardware. Falls back to the 6.7-inch size if omitted.
iPhone 5.5" (Display Class legacy)1242 × 220816:9JPEG or PNG (no alpha)30 MBRequiredRequired if your app supports older 5.5-inch devices (iPhone 8 Plus and earlier).
iPad Pro 12.9" (3rd generation and later)2048 × 27324:3JPEG or PNG (no alpha)30 MBRequiredCanonical iPad size. App Store Connect downscales to other iPad classes when dedicated assets are missing.
iPad Pro 11" / iPad Air1668 × 2388≈ 4.3:3JPEG or PNG (no alpha)30 MBOptionalOptional. Use this slot only if you want pixel-perfect control over the 11-inch iPad listing.

What screenshot sizes does Google Play require in 2026?

Google Play uses a min/max box model rather than fixed pixel dimensions: any screenshot with its short side between 320 and 3840 pixels is accepted, as long as the aspect ratio is sensible for the form factor. Most teams author at the maximum reasonable size for sharper downscaling.

SlotPixelsAspectFormatMax fileRequiredNotes
Phone screenshotmin 320 px on the short side; max 3840 px on the long side16:9 or 9:16 typicalJPEG or 24-bit PNG (no alpha)8 MBRequiredGoogle Play requires at least 2 phone screenshots and supports up to 8. Use the maximum 9:16 dimensions (1080 × 1920 or 1242 × 2208) for the cleanest scaling.
7-inch tablet screenshotmin 320 px short side; max 3840 px long side16:10 or 10:16 typicalJPEG or 24-bit PNG (no alpha)8 MBIf supportedRequired if your app declares tablet support. Without 7-inch assets, the tablet store page reuses phone screenshots which usually look stretched.
10-inch tablet screenshotmin 320 px short side; max 3840 px long side16:10 or 10:16 typicalJPEG or 24-bit PNG (no alpha)8 MBIf supportedRequired if your app declares 10-inch tablet support. The most common authoring size is 1920 × 1200 (landscape) or 1200 × 1920 (portrait).
Wear OS screenshot384 × 3841:1PNG (no alpha)8 MBIf supportedRequired only for apps that declare a Wear OS variant. Square aspect; minimum 1 screenshot.
Android TV screenshot1920 × 108016:9JPEG or 24-bit PNG (no alpha)8 MBIf supportedRequired for Android TV apps. Landscape only. 4K assets are not currently accepted.

Which file formats and color spaces are accepted?

Both stores accept JPEG and PNG. Apple explicitly rejects PNGs with an alpha channel, which catches teams whose design tools default to transparent backgrounds. Always export with a flat background. WebP and HEIC are not currently accepted on either store.

Color space should be sRGB for maximum compatibility. Apple also accepts Display P3, which produces marginally richer color on modern devices. Avoid CMYK or non-tagged color profiles — they will either be rejected or rendered with shifted hues.

Can I mix portrait and landscape screenshots?

On the App Store: no. All screenshots within a single device size and locale must share one orientation. To switch a listing from portrait to landscape, every screenshot in that slot has to be re-uploaded.

On Google Play: technically yes, but the auto-generated thumbnails on the store page will look inconsistent and most ASO teams keep a single orientation per language.

How we compiled this reference

The dimensions in the tables above were collected by manually reviewing the current versions of the official Apple and Google developer documentation, then cross-checking each entry against the live upload validators in App Store Connect and Google Play Console on the date marked above.

Where the documentation gave a range (Google Play's 320–3840 pixel rule) we recorded the range and added a recommended authoring size based on the dimensions the store actually displays on the listing page. Where Apple deprecated a size class within the calendar year, we kept the previous canonical size in the legacy row so teams supporting older devices can find it.

We re-verify the table on a quarterly cadence. If a published size below this date no longer matches the live store, please email eric.isensee@icloud.com and we will republish.

Primary sources

Render every size from one design

Screenshots.live takes a single template and renders it to every required App Store and Google Play size, in every locale, on every release. No manual resizing.

See how the rendering API works