App Store Screenshot Sizes for iPhone, iPad and Mac

Screenshots are most of what people see before they tap Get. They are also one of the fiddlier parts of a submission. Apple lists dozens of pixel sizes across iPhone, iPad, Mac, Apple TV, Apple Vision Pro and Apple Watch, and it is not obvious which ones you have to make and which ones App Store Connect fills in for you. This guide sorts that out, as of 12 March 2026, and adds the review rules that catch small teams out.

Shipping on Android too? The Google Play version of this guide is Google Play Screenshot Sizes, Feature Graphic and Video.

The short version

• Upload between one and ten screenshots for each display size you provide, as .jpeg, .jpg or .png files.
• For iPhone, App Store Connect can scale one set at the largest accepted size, such as 1320 × 2868 pixels in portrait, down to smaller iPhones. Apple's page marks which iPhone size a submission must include, so check it before you upload.
• If your app runs on iPad, you also need a 13-inch iPad set: 2064 × 2752 or 2048 × 2732 pixels in portrait.
• Mac apps need 16:10 screenshots at one of four sizes, up to 2880 × 1800 pixels. Apple Vision Pro apps need 3840 × 2160.
• Screenshots must show the app in use, and you can't change them while the version is Waiting for Review.

The sizes Apple asks for

Apple keeps the full list in App Store Connect Help under Screenshot specifications. As of 12 March 2026, it says you must upload one to ten screenshots in .jpeg, .jpg or .png format. These are the rows that matter for most iPhone, iPad and Mac apps. Landscape sizes are the same numbers swapped round.

Apple's page marks which rows a submission must include, and the device names and requirements change as new devices arrive, so check it before you upload. Apple TV apps need 1920 × 1080 or 3840 × 2160. Apple Watch apps have their own set of sizes per model, and Apple asks you to use the same Watch size across every localisation of the app.

How the fallback works

Each smaller iPhone and iPad row carries a note: if you don't provide screenshots at that size, App Store Connect uses scaled screenshots from a larger one. Follow those notes down the list and a set at the largest size can stand in for the rest. On iPad, the 11-inch and 12.9-inch sizes fall back to 13-inch.

In practice, one iPhone set and one iPad set cover every device. Add a smaller set by hand when your layout changes enough on a smaller screen that the scaled version would mislead, for example when a sidebar collapses into a tab bar.

Uploading them in App Store Connect

You add screenshots per platform, per display size and per language in App Store Connect. Apple's App Store Connect Help walks through the upload screens. You upload your large sets, add other sizes or localisations where you want custom images, and App Store Connect scales the large sets down for smaller devices.

One timing rule is easy to miss. Apple's list of app and submission statuses says that while a version is Waiting for Review, you can't upload or edit screenshots or app previews. You can still remove the build from review. So finish the screenshots before you press Submit, or be ready to pull the build to change them.

What makes a screenshot set work

Apple's product page guidance adds a few points worth planning around. As of 12 March 2026:

• You can feature up to ten screenshots on your product page.
• When there is no app preview, the opening one to three screenshots appear in search results, depending on their orientation. Those few images do most of the work, so lead with what the app is for.
• Give each later screenshot one main benefit or feature.
• If your app supports Dark Mode, Apple suggests including at least one screenshot that shows it.
• Localise screenshots for each market you sell in, along with the description and keywords.

The review rules that apply to screenshots

Screenshots are metadata, so App Review checks them against guideline 2.3, Accurate Metadata. As of 12 March 2026, these parts apply:

• 2.3.3: screenshots should show the app in use, not just title art, a login page or a splash screen. Text and image overlays are allowed.
• 2.3.7: screenshots, like names and subtitles, shouldn't include prices, terms or descriptions that don't belong to that type of metadata.
• 2.3.8: screenshots must suit a 4+ age rating, even if the app is rated higher.
• 2.3.9: you need the rights to everything shown, and you should show fictional account details rather than a real person's data.
• 2.3.10: don't show the names, icons or imagery of other mobile platforms.

The 2.3.9 rule is the one small teams trip on most easily. A screenshot taken from your own account shows your own name, your friends' messages or a real customer's request. Build a demo account with made-up data and capture from that.

A workflow for a small team

1. Capture at the largest sizes. Use the largest iPhone simulator, such as iPhone 17 Pro Max, and a 13-inch iPad simulator, and let App Store Connect scale down.
2. Seed fictional data. Keep a demo account or a debug launch option that fills the app with believable, made-up content.
3. Write captions in a design file, not in the image. Localising then means swapping text, not redrawing.
4. Check the export. Confirm the pixel size matches an accepted size exactly, and that the file is JPEG or PNG.
5. Redo the set when the UI changes. Plan new screenshots alongside the release that changes the screens, not after it.

If you are still preparing a launch, our guides to app icon sizes and publishing an app on the App Store cover the other assets App Store Connect asks for.

How FeedbackKit fits in

FeedbackKit is an in-app feedback board: your users post requests, vote and comment inside your app. It has nothing to do with uploading screenshots, but the two meet in a couple of places.

If your app includes a feature request screen and you show it in a screenshot, guideline 2.3.9 applies to it like any other screen. Fill it with fictional requests before you capture it. And because the FeedbackKit Swift SDK's SwiftUI screens run on iPhone, iPad and Mac (iOS 26, macOS 26 and visionOS 26 or later), the board follows each device's layout in the sizes above. The Kotlin, Flutter and React Native SDKs give the same board to your Android users. Setup for Apple platforms is in the Swift docs.

Here is how that looks in FeedbackKit, with sample data from a fictional hiking app:

Most apps shouldn't lead their screenshots with a feedback screen. Guideline 2.3 asks for the app's core experience, and that is what the opening images should show. The board earns its place after launch, when it tells you which feature the next set of screenshots should be about.

If you want that list of requests from your own users, start free.