Overview
Screenshots are per market and per device family. The Screenshots tab in the editor shows the set the store currently has, and lets you replace it.
Device families
The store groups images by device rather than by exact resolution. Spek follows the same grouping, under Device sizes.
- Phone
- Tablet
- Apple Watch, on iOS where the app has a watch target
Each family has its own accepted resolutions, and the upload tells you when an image does not match one.
Agent screenshots
With the screenshots scope granted, the agent stages localized or redesigned variants over your real images. It never invents a screenshot of an app it has not seen: the source is always your own set.
Staged variants arrive in the review inbox like any other proposal, and pushing one to the store is a separate action. See review and apply proposals.
Common questions
Can I use one set of screenshots for every market?
You can upload the same images everywhere, but localized screenshots are usually the highest-leverage change on a listing after the name.
Review language, on-screen examples and product availability in each locale before reusing a set. Check that the images still show the current app accurately and remain readable in the target device family. Reusing a file is a practical choice, not a substitute for checking its local meaning.
Why is my upload rejected?
The image does not match one of the accepted resolutions for that device family. The strip lists the sizes it will take.
What should I prepare before updating a screenshot set?
Identify the app, locale and device family, then prepare images that accurately show the current product and meet the sizes accepted by that family. Review the ordering as part of the message: the first frame may introduce the main benefit, while later frames can explain specific features. Keep text readable at a realistic viewing size and check that any claim matches the app. The upload control can check supported image requirements, but your team still owns product accuracy and the choice of what the images communicate.
What does localization involve beyond translating image text?
Review the full image for language, examples, units, formatting and product availability in the target market. A translated headline can still sit above a screen that shows another locale or a feature unavailable to that audience. Use your actual app images as the source and check the final composition after the text changes, since longer wording may affect readability. Screenshot proposals in the documented workflow are iOS-specific and remain material for your review before a separate action sends anything to the store.
How do I review an Agent-generated screenshot proposal?
Compare it with the original image and verify that the interface and product claims remain accurate. Check language, visual hierarchy, cropping and the intended device family. A polished image is not enough if it obscures a feature or promises something the app cannot do. Review every affected locale rather than assuming one approved image validates all variants. Keep the distinction between a staged proposal, a provider draft and a submitted store asset clear when coordinating the final release with your team.
What information is useful when an image cannot be uploaded?
Record the selected app, locale, device family, image dimensions and the message displayed by the upload control. Check the accepted sizes shown for that family before trying the same file again. A file intended for a different device group may need a correctly prepared export rather than a new name. If the problem persists, contact support with a non-sensitive example and the relevant context; remove private account or customer information from screenshots used only to demonstrate the issue.