Guide
App Store Localization Languages by Country: The Full Table
Each App Store country has a default language and often extra ones. The US also supports Spanish (Mexico) and 8 more; most countries add English (U.K.).
Every App Store country has a default language, and many also support additional languages whose metadata counts in that country’s search. The United States, for example, supports English (US) plus nine more, including Spanish (Mexico), Chinese (Simplified) and Russian; most other countries default to English (U.K.) or add it as a second language.
That matters for keywords, because each localization has its own 100-character keyword field. The full table from Apple is below, with what ASO tools have found about how it affects search.
Where This Comes From
The table is Apple’s own, from the App Store Connect reference page App Store localizations, as of November 2026. Apple calls them the “default language” and “additional supported language(s)” for each country or region.
Apple’s page says which languages each country supports. It doesn’t say how search uses them. That part comes from ASO tool makers who have tested it:
- AppTweak (March 2023) reports that “keywords in at least two locales can be indexed” in each country, and that “keywords are not combined across localizations.”
- Mobile Action (April 2026) lists the same nine extra US locales and states that “phrase combinations only form within a single locale, not across them.” It also notes this comes from industry observation, since Apple doesn’t document it.
Third-party lists sometimes differ from Apple’s table for smaller countries. When they do, go with Apple’s current table and check your ranks.
The Countries That Matter Most for Indie Apps
| Country | Default | Additional | What it means for you |
|---|---|---|---|
| United States | English (US) | Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico), Vietnamese | Up to ten keyword fields count in the US |
| United Kingdom | English (U.K.) | None | Only English (U.K.) counts |
| Canada | English (Canada) | French (Canada) | Two fields; write real French for Quebec |
| Australia | English (Australia) | English (U.K.) | Two English fields |
| Japan | Japanese | English (US) | Your English (US) field also counts in Japan |
| Germany | German | English (U.K.) | Your English (U.K.) field also counts in Germany |
| Mexico | Spanish (Mexico) | English (U.K.) | Spanish (Mexico) serves Mexico and most of Latin America |
| Brazil | Portuguese (Brazil) | English (U.K.) | Portuguese (Brazil) is separate from Portugal |
| India | English (U.K.) | Bangla, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu, Urdu | Many options; Hindi is the usual first step |
Two patterns stand out:
- English (U.K.) is everywhere. It’s the default language in most countries in Apple’s table and an additional language in many others, including Germany, France, Mexico and Brazil. A well-filled English (U.K.) keyword field works in far more countries than the United Kingdom.
- Spanish (Mexico) covers Latin America. It’s the default in Argentina, Chile, Colombia, Peru and most other Spanish-speaking countries in the Americas, and an additional language in the US, Belize and Uruguay. Spanish (Spain) is used only in Spain.
How to Use the Extra Localizations
Fill Them With Real Keywords First
For the US, your Spanish (Mexico) field is the obvious second field: many people in the US search the App Store in Spanish. Fill it with Spanish keywords that describe your app, written by someone who speaks the language. For a budgeting app, that might be:
presupuesto,gastos,ahorro,deudas,quincena,nómina,hogar,mensual,factura,cartera,meta,pareja,familia
That’s 98 characters (99 bytes, because of the accent in nómina), in a field that also works in Mexico and much of Latin America.
Know the Tactic and Its Risk
Many developers put extra English keywords into an additional localization’s field, for example English words in the Spanish (Mexico) field, to rank in the US. AppTweak’s example shows it can work, and notes that Apple frowns on it. Apple’s Guideline 2.3.7 asks for keywords “that accurately describe your app.” The risk is yours to weigh; the safer use is real Spanish.
Keep Phrases in One Localization
Because words don’t combine across localizations, a phrase like “budget planner” works only if both words are in the same localization’s name, subtitle or keyword field. Split it across two localizations and you rank for neither phrase.
Don’t Forget the Visible Text
Users in Japan who see your English (US) listing see English. An extra localization helps search; it doesn’t replace a proper translation for the people who read it. Our App Store localization page shows how AppMeerkat helps translate and adapt a listing with your own AI agent, and saves the result as a draft in App Store Connect.
Checking That It Worked
After you add a localization, check your ranks in each country it covers, not just the main one. A Spanish (Mexico) field should show up in US ranks for Spanish keywords and in Mexico, Colombia and the rest. Our guide on tracking keyword rankings in every country covers how. AppMeerkat checks every keyword in every country the App Store serves, so you can see where a new localization moved you on one board.
For a quick lookup while writing, the free localization cheat sheet has this table in a searchable form.
Limits
- Apple can change the table. Recheck Apple’s page before planning a big localization push.
- Indexing behavior is observed, not documented. Apple doesn’t say how much weight an additional language has compared with the default.
- Display isn’t search. Apple says the language a user sees depends on their device settings, the App Store language for their location and the languages you’ve added.
- Google Play works differently. Play has no keyword field; its listings are per language, and custom store listings target countries. See Google Play ASO.
The Full Table
Apple’s table, limited to countries and regions that have at least one additional language. Every other country or region in Apple’s table uses English (U.K.) as its default with no additional language.
| Country | Default language | Additional languages |
|---|---|---|
| Algeria | English (U.K.) | Arabic, French |
| Argentina | Spanish (Mexico) | English (U.K.) |
| Australia | English (Australia) | English (U.K.) |
| Austria | German | English (U.K.) |
| Bahrain | English (U.K.) | Arabic |
| Belgium | English (U.K.) | Dutch, French |
| Belize | English (U.K.) | Spanish (Mexico) |
| Benin | English (U.K.) | French |
| Bolivia | Spanish (Mexico) | English (U.K.) |
| Bosnia and Herzegovina | English (U.K.) | Croatian |
| Brazil | Portuguese (Brazil) | English (U.K.) |
| Burkina Faso | English (U.K.) | French |
| Cambodia | English (U.K.) | French |
| Cameroon | French | English (U.K.) |
| Canada | English (Canada) | French (Canada) |
| Chad | English (U.K.) | French |
| Chile | Spanish (Mexico) | English (U.K.) |
| China mainland | Simplified Chinese | English (U.K.) |
| Colombia | Spanish (Mexico) | English (U.K.) |
| Congo, Democratic Republic of the | English (U.K.) | French |
| Congo, Republic of the | English (U.K.) | French |
| Costa Rica | Spanish (Mexico) | English (U.K.) |
| Cote d’Ivoire | French | English (U.K.) |
| Croatia | English (U.K.) | Croatian |
| Cyprus | English (U.K.) | Greek, Turkish |
| Czechia | English (U.K.) | Czech |
| Denmark | English (U.K.) | Danish |
| Dominican Republic | Spanish (Mexico) | English (U.K.) |
| Ecuador | Spanish (Mexico) | English (U.K.) |
| Egypt | English (U.K.) | Arabic, French |
| El Salvador | Spanish (Mexico) | English (U.K.) |
| Finland | English (U.K.) | Finnish |
| France | French | English (U.K.) |
| Gabon | French | English (U.K.) |
| Germany | German | English (U.K.) |
| Greece | English (U.K.) | Greek |
| Guatemala | Spanish (Mexico) | English (U.K.) |
| Guinea-Bissau | English (U.K.) | French |
| Guyana | English (U.K.) | French |
| Honduras | Spanish (Mexico) | English (U.K.) |
| Hong Kong | Chinese (Traditional) | English (U.K.) |
| Hungary | English (U.K.) | Hungarian |
| India | English (U.K.) | Bangla, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu, Urdu |
| Indonesia | English (U.K.) | Indonesian |
| Iraq | English (U.K.) | Arabic |
| Israel | English (U.K.) | Hebrew |
| Italy | Italian | English (U.K.) |
| Japan | Japanese | English (US) |
| Jordan | English (U.K.) | Arabic |
| Kuwait | English (U.K.) | Arabic |
| Laos | English (U.K.) | French |
| Lebanon | English (U.K.) | Arabic, French |
| Libya | English (U.K.) | Arabic |
| Luxembourg | English (U.K.) | French, German |
| Macau | Chinese (Traditional) | English (U.K.) |
| Madagascar | English (U.K.) | French |
| Malaysia | English (U.K.) | Malay |
| Mali | English (U.K.) | French |
| Mauritania | English (U.K.) | Arabic, French |
| Mauritius | English (U.K.) | French |
| Mexico | Spanish (Mexico) | English (U.K.) |
| Montenegro | English (U.K.) | Croatian |
| Morocco | English (U.K.) | Arabic, French |
| Netherlands | Dutch | English (U.K.) |
| New Zealand | English (Australia) | English (U.K.) |
| Nicaragua | Spanish (Mexico) | English (U.K.) |
| Niger | English (U.K.) | French |
| Norway | English (U.K.) | Norwegian |
| Oman | English (U.K.) | Arabic |
| Pakistan | English (U.K.) | Urdu |
| Panama | Spanish (Mexico) | English (U.K.) |
| Paraguay | Spanish (Mexico) | English (U.K.) |
| Peru | Spanish (Mexico) | English (U.K.) |
| Poland | English (U.K.) | Polish |
| Portugal | Portuguese (Portugal) | English (U.K.) |
| Qatar | English (U.K.) | Arabic |
| Republic of Korea | Korean | English (U.K.) |
| Romania | English (U.K.) | Romanian |
| Russia | Russian | English (U.K.), Ukrainian |
| Rwanda | English (U.K.) | French |
| Saudi Arabia | English (U.K.) | Arabic |
| Senegal | English (U.K.) | French |
| Serbia | English (U.K.) | Croatian |
| Seychelles | English (U.K.) | French |
| Singapore | English (U.K.) | Chinese (Simplified) |
| Slovakia | English (U.K.) | Slovak |
| Slovenia | English (U.K.) | Slovenian |
| Spain | Spanish (Spain) | Catalan, English (U.K.) |
| Suriname | English (U.K.) | Dutch |
| Sweden | Swedish | English (U.K.) |
| Switzerland | German | English (U.K.), French, Italian |
| Taiwan | Chinese (Traditional) | English (U.K.) |
| Thailand | English (U.K.) | Thai |
| Trinidad and Tobago | English (U.K.) | French |
| Tunisia | English (U.K.) | Arabic, French |
| Türkiye | English (U.K.) | Turkish |
| Ukraine | English (U.K.) | Russian, Ukrainian |
| United Arab Emirates | English (U.K.) | Arabic |
| United States | English (US) | Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico), Vietnamese |
| Uruguay | English (U.K.) | Spanish (Mexico) |
| Vanuatu | English (U.K.) | French |
| Venezuela | Spanish (Mexico) | English (U.K.) |
| Vietnam | English (U.K.) | Vietnamese |
| Yemen | English (U.K.) | Arabic |
Questions
Which languages does the US App Store index?
Apple's table lists English (US) as the default for the United States, with Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico) and Vietnamese as additional languages. ASO tools report that keywords in all of these count in US search.
Do keywords combine across two localizations?
ASO tools that have tested it say no. A word in your English (US) keyword field and a word in your Spanish (Mexico) field don't form a phrase together. If a phrase matters, keep its words in the same localization.
Is it allowed to put English keywords in the Spanish (Mexico) field?
It's a common tactic, but Apple's guidance asks for relevant, accurate metadata, and AppTweak notes Apple frowns on it. Use the extra localization for real Spanish keywords that US Spanish speakers search, and you stay on solid ground.
Why does English (U.K.) matter so much?
In Apple's table, English (U.K.) is the default language for most countries and an additional language in many more. If you only localize English (US), most of those countries fall back to whatever Apple shows by default.
Read next
Launching soon
Let a meerkat watch your ranks.
AppMeerkat tracks every keyword, in every country, on both stores. One email at launch, with the early-bird price.