A pre-flight checklist for store visuals
Store visuals are usually finished at the last minute, which is exactly when the avoidable mistakes happen: an alpha channel that blocks upload, a caption in the wrong language, a set where half the images have a status bar. Running a fixed checklist takes ten minutes and catches almost all of them.
Technical
Exact pixel dimensions for each class. No alpha channel on App Store screenshots or the Play feature graphic. Every image in a set the same orientation and aspect ratio. File format PNG or JPEG, and JPEG quality high enough that gradients do not band — flat gradients are where compression artefacts show first. Check the exported file at 100 percent, not in the export dialogue preview.
Editorial
Slot one shows the core job with realistic content. Captions state benefits, not descriptions, and are three to six words. Order is deliberate across the first three. No placeholder names, no lorem ipsum, no test data with a colleague's phone number in it. Status bars, battery levels and clocks are consistent or hidden across the whole set.
Localisation and consistency
If the listing is localised, the captions are too — and the translated text still fits the caption band. Background, accent colour and type are identical across screenshots, feature graphic and video poster frame. The device shown matches the platform you are uploading to. Finally, view the whole set as a strip at thumbnail size and ask whether it looks like one product designed by one team.
Frequently asked questions
What is the most common reason store screenshots get rejected?
Transparency in the file, wrong dimensions, and images that misrepresent the app — for example showing features that require a subscription without any indication.
How often should I refresh store visuals?
When the interface changes enough that the screenshots no longer match, and whenever you have a testable hypothesis about ordering or captions.
Do I need different screenshots per country?
Translated captions at minimum. Genuinely different imagery is worth it only in markets where the use case differs.
Make it in the browser. Drop a screenshot into a 3D device, move the camera, export a still or a video. No install, no account.
Open the 3D editor Open the photo editor