Technical Requirements
- Minimum 2 screenshots — Required for submission. Maximum 8 per device type
- File format — JPEG or 24-bit PNG (no alpha/transparency)
- File size — Maximum 8 MB per screenshot
- Aspect ratio — 16:9 or 9:16 (landscape or portrait)
- No device frames required — But they can make screenshots look more professional
- No excessive text — Screenshots should primarily show the app, not marketing text
Use each slot deliberately
Recommended Dimensions
| Device Type | Minimum | Recommended | Maximum |
|---|---|---|---|
| Phone | 320 x 320 px | 1080 x 1920 px | 3840 x 3840 px |
| 7" Tablet | 320 x 320 px | 1200 x 1920 px | 3840 x 3840 px |
| 10" Tablet | 320 x 320 px | 1600 x 2560 px | 3840 x 3840 px |
| Chromebook | 320 x 320 px | 1920 x 1080 px | 3840 x 3840 px |
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 feature graphic is a 1024 x 500 promotional asset used on supported Google Play surfaces. Prepare it from the current asset specification 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 includes screenshot localization for all target markets.
Common Screenshot Rejections
- 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
Evidence 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