App Store Connect languages: all 50, with locale codes

App Store Connect languages number 50: that's how many languages and locales you can localize your App Store product page metadata into. Eleven of them (Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu) arrived in March 2026, so any list showing 39 is out of date. Below is every language with the exact locale code the App Store Connect API expects, and notes on where each one actually appears.

We checked every row against two Apple pages: the App Store localizations reference in App Store Connect Help (the language list and the storefront table) and the API article Managing metadata in your app by using locale shortcodes (the codes).

All 50 App Store Connect languages and locale codes

Names follow App Store Connect Help. "Shown in" comes from Apple's storefront table, which lists a default language and any additional languages for each of the 175 storefronts.

Language	Locale code	Notes
Arabic	ar-SA	Right-to-left. Additional language in 16 Arab storefronts (Saudi Arabia, UAE, Egypt and others) plus the US
Bangla	bn-BD	Added March 2026. The API doc calls it "Bengali". Shown in India
Catalan	ca	Additional language in Spain only
Chinese (Simplified)	zh-Hans	Default in China mainland. Additional in Singapore and the US
Chinese (Traditional)	zh-Hant	Default in Taiwan, Hong Kong and Macau. Additional in the US
Croatian	hr	Croatia, Bosnia and Herzegovina, Montenegro, Serbia
Czech	cs	Czechia
Danish	da	Denmark
Dutch	nl-NL	Default in the Netherlands. Additional in Belgium and Suriname
English (Australia)	en-AU	Default in Australia and New Zealand
English (Canada)	en-CA	Default in Canada
English (U.K.)	en-GB	Default in 135 of 175 storefronts. Not en-UK
English (U.S.)	en-US	Default in the US. Additional in Japan
Finnish	fi	Finland
French	fr-FR	Default in France, Cameroon, Côte d'Ivoire and Gabon. Additional in 28 more, including Belgium, Switzerland and the US
French (Canada)	fr-CA	Additional language in Canada
German	de-DE	Default in Germany, Austria and Switzerland. Additional in Luxembourg
Greek	el	Greece, Cyprus
Gujarati	gu-IN	Added March 2026. India
Hebrew	he	Right-to-left. Israel. Not the legacy iw
Hindi	hi	India. No region suffix, unlike the Indian languages added in 2026
Hungarian	hu	Hungary
Indonesian	id	Indonesia
Italian	it	Default in Italy. Additional in Switzerland
Japanese	ja	Default in Japan
Kannada	kn-IN	Added March 2026. India
Korean	ko	Default in South Korea. Additional in the US
Malay	ms	Malaysia
Malayalam	ml-IN	Added March 2026. India
Marathi	mr-IN	Added March 2026. India
Norwegian	no	Norway. Not nb
Odia	or-IN	Added March 2026. The API doc calls it "Oriya". India
Polish	pl	Poland
Portuguese (Brazil)	pt-BR	Default in Brazil. Additional in the US
Portuguese (Portugal)	pt-PT	Default in Portugal
Punjabi	pa-IN	Added March 2026. India
Romanian	ro	Romania
Russian	ru	Default in Russia. Additional in Ukraine and the US
Slovak	sk	Slovakia
Slovenian	sl-SI	Added March 2026. App Store Connect Help spells it "Slovenia". Shown in Slovenia
Spanish (Mexico)	es-MX	Default in Mexico and 15 other Latin American storefronts. Additional in the US, Belize and Uruguay
Spanish (Spain)	es-ES	Default in Spain
Swedish	sv	Default in Sweden
Tamil	ta-IN	Added March 2026. India
Telugu	te-IN	Added March 2026. India
Thai	th	Thailand
Turkish	tr	Türkiye, Cyprus
Ukrainian	uk	Ukraine, Russia
Urdu	ur-PK	Added March 2026. Right-to-left. India and Pakistan
Vietnamese	vi	Vietnam, US

A few codes trip people up every time they write a script against the API. British English is en-GB, never en-UK. Chinese uses script subtags (zh-Hans, zh-Hant), not zh-CN or zh-TW. Some languages carry a region (de-DE, nl-NL, fr-FR, es-ES) and others don't (it, ja, sv, pl), so you can't derive the code from the language name. Copy it from the table.

Which App Store languages were added in 2026?

Apple announced on 31 March 2026 that the App Store expands support to 11 new languages: Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu. The App Store Connect release notes date the metadata change to 30 March 2026, and the App Store Connect app (3.2) and TestFlight (4.2) picked up the same 11 languages in April. That took the list from 39 to 50.

Ten of the eleven are languages of India, and Apple said as much in the announcement. In the storefront table all ten appear only as additional languages in the India storefront (Urdu also shows in Pakistan), alongside Hindi, which was already there. India's default language is still English (U.K.).

Two oddities are worth knowing before you add them. Bangla's code is bn-BD, yet Bangladesh isn't in Apple's storefront table at all, so in practice Bangla is an India-storefront language. And Slovenian is the one European language in the batch: it gets sl-SI and shows in Slovenia, where English (U.K.) is the default.

Apple's announcement says the new localizations go in with your next version submission for each platform. You can't add them to a version that's already live.

Metadata languages are not the same as storefronts

