Skip to main content

Play Store

Google Play screenshot resource hub

Phone screenshot sizes, feature graphics, listing order, localization, and what to ship after your Play Store visuals are ready. Keep 1080×1920 phone screenshots separate from the 1024×500 feature graphic.

4 guides in this hub

Open Play Store generator

Screenshots are not feature graphics

Phone screenshots explain the app in the gallery at 1080×1920. A feature graphic is a separate wide 1024×500 asset used in Play surfaces that expect a banner. StoreShots does not generate 1024×500 feature graphics yet. Read Play Store feature graphic vs phone screenshots so your team does not crop a phone PNG and call it a feature graphic.

Make slide one earn the scroll

Use an outcome-focused headline and a legible production screen. Follow with the main action and differentiator, then add depth or proof only when each slide adds a new reason to install. Design for the phone carousel: readable as a thumbnail, with key copy away from crop edges.

Plan testing after creatives

Listing screenshots and closed testing are different workstreams. StoreShots creates listing assets. When you need real testers for Google Play closed testing, use TestMyApps, a related ClyroLabs product and not a StoreShots feature. Keep the CTAs separate; see closed testing after screenshots.

Check the final Play upload

Open every PNG, check text safe areas and current Google Play rules, and upload manually after review. StoreShots creates the files; it does not submit listings or run testing. Use the pre-submit checklist.

Localize after the first story works

Translate the benefit, not only the literal headline. Longer strings may need a shorter variant, a different line break, or a separate capture when the app itself is localized. Review each locale at phone scale before uploading to Play Console. Guide: localize App Store and Play Store screenshots.

Maintain a release checklist

For each Android release, confirm the production build, screenshot order, 1080×1920 dimensions, file format, feature-graphic status, and policy requirements. Keep manual Play upload and any closed-testing service as separate checklist steps. StoreShots does not submit the listing or guarantee approval.

Use one source of product truth

The best Play packs begin with the current Android build and a short audience description. Keep screenshots, listing copy, and release notes aligned so a shopper sees the same promise before install that the app delivers after install. Refresh after launch when the product changes using refresh Play screenshots.

Messaging and accessibility on Android

Play shoppers often see the first screenshot in a denser grid than iOS. Lead with a short outcome line, keep the device large enough to read primary UI, and avoid decorative chrome that eats the safe area. Never invent ratings or download numbers in the frame.

High-contrast headlines help more than decorative gradients. Avoid tiny legal text inside the frame and preview on light and dark system themes when captures include translucent UI. International teams should confirm translated headlines do not collide with gesture areas or rounded corners.

Workflow summary

  1. Capture production Android UI.

  2. Write the carousel story: outcome, action, differentiator, proof.

  3. Generate 1080×1920 slides in StoreShots.

  4. Create or update the 1024×500 feature graphic outside StoreShots for now.

  5. Localize if needed and phone-review every locale.

  6. Upload manually; schedule closed testing separately via TestMyApps if required.

Frequently asked questions

What Play screenshot size does StoreShots export?

Phone portraits at 1080×1920. Do not promise tablet packs unless the current generator documents them.

Does StoreShots make the 1024×500 feature graphic?

No, not yet. Plan that banner as a separate asset.

How do credits work?

One credit per phone slide; approved re-export is free; packs never expire at $10/50 or $18/100.

Can StoreShots run Play closed testing?

No. Use related product TestMyApps for managed testing after visuals are ready.

Is this the same as storeshots.org?

No. They are unrelated products and makers.