App Store screenshot sizes 2026: complete reference

What are the current app store screenshot sizes for iOS, Google Play, and Microsoft Store in 2026?

Each platform organizes its size requirements around a different anchor. Apple groups devices into display classes (iPhone, iPad, Apple Watch, Mac, Apple TV, Vision Pro) and propagates the largest asset down. Google Play sorts by form factor (phone, 7-inch tablet, 10-inch tablet, Chromebook). The Microsoft Store treats store listing screenshots, logos, and hero art as separate slots with their own pixel specs. The table at the bottom of this guide maps all of them in one place.

Why pixel-perfect dimensions still matter at submission

The most common rejection triggers across all three stores are dimension mismatches (often caused by exporting at non-integer scaling), embedded alpha channels in PNGs, the wrong color profile (anything other than sRGB), and portrait-versus-landscape orientation mistakes on shelves that expect a specific orientation. Flattening the PNG, locking the canvas to integer dimensions, and converting to sRGB before upload eliminates the majority of validator-triggered rejections.

Apple's cascading size system explained

The 6.9-inch lead asset (1320x2868) propagates down to 6.7-inch (1290x2796), 6.5-inch (1242x2688), and 5.5-inch (1242x2208) shelves automatically. If your app only ships an iPad version, the 12.9-inch legacy slot can still be required — check App Store Connect against the device families your build declares. Apple Watch, Mac, Apple TV, and Vision Pro each carry their own non-cascading size families; submit the lead asset for each platform you actually support.

Google Play's flexible size rules

The phone slot is the most forgiving spec across all three stores — almost any modern export will pass — but the 1024x500 feature graphic is rigid and the most common rejection cause on Google Play. It must be exactly 1024x500, PNG or JPG, with no alpha channel and no transparent pixels. If you ship tablet or Chromebook builds, fill those slots too; an empty tablet shelf is not a rejection, but it looks unfinished in the listing.

Microsoft Store screenshot dimensions for Windows submissions

The Microsoft Store surface area is wider than most teams expect. Beyond screenshots you have the app logo (multiple sizes), the hero image, and an optional feature graphic — each with its own pixel spec inside Partner Center. The trailer slot prefers 1080p ProRes encoded at 29.97 FPS; H.264 fallbacks are accepted but compressed harder by the store. None of this cascades the way Apple does, so plan to export each slot explicitly.

Privacy considerations for pre-launch UI

The threat model is not theoretical. Web uploaders frequently cache assets on a CDN with predictable URLs, and search engines have been known to index unreleased marketing copy embedded in screenshots. A local-first workflow keeps the file, its hash, and its EXIF metadata on the same disk as your source code, which is both safer and faster — no upload progress bar between every iteration.

Export every required size locally without a subscription

The workflow has three steps. Pick a base canvas at the largest required dimension (1320x2868 for iPhone-first projects). Set up downscale presets per store — Apple display classes, Google Play phone, tablet, Chromebook, and feature graphic, plus the Microsoft Store screenshot, logo, and hero slots. Validate every export against the spec before opening Partner Center, App Store Connect, or Google Play Console: integer dimensions, flattened PNGs, sRGB color profile, no alpha channel.

Complete 2026 reference table