Google Play store listing requirements: asset checklist
Before you upload anything to Google Play, it helps to have the exact specs in front of you — because Play Console rejects assets that miss a dimension or use the wrong format, and the rules differ enough from the App Store that you can't reuse the same files blindly. Here is the full checklist in one table, then a short note on each row and the two or three things that catch people out. Every spec is verified against Play Console Help (2026); sources are linked at the bottom.
The full Google Play listing asset spec
| Asset | Dimensions / limit | Format | Rules & notes |
|---|---|---|---|
| App icon | 512 × 512 px | 32-bit PNG, with alpha; max 1 MB | Required. Play masks it to a rounded shape, so keep detail out of the corners. |
| Feature graphic | 1024 × 500 px | JPEG or 24-bit PNG, no alpha | Required. Also the cover frame for a promo video; only shown on the listing when a video is present. |
| Phone screenshots | Min 2, up to 8. Each side 320–3840 px; longest side ≤ 2× shortest (max 2:1) | JPEG or 24-bit PNG, no alpha; max 8 MB each | At least 2 (across device types) to publish; 4+ recommended to be eligible for promotion. 9:16 portrait is typical. |
| 7-inch tablet screenshots | Up to 8. Same 320–3840 px / 2:1 rules | JPEG or 24-bit PNG, no alpha | Optional, but recommended if you support tablets — Play surfaces a separate tablet listing. |
| 10-inch tablet screenshots | Up to 8. Same 320–3840 px / 2:1 rules | JPEG or 24-bit PNG, no alpha | Optional, same as 7-inch. Larger tablet slot for 10-inch devices. |
| App title | Max 30 characters | Text | No promotional words (see below). Counts spaces and symbols. |
| Short description | Max 80 characters | Text | The one-line summary shown above the fold. Spaces and symbols count. |
| Full description | Max 4000 characters | Text | The long listing body. You rarely need all 4000; the first lines do the work. |
| App binary | — | AAB (Android App Bundle) | New apps must ship as an .aab, not an APK — required since August 2021. |
That table is the whole listing surface: three graphic assets, three text fields, and the binary. The rest of this post is the detail behind each row.
App icon: 512 × 512, and mind the corners
The icon is a single 512×512 px file, uploaded as a 32-bit PNG with an alpha channel, under 1 MB. Play renders it inside a rounded mask, so anything you push into the extreme corners gets clipped. Design a full square, keep the important marks centred, and let the mask do its thing. This is one of the few Play assets that keeps alpha — the feature graphic and screenshots do not.
Feature graphic: required, but only shown sometimes
The feature graphic is a 1024×500 px banner in JPEG or 24-bit PNG with no alpha channel. It is a required asset — you can't complete the listing without one. The catch is that it only appears on the store listing itself when you also attach a promo video, because it doubles as the video's cover frame. Even so, Play uses the feature graphic in other promotional placements, so it is never optional. Treat it as a real design job, not a placeholder: text needs to survive being cropped on different surfaces, and it stays clear of the promotional wording Play bans (next section).
Screenshots: the 2:1 rule is the one people miss
You need a minimum of 2 screenshots across device types before Play lets you publish, and you can upload up to 8 per device type. Each is a JPEG or 24-bit PNG with no alpha, up to 8 MB. The dimension rule is where uploads get rejected: every side has to be between 320 and 3840 px, and the longest side can be no more than twice the shortest. That second half is the 2:1 aspect-ratio ceiling. A tall marketing panel at, say, 1080×2400 is 2.22:1 — over the limit, and Play rejects it even though both sides are inside 320–3840.
This is the single most common Play screenshot rejection, and it's why an App Store screenshot set doesn't drop straight into Play. iPhone screenshots are frequently taller than 2:1; Play won't take them. You want a phone canvas that lands at or under 2:1 — a 9:16 portrait at 1080×1920 is a safe, common choice — and if you're carrying a design over from the App Store, it has to be re-sized to fit the ratio, not just re-exported.
Tablet screenshots (7-inch and 10-inch) follow the same 320–3840 px and 2:1 rules and are optional, but if your app supports tablets it's worth filling both slots — Play shows a distinct tablet listing to those users. Wear OS, Android TV, and Chromebook each have their own separate screenshot slots if you target those form factors.
Text limits — and the words you can't use
The three text fields are strict character counts: 30 for the app title, 80 for the short description, 4000 for the full description. Spaces and symbols count toward every one. Those are the same limits App Store Connect happens to share for some fields, but don't assume — Play counts its own way and truncates hard at the limit.
The trap that isn't about length: Google bans promotional and performance wording in the icon, title, short description, and developer name. Words like "free", "best", "#1", "top", "new", "sale", or "discount" — anything that implies store ranking, price, or a promotion — will get the listing flagged. The same rule extends to the feature graphic and promo video: no store-performance claims, no accolades you didn't earn from Google, and no call-to-action overlays like "Download now" baked into the art. Official "Best Of" or Editor's Choice badges awarded by Google Play are the exception you're allowed to show.
The binary: AAB, not APK
Since August 2021, every new app on Google Play has to be published as an Android App
Bundle (.aab) rather than a standalone APK. Play generates the per-device
APKs from your bundle. This isn't a listing asset, but it's part of the same "can I
actually publish" checklist, and it's a step people who last shipped years ago don't
expect. Existing APK-based apps can keep updating, but a brand-new listing needs the AAB.
Where Mokbi fits
Mokbi is built to hand you Play-valid assets straight out of the editor. Publish to Play from Mokbi and the phone screenshots go out at 1512 × 2688 — exactly 9:16, well inside Play's 2:1 ceiling, so nothing gets bounced for being too tall. It also produces the 1024×500 feature graphic from the same project, and drafts and translates the listing text — title, short description, full description — into 50 languages, kept inside Play's character limits per locale so nothing truncates mid-sentence. Designing is free; unlimited export and publishing come with a subscription — Solo at €29.99/mo or Studio at €49.99/mo, with no one-time purchase.
Mokbi doesn't stop at the files — it publishes them. Once the icon-adjacent design, the 1024×500 feature graphic, the Play-valid 2:1 screenshots, and the listing text in 50 languages are ready, Mokbi pushes the listing and assets straight to Google Play through the Play Developer API. For the App Store it stages the version in App Store Connect ready to submit — Apple requires the final Submit and review. What the tool removes is the part where you fight the dimensions and the consoles: the canvases are already the right shape, the exports already match the specs in the table above, and the upload happens for you.
The short version
- Icon: 512×512, 32-bit PNG with alpha, under 1 MB, safe corners.
- Feature graphic: 1024×500, JPEG or 24-bit PNG, no alpha, no promo wording.
- Screenshots: 2–8, each side 320–3840 px, longest ≤ 2× shortest, no alpha. Watch the 2:1 ceiling.
- Text: title ≤ 30, short ≤ 80, full ≤ 4000. No "free / best / #1 / top / new / sale".
- Binary: new apps ship an AAB, not an APK.
Google revises these tables from time to time. If you're reading this well after the publish date, confirm the current numbers in Play Console Help before you submit. As of 2026, the specs above are what the sources below list:
- Add preview assets to showcase your app — Play Console Help (icon, feature graphic, screenshot specs).
- Best practices for your store listing — Play Console Help (title/description limits, banned wording).
- Android App Bundle FAQ — Android Developers (AAB requirement for new apps).