Tailles des captures App Store

Apple requires screenshots for specific device size classes, not individual models. As of 2026, you must provide screenshots for the 6.7-inch display class and the 5.5-inch display class at minimum. Providing screenshots for the 6.1-inch class is optional but recommended for a polished presentation on the most popular iPhone size.

The 6.7-inch class (iPhone 16 Pro Max, iPhone 15 Pro Max) requires screenshots at exactly 1320 x 2868 pixels in portrait or 2868 x 1320 in landscape. This is the most important size class because Apple uses these screenshots as the primary display in search results and your product page. If you only create one size, make it this one.

The 6.1-inch class (iPhone 16, iPhone 16 Pro, iPhone 15) uses 1206 x 2622 pixels in portrait. If you don't provide this size, Apple automatically scales down from your 6.7-inch screenshots. The auto-scaling generally looks acceptable, but custom screenshots at the native resolution will be sharper and demonstrate more polish.

The 5.5-inch class (iPhone 8 Plus and older) requires 1242 x 2208 pixels. This size class exists for backward compatibility and is still required by Apple for App Store submission. Many developers create these as scaled versions of their 6.7-inch screenshots rather than designing them from scratch. When scaling down, verify that text remains legible at the smaller size — you may need to slightly increase font sizes for this smaller format.

Apple accepts PNG and JPEG formats with no alpha channel (transparency). The maximum file size is not explicitly documented but practically stays under 10 MB per image. Export as PNG for maximum quality, especially if your screenshots contain text — JPEG compression can create visible artifacts around text edges that look unprofessional on Retina displays.

If your app runs on iPad — including all Universal apps — you must provide iPad screenshots. Apple requires screenshots for the 12.9-inch iPad Pro display class at 2048 x 2732 pixels (portrait) or 2732 x 2048 (landscape). This is the only required iPad size, as Apple scales it for other iPad models.

Optionally, you can provide separate screenshots for the 11-inch iPad Pro at 1668 x 2388 pixels and the standard iPad (10.2-inch) at 1620 x 2160 pixels. Providing these optional sizes ensures pixel-perfect presentation on each iPad model rather than relying on Apple's automatic scaling.

iPad screenshots present a unique design challenge because the larger canvas changes the visual balance. Text overlays that look proportional on a phone screenshot can look tiny on an iPad canvas if you simply scale them up proportionally. Instead, redesign your text placement for the iPad aspect ratio, using the additional space to show more of your app's interface or to add secondary information.

The 4:3-ish aspect ratio of iPad screenshots (compared to the approximately 19.5:9 ratio of modern iPhones) means you often cannot directly scale your phone screenshots to iPad. Elements positioned at the top and bottom of a phone screenshot may look oddly placed in the wider iPad format. Most successful apps create separate iPad screenshot compositions that take advantage of the different aspect ratio.

If your app has a distinct iPad layout with sidebar navigation or split-view support, make sure your iPad screenshots showcase these tablet-specific features. Users browsing on iPad want to see that your app takes advantage of the larger screen, not just stretches the phone UI. This is especially important for productivity, creative, and reference apps where iPad users have high expectations for the tablet experience.

Google Play's screenshot requirements are more flexible than Apple's, specifying ranges rather than exact pixel dimensions. This flexibility is both a blessing and a potential pitfall — you have more choices but also more ways to get it wrong.

For phone screenshots, the recommended target is 1080 x 2400 pixels, which matches the resolution of most modern Android flagships including the Pixel 9 and Samsung Galaxy S24 series. This resolution ensures sharp images across the widest range of devices. The absolute minimum usable resolution is 1080 x 1920 (standard 16:9), but the taller 9:20 ratio better represents how modern Android phones actually look.

For 7-inch tablets, use 1200 x 1920 pixels. For 10-inch tablets, use 1600 x 2560 pixels. These dimensions match common tablet display resolutions and ensure your screenshots look native on larger screens. Providing tablet screenshots is especially important for Chromebook visibility, as Google increasingly promotes tablet-optimized apps to Chromebook users.

