What to know

Apple accepts one to 10 screenshots in JPEG, JPG, or PNG format. The current size rules depend on the device family and display size, so check Apple’s specification table before exporting a final set.

Start with the highest-resolution screenshots Apple requires for the devices your app supports. A current specification table may change as Apple adds devices or display sizes. Do not copy a pixel number from an old blog post into a new release without checking Apple’s page.

Use the device family, display size, orientation, pixel dimensions, file type, locale, and upload status as separate checklist fields. If a screenshot is scaled or cropped, confirm that the interface still proves the same feature and that text remains readable.

When App Store Connect reports wrong dimensions, compare the exported file with the exact device row in Apple’s table. Check width and height order, portrait versus landscape, file extension, and whether the design tool exported a different canvas than the one you reviewed.

Keep the creative review separate from the file review. A correctly sized image can still be a weak first screenshot. After the technical check, read the screenshots in sequence and confirm that each one adds a new piece of proof.

Store the final files with the device family, locale, export date, and source-table date. Recheck the set after a device update or a redesign. This creates a small evidence trail when a reviewer asks which assets were uploaded.

Use a fixed debug order when an upload fails: identify the device family, open Apple’s current row for that display size, inspect the actual exported width and height, confirm orientation, check the file type and color profile, and export again from the reviewed canvas. Do not resize by guesswork until the source row is clear.

Keep a contact sheet for the final set with the filename, locale, device target, message, and build screen shown. This helps catch a technically valid image that belongs to the wrong locale or shows a feature that is no longer in the submitted build.

Run the file checklist before the creative approval, then run the sequence review again after any resize or localization change. A new export can fix dimensions while changing text legibility, cropping, or the visual proof. Save the final checksum or version label with the upload record when the team needs repeatability.

When a tool reports a dimension error, preserve the original export and record the failed filename, target row, measured dimensions, and corrected output. This makes the fix repeatable and helps distinguish a wrong canvas from a wrong device target or a later resize step.

Review the screenshots at the size a visitor will actually see them. Check headline contrast, safe margins, small labels, localization expansion, and whether the interface state supports the caption. Technical acceptance is only the first gate. The image still needs to communicate a real product benefit.

Keep the upload record connected to the approved build and locale. If a screen, feature name, or device layout changes, reopen the contact sheet and message map before reusing the asset. A stable filename is not proof that the image still represents the current product.

Create one asset-manifest row before upload: filename, device target, orientation, pixel dimensions, file type, locale, build screen, message, source-table date, and reviewer. Compare the measured file with the intended row rather than trusting a design-tool preset or filename.

Run a mismatch check across the whole set before opening App Store Connect. Look for a portrait image assigned to a landscape target, a localized file in the wrong slot, a stale build screen, or a resized export whose dimensions are right but whose caption or proof has changed.

Keep failed exports in a separate record instead of overwriting them. The original filename, measured dimensions, target specification, and corrected output show whether the issue came from the canvas, orientation, export step, or upload selection.

ASOgenic can help organize the asset checklist and keep a metadata draft connected to the release record. The final image export and upload still need a person to verify the current Apple requirements.