App Store Localization Languages: Full List of All 50 (2026)

Quick answer: App Store Connect currently supports 50 languages and locales for App Store metadata: four English variants, two each of Spanish, Portuguese, French and Chinese, and 38 other languages from Arabic to Vietnamese. Apple changes the list over time, so confirm it in Apple's App Store localizations reference before you plan. Google Play accepts more than 80 store listing languages.

The table follows Apple's App Store localizations reference. The locale shortcode is what the App Store Connect API (and tools built on it) use; the script column tells you what fonts and layout your screenshots need.

Two naming quirks: Apple's API documentation calls Bangla "Bengali" and Odia "Oriya," but the codes are the same. Also note that some codes carry a region (de-DE, nl-NL) and others don't (it, sv), so copy them exactly when you automate uploads.

Twelve of the 50 entries are regional versions of five languages. Each variant has its own name, subtitle, keywords field and screenshots, so they're worth treating separately:

• English (U.S., U.K., Canada, Australia): spelling ("color" vs "colour"), vocabulary ("cell phone" vs "mobile") and, most usefully, four separate 100-character keywords fields.
• Spanish (Mexico, Spain): different everyday vocabulary and tone. Spanish (Mexico) is also listed as an additional language in the United States storefront.
• Portuguese (Brazil, Portugal): spelling and vocabulary differ enough that Brazilian copy can read as foreign in Portugal, and vice versa.
• French (France, Canada): Canadian French has its own vocabulary, and French (Canada) is the additional language in the Canadian storefront.
• Chinese (Simplified, Traditional): different character sets. Apple lists Simplified as the default in mainland China and Traditional as the default in Hong Kong and Taiwan.

If budget is tight, start with the variants that share most of your existing copy. English variants in particular are close to free.

Eighteen languages on the list need more than a translation file:

Never apply letter spacing to connected scripts like Arabic or the Indian scripts; it breaks the letterforms. And test every caption at thumbnail size, because complex scripts lose legibility faster than Latin text. How to localize App Store screenshots covers the design details.

Languages and storefronts aren't the same thing. Apple's reference assigns every country or region a default language and, often, additional supported languages:

Which localization a person actually sees depends on their storefront, their device language and the languages you've added. If nothing matches, they see your primary language. The App Store localization guide explains these fallback rules and how teams use additional languages for keywords.

Google Play's list is longer. Play Console Help currently lists more than 80 languages and locales for store listing translations, including several App Store Connect doesn't offer, such as Afrikaans, Filipino, Swahili and Spanish (Latin America).

Differences that trip people up:

• Different codes. Play uses its own codes, such as iw-IL for Hebrew, ja-JP for Japanese and zh-TW for Traditional Chinese. Don't reuse App Store codes in Play automation.
• More English and Spanish variants. Play adds variants such as English (India), English (Singapore) and Spanish (United States).
• Automatic fallback. If you don't translate your listing, Play can offer users an automated translation.
• Free machine translation. Play Console offers it for a short list of languages; everything else needs your own or a paid translation.

For field limits and listing structure, see the Google Play store listing guide.

Fifty is a list of options, not a to-do list. A practical order:

1. Add the English variants (U.K., Canada, Australia) for their extra keywords fields.
2. Add the additional languages of your biggest storefront. For a US-heavy app, Spanish (Mexico) is the usual first pick.
3. Add the languages of countries where App Store Connect Analytics already shows impressions or downloads.
4. Add large non-English storefronts that fit your category, such as Japanese, German, French, Korean or Portuguese (Brazil).
5. Expand to the rest once your translation and screenshot workflow is repeatable. How to translate App Store screenshots into 40+ languages shows one.

For keyword writing in each locale, follow the rules in the App Store keywords field guide. ScreenShipper's language help page explains how languages work inside a screenshot project.