App Store Screenshot Sizes: Build for the Target, Not the Guess

There is no single image size that covers every app store asset. Apple groups iPhone and iPad screenshots by supported display classes, while Google Play listing screenshots and feature graphics follow separate rules. The correct export depends on the target storefront, device class, and asset type.

The safest habit is to select the store and device target before designing. Then let one maintained requirement list drive the canvas, export, and final checks.

Start with the official references

Apple publishes accepted screenshot dimensions and display classes in App Store Connect screenshot specifications. The page changes as Apple adds or retires device classes, so check it when preparing a release instead of relying on an old design file.

Google Play has its own asset requirements. A feature graphic is a different asset from a phone screenshot. It has its own 1024 by 500 pixel requirement and transparency rules. Keep these canvases separate in your project.

Do not scale one flat image blindly

When a design moves between aspect ratios, text and product UI can land in the wrong place. A good editor scales the overall composition while keeping headlines, app screens, and margins in sensible relationships. Inspect every target after resizing. For some layouts, a small manual adjustment is better than automatic scaling.

Keep important copy and UI away from the edge. Store previews can appear in different contexts and at smaller sizes, and a device frame can reduce the area available for the real interface.

Export checks before upload

For each selected target, verify:

• Pixel width and height match the currently accepted specification.
• File format and transparency meet that asset type's rules.
• Screenshot count is within the store's limits.
• The image still looks clear at full resolution and as a small listing preview.
• File names identify the store, device, language, and position in the set.
• The image depicts the app's current experience and does not promise unavailable features.

Apple currently documents one to ten screenshots per supported device size and accepts JPEG/JPG/PNG without alpha transparency. Google Play lists asset-specific rules; do not reuse its feature graphic canvas as a phone screenshot preset.

Maintain a versioned size catalog

If you create screenshots often, store the requirements as structured data with a source URL and review date. Then the editor can share the same values between its compatibility filter, canvas setup, output filenames, and validation panel. When a store changes its rules, update one record and recheck affected templates.

This guide is a workflow aid, not the final word on a submission. Always confirm the current Apple and Google requirements for your exact target before uploading.