1. Why Play Store Screenshot Sizes Matter
Store listing screenshots are your app's primary sales tool. Research shows that professionally designed screenshots with marketing text and device frames increase conversion rates by up to 35% compared to raw app captures. Getting the dimensions wrong results in stretched, cropped, or blurry images that instantly erode user trust.
While the developer console is more flexible than other marketplaces in terms of accepted dimensions, following the recommended sizes ensures your screenshots display optimally across all handheld devices, large tablets, and web listings without awkward letterboxing.
2. Phone Screenshot Sizes
Developer consoles accept a range of sizes for phone screenshots, but the recommended dimensions below produce the crispest results across all device form factors and web viewports.
| Aspect Ratio | Recommended Size | Min Size | Max Size |
|---|---|---|---|
| 9:16 Portrait (Recommended) | 1080 × 1920 px | 320 × 569 px | 3840 × 6827 px |
| 16:9 Landscape | 1920 × 1080 px | 569 × 320 px | 6827 × 3840 px |
While developer consoles accept custom dimension ranges between 320px and 3840px, 1080 × 1920 px (9:16 portrait) is the universal standard. It renders crisply across mobile search cards, web listings, and cross-channel marketing campaigns. ReinShots Studio includes this as a one-click export preset.
3. Tablet & Large Display Form Factors
Large display screenshots are shown separately when users browse from tablet hardware. If you do not provide dedicated tablet screenshots, the marketplace will fall back to showing your phone screenshots, which stretch awkwardly on wider aspect ratios.
| Display Class | Recommended Size | Min Size | Form Factor Context |
|---|---|---|---|
| 7" Tablet | 1200 × 1920 px | 320 × 480 px | Compact handheld tablet displays (16:10) |
| 10" Tablet | 1800 × 2560 px | 320 × 480 px | Flagship large tablet displays (16:10) |
4. Feature Graphic (Required)
The feature graphic is the large banner image at the top of your store listing. It is also used in editorial highlights, promotional placements, and app discovery feeds. This graphic is mandatory for all published applications.
| Asset | Exact Size | Format | Key Requirement |
|---|---|---|---|
| Feature Graphic | 1024 × 500 px | PNG (24-bit, no alpha) or JPEG | Must not contain transparency |
Store interfaces crop the feature graphic differently depending on device context (mobile portrait, tablet carousel, desktop browser, or TV). Keep critical branding, logos, and value propositions within the center-safe area (approximately 900 × 400 px centered) to ensure vital details are never truncated.
5. Full Graphic Asset Specification Matrix
| Asset | Dimensions | Aspect Ratio | Required? |
|---|---|---|---|
| App Icon (Hi-res) | 512 × 512 px | 1:1 Square | Required |
| Feature Graphic | 1024 × 500 px | ~2.05:1 | Required |
| Phone Screenshots | 1080 × 1920 px | 9:16 Portrait | Required (min 2) |
| 7" Tablet Screenshots | 1200 × 1920 px | 16:10 | Optional / Strongly Advised |
| 10" Tablet Screenshots | 1800 × 2560 px | 16:10 | Optional / Strongly Advised |
| Promo Video | YouTube URL | 16:9 Landscape | Optional |
| TV Banner | 1280 × 720 px | 16:9 Landscape | For TV listings |
| Wearable Screenshots | 384 × 384 px | 1:1 Circular / Square | For wearable listings |
| Desktop / Chromebook | 1920 × 1080 px | 16:9 Landscape | For desktop runtime |
6. Safe Zone Margins & UI Overlays
Modern mobile operating systems utilize rounded corners, punch-hole cameras, and floating gesture navigation bars. When presenting mockups inside device frames or as edge-to-edge graphics, adhering to safe margins is critical to avoid visual clutter.
| Zone | Margin Guideline | Rationale |
|---|---|---|
| Top Safe Margin | Leave 120 px clear at top | Prevents status bar icons, battery indicators, or camera cutouts from overlapping headline text. |
| Bottom Safe Margin | Leave 90 px clear at bottom | Prevents system gesture navigation indicators and store UI overlays from obscuring call-to-action buttons. |
| Horizontal Padding | Minimum 48 px left and right | Ensures high legibility when browsing listings in reduced carousel viewports on smaller screens. |
7. Store Listing Submission Rules
- Minimum 2 screenshots per device category, maximum 8 screenshots per form factor.
- Aspect ratio constraint: Must be either 16:9 or 9:16. Custom arbitrary ratios will trigger automated upload errors.
- Strictly no transparency: 24-bit PNG files must not contain an alpha channel; JPEG files must have maximum quality compression without visible artifacts.
- Authentic representation: Screenshots must accurately reflect real app gameplay or utility. Deceptive mockups violate store listing policies and risk removal.
- Concise benefit text: Store review teams encourage concise overlay headlines that explain user value rather than crowded wall-of-text feature lists.
- Localization per storefront: Providing translated screenshots for target languages significantly boosts international conversion rates.
8. Console Rejection Prevention Checklist
Review this checklist before uploading your final package to the submission console to avoid costly launch delays:
| Checklist Item | Requirement | Common Failure Cause | Prevention |
|---|---|---|---|
| Aspect Ratio | Exact 9:16 or 16:9 | Exporting raw desktop captures with random browser window widths. | Use standard 1080 × 1920 px presets in ReinShots. |
| Alpha Channel | No PNG transparency | Exporting PNG with transparent background outside rounded bezels. | Fill mockup background with solid color or rich gradient. |
| Feature Graphic Dimensions | Exact 1024 × 500 px | Uploading 1000 × 500 or 1024 × 512 px images. | Ensure exact pixel dimension match before upload. |
| Minimum Resolution | Longest side at least 320 px | Uploading heavily downscaled thumbnail assets. | Keep assets at high resolution (1080px wide minimum). |
| Accurate UI Depiction | Shows actual app UI | Uploading only marketing graphics without real app interfaces. | Feature authentic app screenshots inside every mockup card. |
9. Platform Dimension Differences
If you are shipping your application across multiple mobile marketplaces simultaneously, here are the critical technical differences to plan for:
| Attribute | Major Marketplace A | Major Marketplace B |
|---|---|---|
| Max Screenshots | 10 per display class | 8 per device type |
| Dimension Enforcement | Strict pixel dimensions required | Flexible range with aspect ratio constraint |
| Feature Graphic | Not used in storefront | Mandatory banner asset (1024 × 500 px) |
| Preview Video Format | Direct video upload (.mp4 / .mov) | YouTube video link URL |
| Primary Display Classes | 6.9", 6.5", 13" tablet | Phone, 7" Tablet, 10" Tablet |
Cross-platform developers can design their presentation once in ReinShots Studio and export compliant assets across all required formats in a single click.
10. Frequently Asked Questions
What DPI should mobile store screenshots be?
Store review consoles do not enforce a specific metadata DPI tag — only exact pixel dimensions matter. However, exporting at high density (typically matching 480 DPI / xxhdpi standards) ensures that text and interface elements render crisply on ultra-high-resolution OLED displays.
Can I use the same screenshots for phone and tablet listings?
While console systems may technically permit reusing phone assets across tablet slots, doing so results in awkward letterboxing and lower conversion rates. Tablet shoppers expect native interface layouts designed for larger screens.
Are promo preview videos required?
No, promotional preview videos are optional. If provided, they are linked via landscape video URLs and appear before your screenshot gallery. Listings featuring high-quality short video demonstrations often see improved conversion rates.
What file formats are accepted for store screenshots?
Standard developer consoles accept 24-bit PNG files (without alpha transparency) or high-quality JPEG files. For graphics with sharp text and device frames, PNG is strongly recommended to eliminate compression artifacts.
How many screenshots should I upload?
While consoles require a minimum of 2 and permit up to 8 per device class, publishing 4 to 6 focused, story-driven screenshots is the ideal sweet spot for conversion without overwhelming prospective users.
Create Store Screenshots in Minutes
Design stunning mobile mockups with panoramic continuous backgrounds, modern device frames, and instant multi-size export — completely in your browser.
Open ReinShots Studio Free →