App Store screenshot sizes for every Apple device.

App Store screenshot requirements at a glance

Apple names iPhone display groups by hardware feature (Dynamic Island, Face ID, Home button) rather than by screen size. Many guides, and the older App Store Connect labels, still say “6.9-inch” or “6.5-inch”. The tables below use Apple's current group names, list the devices in each group, and give a translation table for the inch names.

Sources: Apple screenshot specifications, Apple app preview specifications and the App Store Review Guidelines, all checked October 29, 2026. Apple updates these lists when new hardware ships, so App Store Connect is the final word on the day you upload.

Which App Store screenshot sets are actually required?

You do not need to design every size in the tables. Apple's rule is that if your interface is the same across device sizes and localizations, you supply only the highest required resolution and App Store Connect scales it down for the other groups. Every optional group has a named fallback, shown in the “If missing” column below.

What Apple's specification lists as required:

• iPhone: at least one screenshot for iPhone with Dynamic Island (medium display), the 1206 × 2622 / 1179 × 2556 group.
• iPhone, second rule: the Face ID (large display) group (1284 × 2778 or 1242 × 2688) is required if the app runs on iPhone and you don't provide Dynamic Island (large display) screenshots.
• iPad: at least one 13-inch screenshot (2064 × 2752 or 2048 × 2732) if the app supports iPadOS.
• Mac, Apple TV, Apple Vision Pro, Apple Watch: required only for apps that ship on that platform.
• iPhone Duo: optional today; Apple says it becomes required in April 2027 for apps using the iOS 27.1 SDK or later.

The scaling chain is why one large set usually fills a whole iPhone column in App Store Connect: Dynamic Island (large) and Face ID (large) fall back to each other, Dynamic Island (medium) falls back to Face ID (large), and every smaller group falls back to the next one up. Upload tailored sets only when the interface really differs on smaller screens, for example when a compact layout hides a panel.

iPhone App Store screenshot sizes (all groups)

Each group accepts any one of its listed sizes. Choose the size that matches the device or simulator you captured on, so the interface is not stretched, and keep every screenshot in a set at the same size and orientation. Portrait and landscape are both accepted; use the orientation your app actually runs in.

The two oldest Home-button groups list sizes “with” and “without” the status bar. Few apps still need them, and both scale from larger sets when left empty.

Inch names vs pixel sizes: which is which?

Search queries and older tutorials use inch names; Apple's screenshot reference uses device groups; and design tools label presets in their own way. Always pick a canvas by its pixel numbers. The inch labels below are the ones Apple still uses on its app preview reference page.

Labels differ between tools. MockupX's own preset list, for example, calls 1206 × 2622 “iPhone 6.3″” and 1170 × 2532 “iPhone 6.1″”, while Apple's preview reference calls those groups 6.1-inch and 5.8-inch. The pixel sizes are what App Store Connect checks, so match those.

iPad App Store screenshot sizes

iPad groups are named in inches. Design the 13-inch set first and let App Store Connect scale it, unless the iPad layout changes meaningfully on smaller screens such as iPad mini.

A landscape-first iPad app should upload landscape screenshots (2752 × 2064) rather than a landscape interface squeezed into a portrait canvas. Keep one orientation per set; a gallery that alternates looks unfinished.

Mac, Apple TV, Vision Pro and Apple Watch screenshot sizes

These sets are required only when your app ships on that platform.

Mac screenshots are the one place where a desktop capture is the source rather than a phone. Capture the app window at a size that keeps labels readable once the whole 16:10 canvas is shown in the Mac App Store, and leave the desktop background quiet. For watchOS, App Store Connect says the required Watch screenshots are uploaded from the “View All Sizes in Media Manager” view.

iPhone Duo screenshot sizes

Apple's specification now includes a separate iPhone Duo group with two displays:

Apple says these screenshots will be required starting April 2027 for any app built with the iOS 27.1 SDK or later, and that submitting them displays a badge on the product page telling people the app is optimized for iPhone Duo. Both displays are much wider in proportion than a regular iPhone, so plan a separate composition; scaling a 1320 × 2868 card onto 2007 × 2853 leaves large empty bands or crops the interface.

App Store Connect upload rules and review guidelines

File checks happen at upload; content checks happen in App Review. Both can stop a release.

File rules (App Store Connect)

• At least one and at most ten screenshots per device size.
• File types: .jpeg, .jpg or .png.
• No alpha channel or transparency. A PNG saved with an alpha channel can be refused even when it looks opaque.
• Exact pixel dimensions from the accepted list for that group. A file a few pixels off is not accepted.
• Watch screenshots use the same size across all localizations.

Content rules (App Store Review Guidelines)

• 2.3.3: screenshots should show the app in use, not merely title art, a login page or a splash screen. Text and image overlays are allowed.
• 2.3.7: metadata, including screenshots and previews, should not include prices, terms or descriptions that are not specific to the metadata type.
• 2.3.8: screenshots and previews must suit a 4+ age rating even if the app is rated higher.
• 2.3.10: don't include names, icons or imagery of other mobile platforms or alternative app marketplaces. Do not reuse an Android device frame or a Google Play badge in an App Store set.
• 2.3.1: marketing that promotes content or services the app does not offer, or a false price, can lead to removal.

App preview video specs (sizes, length, format)

App previews are optional videos that sit in front of your screenshots. Apple's rules:

