Yannick
Feature graphic composition
Keep the focal point safe across Play surfaces
Center the promise
Keep the essential subject and message away from cropped edges.
Reduce fine detail
Design for small placements, not only the full 1024 × 500 file.
Localize the asset
Adapt text and imagery for markets that matter to the launch.
Template ideas
Product UI plus one benefit
App icon plus visual world
Before and after outcome
Seasonal launch variation
Category-specific proof
Minimal brand banner
What Google expects from preview assets
Google describes feature graphics, screenshots, short descriptions, and videos as preview assets that can be used to highlight and promote your app. Requirements are mandatory, while quality guidelines can affect whether assets are eligible for more promotional surfaces.
Examples that usually work
- A clean app UI crop with one clear benefit-led visual hierarchy.
- An icon-led banner for simple utilities where brand recognition matters.
- A social-proof or outcome layout for apps with visible results.
- A localized version where the same composition uses market-specific copy.
- A seasonal variant for campaigns, events, or major product moments.
How to keep templates conversion-safe
Keep claims honest, avoid crowded text, and make sure the graphic matches the rest of the listing. Google recommends localized screenshots and videos for supported languages, and the same thinking applies to your feature graphic when a market is important.
The non-negotiable export rules
Upload a 1024 × 500 JPEG or 24-bit PNG without alpha. Keep the focal point near the center because Google may display the graphic at different crops and sizes. Avoid tiny detail that disappears in recommendation cards, and preview the asset at thumbnail size before upload.
Google also advises against icon-like branding that duplicates the app icon, store badges, obsolete device imagery, and promotional claims about rankings, prices, or calls to action. Let the creative explain the product rather than imitate store UI.
