Release notes locale template generator.

Why localized release notes matter

Release notes ("What's New" in App Store Connect) are not indexed for App Store search — the name, subtitle, and keyword field do that work. But release notes affect conversion in three concrete ways:

• Users who open your App Store page and tap Version History read them. For utility apps, that click-through rate is meaningful.
• Update prompts in the App Store app show the What's New entry inline. A localized entry in Japanese or German looks native; an English entry to a non-English user reads as a missing localization.
• For apps with in-app update prompts powered by App Store Connect API data, release notes drive the copy users see on the first launch after updating.

Apple's fallback behavior

If you do not provide a localized What's New for a given locale, Apple displays the entry from your default locale (usually en-US). The version itself is still available in every territory — only the release notes text falls back. That's why many teams ship release notes in only their top 5-10 markets and let the rest fall back.

Machine translation — when it works, when it doesn't

Short, concrete feature bullets generally translate well via MT (DeepL, Google, Apple's own translation APIs). Longer marketing copy with tone, humor, or metaphors does not. A safer middle ground:

• Use MT on your structured template to seed the translation.
• Have a native speaker review, or at minimum back-translate into your source language to spot semantic drift.
• Keep bullets short and concrete — they MT better and read better in every language.

Structure recommendations

• Lead with the most user-visible change. "New biomarker charts" before "Improved memory handling on older devices."
• Bullet points beat paragraphs. Users scan release notes, they don't read them.
• Name features the same way the app names them. If the settings screen says "Sync", call it Sync in release notes — not "Synchronization" or "Cloud sync."
• Don't advertise unreleased features. If a feature is being A/B-tested or is gradual-rollout, it will confuse users who don't see it.

What App Store Connect locales actually cover

App Store Connect supports a fixed list of localization locales for metadata — around 40 in 2026. They do not map 1:1 to App Store territories. A Portuguese-language user in Brazil sees metadata from the pt-BR locale; the same user in Portugal sees pt-PT. This tool uses the exact locale codes App Store Connect accepts in its API (for example, en-US, zh-Hans, pt-BR) so the generated template keys match what the API expects when you submit release notes programmatically.

Which locales are worth the effort

For most apps, the highest-ROI locales are the ones where your app already has an existing install base or where you plan active marketing. Generic starter set: en-US, zh-Hans, ja, de-DE, fr-FR, es-ES, pt-BR, ru, ko. For EU-focused apps, add it, nl-NL, pl, sv. For emerging markets, id, hi, th, vi. Adding a locale for a market where you have no users and no marketing generally won't move the needle, even with a perfect translation.

Frequently asked questions

Does the App Store fall back to English if I don't provide release notes in a locale?

Yes — Apple falls back to your default locale's What's New entry. This is why adding a locale with only half the metadata filled still works, though the result is mixed languages on the product page.

How many locales does the App Store support for release notes?

Roughly 40 localization locales in 2026. This tool lists the full current set.

Should I use machine translation for release notes?

MT is fine for structured feature lists but should have a native review pass before publishing. Don't ship un-reviewed MT to paying customers.

Do release notes affect App Store search ranking?

No — they are not indexed for search. They affect conversion, not discovery.