Google Play Screenshot Dimensions 2026: Every Size You Need

Getting Google Play screenshot dimensions wrong delays your launch. Google rejects listings with incorrectly sized assets, and the requirements differ from Apple's. Last updated: April 2026.

Here are the exact dimensions you need for every Google Play device type.

Phone Screenshot Dimensions

Google Play is more flexible than Apple on exact pixel sizes, but you still need to stay within the accepted range.

Which Phone Size to Use

Start with 1080 x 1920 px (portrait). This is the standard Full HD resolution that displays well on virtually all Android phones. It's the safest default and produces clean, sharp screenshots across devices.

If your app is landscape-only (games, video apps), use 1920 x 1080 px instead.

Tablet Screenshot Dimensions

Tablet screenshots are strongly recommended if your app supports tablets. Google may limit your app's visibility on tablet devices without them.

You must upload at least 1 screenshot for the tablet listing. Using the 10" tablet size gives you the best coverage across larger Android devices.

Chromebook Screenshots

If your app runs on Chrome OS, Chromebook screenshots help your listing stand out in the Google Play Store on desktop.

Chromebook users browse in landscape mode, so landscape screenshots are the only practical choice here.

Wear OS Screenshots

For Wear OS companion apps or standalone watch apps:

Keep the design centered and avoid placing critical content near the edges, since Wear OS displays are circular and will clip corners.

Feature Graphic

The feature graphic is required for every Google Play listing. It appears at the top of your store page and in promotional placements.

Design it like a banner ad: your app icon, a tagline, and a clean background. Avoid small text—it gets compressed on smaller screens.

Quick Reference Cheat Sheet

All dimensions in one table:

Google Play Image Requirements

Beyond dimensions, your screenshots must meet these technical specs:

Format:

• JPEG or PNG (24-bit color)
• No alpha channel (no transparency)
• Maximum file size: 8 MB per image

Content rules:

• Must accurately represent your app
• No misleading content or fake UI elements
• No excessive promotional text
• Screenshots should show actual app functionality

What to avoid:

• Outdated UI that doesn't match the current app version
• Device frames that misrepresent the device type
• Content that violates Google Play policies

How to Create the Right Sizes

Option 1: Use a Screenshot Generator

A Play Store screenshot generator like Screenhance lets you:

1. Upload any screenshot

2. Select Google Play dimensions

3. Add device frames and backgrounds

4. Export at exact required sizes

This is the fastest path from raw screenshot to store-ready asset.

Option 2: Android Emulator

Capture directly from Android Studio's emulator at native resolution:

1. Run your app in the emulator

2. Select the target device profile

3. Use the screenshot button in the toolbar

Option 3: Design Manually

Create artboards in Figma or Canva at exact dimensions, then export. Good for adding captions, backgrounds, and marketing text overlays.

Common Mistakes

Wrong aspect ratio

Google Play enforces 16:9 or 9:16. A screenshot at 4:3 or any other ratio will be rejected. Always verify your aspect ratio before uploading.

Too low resolution

Uploading images below 1080 px wide for phones makes text and UI elements look blurry. Always work at the recommended resolution or higher.

Alpha channels in PNG files

Google Play does not allow transparency. If your PNG has an alpha channel, flatten it against a solid background before exporting.

Wrong file format

Google Play accepts JPEG and PNG only. WebP, AVIF, TIFF, and BMP files will be rejected. Convert before uploading.

Foldable Screen Sizes Google Added in 2025: What Changed and What Didn't

Google's 2025 Play Console updates extended the screenshot pipeline to better support foldables — Samsung Galaxy Z Fold, Pixel Fold, OnePlus Open, and friends — but the changes were quieter than most ASO blogs suggested. There is no new dedicated foldable upload slot. What changed was how Google evaluates large-screen UX, what badges your listing can earn, and how foldable previews get composited from the assets you already provide.

In practice, foldables consume your 7-inch tablet screenshots when the device is unfolded, and your phone screenshots when it's in cover-display mode. That means the same listing has to look intentional in both shapes. The trap is uploading phone-only screenshots that get auto-scaled onto the inner display, producing letterboxed assets with empty padding bars that scream "this app wasn't designed for me." Pixel-tall captions and dense edge-aligned content get sliced when Google centers your 9:16 phone screenshot inside a roughly 6:5 inner panel.

What didn't change: Google still does not require foldable-specific screenshots, and the 10-inch tablet bucket is still your best leverage point if your app genuinely adapts to wider canvases. If you want the "Designed for large screens" treatment, the 10-inch tablet upload is the unlock — not a phantom foldable slot. Treat the 1200 x 1920 tablet category as your foldable-friendly export and reserve the 10-inch slot for genuine tablet layouts.

Play Store Screenshot Rejection Patterns: The Four Most-Common Reasons Assets Get Bounced

Google's policy reviewers don't reject screenshots for aesthetic reasons, but they do reject them for misrepresentation. After years of submission cycles, four patterns account for the bulk of rejections, and all four are avoidable.

