Android Screenshot Sizes 2026: Complete Google Play Store Dimensions Guide

Getting your Google Play Store screenshot dimensions wrong means rejection. Getting them right but not optimized means wasted potential. This guide covers every dimension you need for the Play Store in 2026, including phones, tablets, and Chromebooks, so you can submit with confidence and design for maximum impact.

Phone Screenshot Dimensions

Phone screenshots are the most important asset in your Play Store listing. They appear in search results, on your listing page, and in any featured placements. Here are the exact specifications.

Recommended phone dimensions:

• Portrait: 1080 x 1920 pixels
• Landscape: 1920 x 1080 pixels

Google's minimum and maximum limits:

• Minimum dimension: 320 pixels on the shortest side
• Maximum dimension: 3840 pixels on the longest side
• Aspect ratio: Must not exceed 2:1 ratio

While Google accepts any dimension within these bounds, 1080 x 1920 is the standard you should use. This matches the resolution of most modern Android phones, renders crisply across the Play Store's various display contexts, and is the output size of most Android emulators and screen capture tools.

If you also publish on iOS and want to minimize design work, 1242 x 2208 pixels works as a cross-platform compromise. It matches the iPhone 6/7/8 Plus resolution and falls within Google's accepted range.

7-Inch Tablet Screenshot Dimensions

If your app supports tablets, adding tablet screenshots unlocks the "Designed for tablets" badge in the Play Store. This badge improves visibility in tablet-specific search results and signals quality to users browsing on larger screens.

Recommended 7-inch tablet dimensions:

• Portrait: 1200 x 1920 pixels
• Landscape: 1920 x 1200 pixels

These dimensions match common 7-inch Android tablets like the older Nexus 7 and similar mid-size devices. Even though 7-inch tablets are less common than they used to be, Google still uses this category to evaluate tablet compatibility.

10-Inch Tablet Screenshot Dimensions

The 10-inch category covers full-size tablets like the Samsung Galaxy Tab series and the Google Pixel Tablet. These screenshots are displayed when tablet users browse the Play Store on larger screens.

Recommended 10-inch tablet dimensions:

• Portrait: 1920 x 2560 pixels (or 1800 x 2560 pixels)
• Landscape: 2560 x 1920 pixels (or 2560 x 1800 pixels)

For apps with landscape-oriented UIs (productivity tools, games, media apps), landscape tablet screenshots can be more effective than portrait because they show more of the interface.

Chromebook Screenshot Dimensions

Chromebooks run Android apps through the Play Store, and Google has increasingly emphasized Chromebook compatibility. While Chromebook-specific screenshots are not strictly required, adding them can improve your listing's appearance for the growing Chromebook user base.

Recommended Chromebook dimensions:

• Landscape: 1920 x 1080 pixels (standard HD)
• Alternative: 2560 x 1600 pixels (matches higher-resolution Chromebooks)

Chromebook screenshots are typically landscape because Chromebooks are laptop-form-factor devices. If your app adapts well to larger screens, showcasing this in Chromebook screenshots demonstrates that your app is not just a stretched phone app.

File Format and Size Requirements

Google is specific about file formats and sizes. Submitting files outside these specs will result in upload errors.

Accepted formats:

• JPEG (most common, smaller file size)
• 24-bit PNG (lossless quality, larger file size)

Important: PNG files must use 24-bit color depth. Alpha transparency is not allowed. If your PNG has a transparent background, the upload will fail. Always flatten your images to a solid background before exporting. File size limit:

• Maximum 8 MB per image

In practice, phone screenshots at 1080 x 1920 rarely approach this limit. A well-compressed JPEG is typically 200-500 KB. PNG files at the same dimensions run 1-3 MB. You will only hit the 8 MB ceiling with very large tablet or Chromebook images saved as uncompressed PNGs.

Color space: sRGB is the standard and safest choice. Avoid wide-gamut color spaces (like Display P3) as they may render differently across devices.

Aspect Ratio Rules

Google does not enforce a single aspect ratio, but there are constraints.

The rule: The aspect ratio of your screenshot cannot exceed 2:1. This means:

• 1080 x 1920 (16:9) is fine
• 1080 x 2160 (18:9) is fine
• 1080 x 2400 (20:9) is fine
• 1080 x 2700 (2.5:1) would be rejected

16:9 is the safest and most universally compatible aspect ratio. It displays well in all Play Store contexts and works across all device types. If you use a taller aspect ratio (like 19.5:9 to match modern phone screens), your screenshot may get cropped or display with black bars in certain store placements.

Quick Reference Table

Screenshot Count Limits

Google allows a minimum of 2 and maximum of 8 screenshots per device type. That means you can have up to 8 phone screenshots, 8 seven-inch tablet screenshots, 8 ten-inch tablet screenshots, and 8 Chromebook screenshots.

Always fill all 8 phone slots. Every empty slot is a missed opportunity to communicate your app's value. For tablets and Chromebooks, aim for at least 4 screenshots if your app supports those form factors.

How to Get the Dimensions Right Every Time

The most common cause of dimension-related rejections is not the screenshot itself but the device frame or background added around it. When you add a device mockup, text overlay, or decorative background, the final exported image needs to match the required dimensions exactly.

A Play Store screenshot generator handles this automatically. Upload your raw app screenshot, choose your layout and device frame, and the tool exports at the exact dimensions Google requires. No manual resizing, no guessing aspect ratios, no rejected uploads.

If you are designing manually, set up your canvas in Figma or Photoshop at exactly 1080 x 1920 for phones before you start. Add your device frame, text overlays, and background within that canvas. Export the entire canvas as a flattened JPEG or PNG. Do not resize after export as that introduces compression artifacts.

For Android-specific device frames, an Android mockup generator gives you accurate Pixel and Galaxy frames sized correctly for the Play Store, saving you from hunting down frame assets and aligning them manually.

Common Mistakes to Avoid

Uploading raw screenshots without any design treatment. Raw screenshots with no device frame, background, or text overlay look amateurish and fail to communicate your app's value at thumbnail size. Using iPhone frames in the Play Store. This happens more often than you would think, especially for cross-platform apps. iPhone frames in the Play Store signal carelessness and confuse Android users. Forgetting to remove alpha transparency. If your background has any transparency, the upload will fail. Always export with a solid background. Using text that is unreadable at thumbnail size. In search results, your screenshots are tiny. If your text overlay requires zooming in to read, it is not doing its job. Ignoring tablet screenshots. If your app runs on tablets, skipping tablet screenshots means missing the "Designed for tablets" badge and losing visibility with tablet users.

The 'Three Androids' Problem: Phone, Foldable, and Tablet Screenshot Strategies

Android isn't one platform anymore — it's three, and the screenshot strategy that works for each is different. The phone bucket covers everything from a five-inch budget Moto to a six-and-a-half-inch Galaxy flagship. Foldables introduce a second display state that's neither phone nor tablet but reuses Google's existing 7-inch tablet upload slot. Tablets proper — Galaxy Tab S, Pixel Tablet — have their own conventions and their own expectations. Designing one set of screenshots and uploading them everywhere is the single biggest reason apps lose on form-factor-diverse Play Store traffic.

The phone strategy is conversion-driven: hero shot first, four to six benefit-led screens, dense captions readable at thumbnail size. The foldable strategy is "show me you adapted." A foldable user opens your inner display, sees a stretched phone layout with two huge sidebar margins, and concludes the app wasn't designed for them. The fix is uploading the 7-inch tablet bucket with a layout that actually uses the wider canvas — a master-detail view, a multi-column list, a workspace that takes advantage of the real estate. The tablet strategy is closer to a desktop app: keyboard-aware, multi-pane, contextual side panels. Most apps fail this test because their tablet screenshots are just phone screenshots scaled up.

The cost of getting this right is real — three distinct creative tracks, three rendering pipelines, three rounds of testing. The cost of getting it wrong is fragmented install conversion across device classes. Google's Play Console exposes per-form-factor conversion data, and the gap between phone conversion and tablet conversion for most apps is wide enough to justify the design work. A Play Store screenshot generator that handles all three buckets in a single project is the practical fix — it keeps your brand consistent across form factors without requiring you to manage three separate Figma files.

