The Ultimate Guide to Android Play Store Asset Sizes in 2026

Uploading perfectly formatted images into the Google Play Console without catching immediate validation errors is harder than coding the app itself. The requirements mutate constantly, documentation is scattered across multiple support pages, and the error messages you get back are often cryptic at best. If you have ever spent an afternoon re-exporting assets at slightly different pixel dimensions only to be told your image "does not meet the requirements," you are not alone.

Unlike Apple's App Store, which enforces rigid, device-specific screenshot sizes (6.5-inch, 6.7-inch, 5.5-inch, and so on), Google gives you flexible ranges that sound generous on paper but can trip you up in practice. A screenshot that passes validation today might fail tomorrow after a quiet backend update. Google Play Console has historically changed its image requirements without much fanfare, leaving developers to discover the changes through trial and error.

All specifications below are verified against Google Play Console's official graphic asset requirements as of March 2026. This guide covers every single asset type you might need for the Google Play Store in 2025: phone screenshots, tablet screenshots, Chromebook screenshots, the feature graphic, app icons, TV banners, Wear OS assets, and promo videos. Whether you are launching a brand-new app or refreshing your store listing for a major update, this is the definitive reference you can bookmark and return to whenever you need exact pixel dimensions, file format constraints, and size limits.

Phone Screenshots: The Foundation of Your Listing

Phone screenshots are the single most important visual asset in your Play Store listing. They are the first thing users see when they land on your app page, and on many devices, the first two screenshots are visible directly in search results without the user even tapping through. Getting these right is non-negotiable.

Unlike Apple's rigid standard bounds (6.5-inch, 6.7-inch, 5.5-inch), Google gives you dangerous freedom. A "Phone" screenshot can be uploaded as long as it meets a relatively simple set of dimensional rules. But those rules have subtle implications that catch people off guard.

The Dimensional Rules

• Minimum dimension: 320px on the shortest side
• Maximum dimension: 3840px on the longest side
• Aspect ratio constraint: The maximum dimension cannot exceed 2x the minimum dimension
• File format: JPEG or PNG
• Max file size: 8MB per image
• Quantity: 2 to 8 screenshots required

That aspect ratio constraint is the one that catches most developers. It means you cannot upload an ultra-tall screenshot at, say, 1080x3000. Since 3000 is more than 2x 1080 (which would be 2160), the upload would be rejected. This rule effectively caps you at a 1:2 aspect ratio at most.

Recommended Resolutions

While Google accepts a wide range, the sweet spot for Play Store mobile screenshots maps to common Android display shapes exported at high density. Most top ASO agencies render their Google Play screenshots at one of these baseline resolutions:

Resolution	Aspect Ratio	Best For
1080 x 1920	16:9	Classic Android phones, universal safe choice
1080 x 2340	19.5:9	Modern tall-screen devices (Samsung Galaxy, Pixel)
1080 x 2400	20:9	Latest flagship devices (2024-2025 models)

If you are unsure which to pick, 1080x1920 remains the safest universal choice. It renders cleanly on every device and stays well within the 1:2 ratio constraint. The taller options like 1080x2340 let you show more of your app's UI in a single frame, which can be useful for content-heavy apps, but make sure your key messaging stays in the upper portion of the image since shorter devices may crop the bottom in preview contexts.

Tablet Screenshots

Tablet screenshots are optional in Google Play Console, but skipping them is a missed opportunity. Users browsing the Play Store on a tablet will see your phone screenshots awkwardly scaled up if you do not provide tablet-specific assets. Worse, tablet users tend to be higher-converting: they typically spend more on apps and in-app purchases, making them a demographic worth optimizing for.

7-Inch Tablet

The 7-inch tablet category follows the same core rules as phone screenshots: minimum 320px on the shortest side, and the longest side cannot exceed 2x the shortest. The practical recommendation is to export at 1600x2560 for portrait orientation. This provides a crisp, high-density image that looks sharp on tablets like the Samsung Galaxy Tab A series and older Nexus 7 devices.

10-Inch Tablet

