App Store listing checklist before submission

Check metadata and keywords

Read the name, subtitle, description, and localized fields together. Remove outdated claims and confirm each keyword and category accurately describes the app.

Review screenshots and preview video

Check every required device slot, screenshot order, caption, and video export. Make sure the first images explain the app and that the assets show current product behavior.

Confirm age and privacy information

Recheck the age rating answers, privacy disclosures, and any required product details against the current app build. Keep the listing consistent with the app’s actual data practices.

Validate each localization

Review copy, screenshot text, line breaks, and RTL behavior for each submitted locale. Confirm that the intended assets are assigned to the matching storefront.

Test the upload before release

Upload the final set in App Store Connect and resolve validation warnings or errors. Keep a record of source files and verify the submitted version after processing.

Final submission pass

Open the processed version in App Store Connect and verify the actual uploaded assets, not just the files in the local export folder. Check locale assignments, display slots, ordering, and any processing errors.

Compare every promotional statement with the current binary. Screenshots should not imply unavailable content, old pricing, unsupported device behavior, or a feature that was removed from the submitted version.

Keep a traceable asset record

Save the source design, export date, target locale, and destination slot alongside the final set. If review asks for a change, the record makes it possible to rebuild the correct image without guessing which file was submitted.

Verify version-specific details

Check that preview video and screenshots use the submitted interface, and that pricing, subscription language, and availability claims match the app and storefront. Remove temporary staging content and test accounts from all captures.

Confirm the current App Store Connect fields and review rules for the particular release. A previous approved listing is not proof that a changed feature or new locale still meets the requirements.

Run the final locale audit

For each locale, verify the intended text, screenshot order, line breaks, and direction. Confirm the storefront points to the right localized assets after processing rather than assuming the upload order is preserved.

Keep source files and the final upload list together. This gives the reviewer and release owner a simple way to track any asset that has to be corrected.

A last pass on accuracy

Compare the store images with the exact submitted build and remove staging labels, test account details, expired promotions, or UI that no longer exists. Check that screenshots do not promise a feature that is still behind an unavailable rollout.

Review metadata and assets in the target locales after processing. Correct source files are not enough if the wrong language or device set was assigned in App Store Connect.

Keep submission evidence together

Save the asset list, locale coverage, validation notes, and release version with the submission record. If the review team requests a change, this provides a clear reference for the exact item that needs revision.

Check screenshots at their final upload size

Inspect each exported file at its actual pixel dimensions and again as a small store preview. Confirm the type stays legible, the first image makes sense without zooming, and no text or interface control is cut off.

Keep a list of the version, device slot, and locale for each export. This makes it easier to replace the exact image if App Store Connect reports a problem during processing.