Play Store App Images: The 2026 Guide to Screenshots, Feature Graphics & Conversion
Play Store app images are the visuals Google Play shows on your listing before anyone reads a word: the app icon, the feature graphic, and the screenshots. Getting them right is a conversion job, and the specs are public, so there is no reason to guess.
Play Store app images are the graphic assets you upload in Play Console to represent your app: the icon, the required 1024 x 500 feature graphic, and a set of phone, tablet, and optional Chromebook screenshots.
The exact Google Play image specs (and where they come from)
Google publishes the current asset requirements in Play Console Help, Add preview assets to showcase your app. That page is the one to check before every upload, because Google does revise it. As of this writing:
| Asset | Format | Requirement |
|---|---|---|
| App icon | 32-bit PNG | 512 x 512 px, max 1 MB |
| Feature graphic | PNG or JPEG | 1024 x 500 px |
| Phone screenshots | PNG or JPEG | 2 to 8 images, 16:9 or 9:16, each side 320 to 3840 px |
| 7-inch tablet screenshots | PNG or JPEG | 4 to 8 images, 16:9 or 9:16, each side 1,080 to 7,680 px |
| 10-inch tablet screenshots | PNG or JPEG | 4 to 8 images, 16:9 or 9:16, each side 1,080 to 7,680 px |
| Promo video | YouTube URL | Public or unlisted, not age-restricted |
The line most developers trip on is the 2-image minimum for phone screenshots. If you upload one screenshot, the listing will not publish. Tablet screenshots carry their own higher minimum of 4, and leaving them empty on an Android tablet makes your app look broken to a large slice of the install base.
Dimension checks are cheap to fail and cheap to fix. Drop the file into the free screenshot resizer before you open Play Console, or read the full spec sheet in screenshot sizes.
What you see in Play Console when you upload
The upload flow has not changed much in years, and that is good news if you are following an old tutorial. In Play Console: your app, then Grow users > Store presence > Main store listing. The Graphics section holds the app icon, feature graphic, and screenshots. Select Add phone screenshots, drag your files in order, and drag to reorder.
Two things are worth knowing before you hit save. First, reordering is real and it matters: the first two frames are the ones that appear on the search result card, so they are not "screenshots 1 and 2", they are your ad. Second, changes to a published listing can go to review. Google documents the review process in Prepare your app for review; assume a real-world turnaround of hours to a few days and pick your timing accordingly, especially in December.
After saving, open the listing on a real device. The preview inside Play Console renders a browser mock. A physical phone in your hand is the only honest preview.
Designing screenshots that convert on Google Play (first-hand)
I have rebuilt screenshot sets for utility apps, subscription apps, and a couple of games, and the pattern that holds across all of them: the screenshot is a headline with a picture behind it, not a product tour.
A structure that has worked repeatedly:
- Frame 1 is the promise. One benefit, stated in the words a user would use. "Track 12 currencies offline" beats "Comprehensive FX toolkit".
- Frames 2 and 3 carry the proof. Real UI, cropped to the part that supports the claim. Fake screens cost you trust on the second look.
- Frames 4 through 6 handle objections. Privacy, price model, one-handed use, whatever review complaints you got last quarter.
- The last frame is a soft prompt. Not "Install now", but a nudge that matches your listing (a 7-day trial line, a "no account needed" line).
Text scale is where most sets fail. Cap the overlay to roughly six words per frame and test it at thumbnail size, because on a phone the listing gives each screenshot about a third of the screen. If you cannot read the frame at that size, rewrite it shorter rather than shrinking the font.
One craft note: build each frame at 1080 x 1920 and export at the same ratio. Designers who start at 1242 x 2208 (an iOS frame) end up with awkward crops in the 16:9 Android slot.
The feature graphic is a banner, not a hero image
The feature graphic is required for a published Android listing. Google shows it at the top of your app's listing page, and it can also be used as a promotional placement inside the store. Because it gets cropped and scaled in different placements, the safe move is to put your only important element in the middle 70 percent of the 1024 x 500 canvas and leave the outer edges quiet. No text you actually need near the corners, no logo smaller than about 60 px tall.
A developer-founder habit that pays off here: export the graphic at the final size and view it in a phone frame, the way a user would see it. Banners that look elegant on a 27-inch monitor often read as mush on a 6-inch one.
Android and iOS asset rules differ, so stop reusing one export
This is the part of most Play Store image guides that quietly gets it wrong, so it is worth stating plainly: Google Play and the App Store want different assets. Reusing a single export is possible only by accident, and the accident shows up as a letterboxed or cropped listing on one store.
| Asset | Google Play (Android) | App Store (iOS) |
|---|---|---|
| Required banner | Feature graphic, 1024 x 500 px | None. There is no equivalent asset |
| Screenshot count | 2 to 8 per phone, 4 to 8 per tablet | 3 to 10 per device class |
| Orientation rule | One 16:9 set and one 9:16 set per device class | One orientation per device class |
| App icon | 512 x 512 px PNG | 1024 x 1024 px in the asset catalog |
| Product page experiments | Store listing experiments, including graphics | Product page optimization with up to three variants |
| Extra text asset | None | Promotional text, editable without a new build |
The takeaway is operational: build the Android set and the iOS set as two jobs with two export presets, even if they share the same design language. Apple's own requirements live in Screenshot specifications, and that page also tells you which device sizes currently need images.
Localize Play Store app images, then check them in the store language
Google Play screenshots follow the language of the listing, which means a screenshot set with English text is what a German user sees under a German description unless you upload a German set. That mismatch is one of the quietest conversion leaks in Android ASO, and it costs nothing to spot.
A workable order of operations, in the sequence I actually use:
- Ship the localized listing text first. There is no point localizing images for a listing whose description is still English.
- Localize screenshots for the two or three markets that produce meaningful installs. Not every locale.
- Keep the layout identical across languages and vary only the text. Shorter strings in German and longer strings in Spanish both have to fit, and rebuilding layout per language doubles the review risk.
- Leave the feature graphic visually language-free if you can. A single graphic with no words survives every locale.
Then verify by switching your device language and opening your own listing. If you have localized textures but your screenshots still say "Tap to start" in English, you will see it in about four seconds.
Common Play Store image mistakes I keep seeing
A short list, drawn from scanning hundreds of Android listings with the free ASO score tool, which flags several of these automatically:
- One screenshot. Below the two-image minimum. The listing will not publish, and if it somehow does you have wasted the strongest real estate you own.
- Below the 320 px minimum side. Rejected, or scaled so badly it reads as a bug.
- UI that no longer exists. Screenshots from build 2.1 sitting on a listing for build 4.0. Users spot it in the reviews.
- An oversized feature graphic message. The graphic is a banner, and any sentence over roughly five words gets cropped in at least one placement.
- Keyword stuffing in image text. Google's Spam and Minimum Functionality policy treats repeated, irrelevant keywords in listing content as abuse. Image text is listing content. Write for a human, and put the keywords in the description where they belong.
- English screenshots on a non-English listing. Covered above, still the most common one I find.
How to check your Play Store images before you ship
Before you upload, walk this checklist once. It takes about two minutes and catches nearly everything that triggers a rejection or a flat conversion rate.
- Every phone screenshot is between 320 and 3840 px on each side, and every tablet screenshot is between 1,080 and 7,680 px on each side.
- The feature graphic is exactly 1024 x 500 px.
- There are at least two phone screenshots and at most eight; at least four tablet screenshots and at most eight.
- Frame 1 passes the thumbnail test: readable on a 6-inch phone at listing size.
- No screenshot shows UI you cannot ship today.
- The feature graphic has no important element within 15 percent of any edge.
- Every localized listing has matching localized screenshots.
- You checked the character budget on any text overlay using the character counter, since the same string has to fit the frame and the store card.
For the wider Android-specific picture, including how the title, short description, and full description get indexed, see Google Play app optimization: what the store actually reads. If you are working on the iOS side of the same app, App Store A/B testing covers product page optimization and custom product pages.
FAQ
How do I change Google Play app images?
Open Play Console, choose your app, then Grow users > Store presence > Main store listing. Upload the new icon, feature graphic, or screenshots in the Graphics section and save. If the app is already published, expect the change to pass through review before it goes live. Google documents the required assets at Add preview assets to showcase your app.
How many screenshots does Google Play require?
At least two and no more than eight phone screenshots, each between 320 and 3840 px on every side. Tablet screenshots have a higher minimum of four (also up to eight), each between 1,080 and 7,680 px on every side. All in PNG or JPEG. Source: Play Console Help.
What size is the feature graphic?
1024 x 500 px, PNG or JPEG. It is required for a published Android listing and appears at the top of the listing page. Keep the meaningful content toward the center, since the graphic gets cropped in some placements.
Do Play Store screenshots affect conversion?
They are the main visual a user sees before tapping Install, so they influence whether store traffic converts. They are not a ranking input. The honest framing: better screenshots change how many of the people who already found your listing install the app, and how many of those installs stick around.
Can I use the same images on the App Store and Google Play?
Usually not without rework. Google Play wants a 1024 x 500 feature graphic; the App Store has no equivalent asset. Screenshot counts, aspect ratios, and orientation rules also differ, and Apple's current requirements are listed at Screenshot specifications.
Should I put keywords in my Play Store screenshots?
No. Google indexes the title, short description, and full description, not your image text, and its Spam and Minimum Functionality policy covers listing content including images. Write screenshot copy for the person deciding whether to install, and put keywords in the copy that gets indexed. For how those indexed fields work, and how search demand for the terms you are targeting breaks down (for example, "app name" sees 97 searches a month in the US at a difficulty of 0/100, while "app store optimization" runs 60 searches at 50/100), see App Store Keywords.
If you want a second opinion before you upload, run your app through the free 60-second ASO scan. It checks your listing on both stores and shows what to fix first, no account needed.