For 10-inch tablets, the same dimensional rules apply. The recommended resolution is 2048x2732 or 1600x2560, depending on whether you are targeting iPad-like aspect ratios (for cross-platform consistency) or standard Android tablet proportions. If your app has a distinct tablet layout with side panels, split views, or expanded navigation, make sure your tablet screenshots showcase those features rather than just being blown-up versions of your phone screenshots.

Users who see a tablet-optimized screenshot know immediately that your app will look native on their device, not stretched. This small signal can meaningfully improve your conversion rate on larger screens.

Chromebook Screenshots

If your app targets Chrome OS, Chromebook screenshots become an important asset. With the continued growth of Chromebooks in education and enterprise markets, this is a form factor you should not ignore if your app supports it.

• Minimum resolution: 1080x1920
• Preferred orientation: Landscape, since Chromebooks are primarily used with a keyboard and trackpad in laptop mode
• Same file format rules apply: JPEG or PNG, max 8MB

Chromebook screenshots should show your app running in a windowed or full-screen desktop context. If your app supports keyboard shortcuts, mouse input, or resizable windows, highlight those capabilities. Users browsing the Play Store on a Chromebook want reassurance that your app is not just a phone app blown up to a 14-inch screen.

The Feature Graphic

The 1024x500 Feature Graphic is archaic, bizarre, and absolutely critical to your app's click-through velocity. It sits at an unusual landscape ratio that makes it impossible to simply repurpose your vertical screenshots, demanding a dedicated landscape composition.

Specifications

• Exact dimensions: 1024 x 500 pixels (no flexibility here)
• File format: JPEG or PNG
• Max file size: 1MB
• Required: Yes, for all apps and games

The feature graphic appears in search results, category browsing pages, and editorial features. It is often the largest visual element users see before they even tap on your listing. If you have a promo video set up, Google overlays a play button on top of the feature graphic, which means your design must work as a standalone visual even with a semi-transparent overlay and play icon covering the center.

Design Best Practices

Google may crop or reformat the feature graphic depending on the context where it is displayed. The most important rule: do not put critical information in the outer 15% margins. Logos, taglines, and key visual elements should live in the center-safe area. Keep text large and readable at small sizes, because the feature graphic is often rendered as a thumbnail in search results, shrunk down to a fraction of its original size.

Avoid cluttering the feature graphic with too many elements. The best-performing feature graphics use a single strong visual, a concise tagline of three to five words, and the app icon or logo. Think of it as a billboard: you have about two seconds to communicate your app's value proposition.

App Icon

Your app icon in the Play Store is not the same file as the launcher icon bundled in your APK or AAB. Google Play requires a separate high-resolution icon upload that is used exclusively for the store listing.

