App Store Screenshot Sizes in 2026: Every Required Dimension

The screenshot is the single highest-leverage visual asset on an app listing, and every store measures it in pixels. Apple and Google both require specific dimensions, and those dimensions have changed meaningfully in 2024 and 2025 — the iPhone 16 Pro Max 6.9-inch reference size, the iPad Pro M4 13-inch, the November 2025 Android 15 enforcement cycle. Most published cheat-sheets have not caught up.

This post is the full 2026 App Store screenshot sizes reference, mapped across every Apple and Google device class: iPhone, iPad, Android phone, Android tablet, Apple Watch, tvOS, visionOS, and Mac. Each row tells you what is required, what is optional, and what auto-scales from a single master.

Pair this with the live screenshot size guide (updated whenever either store changes a requirement), or read alongside the App Store vs Google Play listing requirements post for the broader submission context.

The 2026 rules at a glance

Every device class Apple and Google support, mapped to the required reference size and the required vs optional status.

iPhone screenshot sizes

Apple streamlined iPhone screenshot requirements across 2024 and 2025. The practical effect: you render one set at 6.9 inch and Apple handles the rest.

6.9-inch iPhone — required reference size

Target dimensions: 1320×2868 portrait (2868×1320 landscape). This is the iPhone 16 Pro Max reference size, introduced with iOS 18 in late 2024. As of 2026 it is the only iPhone size Apple requires. If you provide only this set, Apple auto-scales to fit every smaller display class in search results and on the product page.

6.7-inch iPhone — optional, auto-scaled

Target dimensions: 1290×2796 (iPhone 15 Pro Max, 14 Pro Max, 13 Pro Max, and earlier Plus models). Now optional. You can still supply a bespoke 6.7-inch set if you want device-specific overlay text or a different composition at that aspect ratio, but most teams skip it.

6.5-inch iPhone — optional, auto-scaled

Target dimensions: 1242×2688 (iPhone 11 Pro Max, XS Max). Optional. Relevant mostly for apps targeting older iPhone hardware.

5.5-inch iPhone — legacy, rarely used

Target dimensions: 1242×2208 (iPhone 6 Plus through iPhone 8 Plus). Still accepted by Apple but rendered on almost no modern device. Drop it unless you have a specific legacy-device testing audience.

How many iPhone screenshots?

Minimum 2, maximum 10. The first screenshot owns the install decision — see the screenshot strategy section of the ASO playbook for indie developers for the 2.5-second rule.

iPad screenshot sizes

iPad screenshots are required only if your app supports iPad. If you ship iPhone-only, skip this section.

iPad Pro 13-inch (M4 and later) — required reference

Target dimensions: 2064×2752 portrait (2752×2064 landscape). This has been the required iPad reference size since the M4 iPad Pro launched in May 2024.

iPad Pro 12.9-inch — legacy, still accepted

Target dimensions: 2048×2732. Relevant for apps that still target 3rd- and 4th-generation iPad Pros. Optional — Apple accepts either the 13-inch or the 12.9-inch master.

Minimum 2 iPad screenshots, maximum 10, same as iPhone. Many teams reuse iPhone designs scaled up to iPad dimensions, which works but often underuses the horizontal space; dedicated iPad compositions convert better.

Google Play screenshot sizes

Google Play is more permissive about dimensions than Apple. You get a range, not a fixed reference, and tablets are optional.

Phone screenshots — required

• Count: minimum 2, maximum 8.
• Long-edge pixel range: 320 to 3840.
• Aspect ratio: between 1:1 and 2:1.
• Orientation:portrait or landscape; Google doesn’t require a specific one but discourages mixing within a single listing.
• File format: JPEG or 24-bit PNG (no alpha channel).

Practical tip: render at 1242×2688 (or 1320×2868 if you want to reuse Apple masters) and Google will accept them unchanged. The scale range means you do not need a separate export.

7-inch tablet screenshots — optional

Same dimensional rules as phone (320–3840 long edge, 1:1 to 2:1 aspect). Up to 8 screenshots. Recommended if your app has a tablet-optimised layout; a tablet screenshot set improves Play Store ranking in tablet searches.

10-inch tablet screenshots — optional

Same rules again. Strongly recommended for productivity, creativity, and enterprise apps where tablets are the primary device.

Feature graphic — required

1024×500 PNG or JPG. Not technically a screenshot, but Play Console lists it alongside. It displays above the short description on every Play Store device. Avoid device mocks and call-to-action overlays — Google rejects both under its Metadata policy.

Apple Watch, tvOS, visionOS, Mac

Platform-specific screenshots are required only for apps that ship on that platform. Minimum 2, maximum 10 for each.

Apple Watch

Sizes vary by Series and case. Current flagship targets:

• Series 10 (46mm):416×496
• Series 10 (42mm):374×446
• Series 9/8/7 (45mm):396×484
• Ultra / Ultra 2:410×502

Provide the largest size you support. Apple scales down. The live screenshot size guide keeps the full per-Series list.

Apple TV (tvOS)

3840×2160 (4K) or 1920×1080(HD), landscape only. tvOS listings also require a full-bleed app icon and top-shelf artwork; check Apple’s tvOS-specific guidance for those.

Apple Vision Pro (visionOS)

3840×2160 landscape.visionOS screenshots should showcase spatial or mixed-reality UI where applicable — conventional screens look flat and lose the platform’s differentiation.

Mac App Store

Apple accepts 1280×800, 1440×900, 2560×1600, or 2880×1800. Retina variants at the higher end are preferred.

Rules reviewers enforce beyond the pixels

The pixel dimensions are table stakes. Reviewers reject for other issues that do not surface in App Store Connect’s submission validator.

• No transparent backgrounds on Apple. App Store Connect accepts alpha channels but Apple rejects under guideline 2.3.3 if the final rendered screenshot shows transparency.
• No device frames in Google feature graphics. Google’s Metadata policy bans device mockups and call-to-action overlays in the 1024×500 feature graphic specifically. Device frames are still allowed inside the phone screenshots.
• Screenshots must match the shipped app. Outdated UI, features you removed, or designs that differ from the build get flagged under Apple guideline 2.3.3 and Google’s Deceptive Behavior policy.
• No cross-platform store badges.An iOS screenshot that shows a “Download on Google Play” badge, or vice versa, rejects on submission.
• No competitor names or trademarks. Same rule as metadata — see the full App Store rejection reasons index.
• Localize overlays per locale. English overlay text dropped into Japanese, German, or Chinese listings is a conversion killer and reads as low-quality to Apple reviewers.

A production pipeline for screenshots

A clean render pipeline cuts the per-release time from a day to an hour. The pattern most indie teams end up with:

1. Render one master per device class.6.9-inch iPhone for Apple, iPad Pro 13-inch if you ship iPad, 1320×2868 reused for Google phone. Apple handles auto-scaling down; Google accepts the range.
2. Design overlays in Figma or Sketch. Separate the UI render from the overlay text layer so you can regenerate localized overlays without re-rendering the app UI.
3. Auto-resize with a single tool.Push My App’s Screenshot Resizer takes one master per device class and exports every store-required size with the correct aspect and padding. The app icon resizer handles the icon side of the same pipeline.
4. Re-render on every UI change. Screenshots become a lie faster than anything else in your listing. Tie the screenshot render step to your release checklist.
5. Verify dimensions before upload. The live screenshot size guide shows every 2026 dimension. Pair with the free ASO pre-submission checklist for the broader pre-flight sweep.

Frequently asked questions