AppMockup Logo AppMockup
Marketing April 29, 2026 10 min read

App Store Screenshot Display Sets: 2026 Requirement Guide

You’ve spent months perfecting your code. The UI is pixel-perfect, the backend is scaling beautifully, and you’re finally ready to hit that "Submit for Review" button in App Store Connect. Then, t...

By AppMockup Team

You’ve spent months perfecting your code. The UI is pixel-perfect, the backend is scaling beautifully, and you’re finally ready to hit that "Submit for Review" button in App Store Connect. Then, the red error messages start appearing. Your screenshots are the wrong size. The aspect ratio is off by a hair. You’re missing a mandatory "display set" for a device that hasn't been sold in Apple Stores for years. It’s an annoying, friction-filled part of the launch process that hasn't changed much in 2026.

Understanding Apple’s screenshot requirements is less about design and more about navigating a specific set of rules that Apple calls "Display Sets." If you get these wrong, your app stays in "Missing Metadata" limbo. If you get them right—and use the "Simplified Metadata" loopholes available today—you can cut your design work by 70%.

This guide breaks down the mandatory requirements for 2026, the mapping logic Apple uses to scale your assets, and why relying too heavily on auto-scaling might actually hurt your conversion rates.

The 2026 'Golden Rule' for iPhone Display Sets

As of early 2026, Apple has streamlined the submission process, but two specific display sets remain strictly mandatory. You cannot submit an iPhone app without providing assets for these two categories. Period.

  1. The 6.7-inch Display Set: This covers the "modern" iPhone layout (iPhone 16 Pro Max, 15 Pro Max, and 14 Pro Max). The required resolution is 1290 x 2796 pixels.
  2. The 5.5-inch Display Set: This covers the "Home Button" legacy layout (iPhone 8 Plus, 7 Plus, 6s Plus). The required resolution is 1242 x 2208 pixels.

Why does the 5.5-inch set still exist in 2026? It feels like a relic. However, according to Apple’s Developer Documentation, a non-negligible segment of the global user base still operates on older hardware or SE models that use the 16:9 aspect ratio. Apple insists on these screenshots to ensure that users on those devices don't see "notched" screenshots that would look awkward on their rectangular screens.

The "Simplified Metadata" loophole is your best friend here. If you provide the 6.7-inch assets, Apple’s Media Manager will automatically use those to cover the 6.5-inch (iPhone XS Max) and 6.1-inch (iPhone 16 Pro, 15 Pro, iPhone 13) displays. You *can* upload custom sizes for every single device, but unless you have a specific reason to do so, the 6.7-inch set acts as the master for all notched and Dynamic Island phones.

Current Aspect Ratio Standards

Research into the latest iPhone 16 Pro Max specs confirms that while the physical screen has grown slightly, the 1290 x 2796 pixel resolution remains the gold standard for the 6.7-inch display set. This maintains the 19.5:9 aspect ratio that has defined the iPhone experience since the transition away from the notch toward the Dynamic Island.

Mapping Table: Which Sizes Cover Which Devices?

Apple uses a "downscaling" logic. They want you to provide the highest resolution for a specific aspect ratio family, and they handle the rest. Understanding which "Master" set covers which "Child" device is the key to not overworking your design team.

Mandatory Display Set Required Resolution (Portrait) Devices Covered (Auto-scaled)
6.7" iPhone 1290 x 2796 px iPhone 16 Pro Max, 15 Pro Max, 14 Pro Max, 16 Pro, 15 Pro, 14 Pro, 13, 12, 11, XR
5.5" iPhone 1242 x 2208 px iPhone 8 Plus, 7 Plus, 6s Plus, iPhone SE (2nd & 3rd Gen)
12.9" iPad 2048 x 2732 px All iPad Pro models, iPad Air, iPad Mini, Standard iPad

The 6.7-inch Mapping Logic