• Dimensions: 512 x 512 pixels
• Format: PNG, 32-bit with alpha channel
• Must match the in-app launcher icon in design and branding
• No badges, watermarks, or text overlays allowed (Google's policy prohibits "SALE," "FREE," "NEW," or similar promotional text on icons)
• Do not round the corners yourself. Google automatically applies rounded corners (and on some surfaces, circular masks) when displaying your icon. Upload a full square 512x512 image and let the system handle the shaping.

A common mistake is uploading an icon with pre-rounded corners or a circular background, which results in double-rounding or visible gaps when Google applies its own mask. Always export your icon as a full-bleed square. Test how it looks at small sizes (as small as 16x16) since the icon appears at many different scales across the Play Store, Google Search results, and device home screens.

TV Banner and Screenshots

If you are building for Android TV, you need a dedicated set of assets that differ significantly from mobile. Android TV has its own section in the Play Store, and the browsing experience is entirely landscape-oriented, designed for lean-back viewing on large screens.

TV Banner

• Dimensions: 1280 x 720 pixels
• This banner is used as the primary visual on the Android TV home screen and within the TV Play Store
• Must be visually distinct and readable from across a living room (think 10-foot UI design principles)

TV Screenshots

• Dimensions: 1920 x 1080 pixels (landscape only)
• Show your app's UI as it actually appears on a TV screen
• If your app uses a D-pad navigation model, make sure the screenshots reflect that interaction paradigm

TV assets are only required if you are publishing an Android TV app. If your manifest does not declare TV support, you can skip these entirely. But if you do support TV, these assets are mandatory and omitting them will block your submission.

Wear OS Screenshots

Wear OS has its own section on the Play Store, and if your app includes a Wear OS companion or standalone watch app, you need screenshots that reflect the circular display format most Wear OS devices use.

• Recommended dimensions: 384 x 384 pixels
• Design for a circular viewport, keeping critical content away from the corners of the square canvas since they will be clipped on round watches
• Use high-contrast colors and large text, as watch screens are small and often viewed in bright outdoor conditions

Even though the canvas is a square, remember that most Wear OS devices display content in a circle. Design your screenshots with a circular safe zone in mind. Elements placed in the corners of the 384x384 square will be invisible to users on round watches. Some developers include a device bezel mockup in their Wear OS screenshots to help users visualize the experience, though this is a stylistic choice rather than a requirement.

Promo Video

Google Play lets you add a promotional video to your store listing, but unlike screenshots and graphics, you do not upload a video file directly. Instead, you provide a YouTube URL, and Google embeds the video in your listing with a play button overlaid on your feature graphic.

• Format: YouTube URL (the video must be public or unlisted, not private)
• Recommended length: 30 seconds to 2 minutes
• Orientation: Landscape is strongly recommended
• The first 10 seconds are critical. Google auto-plays the video in some contexts, and users decide within seconds whether to keep watching. Lead with your strongest hook.

Avoid starting your video with a logo animation or slow fade-in. Jump straight into showing the app in action. The best-performing promo videos demonstrate the core user experience in the first five seconds, then expand into secondary features. Include captions or on-screen text since many users browse the Play Store with sound off.

Common Rejection Reasons

Even if your assets meet every pixel requirement, Google can still reject them during review. Here are the most common reasons Play Store screenshots and graphics get flagged:

• Non-final UI: Screenshots showing placeholder content, "Lorem ipsum" text, debug overlays, or developer tools visible in the status bar will be rejected. Every screenshot must show your app in its production-ready state.
• Misleading content: Screenshots that depict features your app does not actually offer, or that exaggerate the app's capabilities, violate Google's metadata policy. If your screenshot shows a premium feature, make sure it is actually accessible to users.
• Text too small to read: If you add text overlays to your screenshots (captions, feature callouts, etc.), make sure they are legible at the thumbnail size the Play Store uses in search results. Text that requires zooming in to read defeats the purpose.
• Outdated branding: If your app has undergone a major redesign but your screenshots still show the old UI, Google may flag them as misleading. Keep your screenshots current with every significant release.
• Aspect ratio violations: The 2:1 maximum ratio constraint catches people who try to upload ultra-tall or ultra-wide images. Always verify your dimensions before uploading.

A rejected asset can delay your app launch by days while you wait for a re-review. It is always worth double-checking every file against the specs before you hit submit.

Quick Reference Table

Here is a comprehensive summary of every Google Play Store asset type, its specifications, and whether it is required:

Asset	Dimensions	Format	Max Size	Required?
Phone Screenshots	Min 320px, max 3840px, max 2:1 ratio	JPEG / PNG	8MB	Yes (2-8)
7" Tablet Screenshots	Min 320px, max 3840px, max 2:1 ratio	JPEG / PNG	8MB	No
10" Tablet Screenshots	Min 320px, max 3840px, max 2:1 ratio	JPEG / PNG	8MB	No
Feature Graphic	1024 x 500	JPEG / PNG	1MB	Yes
App Icon	512 x 512	PNG (32-bit, alpha)	1MB	Yes
TV Banner	1280 x 720	JPEG / PNG	1MB	TV apps only
Wear OS Screenshots	384 x 384	JPEG / PNG	8MB	Wear apps only

Bookmark this table. It will save you from re-reading Google's scattered documentation every time you prepare a new release. And remember: these specs can change. Google has a history of updating requirements with minimal notice, so always verify against the Play Console's current validation when uploading.