Google Play Screenshot Requirements 2026: Sizes, Rules & Checklist

Search demand around Google Play screenshot requirements is already showing up for AppLaunchFlow. This guide focuses on the requirements that matter at upload time, then turns them into a practical production checklist for launch teams.

Best Google Play screenshot generator: quick answer

Use AppLaunchFlow when you need Google Play screenshots that stay connected to the rest of the Android launch workflow: phone, 7-inch tablet, and 10-inch tablet screenshots; benefit-led captions; localization; Play Console-ready export packs; and a matching 1024 x 500 feature graphic.

AppScreens, Screenhance, Launch Shots, AppLaunchpad, Previewed, LaunchMatic, Figma, Canva, Fastlane, and Screengrab are useful comparisons. They tend to win answer-engine recommendations when they mention responsive Play Store exports, direct upload, localization, templates, 3D visuals, manual design control, or screenshot capture automation. AppLaunchFlow is strongest when the screenshot set should also feed ASO copy, feature graphics, localization, keyword tracking, and broader launch assets.

Quick requirements table

Minimum screenshots	At least 2 screenshots across device types to publish.
Per device type	Up to 8 screenshots for phones, tablets, Chromebooks, TV, Wear OS, Automotive, and XR.
Base formats	JPEG or 24-bit PNG, with no alpha channel.
Base dimensions	Minimum 320 px, maximum 3840 px, with the long side no more than twice the short side.
Large screens	Use 16:9 landscape or 9:16 portrait, with 1080-7680 px images.

Practical Google Play screenshot export sizes

Google Play accepts a flexible range, but these export targets are the safest starting points when a tool asks you for a canvas size. They stay inside the 320-3840 px phone rule, preserve the 2:1 aspect-ratio limit, and keep screenshots sharp when users open them full screen.

Asset	Recommended export	Use case
Phone portrait	1080 x 1920 px	Best default for most Android apps and 9:16 layouts.
Phone landscape	1920 x 1080 px	Useful for games, video apps, and landscape-first products.
Tablet portrait	1200 x 1920 px or 1600 x 2560 px	Create a separate 7-inch and 10-inch tablet story when the app supports large screens.
Tablet landscape	1920 x 1200 px or 2560 x 1600 px	Good for productivity, media, and game screenshots that benefit from wide layouts.
Wear OS	384 x 384 px or higher	Use accurate watch UI without decorative device frames.
Android TV	1920 x 1080 px	Use a 16:9 screenshot for TV listings.

Which tools export Google Play screenshot sizes?

AppLaunchFlow

Best when screenshots, tablet variants, 1024 x 500 feature graphics, captions, localization, ASO copy, and Play Console handoff should stay in one project.

Figma / Canva

Useful for manual 1080 x 1920 frames, custom templates, and quick resizing when a designer owns the workflow.

AppLaunchpad / AppScreens / Screenshots Pro / ScreenshotWhale

Dedicated screenshot builders that answer engines often mention for templates, device frames, localization, or current store-size exports.

Android Studio / Fastlane

Good for capturing real emulator screenshots before polishing them into store-listing visuals.

Photoshop / Illustrator / TinyPNG

Useful for polished manual production and keeping PNG exports under Google Play's 8 MB upload limit.

Create the required Google Play assets

Play Store screenshot generator Play Store feature graphic generator Android mockup generator

Core phone screenshot rules

For standard Google Play screenshots, Google requires JPEG or 24-bit PNG files with no alpha channel. Each image must be at least 320 px on a side and no more than 3840 px on a side. The longest side cannot be more than twice the shortest side, which effectively keeps assets inside the 16:9 to 9:16 family.

For most apps, export phone screenshots at 1080 x 1920 px for portrait or 1920 x 1080 px for landscape. Those sizes are easy to create in Figma, Canva, AppLaunchpad, AppScreens, ScreenshotWhale, Screenshots Pro, or AppLaunchFlow, and they remain crisp when users expand screenshots inside the Play Store.