The first is fake UI chrome. Compositing a fictitious "Download" button or a fabricated 5-star review widget into your screenshot crosses the line from marketing into deception. Reviewers spot this fast because the rendered UI doesn't match the binary they're reviewing. The second is platform misrepresentation — iOS status bars, iPhone notches, or Cupertino-style icons inside a Play Store asset. Even if your app is cross-platform, the Play Store listing must depict Android. The third is reward or pricing claims that change. "$5 off this week" or "Free for a limited time" embedded in a screenshot dates your asset and triggers policy flags because the image outlives the promotion. The fourth is age-inappropriate content visible in the screenshot but locked behind a higher content rating in the binary — this gets the entire listing's age rating re-evaluated, often upward.

Each rejection costs you a review cycle, usually 24 to 72 hours. The fix in all four cases is the same: depict your app accurately, depict it on Android, and keep time-sensitive claims out of permanent assets. If you need to promote a sale, use the Promotional Content section, not a baked-in screenshot.

Frequently Asked Questions

What is the minimum screenshot size for Google Play?

The minimum dimension is 320 pixels on any side, with a maximum of 3840 pixels. However, the recommended size for phone screenshots is 1080 x 1920 pixels. Going below 1080 px wide will result in low-quality images on modern devices.

How many screenshots can I upload to Google Play?

You can upload between 2 and 8 screenshots per device type. Unlike Apple's 10-slot limit, Google caps it at 8. Make every slot count—the first screenshot appears in search results and is your most important visual.

Does Google Play accept WebP screenshots?

No, Google Play only accepts JPEG and PNG files for screenshots. WebP is not supported despite being Google's own format. Convert any WebP files to PNG or JPEG before uploading.

What's the difference between phone and tablet screenshots?

Phone screenshots use a 16:9 aspect ratio at 1080 x 1920 px recommended. Tablet screenshots are larger—1200 x 1920 for 7" tablets or 1600 x 2560 for 10" tablets. Tablets use different aspect ratios to match wider screens. You should provide separate screenshots optimized for each form factor.

Do I need separate screenshots for different Android devices?

No, you don't need screenshots for every individual device. Google Play groups them by category: phone, 7" tablet, 10" tablet, Chromebook, and Wear OS. One set of phone screenshots covers all phone devices. Add tablet screenshots if your app supports tablets.

What are the exact Wear OS screenshot requirements?

Wear OS screenshots are 384 x 384 pixels on a circular display assumption. The image itself is square, but Wear OS hardware crops the corners. Place all critical content within the inscribed circle — roughly 270 px on each side at center. Anything in the outer square margins will be invisible on round watches, which is the majority of the Wear OS fleet.

How do Chromebook and other large-screen exports differ from tablet exports?

Chromebook screenshots are landscape 1920 x 1080 at 16:9, treating the device as a laptop. The 10-inch tablet bucket is taller and supports portrait. If your app has a true 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. Uploading the same stretched phone screen to both tablet and Chromebook slots is the fastest way to look unprofessional on large screens.

Does Google Play support dark theme variants of screenshots?

Not as a separate upload slot. You upload one set per device tier. If your app supports dark mode and your audience skews dark-mode-default (developer tools, reading apps), captioning a screenshot in dark mode often wins more clicks because it stands out against the predominantly light Play Store chrome. There's no SEO or ranking penalty for either choice.

What's the right multi-locale screenshot strategy?

Localize the languages that produce the most traffic, not all of them. For most apps that means English, then the top three to five non-English markets by installs. Translate the caption text and swap any in-screenshot sample data (names, currency, addresses) to local equivalents. Don't translate the UI in your screenshot if your app doesn't actually ship in that locale — Google's reviewers compare screenshot content against the binary's supported languages.

Are there screenshot caps per device tier?

Yes, the cap is 8 screenshots per tier: phone, 7-inch tablet, 10-inch tablet, Chromebook, Wear OS, TV. You can run all six tiers if your app supports them, giving you a theoretical 48-screenshot ceiling per locale. Most apps fill 6–8 phone slots, 4–6 tablet slots, and skip the rest unless they have form-factor parity.

Related Reading

• App Store Screenshot Dimensions 2026 - Apple's requirements for comparison
• App Store vs Play Store Screenshots - Key differences between platforms
• Android Screenshot Sizes 2026 - Full Android sizing guide
• Play Store Screenshot Generator - Generate all required sizes automatically

Conclusion

Google Play screenshot dimensions are flexible but have clear boundaries. Start with 1080 x 1920 for phones, add the 1024 x 500 feature graphic, and provide tablet screenshots if your app supports them.

Get the basics right and your listing will be approved on the first submission. Once your dimensions are locked in, focus on making your screenshots actually sell your app—the right sizes are just the starting point.

Ready to generate every size automatically? Try the Play Store screenshot generator — upload your screenshots, pick a template, and export every required size in minutes.