ScreenShipper
Blog
Google Play

Google Play Screenshot Best Practices That Follow Google's Rules

Google Play screenshot best practices based on Google's guidance, with real UI first, short taglines, no ranking claims, the right devices and tablet screens.

ScreenShipper team · · 6 min read

TL;DR: Lead with real app UI in your first three screenshots, keep taglines short (Google suggests no more than 20% of the image), and leave out rankings, awards, testimonials, prices and calls to action. Skip device imagery or use Android devices only, add tablet screenshots, write alt text, design the feature graphic with the set, and test changes with store listing experiments.

What Google Recommends for Play Screenshots

Google's preview asset guidance is more specific than Apple's, and some habits from App Store design don't carry over. Here is the short version and what it means for your layout:

Google's guidanceWhat it means in practice
Show the actual app or game experienceUse real captured UI, not mockups of features you don't have
Prioritize UI in the first three screenshotsHeadlines are fine, but the screen should dominate early
Keep taglines to no more than 20% of the imageOne short line, not a paragraph
Avoid performance, ranking, testimonials, accolades and awardsNo "#1", laurels, star rows or review quotes
Avoid calls to actionNo "Download now" or "Try it today"
Avoid device imagery and people tapping the deviceFrameless screens are the safest default
Avoid Google Play or other store badgesKeep store logos out of the image
Add alt text of 140 characters or lessDescribe the key element of each screenshot

Google labels most of these as strong recommendations rather than upload checks. The Metadata policy behind them is enforced, though, so treat misleading claims and imagery as hard rules.

Lead With Real UI in the First Three Screenshots

Google specifically asks you to prioritize UI in the first three screenshots. Use them for the core reason someone installs your app:

  1. Screenshot 1: the main screen that shows what the app does, with a three to six word benefit headline.
  2. Screenshot 2: the feature people install for.
  3. Screenshot 3: the result, such as a finished plan, an edited photo or a progress dashboard.
  4. Screenshots 4 to 8: supporting features, personalization, sync and settings worth bragging about.

Write headlines as benefits ("Plan meals in minutes") rather than feature names ("Meal planner"), and keep them inside the 20% guidance. The caption guide has examples that are short enough for Play.

Words and Claims to Keep Out

Google's Metadata policy bans text or images in the app title, icon and developer name that indicate store performance or ranking, price or promotions, or Google Play programs. The preview asset guidance asks for the same restraint in screenshots and the feature graphic.

AvoidExamplesUse instead
Ranking and performance"#1", "Top app", "Best", "Million downloads"A concrete benefit, such as "Track every workout"
Awards and accoladesLaurels, "App of the year"Mention real awards in the full description
Testimonials and ratingsStar rows, review quotesShow the feature reviewers praise
Price and promotions"Free", "50% off", "Sale"Explain what's included in the description
Calls to action"Download now", "Install today"Let the install button do that job
Google Play programs"Editor's choice", "New"Leave them out entirely

Social proof screens that are common on the App Store don't carry over; see social proof in screenshots for the differences between the stores.

Devices, Frames and Hands

Google recommends avoiding device imagery in screenshots because it can become obsolete quickly or alienate some users, and it asks you not to show people interacting with the device, such as fingers tapping the screen. In practice:

  • Go frameless by default. Rounded-corner screens with a soft shadow look finished without a bezel.
  • Never show an iPhone. If you use a frame at all, use an Android device that matches the screenshot.
  • Reserve devices for when the hardware is the message, for example a layout that only makes sense on a foldable.
  • Keep badges and logos out. No Google Play badge, no other store badges and no stock hands.

Design for Phones, Tablets and Large Screens

Large-screen screenshots have their own slots in Play Console, and Google recommends at least 4 of them for visibility on tablets and Chromebooks. Two rules matter most:

  1. Show the real large-screen layout. A stretched phone UI on a tablet canvas tells shoppers your app isn't built for their device.
  2. Keep the same visual system. Use the same colors, type and headline order on phone and tablet so the listing feels like one product.

Watch the aspect ratio on phones too. Raw captures from tall modern phones exceed Play's 2:1 limit; the Google Play screenshot requirements explain the fix.

Make the Feature Graphic and Screenshots Work as a Set

The feature graphic (1024 × 500) is the cover of your promo video and appears in large-format placements, often right next to your screenshots. Design it from the same palette and type, but don't repeat your icon as the main element: Google warns that prominent branding similar to the icon causes duplication. Keep key elements near the center, away from the edges, and leave room for the play button if you add a video. See feature graphic examples for eight layouts that work, and the feature graphic size guide for export specs.

Localize, Add Alt Text and Test

  • Localize headlines and UI for your biggest languages. A translated listing with English-only screenshots looks unfinished.
  • Write alt text for every screenshot. Keep it under 140 characters, describe the key element, and don't start with "Image of" or "Photo of".
  • Test one change at a time. Store listing experiments let you compare variants of your screenshots, feature graphic and icon against your current listing. Good first tests are the first screenshot's headline, frameless versus framed, and screenshot order.

For every other part of your page, from the short description to the category, see the Google Play store listing guide.

Frequently Asked Questions

Can I put text on Google Play screenshots?

Yes. Google suggests keeping taglines to no more than 20% of the image and avoiding small, crowded text, so one short headline per screenshot works well.

Can I show my star rating in Google Play screenshots?

Google's preview asset guidance asks you to avoid content that suggests ratings, testimonials, rankings or awards. Your live rating already appears on the listing, so use the space for UI.

Should Google Play screenshots be portrait or landscape?

Portrait suits most apps; landscape suits games and video apps that are held sideways. Both are accepted as long as the long side stays within twice the short side.

Do I need different screenshots for Google Play and the App Store?

You can share the design, but swap iPhone frames for frameless screens, remove social proof screens and export Play-valid sizes. Current App Store iPhone sizes are taller than Play's 2:1 limit.

Sources

Google Play screenshots and feature graphic, done together

One design exports phone and tablet screenshots plus a matching 1024 × 500 feature graphic, with no alpha channel.

All guides