Google Play Screenshot Sizes, Feature Graphic and Video

Google Play doesn't give you exact pixel sizes per device. It gives you a range, a maximum aspect ratio and a few per-device rules, then a stricter set of guidelines that decides whether your screenshots can appear in Play's large recommendation formats. It is easy to pass the base rules and still miss the stricter set. This guide covers both, along with the feature graphic and the preview video, as of 18 September 2026.

The short version

• Screenshots are JPEG or 24-bit PNG with no alpha, between 320 and 3840 pixels on each side, and the long side can be at most twice the short side.
• You can add up to eight per device type, and you need at least two, across device types, to publish.
• To be eligible for recommendation formats, an app needs at least four screenshots of at least 1080 pixels: 9:16 portrait (1080 x 1920 or more) or 16:9 landscape (1920 x 1080 or more).
• Tablets and Chromebooks take at least four screenshots at 16:9 or 9:16, from 1,080 to 7,680 pixels. Wear OS needs square screenshots of at least 384 x 384.
• The feature graphic is required: 1024 x 500, JPEG or 24-bit PNG, no alpha.

The base rules for every screenshot

Google keeps its asset rules on the Play Console Help page Add preview assets to showcase your app. As of 18 September 2026, it says every store listing needs at least two screenshots across your device types, and that each screenshot must be:

• JPEG or 24-bit PNG, with no alpha channel;
• at least 320 pixels on its shortest side and no more than 3840 pixels on its longest;
• no more than twice as long as it is wide (or twice as wide as it is long).

The last rule catches people out. Many current phones have screens around 20:9, so a raw capture such as 1080 x 2400 pixels is 2.22 times as tall as it is wide, and fails. Crop or compose your screenshots at 9:16 instead, which also matches the recommendation rules below.

Sizes by device type

The same Help page lists the supported device types as phones, 7-inch and 10-inch tablets, Chromebooks, Android TV, Wear OS watches, Android Automotive OS cars and Android XR headsets, with up to eight screenshots for each. You add them in Play Console under Grow users > Store presence > Main store listing, in the Graphics section, where each device type has its own area. As of 18 September 2026:

The large-screen upper bound of 7,680 pixels is higher than the 3840 in the base rules. Both figures are on Google's page as written, so if an upload is refused, check which limit Play Console applied.

The recommendation rules

Google's page splits its guidance into requirements, which can get a listing removed if you ignore them, and "highly recommended" guidelines, which affect where your assets can appear. For screenshots, one part of the second group works as a hard requirement: some sections of Google Play show recommended apps in a large format built from screenshots, and to be eligible for those formats, as of 18 September 2026:

• Apps need at least four screenshots with a minimum resolution of 1080 pixels: 9:16 portrait at 1080 x 1920 or more, or 16:9 landscape at 1920 x 1080 or more.
• Games need at least three 16:9 landscape screenshots at 1920 x 1080 or more, or three 9:16 portrait ones at 1080 x 1920 or more, showing the actual gameplay.

The same section adds content guidance worth following anyway:

• Show the real app. Don't show fingers tapping a device, unless the app is used off the device.
• Taglines should take up no more than 20% of the image.
• No words such as "Best", "#1", "Top", "New", "Discount" or "Sale", no awards or testimonials, and no calls to action such as "Download now".
• Tidy the status bar: no carrier names or notifications, and full battery, Wi-Fi and signal icons.
• No device imagery and no Google Play or other store badges.
• Add alt text of up to 140 characters to each screenshot, describing what it shows.

The feature graphic

You need a feature graphic to publish your store listing. As of 18 September 2026, it must be 1024 x 500 pixels, JPEG or 24-bit PNG, with no alpha. Play uses it as the cover image for your preview video, and in large-format collections of apps, including ads.

Google's recommendations for it, from the same page:

• Keep the logo, app name, slogan and main UI near the centre. The edges fall in cut-off zones that some formats crop or cover.
• Don't repeat your app icon as the main element, because the two are often shown side by side.
• Avoid pure white, black or dark grey backgrounds, which blend into Play's own background.
• Leave out device imagery, store badges and promotional words.

The preview video

A preview video is optional, though Google highly recommends one for games, which need it to appear in some parts of Play. As of 18 September 2026, the rules are:

• Add one video by pasting its YouTube URL into the preview video field. Use the video's own URL, not a playlist or channel, and leave out extra parameters such as timecodes.
• Turn off ads. Disable monetisation on the video, or upload a version without monetisation claims. If it contains copyrighted material, turning off monetisation may not be enough.
• Set it to public or unlisted, never private. It must not be age-restricted, and it must be embeddable.

The video plays from a button over your feature graphic, can also appear on Play's home and search pages, and may autoplay muted for up to 30 seconds, depending on the device, settings and connection. So the opening 30 seconds matter most: Google recommends showing the real app within the opening 10 seconds, keeping at least 80% of the video representative of the experience, and adding captions. Android XR listings can add up to two further videos.

Custom store listings, briefly

You don't have to show everyone the same screenshots. Google's page on custom store listings says, as of 18 September 2026, that you can create up to 50 of them, each with its own app name, icon, descriptions and graphic assets. Each one targets an audience: users in chosen countries, people arriving from a Google Ads campaign, people searching particular keywords, pre-registered users, or lapsed and churned users, among others. You can also give a listing its own URL parameter and link to it from a page about that feature.

Contact details, the privacy policy and the app category are shared by every listing. Custom listings aren't translated for you, so add translations yourself.

One timing note. Store listing changes, including custom listings, appear on Play Console's Publishing overview page among the changes you send to Google for review. Google's page on managed publishing says it holds back store listing changes until you publish them, so you can line up new screenshots with the release they describe.

A workflow for a small team

Capture four or more phone screenshots at 9:16, 1080 x 1920 or larger, so one set passes both the base rules and the recommendation rules. Add a tablet set if your layout changes on a large screen. Fill the app with fictional data from a demo account, and write the alt text as you export.

For the rest of the listing, see our guides to Android app icon sizes and publishing an app on Google Play. If you also ship on iOS, see App Store screenshot sizes.

How FeedbackKit fits in

FeedbackKit is an in-app feedback board: your users post requests, vote and comment inside your app. It has nothing to do with uploading screenshots, but the two meet.

If a screenshot shows your feature request screen, fill it with fictional requests before you capture it, the same as any other screen. And the board appears in your Android app through the Kotlin SDK, with Jetpack Compose screens, or the Flutter and React Native SDKs. Our guide to adding a feedback board to an Android app covers the setup. Here is how that looks in FeedbackKit, with sample data from a fictional hiking app:

Most apps shouldn't lead their screenshots with a feedback screen. The opening images should show what the app is for. The board earns its place after launch, when it tells you which feature the next set of screenshots should be about.

If you want that list of requests from your own users, start free. Pricing lists what each plan includes.