The 50 languages are what you can write metadata in. Which of those a customer sees depends on the storefront and their device. Apple's help page puts it this way: the language shown "could be impacted by factors like the App Store language for their location, their device's language settings, languages you've added, and your primary language in App Store Connect."

Look at the counts in Apple's table and one thing jumps out: English (U.K.) is the default language in 135 of the 175 storefronts. Many storefronts where you'd expect the local language to lead, such as Denmark, Poland, Türkiye and Israel, list English (U.K.) as default and the local language as additional. The US storefront is the most multilingual, with nine additional languages (Arabic, both Chinese scripts, French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico) and Vietnamese).

The table also decides where your localized keywords count. Apple's localize app information page says users "can search for your app using localized keywords in all countries or regions where the App Store supports" that language. That's why a Spanish (Mexico) keyword field can help you in the US. We cover how to use that in App Store keywords localization, and how to pick which languages to do first in which languages to localize your app into.

One more distinction: languages on the App Information page are metadata only. Apple notes this "differs from adding languages to your app in Xcode when you localize your binary." You can ship a Japanese product page for an app whose UI is English-only. Whether you should is another question; reviewers in that market will notice.

English variants: US, UK, Australia and Canada

App Store Connect has four English localizations: en-US, en-GB, en-AU and en-CA. They're independent. Filling in en-US does not fill the other three, and each has its own name, subtitle, keywords and description.

The obvious difference is spelling. British and Australian English write "colour", "organise", "favourite", "centre" and "licence" (noun). US English writes "color", "organize", "favorite", "center", "license". Canadian English sits between them: it usually keeps "colour" and "centre" but often uses "-ize". A UK listing full of "color" and "organize" reads as an American app that didn't bother, and some UK customers do notice.

The less obvious difference is search. Each English localization has its own 100-character keyword field. If your app's primary language is en-US and you also fill in en-GB and en-AU, you get more keyword space for the storefronts that index them, and you can target local terms ("mobile" vs "cell phone", "holiday" vs "vacation").

Our take: if you've written en-US, spend ten minutes on en-GB. It's the default language in most storefronts, the copy needs only spelling changes, and the keyword field is a free second shot at search. Loci converts US spelling to UK spelling when it fills in English (U.K.), and flags US spellings it finds there before you push.

Chinese Simplified vs Traditional

These are two separate localizations, and they map to different storefronts:

Localization	Code	Default in	Also shown in
Chinese (Simplified)	zh-Hans	China mainland	Singapore, US
Chinese (Traditional)	zh-Hant	Taiwan, Hong Kong, Macau	US

Don't run Simplified through a character converter and call it Traditional. The scripts differ, but so does vocabulary: Taiwan and the mainland use different words for plenty of everyday tech terms, and a converted listing reads like it. If you can only afford one, pick based on where your users already are: App Analytics in App Store Connect breaks downloads down by territory.

Right-to-left languages: Arabic, Hebrew and Urdu

Three of the 50 are written right to left: Arabic (ar-SA), Hebrew (he) and Urdu (ur-PK). The text fields themselves are no different. You type or paste RTL text into App Store Connect like anything else.

Screenshots are where RTL matters. If your app supports Arabic or Hebrew, its interface flips: navigation moves to the other side, back buttons point right, progress bars fill the other way. Apple's right-to-left guidelines cover the details, including that digits within a number never reverse and that Arabic text may use Western or Eastern Arabic numerals depending on region. Screenshots of an English left-to-right UI with Arabic captions pasted on top look wrong to an Arabic reader. Take the screenshots from the app running in that language.

If your app isn't localized into Arabic, Hebrew or Urdu, you can still localize the product page text. Just be honest with yourself about what customers will find after they tap Get.

Also note that when you add a language, Apple copies your primary language's screenshots into it by default (everything except the description and keywords starts as a copy of the primary language). So a new Arabic localization shows your English screenshots until you upload new ones.

What happens if a storefront has no localization for your app?

Your metadata falls back. Apple's example: if English is your primary language and you add French, French users see French, French also shows in storefronts that support French but not English, and "if no localization matches a user's language setting, the next most relevant localization is used. In other countries or regions, your metadata displays in the primary language."

In practice:

• An app with only en-US shows en-US everywhere, in all 175 storefronts.
• Remove a language and Apple says storefronts that showed it "revert to showing the information entered for the primary language."
• Your primary language is set under App Information. To switch it, the new language must already be approved by App Review on a previous version, with approved screenshots for every platform at the same sizes as the current primary language.

That last rule catches people. You can't make de-DE your primary language on the version where you first add it. Ship it once, then switch.

Checklist before you add languages

• Use the exact codes from the table above, especially en-GB, zh-Hans, zh-Hant, no and the -IN codes for the 2026 Indian languages.
• Fill in each English variant separately and fix the spelling.
• Check each field against the App Store character limits. German and Finnish run long; the 30-character name and subtitle are where it bites.
• Replace the inherited primary-language screenshots for every language your app itself supports, and shoot RTL screenshots from the RTL interface.
• Add new languages on a version you're about to submit, since they ship with the next version.
• Decide your primary language deliberately. It's what every unlocalized storefront sees.