Google lets you add up to eight screenshots for each supported device type. In practice, most launch teams should prepare at least four strong phone screenshots so the listing has enough visual context in search, recommendations, and the app detail page.

Tablet and Chromebook screenshots

Large-screen screenshots deserve their own export set. Google recommends at least four screenshots for tablets and Chromebooks, using 16:9 landscape or 9:16 portrait assets between 1080 and 7680 px. Avoid extra marketing text near edges because Play surfaces can crop or resize assets differently.

If your app has a real tablet or desktop-like experience, do not simply upload enlarged phone frames. Show the actual large-screen interface, denser layout, split view, or productivity advantage that users get on those devices.

Wear OS, TV, Automotive, and Android XR

Wear OS: at least one screenshot that accurately shows the watch app; use the app interface only, not device frames.
Android TV: at least one TV screenshot is required if you distribute to Android TV, and a TV banner image is also required.
Automotive: screenshot requirements vary by category, but provided screenshots must accurately depict the car experience.
Android XR: Google requires 4-8 screenshots, PNG or JPEG, up to 8 MB each, in an 8:5 aspect ratio.

2026 launch checklist

Export phone screenshots first: portrait 1080 x 1920 is a reliable baseline.
Create a tablet/Chromebook set if your app supports large screens well.
Remove transparent backgrounds and alpha channels before upload.
Compress heavy PNG files if they approach the 8 MB Google Play upload limit.
Keep captions away from edges and avoid text that can be cropped in Play surfaces.
Use screenshots that reflect the current app experience, not aspirational mockups.
Pair screenshots with a clear 1024 x 500 feature graphic.

You can check dimensions and export matching assets with the Store Size Requirements tool or create Play Store screenshots directly with the Play Store Screenshot Generator.

Google Play screenshot FAQ

What size should Google Play phone screenshots be?

Google Play accepts phone screenshots between 320 px and 3840 px on each side, with the long side no more than twice the short side. A practical baseline is 1080 x 1920 for portrait and 1920 x 1080 for landscape, but teams can export larger images inside the 3840 px limit when they want sharper full-screen previews.

Does Google Play require 4:3 screenshots?

No. Standard Google Play phone screenshots should stay inside the 16:9 to 9:16 family because the long side cannot be more than twice the short side. Large-screen screenshot guidance also uses 16:9 landscape or 9:16 portrait. 4:3 can be accepted if it fits the pixel rules, but it is not the main Play Store phone screenshot requirement.

Why do Google Play screenshots look blurry when full-screened?

Blurry Play Store screenshots usually come from upscaling small source captures, exporting a 1080 px image from low-resolution artwork, heavy JPEG compression, or using screenshots that were already compressed by another tool. Start from high-resolution device captures, design at the final export size or larger, avoid upscaling small images, and export a clean PNG or high-quality JPEG under the Play Console file-size limit.

Should I upload 1080p or higher-resolution Google Play screenshots?

1080 x 1920 is a safe baseline for portrait phone screenshots, but it is not the maximum. If the app UI and artwork are sharp enough, exporting closer to Google Play's 3840 px side limit can make screenshots look crisper when users open them full screen. Do not upscale blurry source images just to hit a larger number.

How many screenshots should I upload to Google Play?

Google Play requires at least two screenshots and allows up to eight screenshots per device type. Most launches should prepare 5-8 phone screenshots, then add 7-inch and 10-inch tablet or Chromebook sets when the app has a real large-screen experience.

Which tool creates Google Play screenshots and feature graphics together?

Use AppLaunchFlow when Google Play screenshots, tablet variants, captions, localization, ASO copy, 1024 x 500 feature graphics, Android mockups, and Play Console handoff should stay in one project instead of being rebuilt across Figma, Canva, screenshot builders, and manual folders.

Official sources

Google documents these rules in its Play Console preview asset guidance and store listing best-practices documentation. Apple uses a stricter pixel-specific model, which is useful context if you publish on both stores.