• Previews always appear before screenshots on iPhone, iPad, Mac and Apple TV, even if you reorder them.
• They autoplay with muted audio on the product page, so the first seconds must make sense without sound.
• The poster frame shows when a video doesn't autoplay. It defaults to 5 seconds in, you can choose another, and it can't be edited after the asset is approved.
• iOS previews can be portrait or landscape; Mac, Apple TV and Vision Pro previews are landscape only.
• Guideline 2.3.4: previews may only use video screen captures of the app itself, with optional narration and text overlays.
• Processing can take up to 24 hours after upload. Previews aren't available for iMessage apps.
• If a preview is missing for a language, Apple shows the next best available language's preview.

MockupX produces still images, not video. A short screen recording from the device or simulator, trimmed in a video editor, is the usual route for previews; the screenshot set is where a mockup tool helps.

How many App Store screenshots should you upload?

The limit is ten per device size. Apple's product page guidance says that, depending on orientation, the first one to three images appear in search results when no app preview is available. That makes the first three cards the ones most people see; the rest are read only by visitors who open the listing and swipe.

Use only as many cards as you have distinct things to show. Five cards of the same dashboard tell a visitor nothing the first card didn't. Apple also suggests including at least one Dark Mode screenshot if the app supports it.

Localizing App Store screenshots

Each localization in App Store Connect has its own screenshot slots (choose the language from the menu at the top right of the page). Apple recommends localizing screenshots and previews for each market where you offer the app. Practical rules that save rework:

• Capture the interface in the target language. A French headline over an English interface implies a localization the app may not have.
• Write short source copy. Translations often run longer than English; plan a headline area with room for a third line instead of shrinking the type.
• Use real translations while designing, not placeholder text, and check line breaks and punctuation in every language.
• Keep one master layout and swap only copy and source screenshots, so every locale shares the same visual system.
• Mirror for right-to-left languages only when the app itself mirrors its interface.
• Name files by locale and order (for example de-DE_iphone-69_01.jpg) so the release owner uploads the right set to the right slot.

How to build a complete App Store screenshot set

1. Write the story before the template.List three to six benefits a new visitor should understand, in order. Give each card one job: promise, core workflow, differentiator, proof, next benefit.
2. Capture clean source screens.Use the largest simulator or device you support, realistic sample content and a tidy status bar. In the iOS Simulator, xcrun simctl status_bar booted override --time 9:41 --batteryState charged --batteryLevel 100 fixes the clock and battery, and xcrun simctl io booted screenshot file.png saves a PNG at the simulator's native resolution.
3. Design the 1320 × 2868 master.Set one headline position, type scale, background treatment and device framing, and keep it across every card. Check the first three cards at thumbnail size.
4. Export the required companions.Re-export the same layout at 1206 × 2622 for Dynamic Island (medium). Add iPad, Mac, Watch or TV only if you ship there, and rebuild those compositions for their own proportions.
5. Validate every file before upload.Check pixel size, orientation, file type, absence of an alpha channel, and the order of the set. On a Mac, sips -g pixelWidth -g pixelHeight -g hasAlpha *.png prints all three for a folder.
6. Upload and review in App Store Connect.Use “View All Sizes in Media Manager” to see which groups are filled natively and which are scaled, then review the gallery in each localization.

Doing it in MockupX

MockupX is a browser editor for the design and export steps; it does not upload or submit anything to App Store Connect. Its output-frame list has an App Store group for iPhone, iPad, Mac and spatial, and Watch, and a custom width × height field (320 to 6000 px) for any accepted size without a preset:

• Choose a canvas, drop or paste the capture, pick an iPhone 17, 17 Pro, 17 Pro Max or iPhone Air frame (or iPad Air, iPad Pro, iPad mini, MacBook and Apple Watch frames), and add a headline and description.
• Export at 1×. The 2× option doubles both dimensions (1320 × 2868 becomes 2640 × 5736), which App Store Connect will not accept.
• Use a solid or gradient background, not the transparent one, and prefer JPEG for store uploads: JPEG has no alpha channel, so it cannot trip the transparency rule. If you export PNG, check it for an alpha channel before uploading.
• Export requires sign-in. Free exports are PNG or JPEG with a MockupX watermark, which is fine for drafts and reviews but not for a store listing; a paid plan removes the watermark and adds WebP and 2× export.

Worked example: a habit tracker for iPhone and iPad

A small team ships a habit-tracking app on iPhone and iPad, in English and German, with no Watch app. Here is the full asset list and why each item is there.

Card plan for the iPhone set: 01 “See your week at a glance” on the populated week view; 02 “Log a habit in one tap” on the check-in screen; 03 “Streaks that keep you going” on the streak detail; 04 reminders; 05 home-screen widget; 06 Dark Mode. The German set reuses the layout with German interface captures and headlines, one of which needed a third line, so the headline area was planned for three lines from the start. Total: 32 still images, each checked with sips before upload.

Why screenshots get rejected, and how to check for each

Shipping on Google Play too? What changes

Google Play has different rules, so build both stores from one story and adapt the sets. According to Google's Play Console help, screenshots are JPEG or 24-bit PNG with no alpha, with a minimum dimension of 320 px and a maximum of 3840 px; you can add up to eight per device type and need at least two across device types to publish. Google Play also requires a 1024 × 500 feature graphic (JPEG or 24-bit PNG, no alpha) and a 512 × 512 icon.

Use Android device frames for the Play set and Apple frames for the App Store set; guideline 2.3.10 keeps Android imagery out of App Store screenshots.

Source: Google Play Console Help, preview assets, checked October 29, 2026.