Google Play Screenshots: 10 Design Tips That Follow the Rules

Good Google Play screenshots show real app UI in the first three frames, keep any tagline to 20% of the image or less, use a 9:16 portrait or 16:9 landscape canvas of at least 1080 px, and leave out rankings, prices and calls to action. Do those four things and you're already ahead of a lot of Android listings.

Google Play's rules are not the same as Apple's. A design that works on the App Store can still miss Google's best practices. Below are 10 practical tips, all based on Google's own Play Console Help pages, plus a quick spec table and a pre-upload checklist.

What are Google Play screenshots?

Google Play screenshots are the 2–8 images per device type that appear on your store listing and in some Play discovery surfaces, showing users what your app looks like before they install it. Next to your icon and feature graphic, they are the main visual pitch for an Android app.

All the rules in this article come from Google's Add preview assets to showcase your app page in the Play Console Help Center. Google updates that page from time to time, so check it again before a big launch.

What is the right Google Play screenshot size?

Each Google Play screenshot must be a JPEG or 24-bit PNG with no alpha channel, between 320 px and 3,840 px on each side, and the long side can't be more than twice the short side. Those are the minimums for publishing. Promotion and large-screen surfaces ask for more, as the table shows.

Tip 1: Design at 1080 × 1920 px from the start. That size meets the promotion requirement, stays well inside the 3,840 px cap, and fits the 2:1 ratio rule. If you also need Apple sizes, our App Store screenshot sizes guide lists every iPhone and iPad spec.

Tip 2: Export without transparency. A PNG with an alpha channel will be rejected. Use a solid or gradient background and export as JPEG or as a flattened PNG.

What should go in the first three screenshots?

Google asks developers to "prioritize UI in the first three screenshots as much as possible," so your first three frames should show real, core app screens, not a logo splash or a wall of text. These are the frames most people see without scrolling.

Tip 3: Lead with the job your app does. Order the first three frames like this:

1. Frame 1: the core screen, meaning the one thing people install the app for (the map, the editor, the workout timer).
2. Frame 2: the main differentiator, the feature competitors don't have.
3. Frame 3: proof it's easy, such as a clean onboarding step or a finished result.

Tip 4: Split layouts are allowed, so use them carefully. Google explicitly allows stylized layouts where the UI flows across several images, which is the panoramic look. Make sure each frame still makes sense on its own, because a user may only see one or two at a time.

How much text can you put on Google Play screenshots?

Taglines should not take up more than 20% of the image, and Google recommends using them only when they're needed. On a 1080 × 1920 px canvas, that's a band of about 384 px tall for all text combined.

Tip 5: One short line, big type. Write a headline of 3–6 words that names a benefit ("Plan meals in 5 minutes"), and set it large enough to read at thumbnail size. Google warns against small text and busy backgrounds behind text. For copy ideas, see our screenshot caption tips. They were written for the App Store, but most of them carry over.

Tip 6: Avoid the words Google flags. The Play Console Help page lists these as things to avoid in screenshots:

• Ranking or award claims such as "Best," "#1" or "Top"
• Testimonials, prices and promotional words like "Sale" or "Free for a limited time"
• Calls to action such as "Download now" or "Install today"
• Time-sensitive content that will go stale quickly
• Third-party trademarked characters or logos you don't have permission to use

Should Google Play screenshots use device frames?

Google's best practices recommend avoiding device imagery in Google Play screenshots, because it "can become obsolete quickly or alienate some users." For Wear OS, frameless screenshots are a requirement. This is the biggest difference from typical App Store design, so it's worth planning for.

For phone screenshots, this is listed as a best practice and not a hard publishing requirement. Still, a frameless, full-bleed UI is the safest default for Google Play, and it's the only option for Wear OS apps and watch faces. Where device mockups do help an Android app:

• Outside the store: your website hero, Product Hunt gallery, press kit, social posts and pitch decks, where a 3D phone helps people see the context.
• On the App Store: if you ship on iOS too, framed screenshots are common there. See when to use device mockups for the trade-offs.
• As an experiment: if you want to try a framed version on Google Play anyway, test it against a frameless one with real traffic instead of guessing (see the testing section below).

Tip 7: Keep one source design, export two styles. Build each screen once, then export a frameless version for Google Play and a mockup version for the App Store and your marketing. You get one consistent visual identity without breaking either store's conventions.

How do you make Android app screenshots look polished?

Polished Android app screenshots come from clean source captures: a tidy status bar, realistic sample data, and sharp images at the right proportions. Google's guidance names each of these.

Tip 8: Clean the status bar. Google recommends hiding notifications and carrier names and showing full battery, Wi-Fi and cell signal icons. Android's demo mode in developer settings, or the Android emulator, makes this easy to do consistently.

Tip 9: Use color that stands out from the store. For the feature graphic, Google warns that pure white, black or dark gray can blend into Google Play's background. The same logic is a good rule of thumb for screenshot backgrounds. Pick a brand color or a gradient with strong contrast against your headline, and avoid stretched, compressed, blurry or pixelated captures.

Two more things Google mentions that people often skip:

• Localize the text. Translate taglines and overlays for each market you target, not just the description.
• Write alt text. Play Console lets you add alt text to screenshots. Keep it to 140 characters or less and describe what the screen shows, without starting with "image of."

How do you A/B test Google Play screenshots?

Google Play Console's store listing experiments let you test up to 2 screenshot variants against your current listing on real traffic. This is the honest way to settle debates like framed vs. frameless or light vs. dark backgrounds.

Tip 10: Test one change at a time. According to Google's Run A/B tests on your store listing page, a default graphics experiment can include variants of your icon, feature graphic and screenshots. Each app can run one default graphics experiment or up to five localized experiments at once, and experiments stop automatically after 6 months. Change a single variable per test, such as frame 1 or the background color, so you know what caused the difference.

Where mockiso fits in your Android workflow

Since Google discourages device imagery in Play screenshots, use mockiso for everything around the store listing: your landing page, launch posts and the iOS version of your screenshots. A typical flow:

1. Create a free account and start a new project.
2. Pick an Android device such as the Pixel 9 Pro, Galaxy S24 Ultra or Galaxy Z Fold7 (see all devices).
3. Paste your cleaned-up capture with Ctrl/Cmd+V, then choose an angle preset like hero left or float.
4. Set a gradient or one of the 70 backdrop templates, add an optional headline and subline, and use the duo or trio layout for consecutive screens.
5. Export PNG, JPEG or WebP using a social or store canvas preset, or download a ZIP of all angles.

The Free plan includes 1× export with a watermark. Pro adds 2× export up to 8K and batch ZIP export. Check pricing for current limits.

Key takeaways

• Google Play screenshots must be JPEG or 24-bit PNG without alpha, 320–3,840 px, with the long side no more than twice the short side.
• For promotion eligibility, apps need at least 4 screenshots at 1080 × 1920 px (9:16) or 1920 × 1080 px (16:9).
• Put real core UI in the first three screenshots and keep taglines to 20% of the image or less.
• Avoid rankings, prices, calls to action and device imagery. Wear OS screenshots must have no device frames.
• Use Play Console store listing experiments to test up to 2 variants against your current screenshots.

Ship screenshots that work in both stores

Google Play rewards clear, honest, UI-first screenshots. Build frameless Play assets first, then reuse the same screens for 3D mockups on your website, launch posts and App Store listing. Start your free 24-hour Pro trial on mockiso, no card required, and turn your Android screens into marketing visuals in a few minutes.