Apple’s scaling algorithm is surprisingly decent, but it follows a strict hierarchy. When you upload a 6.7-inch screenshot, App Store Connect essentially tells the 6.5-inch and 6.1-inch sections: "Use the big one." This works because the aspect ratios are identical or nearly identical across these models.

However, the 5.5-inch set is a different beast. Because it uses a 16:9 aspect ratio compared to the 19.5:9 of modern iPhones, Apple cannot "map" or scale your 6.7-inch screenshots to the 5.5-inch slots. If you try to force it, the images will either be rejected for incorrect dimensions or look horribly squashed. This is where tools like AppMockup become essential—they can take your raw screen captures and instantly wrap them in both 6.7-inch and 5.5-inch device frames with the correct padding and background ratios.

It's worth noting that the 6.5-inch display set (1242 x 2688 px) is now entirely optional. Unless your app has a specific UI bug that only appears on the iPhone XS Max, there is zero reason to spend time creating these assets manually in 2026.

Editorial Opinion: Why 'Auto-Scaling' is a Trap for Pro Apps

We’ve all done it. You’re tired, it’s 2 AM, and you just want to ship the update. You upload the 6.7-inch screenshots and let Apple scale them down to the 6.1-inch devices. On paper, it looks fine. In practice, it can be a conversion killer.

The "Fuzzy Text" problem is real. When Apple downscales a high-resolution 6.7-inch screenshot to fit a smaller 6.1-inch screen (like the standard iPhone 16), small UI elements and captions can lose their crispness. If your marketing strategy relies on "fine print" or detailed data visualizations in your screenshots, that text often becomes unreadable. A user scrolling through the App Store on a smaller device isn't going to squint; they're just going to keep scrolling.

Then there’s the Dynamic Island/Notch issue. Apple’s auto-scaling doesn’t always account for how elements interact with the top of the screen across different models. We’ve seen instances where a 6.7-inch screenshot looks perfect, but once scaled and viewed on a device with a slightly different "safe area," the Dynamic Island or the status bar overlaps with the marketing title.

The Professional Approach: If you're managing a high-LTV (Lifetime Value) app—think FinTech, SaaS, or Pro-level creative tools—don't trust the auto-scaler for your primary locale. Use AppMockup to generate specific sets for the 6.1-inch display. It takes an extra minute but ensures your typography is sharp and your layout is intentional, not accidental. A half-blurry screenshot screams "unpolished," and users won't trust an unpolished app with their data or money.

The iPad Exception: 12.9-inch is the King

If your app is "Universal" (meaning it runs on both iPhone and iPad), you hit a new wall of requirements. The iPad screenshot situation is actually simpler than the iPhone one, but much more punishing if you ignore it.

The 12.9-inch iPad Pro (specifically the 6th and 7th Gen models) is the mandatory display set. Even in 2026, with the introduction of newer M4 and M5-powered iPad Pro models, the 2048 x 2732 pixel resolution remains the submission standard.

Unlike the iPhone, where you have a few different aspect ratios to juggle, the iPad ecosystem is very consistent. One set of 12.9-inch screenshots will cover:

  • The 11-inch iPad Pro
  • The iPad Air (all sizes)
  • The iPad Mini
  • The standard entry-level iPad

The challenge most developers face is that iPhone screenshots are 9:16 (or 9:19.5), while iPads are 3:4. You can't just "stretch" an iPhone screenshot to fit an iPad. It looks amateurish. This is a common point of failure during the App Store review process; Apple will often reject apps if the iPad screenshots are clearly just blown-up iPhone images with black bars on the sides.

To solve this without redesigning everything, you can use the AppMockup iPhone-to-iPad converter. This tool takes your existing iPhone mockups and intelligently extends the background and repositions the text to fit the 3:4 iPad ratio. It’s a "one-credit" fix that saves hours of manual layout adjustments in Figma.

Common 'Missing Metadata' Error Triggers

You’ve uploaded the right sizes, but you’re still getting errors. We’ve been through this dozens of times. Here are the most likely culprits for why your "Display Sets" are being flagged as invalid in 2026.

1. The Alpha Channel Headache

