01 / Apple requirements
Prepare both iPhone Duo displays
The iPhone Duo slot has four accepted sizes: 2007 × 2853 and 2853 × 2007 for the inner display, plus 1398 × 2034 and 2034 × 1398 for the outer display. The inner and outer sizes form one requirement group.
The dedicated Duo screenshots are optional for now. Apple can show scaled large-iPhone screenshots when they are absent; they become required from April 2027 for apps built with the iOS 27.1 SDK or later. Use dedicated artwork when the foldable layout or outer display tells a different story.
- Inner portrait: 2007 × 2853.
- Outer portrait: 1398 × 2034.
- Landscape uses the same dimensions reversed.
02 / Apple requirements
Start with the supported device families
Apple’s current reference covers iPhone, iPad, Mac, Apple TV, Apple Vision Pro, and Apple Watch. The table above keeps every documented slot and accepted pixel size together instead of reducing the requirement to one phone and tablet preset.
The downloadable JSON and CSV contain the same dimensions, orientation labels, conditional requirements, and scaling notes. Use them in a release checklist or internal validation script, and re-check the source date before treating them as permanent.
- Use JPEG, JPG, or PNG.
- Provide from one to ten screenshots for a selected Apple slot.
- Do not use transparency or an alpha channel.
03 / Apple requirements
Know which iPhone size Apple requires
Apple now names iPhone slots by display type instead of inches. Its summary of required sizes asks for at least one screenshot for iPhone with Dynamic Island (medium display): 1206 × 2622 or 1179 × 2556 in portrait. Its device table still describes the Face ID (large display) slot, formerly 6.5-inch, as required when no Dynamic Island (large display) screenshots are uploaded.
Uploading the Dynamic Island (medium display) size meets the summary. Adding Dynamic Island (large display) screenshots, formerly 6.9-inch, covers the Face ID (large display) slot through scaling.
04 / Apple requirements
Use scaling only when the interface is genuinely the same
Apple says a highest-resolution required screenshot can scale down to smaller device sizes when the interface is the same across those sizes and localizations. This reduces duplicate work, but it is not permission to show the wrong interface or let important copy crop badly.
Use Media Manager when a device family or language needs custom artwork. Review the longest localized headline at the narrowest selected output before relying on a shared composition.
05 / Apple requirements
Stay inside Google Play’s shared limits
Google Play does not use exact slots. Each screenshot has to be a JPEG or 24-bit PNG without alpha, 320 to 3,840 px per side, with the long side no more than twice the short side. You can add up to eight per device type and need at least two across device types to publish.
For recommendation formats, Google asks apps for at least four screenshots at 1080 px or more: 1920 × 1080 in landscape or 1080 × 1920 in portrait. The 1024 × 500 feature graphic and the 512 × 512 app icon are required as well.
06 / Apple requirements
Export PNG for the Microsoft Store
Partner Center accepts PNG screenshots only, up to 50 MB each, in landscape or portrait. Desktop screenshots start at 1366 × 768 and can be 4K. You can upload up to ten desktop screenshots, and one screenshot in any device family is enough to publish.
Add a caption of up to 200 characters to each screenshot. Microsoft’s FAQ calls a Store logo mandatory, so prepare the 1:1 box art at 1080 × 1080 or 2160 × 2160 with the screenshots.
- Use PNG, not JPEG.
- Keep each file under 50 MB.
- Start desktop screenshots at 1366 × 768.
07 / Apple requirements
Validate the exported files as a set
A correct canvas preset does not prove that the exported file still has the right dimensions, encoding, transparency, and count. Validate the finished images, then inspect the complete language-and-size matrix for omissions.
Screen Studio Kit keeps captures, copy, frames, and backgrounds editable across output presets. Its preflight can flag missing translations or assets and likely overflow before deterministic PNG or JPEG batch export.
- Check the files after export.
- Review every selected language and size.
- Keep one editable source project for future updates.
