Quick answer
Google Play phone screenshots must be at least 320px on the shortest side and at most 3840px on the longest, with an aspect ratio no wider than 2:1. The safe, sharp default is 1080×1920 (portrait) or 1920×1080 (landscape). You can upload 2 to 8 per listing, plus a 1024×500 feature graphic and a 512×512 app icon. Everything below is the full spec, plus how to export at these exact sizes for free.
What are the exact Play Store screenshot sizes?
Let me give you the table first, because that's probably why you're here. These are the current Google Play requirements for the graphic assets on a store listing:
| Asset | Required size | Format | Limit | |-------|---------------|--------|-------| | Phone screenshot | 1080×1920 (min 320px short side) | PNG or JPEG | 2–8 | | 7" tablet screenshot | 1080×1920 or 1920×1080 | PNG or JPEG | up to 8 | | 10" tablet screenshot | 1920×1200 or 1200×1920 | PNG or JPEG | up to 8 | | App icon | 512×512 | 32-bit PNG | 1 | | Feature graphic | 1024×500 | PNG or JPEG | 1 |
The two hard rules Google enforces on every screenshot: the shortest side has to be at least 320 pixels, the longest side can't exceed 3840 pixels, and the aspect ratio can't be wider than 2:1. As long as you stay inside that box, the upload goes through.
That said, "goes through" and "looks good" aren't the same thing. A 320px screenshot technically passes validation and then renders as a blurry mess on a modern phone. I default to 1080×1920 for portrait phone shots because it matches the resolution of a typical Android device and stays crisp on high-density screens. If you're showing a landscape game, flip it to 1920×1080.
Don't overlook the two assets that aren't screenshots: the 512×512 app icon and the 1024×500 feature graphic. The icon is a 32-bit PNG and it's the first thing anyone sees — in search, in the carousel, on the home screen after install — so it carries more weight per pixel than any single screenshot. The feature graphic sits at the top of your listing and gets pulled into promotional placements and the Play Store's own merchandising, so keep your app name and any key text well inside the safe area, away from the edges where different layouts can crop it. Both are required before a listing can publish.
For the official source, Google keeps the current numbers on the Play Console graphic assets help page — worth bookmarking, since they adjust it every couple of years.
| Asset | Required size | Format | Limit | |-------|---------------|--------|-------| | Phone screenshot | 1080×1920 (min 320px short side) | PNG or JPEG | 2–8 | | 7" tablet screenshot | 1080×1920 or 1920×1080 | PNG or JPEG | up to 8 | | 10" tablet screenshot | 1920×1200 or 1200×1920 | PNG or JPEG | up to 8 | | App icon | 512×512 | 32-bit PNG | 1 | | Feature graphic | 1024×500 | PNG or JPEG | 1 |
The two hard rules Google enforces on every screenshot: the shortest side has to be at least 320 pixels, the longest side can't exceed 3840 pixels, and the aspect ratio can't be wider than 2:1. As long as you stay inside that box, the upload goes through.
That said, "goes through" and "looks good" aren't the same thing. A 320px screenshot technically passes validation and then renders as a blurry mess on a modern phone. I default to 1080×1920 for portrait phone shots because it matches the resolution of a typical Android device and stays crisp on high-density screens. If you're showing a landscape game, flip it to 1920×1080.
Don't overlook the two assets that aren't screenshots: the 512×512 app icon and the 1024×500 feature graphic. The icon is a 32-bit PNG and it's the first thing anyone sees — in search, in the carousel, on the home screen after install — so it carries more weight per pixel than any single screenshot. The feature graphic sits at the top of your listing and gets pulled into promotional placements and the Play Store's own merchandising, so keep your app name and any key text well inside the safe area, away from the edges where different layouts can crop it. Both are required before a listing can publish.
For the official source, Google keeps the current numbers on the Play Console graphic assets help page — worth bookmarking, since they adjust it every couple of years.
What dimensions does Google actually require vs recommend?
There's a gap between what Google *requires* and what Google *recommends*, and it trips people up constantly.
Required (your upload fails without these): minimum 2 phone screenshots, shortest side ≥ 320px, longest side ≤ 3840px, ratio no wider than 2:1, PNG or JPEG, under 8MB each.
Recommended (your listing looks unprofessional without these): a full set of 4–8 screenshots, consistent dimensions across all of them, portrait orientation for phone-first apps, and the first two shots carrying your strongest message because that's all most people see in search results.
That last point matters more than the pixel math. On the Play Store search and category pages, users see your icon and roughly the first two screenshots before they ever tap through to the full listing. So the dimensions get you in the door, but the first two frames do the actual selling.
One mistake I see a lot: mixing aspect ratios. If three of your screenshots are 1080×1920 and two are 1080×2400, Google accepts all of them, but the listing carousel shows them at inconsistent heights and it looks sloppy. Pick one canvas size and render every screenshot to it. If you frame your screenshots in a device mockup, this happens automatically — every export lands on the same canvas. You can see all the device frames PlayMockUp ships with and they each export to a fixed, store-safe size.
Required (your upload fails without these): minimum 2 phone screenshots, shortest side ≥ 320px, longest side ≤ 3840px, ratio no wider than 2:1, PNG or JPEG, under 8MB each.
Recommended (your listing looks unprofessional without these): a full set of 4–8 screenshots, consistent dimensions across all of them, portrait orientation for phone-first apps, and the first two shots carrying your strongest message because that's all most people see in search results.
That last point matters more than the pixel math. On the Play Store search and category pages, users see your icon and roughly the first two screenshots before they ever tap through to the full listing. So the dimensions get you in the door, but the first two frames do the actual selling.
One mistake I see a lot: mixing aspect ratios. If three of your screenshots are 1080×1920 and two are 1080×2400, Google accepts all of them, but the listing carousel shows them at inconsistent heights and it looks sloppy. Pick one canvas size and render every screenshot to it. If you frame your screenshots in a device mockup, this happens automatically — every export lands on the same canvas. You can see all the device frames PlayMockUp ships with and they each export to a fixed, store-safe size.
How many screenshots should you upload?
Google lets you upload up to 8 phone screenshots and requires a minimum of 2. So how many should you actually use?
Upload all 8 if you can fill them with real value. Here's the structure I use, in order:
1. The hook — your single biggest benefit, stated as a headline over a clean screen. This is the one that has to win the search-results glance. 2. The core feature — the main thing your app does, shown mid-action. 3. A second feature — the next reason someone keeps the app installed. 4. Social proof or results — a rating, a stat, a before/after. 5–8. Supporting features, settings, breadth — show range without repeating yourself.
The reason to use all 8 isn't to pad the listing. It's that each extra screenshot is a free piece of search real estate, and apps with fuller, captioned screenshot sets tend to convert better than ones with two bare phone screens. If you genuinely only have two screens worth showing, that's a sign your store page needs design work, not that two screenshots is enough.
A caption on each screenshot — a short headline baked into the image — is the single highest-leverage thing you can add. Bare screenshots make the user do the work of figuring out what they're looking at. A three-word headline does it for them.
Upload all 8 if you can fill them with real value. Here's the structure I use, in order:
1. The hook — your single biggest benefit, stated as a headline over a clean screen. This is the one that has to win the search-results glance. 2. The core feature — the main thing your app does, shown mid-action. 3. A second feature — the next reason someone keeps the app installed. 4. Social proof or results — a rating, a stat, a before/after. 5–8. Supporting features, settings, breadth — show range without repeating yourself.
The reason to use all 8 isn't to pad the listing. It's that each extra screenshot is a free piece of search real estate, and apps with fuller, captioned screenshot sets tend to convert better than ones with two bare phone screens. If you genuinely only have two screens worth showing, that's a sign your store page needs design work, not that two screenshots is enough.
A caption on each screenshot — a short headline baked into the image — is the single highest-leverage thing you can add. Bare screenshots make the user do the work of figuring out what they're looking at. A three-word headline does it for them.
What about tablet, Chromebook, and other form factors?
If your app supports tablets, Google strongly nudges you to add tablet screenshots — and as of the last couple of Play Console updates, large-screen quality is a ranking and featuring signal for tablet and Chromebook users. Skipping tablet screenshots means your app can get filtered out of the large-screen experience entirely.
The tablet sizes:
- 7-inch tablet: 1080×1920 (portrait) or 1920×1080 (landscape) - 10-inch tablet: 1200×1920 (portrait) or 1920×1200 (landscape)
Note the 10-inch ratio is 16:10, not 16:9 — that's the standard Android tablet aspect ratio, and a screenshot stretched from a phone canvas will look obviously wrong. Capture or frame at the real tablet dimensions instead of upscaling a phone shot.
The same applies to a MacBook or desktop frame if you're showing a companion web app or a large-screen layout. The trick across every form factor is the same: start from the device's true resolution so nothing gets stretched. PlayMockUp ships 7-inch, 10-inch, and generic tablet frames plus laptop and desktop frames precisely so you don't have to hand-calculate each one — you drop your screenshot in and the export comes out at the right size.
For the canonical tablet and large-screen guidance, Google's large-screen app quality docs are the source of truth.
The tablet sizes:
- 7-inch tablet: 1080×1920 (portrait) or 1920×1080 (landscape) - 10-inch tablet: 1200×1920 (portrait) or 1920×1200 (landscape)
Note the 10-inch ratio is 16:10, not 16:9 — that's the standard Android tablet aspect ratio, and a screenshot stretched from a phone canvas will look obviously wrong. Capture or frame at the real tablet dimensions instead of upscaling a phone shot.
The same applies to a MacBook or desktop frame if you're showing a companion web app or a large-screen layout. The trick across every form factor is the same: start from the device's true resolution so nothing gets stretched. PlayMockUp ships 7-inch, 10-inch, and generic tablet frames plus laptop and desktop frames precisely so you don't have to hand-calculate each one — you drop your screenshot in and the export comes out at the right size.
For the canonical tablet and large-screen guidance, Google's large-screen app quality docs are the source of truth.
How do you hit these sizes without design software?
Here's the part nobody tells first-time app developers: you don't need Photoshop, Figma, or any design skill to produce store-ready screenshots. You need three things — a raw screenshot from your phone, a device frame to drop it into, and an export at the correct dimensions.
The manual route is painful. You take a screenshot, open a design tool, find a device mockup PNG, line your screenshot up inside the bezel by hand, fight with the corner radius, add a background, then resize-export and hope the final pixel dimensions match what Google wants. I did this for my first app and it took an entire evening for five screens.
The faster route: use a tool built for exactly this. Open the PlayMockUp online studio right in your browser, pick a real device frame, drop your screenshot in, add a headline and background, and export. The export already matches Play Store dimensions, the corners and bezel are real, and you can batch all your screens to the same canvas in a few minutes. No signup, and the screenshots never leave your browser.
A few things to get right regardless of which tool you use:
- Export as PNG for screenshots with text and UI — it stays sharp. JPEG is fine for photo-heavy backgrounds. - Keep every screenshot on one canvas size so the carousel is even. - Put your headline in the top third — it's the part that survives the search-results crop. - Check it on an actual phone before you publish. The Play Console preview lies slightly; a real device tells the truth.
Get the dimensions right once, save your canvas, and every future update is a five-minute re-export instead of an evening of pixel-pushing.
The manual route is painful. You take a screenshot, open a design tool, find a device mockup PNG, line your screenshot up inside the bezel by hand, fight with the corner radius, add a background, then resize-export and hope the final pixel dimensions match what Google wants. I did this for my first app and it took an entire evening for five screens.
The faster route: use a tool built for exactly this. Open the PlayMockUp online studio right in your browser, pick a real device frame, drop your screenshot in, add a headline and background, and export. The export already matches Play Store dimensions, the corners and bezel are real, and you can batch all your screens to the same canvas in a few minutes. No signup, and the screenshots never leave your browser.
A few things to get right regardless of which tool you use:
- Export as PNG for screenshots with text and UI — it stays sharp. JPEG is fine for photo-heavy backgrounds. - Keep every screenshot on one canvas size so the carousel is even. - Put your headline in the top third — it's the part that survives the search-results crop. - Check it on an actual phone before you publish. The Play Console preview lies slightly; a real device tells the truth.
Get the dimensions right once, save your canvas, and every future update is a five-minute re-export instead of an evening of pixel-pushing.
Frequently asked questions
What is the best Play Store screenshot size in 2026?
1080×1920 pixels for portrait phone screenshots and 1920×1080 for landscape. Both stay sharp on modern Android screens, sit inside Google's 2:1 maximum aspect ratio, and match typical device resolution so nothing looks stretched.
How many screenshots can you upload to Google Play?
You can upload between 2 and 8 phone screenshots per listing, plus up to 8 each for 7-inch and 10-inch tablets. Google requires a minimum of 2 phone screenshots before a listing can go live.
What is the Play Store feature graphic size?
The feature graphic is 1024×500 pixels, in PNG or JPEG. It's required and appears at the top of your listing and in promotional placements, so keep important text away from the edges where it can get cropped.
Do my screenshots need a device frame?
No, Google accepts raw screenshots. But framed screenshots with a headline and background consistently look more professional and convert better. You can frame yours for free in the [PlayMockUp studio](/create) and the export lands at the correct Play Store size automatically.
What file format should app screenshots be?
PNG or JPEG, under 8MB each. Use PNG for screens with UI text and sharp edges so they stay crisp, and JPEG only when the image is mostly a photographic background.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.