Link copied!
Guides·Updated ·3 min read

“Please Save New Locales” in App Store Connect

The error is literal: the language you just added is not on Apple’s server yet. Save the locale, then upload screenshots. Here is the order that stops the loop.

Lavender editorial thumbnail of a globe with a save check, a locale card, and stacked screenshot frames

Quick answer

How do you fix “Please save new locales before uploading screenshots or previews”?

Stop uploading. Add the language from the version-page language menu, enter the required localized metadata (description and keywords are not copied from the primary language), click Save, wait for the page to persist, then upload screenshots or previews. If the banner remains after a real save, open View All Sizes in Media Manager and upload there. The locale has to exist on the server before media can attach to it.

  • Add the locale, fill required metadata, click Save — then upload
  • Description and keywords do not inherit from the primary language
  • Media Manager is the workaround when the version page still blocks you
  • You do not need to save again for later uploads to an existing locale
  • Prepare localized screenshot files before you open Connect
On this page

The banner is not a broken Media Manager. App Store Connect created the language in your tab when you clicked +. Screenshot and preview uploads go to a different endpoint that will not attach files to a locale that has not been saved. If you drag a PNG in first, you get exactly the sentence Google is showing you: please save new locales before uploading screenshots or previews.

Apple’s order is in Localize app information : add the language, enter localized metadata, click Save. Screenshots for extra sizes and locales go through Media Manager .

The order that actually works

Add a locale and upload screenshots without the banner

Do this on an editable version. You need a role that can edit app information.

  1. Add the language from the version page

    Open the platform version. Use the language menu at the top right, scroll to Not Localized, and click + beside the locale.

  2. Fill description and keywords

    Apple does not copy description and keywords from the primary language. A locale that cannot save empty will sit in limbo and keep blocking media.

  3. Click Save and wait

    Do not upload yet. Wait until the page confirms the save. The locale now exists on the server.

  4. Upload screenshots or previews

    Stay on the locale. Drop files in the version wells, or click View All Sizes in Media Manager and upload per device size.

  5. If the banner stays, use Media Manager

    Open View All Sizes in Media Manager, pick the locale and device tab, and replace or add files there. That path is what unblocks teams after a save that the version wells still ignore.

Why Connect is this picky

When you add a language, screenshots and most properties default to the primary language — except description and keywords. The UI looks ready. The locale is not committed until Save. Media uploads cannot target a draft locale. That is the whole bug report.

What inherits when you add a language
Copies from primary languageYou must enter
Screenshots and most properties, until you override themDescription
Name and subtitle if you leave themKeywords

Apple’s localize-app-information help is explicit: description and keywords do not default from the primary language. Fill them or you cannot save the locale.

Custom Product Pages need their own screenshots

If the app has a Custom Product Page, Apple requires screenshots in that language for each custom page before you can make the language the primary language. Upload the default set and the CPP set after the locale is saved. See Custom Product Pages.

Prepare the files before you open the well

The error is a save-order problem. The follow-on rejection is usually the wrong pixel size or a caption that overflowed in German. Export the locale from a real screenshot set — how to localize App Store screenshots — and keep current screenshot sizes next to the upload.

Save-locales questions

I already clicked Save. Why do I still see the error?

Confirm the locale is selected and that description and keywords are filled. Reload the version page. If the banner remains, open View All Sizes in Media Manager and upload from that screen. Teams regularly report that Media Manager accepts files the version wells still reject.

Do I have to save before every screenshot upload?

Only after you add a new locale. Once the language exists, you can replace screenshots on that locale without saving a new language first. After App Review approves a version, you need a new version to change screenshots.

Does this happen on Google Play too?

Play’s listing translations are a different console. This banner is App Store Connect wording. Play still wants the locale created before you attach store-listing graphics, but the error string is Apple’s.

Can a tool upload around the error?

Any API or uploader still needs the locale to exist. AppGrowthKit prepares and exports the localized screenshot files. You save the locale in Connect, then upload. We do not publish directly to App Store Connect.


Sources, verified 2026-09-19:

Free tools that help here

Save the locale. Then upload a set that fits.

AppGrowthKit localizes screenshot copy for 42 App Store locales on the same editable canvas, then exports the sizes Connect expects — so you are not designing in the upload well.

Try AppGrowthKit for Free