Why Google Play Rejects Your Phone Screenshots (the 2:1 Rule)

You grab a screenshot on your Pixel, drag it into Play Console, and it bounces. The file is sharp, the right format, and well under any size you’d worry about. Google Play requires that a screenshot’s long side be no more than twice its short side, and almost every current phone screen is taller than that: a Pixel 10 captures at 1080 × 2424, about 2.24:1. The fix is to crop the capture to 9:16 or, better, place it on a 1080 × 1920 canvas, which also meets the shape Google requires for featuring.

This post is about that one problem: why native captures fail, the three ways to fix them, and which fix keeps your app eligible for Play’s large-format placements. If you need the full list of Play asset sizes (icon, feature graphic, TV banner, XR and Wear OS), that’s in our Google Play store listing graphics guide.

All rules quoted here come from Google’s preview assets help page, checked on October 21, 2026.

The rule, word for word

Google lists four hard requirements for screenshots:

JPEG or 24-bit PNG (no alpha)
Minimum dimension: 320 px
Maximum dimension: 3840 px
“The maximum dimension of your screenshot can’t be more than twice as long as the minimum dimension.”

The last one is the 2:1 rule. A portrait screenshot 1080 px wide can be at most 2160 px tall. Anything taller is refused at upload, no matter how good it looks.

You also need at least two screenshots in total across your device types to publish, and you can add up to eight per device type.

Why your phone’s screenshot fails

Phone screens stopped being 16:9 years ago. Manufacturers now quote them as 19.5:9 or 20:9, and a screenshot is the screen’s native resolution, so it inherits that shape. Here’s what that means for a few current phones:

Phone	Native screenshot	Long ÷ short	Passes 2:1?
Pixel 10	1080 × 2424	2.24	No
Pixel 9a	1080 × 2424	2.24	No
Pixel 10 Pro	1280 × 2856	2.23	No
Pixel 10 Pro XL	1344 × 2992	2.23	No
Galaxy S25 (FHD+)	1080 × 2340	2.17	No

The Pixel resolutions are from Google Store spec pages, which list all four as 20:9 displays. Samsung’s own page only labels the Galaxy S25 as “FHD+”; the 1080 × 2340 figure is the widely reported panel resolution, not one Samsung states on that page.

Notice how small the overshoot is. A 20:9 screen is about 2.22:1, only about 11% too tall. That’s why the rejection is so surprising: the image looks like a perfectly normal phone screenshot, because it is one. Your App Store screenshots have the same issue, since Apple’s required iPhone sizes are also around 2.17:1 (see our App Store screenshot sizes guide). You can’t reuse that set on Play as-is either.

Passing the rule isn’t the same as getting featured

Clearing 2:1 gets your listing published. It doesn’t make your screenshots eligible for the places Play shows apps in a large format with screenshots, such as recommendation rows. For those, Google says these are “a requirement”:

Apps: at least four screenshots with a minimum of 1080 px, at 9:16 portrait (minimum 1080 × 1920) or 16:9 landscape (minimum 1920 × 1080).
Games: at least three screenshots at 16:9 (minimum 1920 × 1080) or 9:16 (minimum 1080 × 1920), showing the actual in-game experience.

Google files this under “Highly recommended” and says missing it “will not impact your store listing page, but may result in changes to how your preview assets appear on Google Play or limit promotional opportunities.” So it won’t block you, but there’s no upside to skipping it.

This matters for choosing a fix. A 1080 × 2160 screenshot passes the 2:1 rule and uploads fine, but it isn’t 9:16, so it doesn’t count toward featuring. If you’re going to change your screenshots anyway, change them to 9:16.

Fix 1: Crop to 9:16

The quickest fix is to cut the capture down to the right shape. For a Pixel 10, that means taking 1080 × 1920 out of 1080 × 2424, which removes 504 px, or about a fifth of the height.

	Pixel 10 capture	After crop
Size	1080 × 2424	1080 × 1920
Ratio	2.24:1	9:16 (1.78:1)
Passes 2:1	No	Yes
Counts for featuring	No	Yes, at 1080 px wide

Cropping works well when the top and bottom of the screen don’t matter much: the status bar, a navigation bar, or empty space under a short list. It works badly when your key UI sits at both ends, like a top app bar with a search field and a bottom navigation bar. Cut either and the screenshot stops looking like your app.

Our image cropper has a 9:16 preset and shows the exact pixel size as you drag. It keeps the original format, so a PNG stays a PNG. If Play Console then complains about the PNG, the cause is usually an alpha channel: browsers and most tools save 32-bit PNGs even when every pixel is opaque, and Play wants 24-bit. Convert it to JPEG with the image format converter.

Don’t fix the shape by resizing to 1080 × 1920 without cropping. That squashes the interface, and Google’s guidelines say not to include “images that are stretched or compressed.”

Fix 2: Pad it (letterbox)

The opposite approach is to keep the whole capture and add space at the sides until the image is 9:16. Scale the 1080 × 2424 capture down to 1920 px tall and it’s about 855 px wide, leaving roughly 112 px of background on each side of a 1080 × 1920 image.

