Fitting a 20:9 phone screenshot into Play’s 9:16 rule.

Take a screenshot on a Pixel 8 and you get a 1080×2400 PNG. Drag it into the Play Console and it won’t qualify for the places Google shows screenshots outside your listing, and it fails the upload rule outright. Phones got taller over the last few years and Play’s frame didn’t move with them. Here is how to get a tall capture into the shape Google asks for without squashing it or cutting off the part that matters.

Two rules, and a 20:9 capture breaks both

Google’s preview assets page has two layers of screenshot rules, and it’s worth keeping them apart.

The publishing requirement. Each screenshot is a JPEG or 24-bit PNG with no alpha, between 320px and 3840px on each side, and the long side “can’t be more than twice as long as the minimum dimension”. That is a 2:1 ceiling. A 1080×2400 capture is 2.22:1, and a 1080×2340 capture from a Galaxy S24 is 2.17:1. Both are over the line before you’ve thought about design at all.

The eligibility rule. Separately, Google lists guidelines that it says “are a requirement” for your screenshots to appear in its screenshot-based recommendation formats. For apps, that means at least four screenshots at a minimum of 1080px, in 16:9 landscape (1920×1080 or larger) or 9:16 portrait (1080×1920 or larger). For games it’s at least three, all in one of those two shapes, showing actual gameplay.

Notice what the second rule asks for: 9:16, not “anything under 2:1”. A 1080×2160 image (exactly 2:1) passes the upload and still misses the recommendation formats. The shape that clears both is 9:16, and 1080×1920 is the smallest size of it that qualifies.

What missing the 9:16 rule costs you

Nothing visible, which is why it goes unnoticed. Google is explicit that ignoring the highly-recommended guidelines “will not impact your store listing page”. Your listing looks the same. What changes is everywhere else: Google says it “may result in changes to how your preview assets appear on Google Play or limit promotional opportunities.” The screenshot formats on Play’s home and recommendation surfaces simply don’t pick your app.

You don’t get an email about this. The upload succeeds (once you’re under 2:1), the console shows a green checkmark, and you never see the shelf you weren’t placed on. If your screenshots are anything other than 9:16 or 16:9 today, this is the cheapest discovery fix on your listing.

Option one: crop, and lose 480 pixels

The obvious move is to crop a 1080×2400 capture down to 1080×1920. That throws away 480 pixels of height, a fifth of the screen. Some of it is free to lose: Google’s own guidance asks for a tidy status bar anyway, and the gesture bar at the bottom adds nothing. But those two strips together are well short of 480 pixels on most phones, so the rest of the crop comes out of your UI.

Cropping works when the screen has dead space: a feed that scrolls, a settings list where the bottom rows don’t matter, a map. It fails on screens designed edge to edge, where the bottom navigation or the primary button sits in the last 300 pixels. Cropping the tab bar off a screenshot makes the app look unfinished.

If you do crop, crop from the top and bottom in proportion to what’s there, not evenly by default, and check each frame by eye. A crop that cuts a button in half is worse than a shorter screenshot.

Option two: place the screen on a 9:16 canvas

The better answer for most apps is to stop treating the capture as the screenshot. Make a 1080×1920 canvas and place the full 20:9 screen inside it, scaled down. Scaled to the full 1920 height, a 1080×2400 screen comes out at 864×1920, leaving 108 pixels of background on each side. Scale it to around 75% of the canvas height and you have room above for a headline.

This keeps every pixel of the UI, and it’s the standard composed-screenshot layout for good reason. Two limits from Google’s page shape how far you push it:

Headlines get 20%. “Taglines should not take up more than 20% of the image.” On a 1080×1920 canvas, a full-width text band can be at most 384 pixels tall. That’s comfortably enough for a short headline in two lines at a size that survives the thumbnail, and not enough for a paragraph, which is the point.

UI leads. Google allows stylized screenshots, including ones where UI spans several images, but asks that the actual interface comes first “in the first three screenshots.” Keep the panoramic and text-heavy frames for slot four onward.

One thing the page rules out: device imagery. Google asks you not to include devices in screenshots, so the screen sits on the background as a rounded rectangle, not inside a rendered phone. That suits the format anyway. A bezel takes width you’ve just worked to save.

The text checklist for each frame

Once there’s a headline on the canvas, Google’s copy rules for screenshots apply. Leave out anything that implies Play performance, ranking, testimonials, awards, or price and promotion. Its examples are “Best”, “#1”, “Top”, “New”, “Discount”, “Sale” and “Million Downloads”, and calls to action like “Download now”, “Install now”, “Play now” and “Try now”.

One oddity worth knowing: “Free” appears on Google’s list for the feature graphic but not for screenshots. We still leave it off. It reads as a price claim, it ages badly the day you add a paywall, and nothing on the screenshot list obliges you to spend the words on it.

Then the small things the page also asks for: a clean status bar (no carrier name or notifications, full battery, Wi-Fi and signal), no blurry, stretched or rotated images, no store badges, and alt text of 140 characters or less that doesn’t start with “photo of” or “image of”. The alt text is easy to skip, and it’s the only description a screen-reader user browsing your listing gets.

Tablets and Chromebooks use the same frame

Large-screen screenshots follow the same shapes: 16:9 landscape or 9:16 portrait, between 1,080 and 7,680px, with at least four of them. Google adds a warning specific to these: text that isn’t part of the app can get cut off on Play’s homepages at some screen sizes. So the headline band that works on the phone set is a liability here. Keep tablet frames close to pure UI, and if you must label them, keep the label short and well inside the edges.

If you already have a 9:16 phone layout, the tablet set is a second export, not a second design. Our iPad screenshots post covers the same problem from Apple’s side, for apps that were only ever built for a phone.

Exporting so the upload sticks

Export at exactly 1080×1920 (or a larger 9:16 size such as 1440×2560) as a JPEG or a 24-bit PNG. “No alpha” means the file must have no alpha channel at all, even a fully opaque one, and a design tool exporting RGBA PNGs by default is the most common reason a correctly sized screenshot still fails. The feature graphic post walks through that trap in detail; the fix is the same for screenshots.

ShotCanvas renders every Play slot from one design, headline band and all, and can publish the set straight to Google Play.