App Store Screenshot Requirements for iOS Submission (2026)

Quick answer: Apple requires at least 1 and allows up to 10 screenshots per device size and localization, as .jpeg, .jpg or .png files without alpha. Every iPhone app needs a 6.3″ set (1206 × 2622 or 1179 × 2556) plus either a 6.9″ or a 6.5″ set, iPad apps need a 13″ set, smaller sizes are scaled, and every screenshot must show the app in use.

These are the current rules from Apple's screenshot specifications in App Store Connect Help. Apple updates them as new devices ship, so confirm in App Store Connect before you submit.

You don't have to design for every iPhone ever made. Apple's rule is to provide screenshots for the highest required resolution, and App Store Connect scales them down for smaller devices when your UI is consistent across sizes.

For iPhone, that means two sets in practice:

• 6.3″ (1206 × 2622 or 1179 × 2556): required for every iPhone app.
• 6.9″ (for example 1320 × 2868): optional. If you leave it out, App Store Connect uses scaled 6.5″ screenshots, which then become required.

For iPad, the 13″ display is the one required size, and 11″ and smaller iPads are scaled from it. Because its aspect ratio differs from iPhone, design it as its own set showing your real iPad layout.

Each slot accepts portrait or landscape images, with the width and height swapped. Pick the orientation your app actually uses; most apps use portrait, while many games use landscape.

Every exact pixel size, including Mac, Apple Watch and the new iPhone Duo inner and outer displays, is listed in our App Store screenshot sizes guide, with dedicated pages for iPhone, iPad and iPhone Duo.

Upload problems usually come down to one of three details.

Exact dimensions. App Store Connect accepts only the listed pixel sizes. A design exported at the wrong scale, or a 1179 × 2557 file from a rounding error, will be refused. If you see the error about wrong dimensions, our guide to fixing screenshot dimension errors lists the usual causes.

No alpha channel. Apple's specifications state that images can't include alpha channels or transparency. A PNG can carry an alpha channel even when every pixel looks opaque, which is why exports from design tools sometimes fail. On a Mac you can check with sips -g hasAlpha screenshot.png and convert to a flattened JPEG with sips -s format jpeg screenshot.png --out screenshot.jpg. Our guide on removing the alpha channel covers Preview and design-tool settings too.

Format choice. JPEG keeps files small and has no alpha by definition. PNG preserves crisp text and flat colors, as long as it is exported without transparency. Either works; consistency within a set matters more.

The quickest check is our free screenshot size checker: drop in an image and it shows which App Store or Google Play slot it fits and whether it has an alpha channel.

Screenshots belong to a localization. In App Store Connect you pick the language from the pop-up menu at the top right of the version page and upload a set for that language; the 1–10 limit applies to each language separately.

A few points to know:

• You decide which localizations get custom screenshots. Localizing them is not mandatory, but an English caption in the French storefront is an obvious miss.
• For app previews, Apple says that when a preview isn't provided for a language, the preview in the next best available language appears. Don't rely on fallbacks for screenshots either: open Media Manager and check what each localization actually shows.
• Apple Watch is the exception to per-language sizing. You must use the same Watch screenshot size consistently across all localizations.
• Removing a screenshot also removes it from every display size that uses scaled versions of it.

Technical checks happen at upload. Content checks happen in App Review, under Guideline 2.3. In short, screenshots must show the app in use rather than only title art, a login page or a splash screen, reflect the current version accurately, flag features that need extra purchases, avoid prices and suit a 4+ audience. They also can't show other mobile platforms. Our article on App Store screenshot guidelines explains each rule and the fixes for common rejections.

Screenshots are tied to an app version. According to App Store Connect Help, you can upload and submit them when the version has one of these statuses: Prepare for Submission, Invalid Binary, Rejected, Metadata Rejected or Developer Rejected.

That has practical consequences:

1. To change screenshots on a live app, create a new version and submit it for review with the new set.
2. If only your metadata was rejected, you can replace the screenshots and resubmit, typically without a new build.
3. To try alternative screenshots on a live app, use Product Page Optimization or Custom Product Pages, which are reviewed separately.

If you publish on both stores, the rules differ more than people expect.

See our Google Play screenshot requirements checklist for the Android side, and the Google Play screenshot sizes guide for dimensions. For the design work itself, start with how to make App Store screenshots and then review the set against our App Store screenshot best practices.