Technical Requirements
Google's official preview-asset specification defines the current count, format, file-size, dimension, and aspect-ratio constraints for each asset and device type. It was checked on August 5, 2026; recheck it before every export because Console requirements can change.
- Asset slot: select the exact phone, tablet, Chromebook, TV, Wear OS, or other form factor used by the listing.
- Count and format: copy the current permitted range and accepted file types from the official specification into the release checklist.
- Pixel and file limits: validate the exported file, not only the design canvas.
- Aspect ratio: use a ratio allowed for that asset slot and preview its crop in Console.
- Representative UI: show the shipped app state and do not imply unavailable features, awards, prices, or offers.
- Text and framing: keep the app experience legible; any caption or device treatment must remain accurate after localization and cropping.
Use each slot deliberately
Export Verification Checklist
| Check | Release evidence | Failure to catch |
|---|---|---|
| Specification | Official source URL, check date, slot, count, format, size, dimensions, and ratio | A reusable preset that no longer meets the current requirement |
| Product state | Build version and path used to capture each screen | Old UI, mock features, hidden permissions, or a different app |
| Locale | Language, market, translated caption, and in-app language | Mixed-language or market-inaccurate claims |
| Preview | Console preview for every target form factor and orientation | Crop, unreadable text, repeated screens, or weak first asset |
Design Best Practices
1. Show, Do Not Tell
Screenshots should primarily show your app in action. Marketing text should complement the visuals, not dominate them. Google's policy prohibits screenshots that are primarily promotional banners.
2. First Two Screenshots Are Critical
The first visible assets carry the most decision weight because users may not inspect the full gallery. Put the clearest product state and primary value first, then verify the order in the current listing preview.
3. Use Consistent Design
All screenshots should share a consistent color scheme, typography, and layout style. This creates a professional, cohesive impression.
4. Add Brief Captions
Short, benefit-focused captions help users understand each screen quickly. Examples: "Track your progress", "Connect with friends", "Customize your experience".
5. Highlight Unique Features
Show what makes your app different from competitors. If you have a unique dark mode, a special algorithm, or exclusive content, feature it prominently.
A/B Test
Feature Graphic
The current official specification lists the feature graphic as a 1024 x 500 promotional asset for supported Google Play surfaces. Verify that exact value in the preview-asset requirements before exporting and preview how cropping affects the design.
- Dimensions: 1024 x 500 pixels
- Format: JPEG or 24-bit PNG
- Design: Should work with and without text overlay (Google may crop it)
- Safe composition: Keep essential content away from crop-sensitive edges and verify every preview state
Localized Screenshots
If the app targets multiple languages, localize screenshots when the screen content, value proposition, or market context changes. Measure each locale separately rather than applying a universal conversion-lift estimate.
- Translate all text captions on screenshots
- Show the app in the target language
- Consider cultural differences in design preferences
- Upload screenshots under the appropriate language tab in Play Console
Our app localization service can include screenshot localization for the languages, assets, device layouts, and reviewer workflow named in the written scope.
Listing Integrity Checks
These checks are not a frequency ranking. Compare each asset with the current build, listing, metadata policy, and official preview-asset rules:
- Misleading content — Screenshots showing features the app does not actually have
- Excessive promotional text — Screenshots that are mostly text with small app previews
- Competitor references — Mentioning or comparing to competitor apps in screenshots
- Fake reviews — Showing fake review scores or testimonials in screenshots
- Awards or rankings — Claiming "#1 App" or showing unverified awards
- Price claims — Showing prices that do not match the actual listing
Listing integrity
Creative evidence
Treat screenshots as product evidence, not decoration
The strongest screenshot set makes the product promise legible, follows current asset rules, fits each device layout, and avoids claims the build cannot prove.
Specification
Check current dimensions, formats, device requirements, text limits, and preview behavior before export.
Message order
Lead with the user task and proof, then show differentiators and the next action.
QA
Review localization, clipping, contrast, device framing, and claim accuracy in the actual listing context.
Next step: Provide the current screenshots, target locales, and the product flows they are meant to prove.
Discuss listing and creative scopeEvidence standard
Primary references
These first-party sources support the changeable platform requirements in this guide. Your current Play Console notice remains authoritative for account-specific steps.
Review your next Play Console step
Tell us what the account shows, where the release is blocked, and what has already been submitted. We will scope the work around the evidence in your case.
Discuss Your Release