App Store screenshot sizes (2026): every iPhone, iPad, Mac, Watch, TV and Vision Pro dimension

In 2026, an iPhone app needs one set of 6.9-inch screenshots: 1320 × 2868, 1290 × 2796 or 1260 × 2736 pixels in portrait (or the same sizes turned to landscape). If the app runs on iPad, add 13-inch iPad screenshots at 2064 × 2752 or 2048 × 2732 pixels. Upload 1 to 10 PNG or JPEG images per device size and language, with no transparency, and App Store Connect scales them down to every smaller display. App previews are optional: up to three videos of 15 to 30 seconds per device size and language.

Key takeaways

• iPhone: upload the 6.9-inch size. Apple only asks for 6.5-inch screenshots when no 6.9-inch set is provided, and all smaller iPhones are scaled from these.
• iPad: 13-inch screenshots (2064 × 2752 or 2048 × 2732) are required as soon as the app runs on iPad.
• Files: .png, .jpg or .jpeg, exactly one of the accepted pixel sizes, no alpha channel, 1 to 10 per size and language.
• App previews: 15 to 30 seconds, up to 3 per size and language, 500 MB maximum, 30 fps maximum; 886 × 1920 on modern iPhones and 1200 × 1600 on 13-inch iPads.
• Conversion: depending on orientation, the first one to three screenshots appear in search results when there is no app preview, so they carry most of the message.
• Localization: a new language starts with the primary language’s screenshots; upload a translated set for every market that matters.

The sizes you actually have to upload

Apple’s Screenshot specifications page lists more than a dozen display sizes, but most apps only need one or two of them. Everything else is either derived automatically or only matters for a platform you don’t ship on.

One nuance about iPhone. On the current page, the 6.9-inch entry carries no “required” label; the requirement sits on the 6.5-inch entry, which is “required if app runs on iPhone and screenshots for 6.9″ display aren’t provided”. In other words, you need one of the two, and 6.9-inch is the better choice because every other iPhone size can be scaled from it.

Full table of App Store screenshot dimensions

Here is every size App Store Connect accepts, as published by Apple in October 2026. The last column tells you what happens if you skip that size. Device lists are shortened where Apple’s are long.

iPhone screenshot sizes

At the time of writing, Apple’s page also lists an “iPhone Duo” with an outer display (1398 × 2034) and an inner display (2007 × 2853), with a note that uploads for this device will be supported in App Store Connect later this year. Keep an eye on that entry if your app targets it.

iPad screenshot sizes

Mac, Apple Watch, Apple TV and Apple Vision Pro

How scaling from the largest size works

App Store Connect works as a cascade. Apple’s upload guide puts it simply: if your interface is the same across device sizes and localizations, provide only the highest-resolution screenshots required, and they automatically scale down to smaller device sizes. Each smaller size borrows from the next size up:

• iPhone: 6.9″ → 6.5″ → 6.3″ and 6.1″ → 5.5″ → 4.7″ → 4″ → 3.5″.
• iPad: 13″ → 12.9″ and 11″; 12.9″ → 10.5″ → 9.7″.

Scaling keeps your layout but not the device’s shape. A 6.9-inch screenshot is close to 9:19.5, while the 5.5-inch and 4.7-inch phones are 9:16, so check how your images look once scaled to those older sizes. If you still care about small phones, or if your app’s layout really differs on them (an iPhone SE layout, a compact iPad split view), open View All Sizes in Media Manager and upload dedicated screenshots for those sizes. The same tool shows you the scaled versions, which is the quickest way to check that captions are still readable.

Two rules to remember: you can only change screenshots while the version is editable (Prepare for Submission, Rejected, Metadata Rejected, Developer Rejected or Invalid Binary), and once a version is approved you must create a new version to update them. Plan screenshot refreshes together with an update.

File format, count and the transparency trap

• Formats: .png, .jpg and .jpeg.
• Count: a minimum of one and a maximum of ten screenshots per device size and language.
• Dimensions: exactly one of the accepted sizes. 1320 × 2867 is rejected, and so is a nice 1242 × 2688 render uploaded into the 6.9-inch slot.
• No transparency: Apple’s specification says images can’t include alpha channels or transparencies. Design tools often export PNGs with an alpha channel even when every pixel is opaque.

On a Mac, sips checks a whole folder before upload, and converting to JPEG removes the alpha channel:

# Check size and alpha channel of every screenshot
sips -g pixelWidth -g pixelHeight -g hasAlpha screenshots/en-US/*.png

# Convert one file to JPEG (no alpha channel)
sips -s format jpeg 01-main.png --out 01-main.jpg

Keep the images free of anything App Review frowns upon. Guideline 2.3.3 asks that screenshots show the app in use, “not merely the title art, login page, or splash screen”, while allowing text and image overlays. Guideline 2.3.7 says metadata such as screenshots should not include prices, and 2.3.10 forbids imagery of other mobile platforms. Our App Store submission checklist covers the rest of the metadata Apple reviews.

App preview video specifications

App previews are optional short videos shown before your screenshots. According to Apple’s App preview specifications:

Previews follow the same cascade as screenshots: a 6.9-inch preview is scaled for smaller iPhones if you don’t provide one for them. Guideline 2.3.4 adds that previews may only use video screen captures of the app itself, with optional narration and text overlays. Apple’s product page guide notes that previews autoplay with muted audio, so the first seconds have to work without sound. Processing after upload can take up to 24 hours.

Designing the first three screenshots

Correct sizes get you through App Store Connect; the content of the first images decides whether people tap “Get”. Apple’s product page guidance says that, depending on orientation, the first one to three screenshots appear in search results when no app preview is available, and recommends focusing each following screenshot on one main benefit or feature. With a portrait set, that means up to three images side by side in search: those three images are your ad.

1. Lead with the benefit, not the feature. “Never miss a dose” says more than “Reminder settings”. The caption answers why, the screen underneath proves how.
2. One idea per screenshot. A caption of three to six words, set large enough to read on a search result thumbnail. If you need a second line, the idea is probably two screenshots.
3. Put the strongest reason first. Screenshot 1 is the main promise, screenshot 2 the overview of the app, screenshot 3 the feature people search for. Trust signals (privacy, no account, offline) and secondary features go further right.
4. Show the real interface. Use realistic, generic sample data, never features that are not in the build, and keep the status bar clean.
5. Keep one visual system. Same caption position, typeface and background family across the set; Apple also suggests including a Dark Mode screenshot if your app supports it.
6. Test instead of guessing. Product page optimization in App Store Connect shows alternate screenshot sets to a share of visitors and reports the results in App Analytics. Custom product pages let you match screenshots to a specific campaign or audience.

We deliberately give no conversion percentages here: results vary by category, audience and market, and the only numbers worth trusting are the ones from your own product page tests. Writing captions and choosing the order is the core of our App Store Optimization service, together with keyword research for each market.

Localizing screenshots for each language

Screenshots are localizable metadata, separate from the localization of the app binary. App Store Connect supports 50 languages and locales for the product page. As Apple’s localization guide explains, when you add a language, its screenshots default to those of the primary language. A German user would therefore see your English captions until you upload a German set.

• Translate the captions and capture the UI in that language. A German caption above an English interface looks unfinished. UI tests can launch the app in each language, which our guide to localizing an iOS app with String Catalogs shows.
• Plan for text expansion. German and Finnish captions run longer than English; Japanese and Chinese need a different line-break logic. Leave room in the caption area rather than shrinking the font.
• Mirror for right-to-left languages. Arabic and Hebrew screenshots should show the mirrored interface and right-aligned captions.
• Localize previews where they matter. If a localization has no app preview, the App Store shows the preview from the next best available language.
• Keep sizes consistent. Apple Watch screenshots must use the same size across all localizations, and changing the primary language later requires approved screenshots in that language with the same sizes as the current primary language.

Ten screenshots, two device sizes and a dozen languages quickly add up to hundreds of files, which is why the next section matters. If you would rather hand it over, our app localization service covers the app, the metadata and the screenshot sets, and we translate our own String Catalogs with Xlocalize, the Mac app we built for .xcstrings files.

Tools to produce App Store screenshots

Xcode Simulator

The Simulator saves screenshots at the device’s native pixel resolution, so a simulator from the 6.9-inch group (an iPhone 17 Pro Max, for example) gives you a file in one of the accepted 6.9-inch sizes, and an iPad Pro 13-inch simulator does the same for iPad. Use File › Save Screen, or the command line, and freeze the status bar first so every capture shows the same clean time, network and battery:

xcrun simctl status_bar booted override --time "9:41" --batteryState charged --batteryLevel 100 --cellularBars 4 --wifiBars 3
xcrun simctl io booted screenshot 01-main.png
xcrun simctl status_bar booted clear

fastlane snapshot, frameit and deliver

For more than a couple of languages, automate. fastlane snapshot runs your UI tests on each simulator and language listed in a Snapfile and saves the screenshots in per-language folders. fastlane snapshot init creates the Snapfile and the SnapshotHelper.swift file to add to your UI test target.

# fastlane/Snapfile
devices([
  "iPhone 17 Pro Max",
  "iPad Pro 13-inch (M5)"
])
languages(["en-US", "fr-FR", "de-DE", "ja", "ar-SA"])
scheme("AppUITests")
output_directory("./fastlane/screenshots")
clear_previous_screenshots(true)

func testScreenshots() {
    let app = XCUIApplication()
    setupSnapshot(app)
    app.launch()
    snapshot("01-Today")
    app.buttons["All plants"].tap()
    snapshot("02-Overview")
}

frameit then adds device frames, a background and per-language titles read from title.strings and keyword.strings files, configured in a Framefile.json. Two caveats: fastlane’s documentation warns that framed screenshots without titles keep a larger resolution and can’t be uploaded directly, and its frame library may lag behind the newest devices. Check the output dimensions with sips before uploading. Finally, fastlane deliver (or the App Store Connect API) uploads every set to the right language and size.

Design tools

Many teams compose the final images in a design tool such as Figma or Sketch: one frame per accepted size, the raw simulator capture placed inside, captions as text layers so translators can work on them. Whatever the tool, set the artboard to the exact pixel size (1320 × 2868, not a “close enough” 1320 × 2870), export flattened PNG or JPEG, and keep captions inside a safe area so they survive scaling to smaller devices. If you want the whole set designed for you, see our iOS app design service.

Pre-upload checklist

• 6.9-inch iPhone set at an accepted size; 13-inch iPad set if the app runs on iPad.
• Mac, Watch, TV or Vision Pro sets for every other platform you ship.
• PNG or JPEG, no alpha channel, exact pixel dimensions (checked with sips).
• 1 to 10 images per size and language, the strongest three first.
• Real app UI, no prices, no features missing from the build, clean status bar.
• Translated captions and localized UI for every language you sell in; mirrored for right-to-left languages.
• Scaled versions reviewed in Media Manager, with dedicated sizes where the layout differs.

Develak publishes more than 30 apps of its own on the App Store and runs this checklist for each of them, on iPhone, iPad and Mac. If you want help with your product page, tell us about your app.

FAQ