App Store Localization: Every Storefront's Languages (2026 Table)

In short: App Store Connect supports 50 metadata localizations, and every App Store storefront searches more than one of them. Apple publishes a default language and additional languages for each storefront (the US has English (U.S.) plus nine others, including Spanish (Mexico)) and says localized keywords are searchable wherever the App Store supports that language. Each extra localization gives you another name, subtitle and 100-byte keyword field, so filling the right ones is the cheapest way to rank for more keywords in more countries.

App Store localization does two jobs at once. It shows people your listing in their language, which helps them decide to download. And because the App Store searches several localizations in each country, it gives you more keyword space in markets you already target. Most developers do the first job and miss the second.

This guide gives you the current language list, the storefront table, the rules that decide who sees what, and a worked example for the most valuable pair in the store: English (U.S.) plus Spanish (Mexico).

Localizations and storefronts are not the same thing

A storefront is a country or region's App Store: the US store, the Mexican store, the Japanese store. A localization is one language version of your metadata in App Store Connect: English (U.S.), Spanish (Mexico), Japanese. There are far more storefronts than localizations, and the mapping between them is many-to-many.

Apple describes what each user sees in its localization help, using French as the example:

• The French localization "displays to users whose language setting is in French."
• It "also displays to users in countries or regions where the App Store supports French but not English."
• "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."

And for search, the sentence that matters most: "Users can search for your app using localized keywords in all countries or regions where the App Store supports French." In other words, a localization's keywords count in every storefront that supports its language, not only in the country the locale name suggests.

The 50 App Store localizations (as of October 2026)

Apple's App Store localizations reference lists these:

Arabic, Bangla, Catalan, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English (Australia), English (Canada), English (U.K.), English (U.S.), Finnish, French, French (Canada), German, Greek, Gujarati, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Kannada, Korean, Malay, Malayalam, Marathi, Norwegian, Odia, Polish, Portuguese (Brazil), Portuguese (Portugal), Punjabi, Romanian, Russian, Slovak, Slovenian, Spanish (Mexico), Spanish (Spain), Swedish, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Vietnamese.

Eleven of them are new. On March 31, 2026, Apple added Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu, bringing the total to 50, with India as the main focus. If your keyword research for India predates April 2026, it is out of date.

Which localizations each storefront searches

The table below covers the 25 largest storefronts. The first two columns come from Apple's storefront table, which lists a default language and additional supported languages for each country or region. Apple's statement that localized keywords are searchable wherever a language is supported is what turns that table into an indexing map. Apple does not document how these localizations are weighted in ranking, so the last column compares Apple's list with tables published by ASO practitioners, who test indexing by placing dummy keywords in one localization and searching for them in each storefront.

Treat the table as current guidance, not a guarantee, and verify with your own rank tracking per storefront.

Two patterns stand out when you look at all 173 storefronts in Apple's table. English (U.K.) appears in 170 of them, as the default or an additional language; only the US, Canada and Japan leave it out. And Spanish (Mexico) appears in 19, as the default across most of Latin America and as an additional language in the US.

Is your primary localization searched everywhere?

Apple says your primary language is displayed wherever no other localization applies. Whether it is also indexed in every storefront is less clear: ASO.dev states that "the primary localization of the app is currently indexed in all countries", and AppTweak reports that apps rank globally on their English (U.K.) or English (U.S.) primary metadata. Apple does not say so directly. If you rely on this, confirm it with tracking in the specific storefront.

Rules that make extra localizations work

The field mechanics are covered in our guide to App Store keywords; here is what changes with localization. Each localization has its own name (up to 30 characters), subtitle (30 characters) and keyword field (up to 100 bytes). A few rules decide how much those fields are worth:

1. Phrases do not combine across localizations. AppTweak and ASO.dev both report that the App Store forms phrases only within one localization. "Habit" in English (U.S.) and "tracker" in Spanish (Mexico) will not rank you for "habit tracker".
2. Do not repeat words across localizations indexed in the same storefront. Repeating a word does not boost it; it wastes space you could use for a new keyword.
3. New localizations start without keywords. Apple notes that when you add a language, its screenshots and properties default to the primary language, "except for the description and keywords". An added localization with an empty keyword field adds nothing to search.
4. Bytes, not characters. The keyword field counts bytes. Accented letters such as á or ñ take 2 bytes and Chinese, Japanese or Korean characters take 3, so a Spanish field holds a little less than an English one and a Japanese field roughly 33 characters.
5. Changes ship with a version. You can only edit languages while the app status is editable, and new localized metadata goes out with your next submission.

Which localizations to fill first

Work through this order, and stop where the effort stops paying:

1. The default language of your main markets. Your primary listing should be excellent in the language most of your users read.
2. The free extra slots in those same markets. For a US-focused app, that means Spanish (Mexico) first, because it is a real search language in the US and the default across Latin America, then the other eight additional US languages if their audiences fit your app. For Canada, French (Canada). For Australia, English (U.K.).
3. English (U.K.), if your primary is English (U.S.). Because English (U.K.) is searched in 170 storefronts, it is effectively your English listing for most of the world outside the US, Canada and Japan. Give it its own keywords and British spelling rather than a copy of the US text.
4. Full translations for big non-English markets where you see demand: Japanese, German, French, Portuguese (Brazil), Korean, and now the Indian languages if India matters to you.

