Introduction

Screenshots are part of your App Store presentation, but once an app version is already approved and live, they are no longer freely editable on that version. The historical name was iTunes Connect, but the current tool is App Store Connect, and the workflow is still version-based.

What changes after approval

For a live approved app, the main product page screenshots belong to an app version. In practical terms, that means you cannot simply open the live version and replace screenshots whenever you want.

The usual path is:

1. create a new app version record in App Store Connect
2. upload the updated screenshots to that new version
3. submit the version for review

If the app is still in an editable state such as Prepare for Submission or Metadata Rejected, screenshots can be changed directly on that pending version. The restriction mainly applies once the version has already been approved and is no longer editable.

Why Apple treats screenshots this way

Apple reviews the product page as part of the app submission. Screenshots are not just decorative assets; they are considered customer-facing metadata tied to what the app does and how it is represented.

That is why screenshot changes are generally handled through a new submission rather than as an always-live edit. It keeps the marketing material aligned with the version users can actually download.

A practical workflow

The operational workflow is straightforward:

1. open the app in App Store Connect
2. create the next version number
3. upload the new screenshots for each required device size and localization
4. submit the new version for review

Even if your code change is small, the screenshot update is still associated with that new version entry.

If you are preparing screenshots locally, command-line capture tools can help you generate consistent image sets. For example, on macOS you can capture simulator screenshots like this:

xcrun simctl boot "iPhone 16 Pro"
xcrun simctl io booted screenshot ./screenshots/en-US/home.png
xcrun simctl io booted screenshot ./screenshots/en-US/settings.png

Teams that automate asset preparation often pair that with Fastlane for organized uploads during release prep:

bundle exec fastlane snapshot
bundle exec fastlane deliver

Those commands do not bypass review. They only help you generate and upload assets for the version you are submitting.

What to update and what to verify

When replacing screenshots, check more than image dimensions:

• device sizes must match Apple's accepted slots
• localized screenshots should match localized text
• screenshots should reflect the current UI, not a future unreleased flow
• if you changed ordering only, review whether that counts as a new approved metadata state for your workflow

The last point matters because App Store Connect has a few metadata nuances, but the safe general answer for replacing screenshots on an approved live version is still to create a new version and resubmit.

Using automation carefully

Fastlane can save time, but it should support the release process rather than hide it. A simple Snapfile keeps screenshot generation repeatable:

1devices([
2  "iPhone 16 Pro",
3  "iPad Pro 13-inch (M4)"
4])
5
6languages([
7  "en-US"
8])
9
10scheme("Runner")

That helps you generate consistent screenshots across releases, but you still review the assets before submission so the product page remains accurate.

Common Pitfalls

The biggest mistake is assuming screenshots behave like promotional text or some other metadata that can sometimes be edited more freely. For an already approved live version, screenshots are generally versioned and require a new version workflow.

Another issue is updating screenshots that show features not yet available in the binary under review. That can trigger review problems because the product page no longer matches the app users receive.

It is also easy to forget localization coverage. Uploading only English screenshots while claiming support for several storefront languages produces a weak and inconsistent listing.

Finally, do not rely on the old iTunes Connect name when searching for current documentation. The product is App Store Connect now, and Apple documents current editing states there.

Summary

• After an iOS app version is approved and live, its screenshots are not usually editable in place.
• The standard fix is to create a new app version in App Store Connect and upload the new screenshots there.
• Screenshot updates should match the actual user experience in the submitted build.
• Tools such as xcrun simctl and Fastlane help prepare assets, but they do not bypass review.
• If the app version is still in an editable status, you can change screenshots directly on that pending version.