Pixel vs Samsung Framing in Google Play Screenshots and What It Signals

The device frame you wrap your Android screenshot in is a signal. A Pixel frame says you're aligned with Google's design language and probably value Material You and stock Android conventions. A Samsung Galaxy frame says you've optimized for the largest Android user base by market share and understand that One UI is what most Android users actually see daily. A generic phone frame — the kind with no recognizable manufacturer cues — says you couldn't decide, which most users read as "this app isn't really for me."

The honest answer to "which frame should I use" depends on your audience. Developer tools, dev-adjacent productivity apps, and anything that leans technical default to Pixel frames because the audience reads Pixel as "the developer's Android." Consumer apps, especially in markets where Samsung dominates (Korea, parts of Europe, much of Latin America), default to Samsung frames because that's what users see in the mirror. Cross-platform apps that ship on both stores often default to Pixel for Play Store screenshots because it visually differentiates the Play Store listing from the App Store listing, which uses iPhone frames.

The trap is mixing frames within a single listing. Two Pixel screenshots and a Samsung screenshot in the same set looks like a design accident. Pick one frame style per locale and stick with it. If your app skews toward one OEM in specific markets, vary the frame by locale rather than by screenshot. Samsung-framed screenshots in Korean, Pixel-framed in English — that's intentional. Mixed frames in the same set just look unfinished. An Android mockup generator with both Pixel and Galaxy frame libraries makes this easier than maintaining your own frame assets.

Frequently Asked Questions

Do I need to upload separate screenshots for Wear OS?

Only if you ship a Wear OS app or companion. Wear OS screenshots are 384 x 384 px on a circular display assumption, and Google keeps the upload slot separate from phone screenshots. Keep critical content within the inscribed circle (roughly 270 px on each side at center) — anything in the outer corners gets clipped on round watches. Square Wear OS displays still exist but are rare enough that designing for them is wasted effort.

How do Chrome OS screenshot expectations differ from tablet?

Chromebook screenshots are landscape 1920 x 1080 at 16:9, treating the device as a laptop. Tablet screenshots are taller and usually portrait. If your app has a real desktop-class layout — keyboard shortcuts, multi-pane navigation, hover states — Chromebook screenshots should show the resized desktop UI, not your phone UI stretched to fit. Reusing tablet screenshots for the Chromebook slot looks lazy and signals you didn't actually optimize for Chrome OS.

Do Android Auto listings need their own screenshots?

Yes, if you have an Auto-compatible app. The Play Console exposes a separate Auto Listing where you upload screenshots showing your app inside the Android Auto interface — typically at 800 x 480 px landscape. Auto screenshots are evaluated differently because the safety guidelines for in-vehicle apps are stricter; avoid screenshots that imply interaction with the phone screen while driving. Most automotive apps fail this review on the first pass.

What about screenshots for Google Play's new Tab feature?

Google's tab-focused surfaces — like the "Games" and "Apps" tabs — pull from your standard phone screenshot upload. There's no separate tab-specific upload slot. What changes is which screenshots Google's algorithm features in collections and editorial placements. Lead with screenshots that work both as a single-frame thumbnail and as part of a multi-image collection, since editorial features sometimes show one screenshot, sometimes a carousel.

Should my screenshots reflect Material You theming?

If your app supports Material You — meaning dynamic color theming based on the user's wallpaper — your screenshots should show your app in a coherent theme rather than the default OS palette. Pick a single accent color that matches your brand, render the screenshots in that theme, and accept that users with different wallpapers will see different colors in their actual install. The Play Store screenshot is a marketing artifact, not a perfect preview, so a branded color story beats trying to depict every possible theme variant.

Related Reading

• Google Play Store Screenshot Guide - Full design tips and strategy for Play Store screenshots
• App Store Screenshot Dimensions 2026 - The iOS counterpart with every Apple device dimension
• Best Screenshot Size: Complete Guide - Optimal dimensions across all platforms and use cases