Use the metadata localizations guide to see which extra localizations Searvia's planner lists for your country, and expand your keywords to more countries to score the same keywords in other storefronts before you commit to translating.

Using extra fields without hurting your listing

The trap is forgetting that secondary localizations are also somebody's primary view. Spanish (Mexico) is what a US user with a Spanish-language device sees, and it is the default listing for Mexico, Argentina, Colombia, Chile and the rest of Spanish-speaking Latin America. English (U.K.) is the default listing in Türkiye, India, Saudi Arabia, the UAE and well over a hundred other storefronts.

So split the fields by visibility:

• Name and subtitle are visible. Write them properly in the localization's language. Keep your brand name in every localization.
• The keyword field is invisible. Users never see it, which makes it the safe place to add extra terms. Some developers put leftover English long-tail terms in a secondary keyword field once the local words are covered. It is common practice, but Apple does not document it, and AppTweak notes Apple frowns on it even though no rejections have been publicized. Those words are also indexed in every storefront that searches the localization, so keep them relevant.
• The description is not a search field. Apple lists text relevance as matches in your title, subtitle, keywords and primary category, so translate the description for conversion, not for keywords.

Translating vs transcreating

Literal translation gets grammar right and keywords wrong. People in each market search with their own words, and a translation tool picks a correct word, not necessarily the searched one: for "daily routine" it might offer "rutina cotidiana" when people in Mexico mostly type "rutina diaria". Check which variant has demand before you commit. Transcreation means rewriting for the market: choose the local search terms first, then write the name, subtitle and screenshots around them.

A practical split: translate long text (description, promotional text, what's new) with a good tool and a native review; transcreate the 160 characters that are searched (name, subtitle, keyword field) from local keyword research. Check candidate words in the target storefront with the free App Store keyword checker, which can also score a keyword across the top 30 markets with local-language versions.

Localize screenshots too

Screenshots drive the download decision, and Apple shows the primary language's screenshots in any new localization until you upload your own. Localize at least the caption text on your first screenshots, since Apple lists screenshots among the product page elements that appear in search results. If you only have time for a few languages, start where the localization is the default listing (Spanish (Mexico) for Latin America, Japanese for Japan), because there every visitor sees it.

Worked example: English (U.S.) plus Spanish (Mexico)

A hypothetical habit tracker called Streakly targets the US. Its English (U.S.) listing is built from its keyword research (see App Store keyword research for how the words were chosen). Spanish (Mexico) adds a second, fully Spanish set of searched fields that works in the US for Spanish-language searches and in Latin America as the main listing.

What this achieves:

• In the US, Streakly is indexed for two complete, non-overlapping vocabularies: English phrases such as "habit tracker widget" and Spanish searches such as "racha diaria" or "recordatorio".
• Each phrase is complete inside one localization, so nothing relies on words combining across languages.
• "Widget" is the one word repeated across both listings, on purpose: it is the same word in both languages, and in Latin American storefronts, where English (U.S.) is not searched, only the Spanish listing can carry it.
• The Spanish keyword field uses 98 bytes: "motivación" costs 11 bytes for 10 characters.

Next steps for Streakly would be English (U.K.) with British spelling for the rest of the English-speaking world, then Portuguese (Brazil), which is also searched in the US.

How to measure whether it worked

1. Track ranks per storefront, not globally. A Spanish keyword should be tracked in the US and in Mexico separately, because each store ranks differently.
2. Record a baseline. Note ranks for the new keywords before release; most will be unranked.
3. Wait two to four weeks after the version goes live before judging.
4. Check the board, not single keywords. Look at how many keywords reached the top 10 in each market. Searvia's global keyword board shows every tracked keyword in every storefront on one screen.
5. Watch conversion in App Store Connect for storefronts where the localization is the default, to confirm the new listing does not hurt downloads.

Common mistakes

• Adding a localization and leaving the keywords empty. It only changes what some users see; it adds no search coverage.
• Copying the primary keywords into every localization. Duplicate words across localizations in the same storefront waste space.
• Filling Spanish (Mexico) with English name and subtitle. It breaks your listing for Spanish-speaking users and for most of Latin America.
• Using old storefront tables. India, for example, gained ten localizations in 2026.
• Splitting a phrase across languages. Phrases form within one localization only.

How Searvia helps

Searvia's Metadata tab includes a localization planner that lists the extra localizations the App Store searches in your country and writes title, subtitle and keyword field suggestions for each one from your tracked keywords, so every localization adds new words instead of repeating your main listing. Tracked keywords are checked daily per storefront, and the global keyword board shows where each localization is paying off. Start with the free keyword checker, then track the winners in a free account.