How to localize your iOS app's App Store listing — the 2026 guide

Around 70% of iPhone users live outside the United States. If your App Store listing is English-only, you're effectively invisible to most of your potential market — and Apple's discovery algorithms know it. This is a practical walkthrough of what App Store localization actually involves, which of Apple's 30+ locales to start with, and the two ways to ship localized metadata: the manual workflow inside App Store Connect, and the one-click workflow we built because the manual one is broken.

Why localize at all

Three reasons, in order of importance.

Discovery. Apple's search algorithm matches users' device language to your listing's localized text. An iPhone set to Japanese will not surface your app for the query todo list — it will surface the apps that have localized their title, subtitle, and keywords field into Japanese. No localization, no impressions in that locale.

Conversion. Users browsing the App Store convert two to three times more often when the listing is in their native language. This compounds with the discovery boost — more visits, each with a higher conversion rate.

Editorial reach. Apple's regional editorial teams (Today tab, "New Apps We Love", category features) almost exclusively spotlight apps localized for that region. An English-only listing rules itself out of every editorial slot outside English-speaking markets.

What "localizing your App Store listing" actually means

App Store Connect treats each locale as a separate version of the metadata. For every locale you support, these fields are independently editable:

• App Name — 30 characters max. The single most important field for App Store search.
• Subtitle — 30 characters max. Second most important search field; visible under the app name.
• Keywords — 100 characters, comma-separated, hidden from users but heavily weighted by the search algorithm.
• Promotional Text — 170 characters, displayed above the description, editable without shipping a new app version.
• Description — 4000 characters. Long-form pitch.
• What's New — release notes shown for each version update.
• Support URL, Marketing URL — region-appropriate links if you maintain them per locale.

Two things to note up front. First, every character limit is enforced after translation — which is where naive Google Translate output tends to fall apart, because German and Finnish translations are notoriously longer than the English source. Second, the keyword field is invisible to users but search-critical, and it needs a fundamentally different translation approach than the visible fields. More on both below.

The 30+ App Store locales — which ones matter

Apple supports 30+ locales for App Store metadata. You don't need all of them on day one. A pragmatic rollout order by market size and ROI for most indie apps:

Tier 1 — start here

• Simplified Chinese (zh-Hans) — China is the second-largest App Store market by revenue.
• Japanese (ja) — high-revenue, low-competition for many categories.
• German (de-DE) — pays well, surprisingly underserved.
• French (fr-FR) — covers France plus most French-speaking Europe.
• Spanish — split into es-ES (Spain) and es-MX (Mexico + most of Latin America). They are different markets; do both.

Tier 2 — add when Tier 1 stabilizes

• Korean (ko)
• Italian (it)
• Portuguese — pt-BR for Brazil and pt-PT for Portugal are different
• Dutch (nl-NL)
• Russian (ru)
• Turkish (tr)

Tier 3 — long tail, but cheap to add

English variants (en-GB, en-AU, en-CA) — yes, localize them. The App Store ranks them as separate markets and they have different idioms. Plus Traditional Chinese, Arabic, Polish, Swedish, Norwegian, Finnish, Danish, Czech, Greek, Hungarian, Hebrew, Indonesian, Malay, Thai, Vietnamese, Ukrainian, and Romanian.

Tier 3 is real opportunity for indie apps — competition is light because English-speaking developers ignore these locales, and Apple's editorial teams notice when someone shows up.

The manual way Apple gives you

If you don't use a tool, the workflow looks like this:

1. Open your app in App Store Connect, navigate to App Information, click the language dropdown, add a new locale.
2. For each of the seven-ish fields, paste in the translated text. App Store Connect doesn't tell you the character count until you commit — so translations that were under 30 chars in English often overflow silently.
3. Repeat for every app version that needs new "What's New" text.
4. Repeat for every new locale.
5. Save. Switch context. Save again.

For one app, five locales, and four fields each, that's 20 fields multiplied by the time it takes to translate and paste each one. For Apple's full 30+ locale list, it's a multi-day project that goes stale the moment you change the source English text.

Most indie developers end up doing one of three things: skip localization entirely, localize once and never update, or use Google Translate, miss the character limits, and ship listings that read like a tourist menu. None of these are good outcomes — and the App Store algorithm punishes the third one disproportionately.

Common pitfalls when you DIY

A handful of traps worth knowing about even if you eventually use a tool:

• Brand names get translated. Generic translation engines will happily turn Slack into the Chinese word for "slack rope." Build a glossary of brand and product terms before you translate anything.
• Tone shifts in keyword translations. The keyword field is a comma-separated list, not a sentence — native speakers search with different idioms than the literal English equivalents. A direct word-for-word translation will miss most of the queries people actually type.
• Character limits in translation. The 30-char app name is enforced in the target language. Productivity Tasks (18 chars) becomes Aufgaben für Produktivität (26) in German — borderline. A worse translation like Application de Tâches Productives (33) overflows and gets silently truncated in some App Store views.
• Right-to-left languages. Arabic and Hebrew need RTL-aware screenshot text if you also localize your screenshots — easy to miss.
• "What's New" translates separately per release. Easy to forget on shipping day, especially with frequent updates.

The 5-minute workflow with App Connect Translate

Skip steps 1–5 of the manual workflow. The actual flow is:

1. Paste your source English metadata once — or pull it directly from an existing app via the App Store Connect API.
2. App Connect Translate runs AI translation across all 30+ Apple-supported locales, applying App Store character limits, brand-term glossary protection, and keyword-field-specific handling automatically.
3. Review every locale side-by-side. Edit any field you want before publishing — you stay in control.
4. One click pushes the approved translations to App Store Connect using the official App Store Connect API.

No copy-paste. No spreadsheets. No accidentally truncated app names in Italian. And when you ship a new version with new "What's New" text, you re-translate just that field across all locales — again in one click.

Mini-FAQ

Do I need a paid Apple Developer account?

Yes — you need an active App Store Connect account with API access. The setup guide walks through generating the App Store Connect team key step by step.

Is the AI translation any good?

The base is Gemini's translation model, which is competitive with DeepL for the major locales. App Connect Translate adds post-processing for character limits, keyword-field idioms, and brand-term glossaries — and you review every locale before anything is published. If a translation feels off, edit it inline before pushing.

What about localized screenshots?

Localized screenshot text is on the roadmap. For now, App Connect Translate handles every text-based metadata field. Screenshot localization (overlay text) is best handled in your design tool using the per-locale strings the app generates.

How much does it cost?

A single push — all locales for one app — is a one-time fee on the order of a few coffees. No subscription. See pricing on the homepage for current rates.

What if I only want to localize into one or two languages?

Works the same way. Pick the locales you want, leave the others unchecked. You still get the App-Store-specific handling — character limits, glossary, keyword-field idioms.

Where to start

If you have an app live on the App Store with English-only metadata, the highest-leverage move you can make in the next hour is:

1. Pick three Tier 1 locales. For most indie categories, Japanese, German, and Simplified Chinese are the best starting trio — high revenue, low competition.
2. Translate and push.
3. Wait seven days. Check App Store Connect's metrics for those three new locales — impressions, product page views, and conversion rate, all separated per locale.
4. Use those numbers to decide which Tier 2 locales to add next.

That's the loop. Most indie developers never localize at all, miss the easy 30–80% revenue lift, and never know it was sitting there.