Skip to main content

App Store Connect

How to fix "Please save new locales before uploading screenshots or previews" in App Store Connect

Verified against the primary sources below on

The error

Please save new locales before uploading screenshots or previews.

How to fix it

  1. Save the version page, then reload

    The banner sits in the Previews and Screenshots section, but the Save it asks for is the page-level button at the top right of the version page. Click it even when nothing looks edited, then reload the page and upload again.

    It costs ten seconds, and it is the only fix here that needs no diagnosis.

  2. Find the language that was added but never saved

    Open the language menu at the top right of the version page and walk through each language. Apple's steps for adding a language end with entering its metadata and clicking Save. A language that stopped short of that is the most direct reading of "new locales".

    Apple keeps two sets of localized fields, each with its own Save:

    • The version page: description and keywords for that language, per platform.
    • App Information: the app name and privacy policy URL for that language.

    Apple also notes that a localization added from the version section is added to the shared metadata under App Information and to your other platforms. A language you added while editing the iOS version can therefore show up on the macOS version, where it still needs its own description and keywords.

  3. Upload once, on the primary language, when the images are the same

    You may not need a per-language upload at all. Apple states that screenshots for a new language default to those of the primary language, and that if your app's interface is the same across device sizes and localizations, you provide only the highest resolution screenshots required.

    Upload the set on the primary language. The other languages pick it up. Open a specific language in Media Manager only when its screenshots actually differ, for example when the captions are translated into that language.

  4. One language and nothing to save: wait before rebuilding anything

    On an app with a single language there may be no new locale to find. A developer on the Apple Developer Forums hit this message on a macOS update with only en-US configured, after creating the new version from the Distribution page. By the next day the screenshot had appeared in the draft submission with no change on their side, and the update went through.

    Leave the languages alone while you wait. Removing a language and adding it back creates exactly the unsaved new locale the message is about. Reload later that day and again the next morning before changing anything.

Why this happens

This blocks the upload inside App Store Connect, before anything reaches App Review. Screenshots that upload and are then refused at review are a different gate, covered in the screenshot rejection guide.

Apple does not document this message. Its help pages cover adding a language, saving its metadata and uploading media, and none of them mention this banner, so any cause offered for it is a reading, not a rule.

Read literally, it says the page holds a language App Store Connect has not stored yet. Screenshots and previews can be set per localization, so an upload has no language to attach to until that locale is saved. That fits the case where a language was added and never saved, and step 2 resolves it.

It does not fit the reported one-language case, where nothing was added and nothing was saved, and the block still cleared. That points at the version page and App Store Connect briefly disagreeing about which languages exist, which in that report happened right after a new version was created. Step 4 is the honest instruction for it: reload, wait, change nothing.

When your screenshots genuinely differ per language because the captions are translated, each saved locale needs its own set uploaded. Translating a finished set produces those for any of the 50 App Store languages, right-to-left scripts included.

Sources

Go deeper

The rule behind it

Related guides