Google's hard limits are: minimum 320 pixels, maximum 3840 pixels, and an aspect ratio no greater than 2:1 (the longer side cannot be more than twice the shorter side). Staying well within these limits prevents edge-case display issues. Screenshots that push close to the 2:1 ratio can appear stretched or oddly cropped in certain Play Store layouts.

For Android TV, screenshots should be 1920 x 1080 pixels in landscape orientation. For Wear OS, use 384 x 384 pixels. These specialty form factors have their own screenshot slots in the Google Play Console, and providing appropriate screenshots for each form factor your app supports signals quality and completeness.

Unlike Apple, Google does not enforce specific per-localization screenshot requirements. You can use the same screenshots across all languages if you choose, though localized screenshots perform significantly better as discussed in our localization guide.

With Apple requiring at least two size classes and Google supporting five device types, plus multiple localizations, managing screenshot assets can quickly become overwhelming. A systematic approach saves hours of manual work and reduces the risk of uploading the wrong size to the wrong slot.

Design at the largest size first and scale down. For iOS, this means designing at 1320 x 2868 (6.7-inch) and then creating the 5.5-inch version by scaling down and adjusting text sizes. For Android, design at 1080 x 2400 and create tablet versions by redesigning the layout for the wider aspect ratio. Starting large preserves quality — scaling up from a smaller original always produces inferior results.

Use a template-based design system with separate layers for text, device frames, backgrounds, and app screenshots. This separation lets you swap out one element (like the language of text overlays) without recreating the entire composition. In Figma, use components and auto-layout features to make templates that automatically adjust to different canvas sizes.

Automation tools eliminate the most tedious part of multi-size management. ScreenMagic generates screenshots for all required sizes from a single set of inputs. For manual workflows, Figma plugins like "Batch Export" and scripts using the Sharp image processing library can resize and export multiple sizes from master templates in seconds.

Name your files with a consistent convention that encodes the device, language, and sequence number. A format like "iphone67-en-01.png," "iphone55-en-01.png," "phone-de-01.png" makes it immediately clear which file goes where. This naming convention pays dividends when you are uploading to App Store Connect or the Google Play Console, where the upload interface for multiple languages and device types can be confusing.

Keep a master spreadsheet or document that lists every required asset: device type, dimensions, format, and count. Update it when Apple or Google add new device requirements (which typically happens annually after new device launches). This reference document prevents the all-too-common mistake of forgetting a required size and having your submission delayed or rejected.

The final export step is where many developers unknowingly degrade their screenshot quality. Understanding compression, color profiles, and format nuances ensures your carefully designed screenshots look their best in the stores.

Always export as PNG when screenshots contain text, UI elements with sharp edges, or flat color areas. PNG is lossless, meaning no compression artifacts. JPEG can be acceptable for screenshots dominated by photographic content (games with rich graphics, photo editing apps), but even then, use maximum quality (95-100%) to avoid visible compression around text overlays.

Apple recommends sRGB color profile for App Store screenshots. If you are designing in a wide-gamut color space (Display P3), be aware that colors may shift when converted to sRGB for the App Store. Design in sRGB from the start, or verify colors after conversion. The difference is most noticeable in vibrant oranges, reds, and greens that may appear more muted in sRGB.

For Google Play, use the standard sRGB color profile as well. Google's CDN may re-compress your images during delivery, so starting with the highest quality original gives the best final result. Upload PNGs where possible, as Google's re-compression of already-compressed JPEGs can introduce generation loss.

Check file sizes after export. While neither store publishes a strict per-image limit, keeping screenshots under 5 MB each ensures fast upload and processing. If your PNGs are larger, use tools like pngquant or TinyPNG to reduce file size by 50-70% with visually imperceptible quality loss. Never use lossy compression that affects text readability.

After uploading, always preview your screenshots on an actual device. Open the App Store or Play Store on a phone and tablet to verify that your screenshots look correct at the actual display size. This final verification step catches color shifts, cropping issues, and readability problems that desktop previews can miss.