App Store screenshot sizes: iPhone and iPad upload requirements

App Store screenshot sizes for common iPhone and iPad slots

Pixel dimensions belong to the upload slot. Choose a listed portrait pair or its landscape equivalent; matching the shape alone is not enough. This table covers the five Apple targets in our checker. Apple’s reference includes other device classes and older sizes.

On a small screen, scroll the table sideways to see every column.

Apple accepts JPEG/JPG and PNG, from one to ten screenshots. Images must not contain alpha channels or transparency. Check the actual export, chosen language and current console validation before upload. Reference checked 2026-10-05: Apple screenshot specifications.

Check the pixel dimensions of your export

To inspect PNG/JPEG dimensions and alpha metadata, open the local file checker and choose the matching target. Selected files stay in your browser. A size or header match does not establish screenshot-set completeness, visual accuracy, file integrity or store approval.

Choose the upload slot before producing the whole set

Open the platform version and language you intend to edit. Record the iPhone or iPad slot, build and capture orientation in your asset brief. Those choices belong beside the export dimensions so a designer and developer can review the same target. A filename such as large-phone.png leaves the target uncertain. A name such as en-US_iphone69_onboarding_01.png is easier for your team to trace, although a filename never establishes the actual file size.

Apple’s table makes the 6.5-inch set conditional when a 6.9-inch set is absent, and requires a 13-inch set when the app runs on iPad. Check the platform your build supports before making an iPhone-only export plan. For a tablet app with a sidebar or a different reading layout, capture that layout and review its claims separately. Stretching a phone scene into a tablet canvas can produce a misleading presentation even when the exported pixels fit.

Inspect final pixels, orientation and transparency

An editor’s canvas dimensions and its export dimensions can differ. If a 1320 × 2868 canvas is exported at 2×, the resulting 2640 × 5736 file has the same proportions but does not match the chosen slot. Read the final width and height before renaming or uploading it. Keep the source file so you can correct the export setting rather than repeatedly resampling already exported artwork.

Landscape pairs reverse width and height. Check the encoded pixels as well as what an image viewer displays: a viewer can apply an orientation tag when showing a JPEG. Our checker does not apply JPEG EXIF orientation or decode the complete image. For PNG, an opaque-looking screenshot can still have an alpha channel. Use an export setting that removes the channel and inspect the new file; adding a solid layer alone does not establish how the exporter encoded it.

Review scaled sets in Media Manager

Apple’s upload guidance allows the highest required resolution to scale to smaller sizes when the interface is the same across sizes and localizations. Media Manager also lets you supply specific assets. Use that distinction to plan a manageable set, then inspect what each slot and language actually contains. A canvas-size checklist cannot tell you whether a translated caption is too small or whether a different layout changes the feature you are showing.

When replacing assets, keep an inventory of the language, device slot, screenshot order and current file. After upload, reopen the relevant slots and check the visible sequence. A fictional planner might replace its main English phone set while an older localized set still shows a removed calendar action. Reviewing every intended locale and set catches that inconsistency. Record any unresolved asset instead of assuming all pages changed because one upload finished.

Resolve an upload error with one controlled export

First identify the exact file, target slot and console message. Compare its final dimensions with that slot’s accepted pairs. If the size matches, inspect its actual format and alpha metadata, then read the current console validation for the remaining issue. Renaming another image format to .png does not convert its encoding. Work from the original capture or source design and export one replacement for the failing slot before repeating the whole batch.

Keep the failed file and its settings in a local test note. Change one relevant export setting, inspect the replacement and try the correct upload slot again. A matching header remains a limited check: the store may still reject an incomplete file or content that misrepresents the app. Our tool neither repairs images nor verifies that the compressed image data is intact. The console’s actual result is stronger evidence than a successful preflight message.

Use the accepted export to test the promise

Once the technical export is correct, review the screenshot at a small viewing size. Can someone identify the main task without reading the entire description? Does the caption agree with the visible screen and the released feature? Keep subscription, permission and account requirements understandable. A fictional travel notebook caption saying Save a trip should show the actual supported saving flow and its access boundary.

Ask a fresh participant what the first screenshot leads them to expect, then give them a focused task in the build. Save their private observation separately from your file checks and store reports. That comprehension exercise can expose confusing wording; it does not prove a conversion lift. For an eligible store experiment, preserve the original assets, treatment, language and measurement context in the ASO experiment brief. Choose the next edit from the evidence you obtained.

Your next steps

• Record the platform, locale, upload slot and accepted pixel pair.
• Inspect final exported dimensions, orientation, format and alpha metadata.
• Review every intended screenshot set and language in Media Manager.
• Keep the actual console outcome and comprehension observations separate.