App Store Screenshot Sizes for 2026: Every Size in Pixels

Checked against Apple's App Store Connect Help on October 11, 2026.

Apple's page states the iPhone requirement in two ways as of October 11, 2026: the summary at the top names the Dynamic Island medium display, while the size table marks the Face ID large display as the fallback requirement. One design covers both readings, because 1320 x 2868 and 1206 x 2622 have almost the same shape (about 0.46 wide for every 1 tall). Export both and App Store Connect has nothing left to ask for.

Screen sizes are from the linked Apple Support tech specs pages, checked October 11, 2026. The 5.5 inch screenshot size is larger than the physical screen of the iPhone 8 Plus (1920 x 1080), because Apple asks for the rendered size.

Watch the inch labels. The iPhone Air has a 6.5 inch screen, yet its 1260 x 2736 capture belongs to the Dynamic Island large display, while a template labelled 6.5 inch almost always means 1242 x 2688 for the Face ID large display. Go by the pixels, not the inches. To cover both sizes Apple names, run one large phone (a Pro Max or the Air) and one medium phone (iPhone 17, 17 Pro or 18 Pro). Screens were read on Apple Support on October 17, 2026.

Export JPG from Figma rather than PNG. The same Figma page says its PNG exports always carry an alpha value, and Apple refuses alpha channels. The App Store screenshot size checker reads the exported files and names the display group each one matches, and its page covers the same export from Sketch.

Scaling down keeps text sharp, while scaling a 1206 x 2622 capture up to 1320 x 2868 softens thin lines, so always start from the largest size you have. Any editor that resizes with the proportions locked and crops to typed numbers does the job, Preview on a Mac included. Check the result before you upload, because one pixel off fails.

iPad screenshots are 3 wide for every 4 tall, a different shape from iPhone screenshots, so an iPhone design cannot be resized into one without cropping or a new layout. One exception to swapping the numbers: the 9.7 inch sizes without the status bar are listed in landscape as 2048 x 1496 and 1024 x 748.

Other rules from the same page: files are .mov, .m4v or .mp4 in H.264 (target 10 to 12 Mbps) or .mov in ProRes 422 HQ, at no more than 30 frames per second, with stereo audio. Previews always appear before screenshots, and processing can run up to 24 hours after upload. Apple offers app previews for iOS, macOS, tvOS and visionOS apps, and not for iMessage apps. How to record, edit and plan one is in our app preview video guide.

Video versions of both placements run 5 to 30 seconds at 30 or 60 frames per second, as .mov, .m4v or .mp4. Like screenshots, these images cannot have transparency.

One thing to watch: an iPhone screenshot at 1320 x 2868 is about 2.17 times taller than it is wide, which breaks Google's rule that the long side is at most twice the short side. Export a separate 1080 x 1920 set for Google Play.

• Screens That Do Not Show the App in Use

  Guideline 2.3.3 says screenshots should show the app in use, not only title art, a login page or a splash screen. Text and image overlays are allowed, so a caption above a real screen is fine. A set of pure marketing slides with no interface is the risky case.

• Prices, Discounts and Terms

  Guideline 2.3.7 says screenshots and previews should not include prices or terms. Apple's asset best practices add that you should leave out specific pricing, discounts, website URLs and copyright symbols, so the image stays true in every country.

• Other Platforms in the Picture

  Guideline 2.3.10 tells you not to include names, icons or imagery of other mobile platforms or alternative app marketplaces. An Android phone frame or a Google Play badge in an App Store screenshot is the classic way to trip this.

• Content Above a 4+ Rating

  Guideline 2.3.8 requires icons, screenshots and previews to fit a 4+ age rating even when the app itself is rated higher. For a game with violence, choose frames without gore or a weapon pointed at a character.

• Real People's Data and Borrowed Material

  Guideline 2.3.9 makes you responsible for the rights to everything in your screenshots and asks you to show fictional account information instead of a real person's data. Replace real names, emails, photos and messages before you capture.