This is the #1 cause of "Invalid Binary" or "Invalid Image" errors. Apple’s ingest system hates transparency (alpha channels) in screenshots. If you export your PNGs from a design tool with "Transparent Background" checked—even if the image looks solid—the upload will fail. Ensure your screenshots are flattened, 24-bit RGB PNGs. Most AI-powered generators like AppMockup handle this automatically, but if you're doing it manually, double-check your export settings.

2. Localized Screenshot Mismatches

If your app is available in 10 languages, you need 10 sets of screenshots. A common mistake is uploading the 6.7-inch set for "English (U.S.)" and then forgetting to do the same for "French" or "Japanese." App Store Connect will show a green checkmark next to the English metadata, but the overall "Version" will stay in "Missing Metadata" because the other languages are empty.

Pro Tip: Apple does allow "Global" screenshots, but only if you haven't started localizing the text. Once you add a second language to your app's listing, you are committed to providing localized assets for that language.

3. The 'Media Manager' Sync Delay

Sometimes you upload the 6.7-inch screenshots, but the 6.1-inch slots don't update immediately. This is often just a caching issue in App Store Connect. Before you panic and start uploading 6.1-inch assets manually, try refreshing the page or checking the "Use 6.7-inch Display Set" checkbox (if it’s not already ticked). Honestly, the App Store Connect UI can be incredibly buggy—don't assume the error is on your end until you've refreshed the browser twice.

4. Incorrect Safe Areas

Apple’s reviewers sometimes reject screenshots if the "marketing text" is obscured by the device's physical hardware in the preview. In 2026, with the Dynamic Island being standard, make sure your titles are at least 150 pixels away from the top of the image. If your text is too high, it looks like the hardware is "eating" your message. It’s a small detail, but Apple’s review team is notoriously pedantic about "professionalism."

Final Checklist for 2026 Submissions

To ensure your app moves from "Prepare for Submission" to "Waiting for Review" without a hitch, follow this sequence:

  1. Generate the 6.7" set (1290 x 2796): These are your primary marketing assets for modern iPhones.
  2. Generate the 5.5" set (1242 x 2208): These satisfy the legacy requirement for older devices.
  3. Check for Alpha Channels: Ensure all PNGs are flat with no transparency.
  4. Verify Localization: If you support multiple languages, ensure every language has its mandatory sets uploaded.
  5. iPad Check: If universal, upload the 12.9" set (2048 x 2732).

Managing display sets is a tedious part of the App Store lifecycle, but it's the gateway to your users. By focusing on the 6.7-inch and 5.5-inch sets and being smart about how you scale them, you can maintain a professional presence without losing days to repetitive design work. If you're looking to speed this up, a tool like AppMockup can automate the resizing and framing, letting you get back to what actually matters: building your app.

"The difference between a successful launch and a week of 'Missing Metadata' errors is often just a few pixels. Don't let the 5.5-inch legacy requirement catch you off guard in 2026."

Sources and References

Frequently Asked Questions

Is the 6.1-inch screenshot size mandatory?

No. In 2026, the 6.1-inch display set is optional if you provide the 6.7-inch set. Apple will automatically scale your 6.7-inch screenshots to fit 6.1-inch devices. However, you may want to upload custom 6.1-inch screenshots if your UI text becomes hard to read when downscaled.

Can I use the same screenshots for iPhone and iPad?

No. iPhone and iPad have different aspect ratios (19.5:9 or 16:9 for iPhone vs. 3:4 for iPad). Uploading iPhone screenshots to the iPad display set will usually result in an error or a rejection during the review process. Use a converter to adjust the background and layout for iPad dimensions.

What is the best format for App Store screenshots?

The best format is a high-quality PNG. It must be in the RGB color space and cannot contain any alpha channels (transparency). JPEGs are technically accepted but often result in compression artifacts that look unprofessional on high-resolution Retina displays.

Ready to create professional app store screenshots?

Try AppMockup Free →
← Back to Blog App Store Generator Play Store Generator