All App Store Languages: Which Should You Localize First?

The App Store supports 50 languages. App Store Connect calls them localizations — the languages your app binary, listing metadata, and screenshots can each ship in. You don't need all of them on day one, and shipping them in the right order is worth real money. Here's the complete list, and a practical ranking of which to do first.

The complete list

These are the 50 localizations App Store Connect accepts:

This list grew on 31 March 2026. Apple added eleven metadata localizations — Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu — taking App Store Connect from 39 to 50. Eight of the eleven are languages of India, which is the clearest signal Apple has given about where it expects the next wave of App Store growth. If you last picked your languages before that date, your list is out of date. Source: Apple's App Store localizations reference.

Note the regional variants: English alone has Australian, Canadian, U.K., and U.S. entries; Spanish, French, Portuguese, and Chinese also split by region. Variants matter for metadata (storefront matching) more than for the binary — most apps ship one Spanish and one Portuguese binary localization and localize metadata per storefront.

Which languages to localize first

Before the qualitative ranking below, two published figures are worth anchoring on. Of the $127bn spent across both stores in 2024, $91.6bn was App Store and $35.7bn Google Play, with the United States at roughly $47.6bn and Brazil the fastest-growing market at +73% year over year. That supports exactly two decisions: spend the first metadata effort on the App Store, and treat Brazilian Portuguese as the one speculative addition with a number behind it. Everything after that is inference from your own analytics.

Rank markets by revenue per user × how little English they tolerate:

1. Japanese — the classic first pick: top-tier ARPU, low English proficiency, and users who demonstrably prefer localized apps. Developers repeatedly cite Japan as the market where localization flipped their numbers.
2. German — large paying market, strong preference for German-language products, and text 40–60% longer than English (test your layouts).
3. Korean — high ARPU, mobile-first, English listings underperform badly.
4. French, Spanish, Italian — broad reach across many storefronts; Spanish and French each unlock multiple regions.
5. Simplified Chinese — enormous iOS market; worth it if your category isn't restricted and you can support it.
6. Portuguese (Brazil), Russian, Turkish, Polish… — lower ARPU but often spectacular download growth; several indie 3× stories come from exactly these "smaller" markets (see the numbers).

Metadata first, binary second

For each new market, localize the store listing before or alongside the app — discovery happens in local search, and metadata is a fraction of the word count. Then translate the binary strings so the users you've won stay.

Shipping all of them at once

The old reason to cherry-pick languages was cost — at $350 per language via agencies, localizing into every one of them was absurd. With per-string credits the math inverts: a 200-string app into every App Store language is $9 once (a 500-string app fits the $25 pack), so "all of them" becomes a defensible default. Upload your .strings or .xcstrings file to Localize Your App, select all 50, review the languages you can read, and ship the lot — the cost guide shows the full comparison. Games price out differently, because word count rather than language count drives the bill — the game localization cost guide breaks that down by game type.