• Hidden Purchases and Unearned Awards

  Guideline 2.3.2 says screenshots must make clear when a featured item, level or subscription costs extra. Apple's best practices also tell you to avoid claims that cannot be verified, and not to add Apple recognitions such as Editor's Choice or App of the Day yourself.

1. Step 1

   Check What Takes the Slot Before Your Screenshots

   App previews are always shown before screenshots. If you set a search results creative asset, that appears instead, and Apple's asset best practices say that without one your in app events, app previews and screenshots are used. People who already downloaded your app see an in app event card in place of screenshots while an event is running.

2. Step 2

   Put the Main Job of the App in Screenshot One

   The first image has to explain what the app does to someone who has never heard of it. Show the main screen with real looking content and one short caption that names the outcome, such as "Split any bill in two taps". Save settings, onboarding and sign in screens for later or leave them out.

3. Step 3

   Make Screenshots Two and Three Stand Alone

   Each of the next two should cover one feature or benefit and make sense without the others. Apple's advice is to lead with your strongest features and order them the way someone would use the app. A panorama that only works when three images sit side by side is a gamble, because you do not control how many are shown.

4. Step 4

   Keep Captions Short and Readable at Thumbnail Size

   A search result shows your screenshot far smaller than you designed it. Use one phrase per image, set large, in the center area. Apple recommends a short phrase that adds to the visual instead of describing it, with the focal point kept in the center so nothing is clipped.

5. Step 5

   Preview the Result, Then Localize

   App Store Connect has a Preview tool that shows your product page and search result on iPhone and iPad before anything goes live, described in Apple's guide to managing App Store assets. Once the first three work in your main language, translate the captions for each language you support.

• Exporting at Almost the Right Size

  A canvas of 1290 x 2800, or a capture from a device whose resolution is not on Apple's list, does not match any accepted size. Start the design file at a size from the tables above, and check that the export did not apply a 2x or 0.5x scale.

• Leaving Transparency in a PNG

  Rounded device corners on a transparent background look fine in a design tool, but Apple states that screenshots cannot include alpha channels or transparencies. Flatten the image onto a solid background or export it as JPEG.

• Reusing iPhone Art for iPad or Google Play

  iPhone screenshots are much taller than iPad screenshots, and taller than Google Play allows. Stretching one into the other distorts the interface, which Google's guidelines list among the things to avoid. Plan three layouts: iPhone, iPad and a 9:16 set for Google Play.

• Showing an Old Version of the App

  Section 2.3 of the App Review Guidelines asks you to keep metadata up to date with new versions. After a redesign, old screenshots mislead buyers and invite a metadata rejection. Recapture them in the same release, and say what changed in your app release notes.

• Uploading One Language Everywhere

  A new localization starts with your primary language screenshots. If the captions are in English, a French shopper sees English text over a French listing. Translate the captions at least for your largest markets.

• Capturing Every Size by Hand

  Screenshots for several devices and languages add up fast. The fastlane screenshots guide describes a snapshot tool that captures screenshots in multiple languages across simulators, and a deliver command that uploads them, so a release does not depend on someone pressing buttons in a simulator.

• Resources

  ChatGPT Prompts for Instagram Carousels

  Twenty five copy ready prompts for hooks, slide outlines, captions and app carousels, with the 2026 Instagram carousel rules.

• Resources

  ChatGPT Prompts for a Content Calendar

  Twenty five copy ready prompts for brand voice, pillars, monthly and weekly plans, each network, a launch month and a calendar table for Sheets or Notion.

• Resources

  Claude Prompts for Social Media

  Thirty copy ready Claude prompts for brand voice, post ideas, captions per network, carousels, hooks, replies, export analysis, a weekly review and an audit.

• Use cases

  Startups

  A launch plan by phase for a new app, and the recurring posts Spreadcast covers once the listing is live.

• Tools

  Instagram Post Generator

  Spreadcast designs a 4:5 Instagram post for each app update, 5 star review and rating milestone, writes the caption and publishes it for you.

• Alternatives

  Hootsuite vs Sprout Social

  Both bill per seat. Hootsuite is cheaper for an inbox and listening, Sprout for approvals and report exports. Every plan, seat sums for 1 to 10 people and the verdict.