Prepare your required iPhone screenshot set at 1206×2622 or 1179×2556, and you can avoid discovering a missing device class after exporting every localization.
The trap is treating “latest iPhone” or “6.9-inch” as a complete screenshot specification. Those labels can lead you to a valid large-display export while leaving the required medium-display set unprepared.
The practical fix starts with two checks: which device class needs the image, and which pixel dimensions that class accepts.
Requirements below were checked against Apple’s documentation on November 16, 2026. This example uses portrait screenshots throughout.
Match the official device class before choosing a canvas.
Apple’s current required-device-size list calls for at least one screenshot for iPhone with Dynamic Island (medium display). For apps supporting iPadOS, it also requires at least one screenshot for iPad 13-inch display.
These are the relevant portrait dimensions:
| Apple device class | Accepted portrait dimensions | In the required-device-size list? |
|---|---|---|
| iPhone with Dynamic Island (medium display) | 1179×2556 or 1206×2622 | Yes |
| iPhone with Dynamic Island (large display) | 1260×2736, 1290×2796, or 1320×2868 | No |
| iPad 13-inch display | 2064×2752 or 2048×2732 | Yes, if the app supports iPadOS |
Source: Apple’s screenshot specifications.
A template called “6.9-inch” commonly points to 1320×2868 in the large-display class. A “6.3-inch” template at 1206×2622 maps to the medium-display class. Carry the official class name and pixels into your release notes; an inch label alone leaves room for confusion.
Worked example: nine finished images, one missing target.
Consider a fictional release with three screenshots in each of three locales: US English, German, and Japanese.
You finish the artwork on a 1320×2868 canvas. Every language looks good, the sequence is consistent, and the export contains nine images.
Then App Store Connect asks for the medium Dynamic Island set. Your exported files belong to the large-display class.
This is a target mismatch. The captions may be approved and the artwork may be finished, but the required output still needs preparing.
A second mistake can happen during recovery: you export 1206×2622 correctly, then drop those files into the large-display slot because that is the tab you already had open. The new image has the right dimensions for medium Dynamic Island; the selected destination expects a different set of dimensions.
Treat the destination and the file as a pair.
1. Keep the large-display artwork and add the required output.
Preserve your editable composition and approved copy. Keep the existing 1320×2868 files separately if you intend to use them for large-display coverage.
For this example, choose 1206×2622 for the medium-display output. The alternative 1179×2556 is also accepted; choose one and use it consistently for this set.
Record the decision explicitly:
- Required iPhone target: iPhone with Dynamic Island (medium display).
- Selected portrait output: 1206×2622.
- Additional large-display output, if retained: 1320×2868.
That small record helps keep the next export, review, and upload aligned.
2. Render the composition at the target dimensions.
Return to the editable layout and generate the medium-display version from there.
Changing a filename cannot change an image’s dimensions. Changing resolution metadata cannot turn a 1320×2868 image into a 1206×2622 image either.
Avoid forcing the finished image into the new rectangle by stretching it. That can distort the app UI, typography, and device frame together.
A deliberate resize or crop may be usable, but inspect the result. Rendering from the editable composition gives you control over text wrapping, screenshot placement, margins, and the space around the main feature.
The acceptance check is exact pixels. The design check is whether the image still communicates clearly.
3. Review every locale on the medium canvas.
Approval at 1320×2868 does not establish approval at 1206×2622.
Check the headline and subtitle again at the new output size. Depending on your layout, a line may wrap differently, a subtitle may crowd the screenshot, or a caption may lose the breathing room it had on the original canvas.
Suppose the German headline now occupies three lines where the English headline occupies two. Decide whether that composition still works. Adjust the layout, or have the wording revised through your normal translation process.
For Japanese, inspect line breaks and punctuation placement as well as whether the text fits.
Review all three screenshot positions in each locale. The first image looking good does not establish that the remaining images are ready.
4. Check the exported files themselves.
For the example release, the medium-display set contains nine images: three positions multiplied by three locales.
Open the final files and check their actual pixel dimensions in an image inspector. Do this after export, while you can still connect each file to its source composition.
Confirm that each image has:
- The intended 1206×2622 dimensions.
- The matching locale’s approved headline and subtitle.
- The correct app screenshot and sequence position.
- No clipped text, accidental crop, or unwanted distortion.
Keep medium and large outputs clearly separated. A folder named “final iPhone” is less useful than one that identifies the device class and dimensions.
5. Match the upload destination again.
Before selecting files in App Store Connect, read the active device class.
For the medium Dynamic Island slot, select the medium-display exports. For an additional large-display set, select files accepted by that class.
If a 1206×2622 image is rejected while the large-display slot is open, compare the destination with the table before rebuilding the artwork. You may already have the correct medium-display file.
Apple also documents class-specific scaling and fallback rules. Those notes deserve attention when reviewing existing assets, but they do not make every accepted dimension interchangeable between upload slots.
Read “highest required resolution” carefully.
Apple’s display-scaling guidance is conditional: when the UI is consistent across sizes and localizations, screenshots at the highest required resolution can serve smaller sizes through App Store Connect’s scaling.
The key phrase is “highest required resolution.” Choosing the biggest available canvas does not establish that you have prepared the required class.
Use the required-device-size list to plan the essential outputs, then decide which additional device-specific sets your app needs.
Include the tablet target when applicable.
If your app supports iPadOS, add the required iPad 13-inch set to the same planning record. Review its composition separately; a tablet canvas deserves its own layout check.
Apple also notes that, starting in April 2027, iPhone Duo screenshots will be required for apps using the iOS 27.1 SDK or later. Recheck the official specifications when preparing that release.
A focused check before the next export
- [ ] Required iPhone class recorded as medium Dynamic Island.
- [ ] Portrait output selected as 1206×2622 or 1179×2556.
- [ ] Optional large-display files kept identifiable.
- [ ] Every locale reviewed at the selected output size.
- [ ] Final image dimensions inspected after export.
- [ ] Upload destination matched to those dimensions.
- [ ] Required iPad coverage included when applicable.
Disclosure: I build ScreenParcel. It combines app screenshots with your own translated headlines and subtitles, previews overflow per locale and size, and exports one ZIP organized by locale and size. You can select or deselect sizes, including “iPhone · medium Dynamic Island” at 1206×2622. It does not auto-translate or upload to App Store Connect.
Two locales are free with a watermark. The Release Pack is $9, and the 30-day Pass is $19.
Top comments (0)