App Store Screenshot Sizes: Practical 2026 Guide

Quick answer

• Use Apple screenshot specifications as the final source of truth.
• Validate dimensions before export and before upload.
• Keep one repeatable screenshot workflow to reduce review risk and save time.

Official source first

Use Apple docs before every release cycle:

• App Store Connect screenshot specifications

Any size guide on a third-party site, including this one, is secondary to the official Apple table. Device launches can change the required display classes. Always verify against the source before submitting.

Common iPhone screenshot size groups

Apple accepts multiple pixel dimensions inside each display class. The display class is defined by the screen diagonal size (for example, 6.9 inch, 6.5 inch), and each class accepts screenshots at specific pixel dimensions.

Common groups used by iPhone apps:

• 6.9 inch display class
• 6.5 inch display class
• 6.3 inch display class
• 6.1 inch display class
• 5.5 inch display class

Examples listed in Apple documentation include sizes like:

• 1320 x 2868
• 1290 x 2796
• 1242 x 2688
• 1179 x 2556
• 1170 x 2532
• 1242 x 2208

Always verify your exact required set in the official Apple table before export. The examples above are illustrative. Your specific app and target device set may require a different combination.

Why display classes matter

Apple groups devices by screen size, and you submit screenshots for each class rather than for each specific device model. This means one set of screenshots at the right dimensions covers multiple device models within that class.

The practical implication is that you do not need a separate screenshot set for every iPhone model. You need one set per display class you are targeting. If your app supports iPhone only and you want to cover the full range of current devices, you typically need screenshots for two or three display classes.

If your app supports both iPhone and iPad, you also need separate screenshot sets for iPad display classes. Check the Apple reference for iPad size groups.

Understanding portrait and landscape

Apple accepts both portrait and landscape screenshots for iPhone. Portrait is by far the most common choice for iPhone apps. Landscape is more common for apps that are designed to run in landscape mode, such as games.

If you submit landscape screenshots, the dimensions are the same pixel counts but with width and height reversed.

Practical rules that prevent rejection

Use this checklist:

1. Export in RGB color space. CMYK is not accepted.
2. Use accepted dimensions for your selected device classes. Do not submit non-standard sizes.
3. Keep screenshots clear and readable. Apple may reject screenshots that are blurry, low quality, or show incomplete UI.
4. Avoid UI that looks like a placeholder or test build.
5. Confirm text is legible on smaller phones, not just at full desktop resolution.
6. Do not include content that violates App Store guidelines in the screenshots themselves.
7. Use actual app screens, not illustrations or conceptual graphics that misrepresent the experience.

If your app supports iPad, check iPad screenshot groups in the same Apple reference.

If you ship screenshots in more than one language, use this workflow guide too: App Store Screenshot Localization: Simple 2026 Guide.

If you are deciding whether to use framed device visuals in the store listing, read iPhone Mockup for App Store Listings: Simple 2026 Guide.

If your question is more about clarity and layout than dimensions, read App Store Screenshot Design Tips: Simple 2026 Guide.

How screenshots appear in the App Store

Understanding where your screenshots show up changes how you design them.

Product page: When a user taps your app listing, they see all your screenshots in order. They can swipe through them. Most users see the first two or three before making a decision.

Search results: If you do not have an App Store preview video, Apple may display your first one to three screenshots in the search result card. These are small thumbnails. If your text is only readable at full resolution, it will not work here.

Featured placement: If Apple features your app in a curated section, the screenshots are also visible there.

The search result placement is especially important. It means the first screenshot needs to communicate clearly at a small size without any context from the product name or description.

Simple screenshot production workflow

Use this repeatable process:

1. Capture clean source screens or recordings.
2. Pick one consistent visual style for all screenshots.
3. Apply frames, background, and text overlay if using them.
4. Export target dimensions per Apple requirements.
5. Run a final QA pass on real phone previews.
6. Upload to App Store Connect and verify ordering.

