Google Play Store Screenshots: Sizes, Requirements, and What Gets Rejected

Phone screenshots:

• •Minimum: 320px on the shortest side
• •Maximum: 3840px on the longest side
• •Aspect ratio: 16:9 or 9:16 (portrait/landscape)
• •Format: PNG or JPEG
• •2-8 screenshots required

Tablet screenshots (optional but recommended):

• •Same size requirements as phone
• •2-8 screenshots
• •Shown to users on tablets

Feature graphic (required for featured placement):

• •Size: 1024 x 500px
• •Format: PNG or JPEG
• •No transparency
• •Appears at the top of your store listing

Icon:

• •Size: 512 x 512px
• •Format: PNG
• •32-bit PNG with alpha channel (transparency allowed, unlike App Store)

Key difference from App Store: Google Play doesn't require specific device sizes. You provide one set of screenshots and Google scales them automatically. This is simpler but means you should design at a high resolution and let Google scale down.

Allowed:

• •Real app UI screenshots
• •Device frames (any device, not restricted to Google devices — unlike Apple's App Store)
• •Captions and text overlays (informational, not promotional)
• •Android device frames (Samsung, Google Pixel, etc.)
• •Landscape and portrait orientations

Not allowed:

• •Promotional or marketing language ('Download now!', 'Best app ever!')
• •Pricing information ('Only $2.99!')
• •Misleading content (screenshots that don't reflect the actual app)
• •Inappropriate content (violence, adult content, etc.)
• •Third-party trademarks or logos without permission
• •User data or personal information visible
• •Excessive branding or watermarks
• •Screenshots from other platforms (don't show iOS screenshots for an Android app)

Google's policies are generally less strict than Apple's, but they still reject screenshots that violate content policies. The most common rejection reasons are promotional text and misleading content.

1. 1.Device frames: App Store requires Apple device frames only. Google Play allows any device frames (Samsung, Google Pixel, or no frame). Use Android device frames for Play Store screenshots.

1. 2.Screenshot sizes: App Store requires exact sizes per device family (6.7", 6.5", 6.1", 5.5"). Google Play accepts a range (320-3840px) and scales automatically. This makes Play Store simpler but means you should design at high resolution.

1. 3.Number of screenshots: App Store allows 3-10. Google Play requires 2-8. Use the maximum (8) for both stores.

1. 4.Feature graphic: Google Play has a feature graphic (1024x500px) that appears at the top of the listing. App Store has no equivalent. The feature graphic is your 'hero' image — make it compelling.

1. 5.Icon transparency: App Store icons must be opaque (no transparency). Google Play icons allow transparency (32-bit PNG with alpha). This gives you more design flexibility on Android.

1. 6.A/B testing: Both stores offer A/B testing (Apple's Product Page Optimization and Google's Store Listing Experiments). Google's tool is more mature and allows more variants.

1. 7.Search result display: App Store shows a thumbnail of your first screenshot in search results. Google Play shows your icon and first screenshot. Both autoplay preview videos if available.

1. 8.Localization: Both stores support localization, but Google Play's localization is more granular (you can customize screenshots per locale, not just per language).

1. 1.Wrong dimensions: screenshots outside the 320-3840px range. Fix: resize your screenshots to be within range.

1. 2.Promotional text: marketing language in screenshots ('Best app!', 'Download now!'). Fix: use informational captions only.

1. 3.Pricing information: showing prices in screenshots. Fix: remove all pricing text.

1. 4.Misleading screenshots: screenshots that don't match the actual app. Fix: capture real app screens.

1. 5.iOS screenshots: showing iOS UI elements (iOS navigation bars, iOS keyboards) in an Android app's screenshots. Fix: capture screenshots on Android.

1. 6.Inappropriate content: violence, adult content, or content violating Google's policies. Fix: ensure all screenshots are appropriate for all audiences.

1. 7.Third-party logos: showing brands or logos you don't have permission to use. Fix: remove unlicensed third-party content.

1. 8.Excessive watermarks: large watermarks that distract from the app. Fix: remove or minimize watermarks.

1. 9.Personal information: user names, emails, or photos visible in screenshots. Fix: use demo data, not real user data.

1. 10.Low quality: blurry, pixelated, or poorly cropped screenshots. Fix: capture at high resolution and export as PNG.

Best practices for feature graphics:

• •Show your app's core value visually: the feature graphic should convey what your app does at a glance
• •Use bold, high-contrast design: it's viewed at various sizes, from phone to desktop
• •Include your app name or logo: users should immediately know which app this is
• •No small text: text becomes unreadable at small sizes. Use large, bold text only.
• •No device frames: the feature graphic is a banner, not a screenshot. Don't put a phone frame in it.
• •Match your app's branding: use the same colors and style as your app and screenshots
• •Test on different devices: the feature graphic is cropped differently on different screen sizes. Keep important elements in the center.
• •No transparency: use a solid or gradient background

The feature graphic is required if you want to be considered for featuring on Google Play. Even if you're not aiming for featuring, a good feature graphic improves your listing's visual appeal and conversion rate.

1. 1.Design at high resolution: create screenshots at 1080x1920px (or higher) and let Google scale down. This ensures quality on all devices.

1. 2.Use Android device frames: Google Pixel or Samsung Galaxy frames are appropriate. Don't use iPhone frames (users will notice).

1. 3.Write clear, benefit-driven captions: like App Store, captions should be informational and keyword-relevant. Google also indexes text in screenshots for Play Store search.

1. 4.Use all 8 screenshot slots: more screenshots = more opportunities to showcase features and target keywords.

1. 5.A/B test with Store Listing Experiments: Google's tool lets you test screenshot sets, icons, and feature graphics. Test one variable at a time.

1. 6.Localize screenshots: Google Play lets you customize screenshots per locale. Localized screenshots improve conversion in non-English markets.

1. 7.Create a compelling feature graphic: this is the first thing users see. Make it visually striking and clear.

1. 8.Show real app UI: Google rejects misleading screenshots. Show actual app screens, not mockups.

1. 9.Consistent branding: use the same colors, fonts, and style across your icon, feature graphic, and screenshots. Consistency builds trust.

1. 10.Add a preview video (optional): Google Play supports app preview videos (YouTube-hosted). Videos can increase conversion by 15-35%, similar to App Store.

1. 1.Design once, adapt for each: create your base screenshot design once, then adapt for each store's requirements.

1. 2.Use the right device frames: Apple device frames for App Store, Android device frames for Google Play.

1. 3.Export at correct sizes: App Store needs exact sizes (6.7", 6.5", 6.1", 5.5"). Google Play accepts a range (design at 1080x1920px or higher).

1. 4.Create separate feature graphics: Google Play needs a 1024x500px feature graphic. App Store doesn't have this.

1. 5.Follow each store's content rules: App Store is stricter (no promotional text, Apple devices only). Google Play is more flexible but still rejects misleading content.

1. 6.Localize for both: both stores support localization. Prioritize the same Tier-1 markets (Japanese, German, French, Korean, Spanish, Portuguese).

1. 7.A/B test on both: use Apple's Product Page Optimization and Google's Store Listing Experiments. Find what works on each platform — results may differ.

The most efficient workflow: use a screenshot generator that exports for both stores. Design once, export at App Store sizes and Google Play sizes, with the appropriate device frames for each.