Padding keeps every pixel of your UI. The downside is that the result looks unfinished if the padding is a flat color picked at random: a phone screenshot floating in a slightly too-wide frame. It’s fine for a quick update, and it’s how many developers ship their first listing.

Fix 3: Compose it onto a 1080 × 1920 canvas

This is a designed version of padding: put the capture on a 1080 × 1920 canvas with a background, scale it down a little further, and use the space for a short caption. It keeps your whole UI, looks intentional, and fits Google’s guidelines, as long as you follow a few rules from the same help page:

Taglines should take up no more than 20% of the image. Google also says to add them “only if necessary,” and to avoid small text that “will not be visible on many phone screens.”
No ranking, price or promotion words. Google names “Best,” “#1,” “Top,” “New,” “Discount,” “Sale,” and “Million Downloads,” and asks you to avoid calls to action like “Download now” or “Try now.”
No device imagery. Google lists it among elements to avoid because it “can become obsolete quickly or alienate some users.” That rules out wrapping your capture in a photo-real phone frame.
No fingers tapping the screen, unless your app’s core use is off the device.
Show the real app. Stylized screenshots that run one image across several uploads are allowed, but Google asks you to “prioritize UI in the first three screenshots.”
Clean status bar. No carrier name or notifications; battery, Wi-Fi and signal full.

The status bar is worth sorting out before you capture, since a composed screenshot still shows it. Clear your notifications and charge up first, or crop just the status bar off the top before composing.

How our generator handles it

The Google Play Screenshot Generator is built around fix 3. What it does, based on its source:

Starts the phone tab on 1080 × 1920. Other phone sizes are 1440 × 2560 and 2160 × 3840 (the largest 9:16 under the 3840 px cap), plus landscape versions of each. A 1080 × 2160 “2:1” size sits under “More sizes” and is labeled as not counting toward featuring.
Fits your capture instead of cropping or stretching it. It detects tall phone captures by aspect ratio rather than exact pixels, so 1080 × 2424, 1080 × 2340 and 1344 × 2992 all land on the phone tab and are scaled into the canvas with your background around them.
Defaults to no device frame, since Google advises against device imagery. Generic Android phone, tablet and Chromebook frames are available, and the checks remind you of Google’s advice when one is on.
Runs Play’s rules as pre-flight checks: the 320 to 3840 px limits, the 2:1 rule, at least 2 screenshots to publish and up to 8 per device, featuring readiness (exactly 9:16 or 16:9, at least 1080 px, 4 or more screenshots), the banned promotional words, and an estimate of how much of each image your captions cover against the 20% guideline. The text-coverage number is an estimate from the caption boxes, not a pixel count.
Exports true 24-bit PNGs with no alpha, in one ZIP with a folder per device type.

Everything runs in your browser; your screenshots aren’t uploaded anywhere.

Tablets and Chromebooks

Large screens have their own guidance on the same page. Play Console has separate 7-inch and 10-inch tablet sections, but the guidance gives no separate numbers for them. For tablets and Chromebooks, Google says:

Add at least 4 screenshots.
Upload screenshots between 1,080 and 7,680 px.
Use 16:9 for landscape or 9:16 for portrait.
Leave out text that isn’t part of the core app, because it “can get cut off on Play homepages on certain screen sizes.”

Tablet captures are rarely too tall; the issue is the opposite. Many Android tablets have 16:10 screens, so a native capture such as 2560 × 1600 passes the 2:1 rule easily but isn’t the 16:9 shape Google asks for. The generator offers 16:10 sizes under “More sizes” for that reason, and labels them as not counting toward featuring. Its default tablet and Chromebook sizes are 16:9, starting at 1920 × 1080.

The 7,680 px figure is worth a note. The general requirements cap every screenshot at 3,840 px, and Google doesn’t say whether the large-screen number overrides that. The generator stays at or below 3,840 px, which satisfies both.

Because of the cut-off warning, captions on tablet and Chromebook screenshots are riskier than on phones. If you do add them, keep them short and away from the edges.

A quick decision guide

Your situation	Best fix
Top and bottom of the screen are just status bar and empty space	Crop to 1080 × 1920
Important UI at both ends of the screen	Compose onto a 1080 × 1920 canvas
You need something uploaded today, design later	Pad to 9:16 on a plain background
A game	16:9 or 9:16 at 1920 × 1080 / 1080 × 1920, showing gameplay, at least 3
Tablet or Chromebook	16:9, 1920 × 1080 or larger, little or no added text

Whatever you pick, aim for four phone screenshots at 1080 × 1920 from the start. It’s the same work as two, and it covers the featuring rule.

The rest of the listing

Screenshots aren’t the only asset with a strict shape. The feature graphic must be exactly 1024 × 500 with no alpha channel; the Play Feature Graphic Generator exports it at that size and runs the same promotional-word checks. If your listing is ready but the Production button is still greyed out, the cause is probably the 12 testers, 14 days closed-testing rule for new personal accounts. And before you submit, the Google Play publishing checklist walks through the Data safety form, content rating and everything else Play Console asks for.