Consistency across screenshots usually improves conversion and reduces review issues. When the set looks uniform, it signals a polished, well-maintained app.

Exporting at the right resolution from a mockup tool

If you use a mockup tool like 60fps Mockup to create framed device visuals, the tool exports at its own canvas size (for example, 2160x2160 for a square format). You may need to check whether this matches the required screenshot dimensions for your target display class.

Some teams use square format mockups for social and press kit assets, and export separately at the exact App Store dimensions using the raw screenshots. Others use the mockup output directly and check whether the dimensions are accepted by App Store Connect.

The safest approach is to validate every export against Apple screenshot specifications before submitting.

Tools that help with screenshot production

60fps Mockup

Useful when your source is iPhone recordings and you want clean framed output quickly. Exports at up to 2160x2160 with image and video output from the same recording.

Shots.so

Useful for quick screenshot polish and launch assets. A fast browser tool for teams that start from screenshots.

Mockuuups Studio

Useful for teams that need lots of visual variety from screenshots. Desktop app with a large template library.

Canva Mockups

Useful for teams already using Canva for broader launch design work.

Where 60fps Mockup fits

60fps Mockup exports at 2160x2160, which covers the resolution needed for App Store screenshot quality. For App Store preview videos, it exports full quality MP4 in the correct format.

Snapshot:

• Best for: teams starting from iPhone recordings who need clean framed output fast
• Strong point: fast conversion from recording to clean mockup output, image and video from the same file
• Watch for: you still need to validate final upload sizes against Apple requirements for your specific display class

Quality checklist before upload

Run this before submitting to App Store Connect:

• Title text is readable at small size (shrink the image to check).
• Visual hierarchy is clear on each screenshot.
• Screenshots show core value in the first two images.
• No clipping, blur, or compression artifacts.
• Dimensions match Apple accepted sizes for your display classes.
• Status bar is clean and consistent if visible.
• Device frame is consistent across the full set.
• Screenshot order tells the right story.
• All text overlays are free of typos.
• Color space is RGB, not CMYK.

What happens if you submit the wrong size

App Store Connect will reject screenshots that do not match accepted dimensions. You will see an error during the upload process. The rejection happens before review, so it does not affect your review status.

The fix is to re-export at the correct dimensions and re-upload. This is why it is worth checking sizes before you start production, not after.

Decision checklist

1. Which iPhone display classes do we need to support?
2. Are we exporting dimensions from the latest Apple table?
3. Is text readable at small preview size?
4. Are our first two screenshots showing the core value clearly?
5. Did we run final QA before upload to App Store Connect?
6. Have we checked the iPad display classes if our app supports iPad?

FAQ

Which sizes should I trust for App Store screenshots?

Use the official Apple screenshot specifications as the source of truth before every release. Any third-party guide, including this one, is secondary.

Can I reuse one screenshot size for every iPhone class?

Not always. Apple accepts specific size groups by display class, so verify the required set for your app before export. Some size groups overlap, but you should confirm this in the official table.

How do I reduce App Store screenshot rejections?

Use valid dimensions, keep text readable, avoid placeholder UI, and run a final QA pass for clipping, blur, and ordering before upload.

Do I need to submit screenshots for every iPhone model?

No. Apple uses display classes, not individual device models. You submit screenshots for each display class you want to cover. One set of screenshots at the right dimensions covers multiple devices within that class.

Can I use landscape screenshots for portrait apps?

You can submit landscape screenshots, but Apple may default to displaying portrait for portrait-oriented apps. If your app is portrait-only, portrait screenshots are the right choice.

What file format should screenshots be in?

JPEG or PNG. PNG is recommended for clean screenshots with text overlays because it is lossless. JPEG can introduce compression artifacts at screenshot quality.

Final summary

• Use Apple docs as the final authority.
• Keep one repeatable export workflow.
• Validate sizes before every submission.
• Check readability at small size, not just at full resolution.