App Store Connect's new Indian languages: what changed and how to test them (2026)

On March 31, 2026, Apple added 11 metadata languages to App Store Connect to help apps reach more people, "especially in India," taking the total to 50 localizations (Apple Developer News, 2026). Overnight, the India App Store's localization list grew from two to twelve, more than any other storefront (Apple, App Store localizations).

Six months later, the basics are still muddled. Is it ten Indian languages or eleven? Does App Store Connect accept all 50, or only 39, as one developer blog reports? And does India's search actually read a Tamil keyword field? We haven't found anyone who has checked. Paying for ten translations on an untested guess is how localization budgets disappear.

What we can show today is narrower. We re-checked Apple's list on September 28, sized India's iOS market, traced the locale-code trap and took our September 27 snapshot of India's top apps. We also wrote a 28-day indexing protocol you can run yourself. If the mechanics are new, start with how one storefront reads several keyword fields.

What did Apple add on March 31, 2026, and why is it 10 languages for India, not 11?

Apple added 11 metadata localizations in 2026 (Apple Developer News, March 31, 2026). That brought App Store Connect to 50, and the new ones are Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu and Urdu. Ten are South Asian, and Apple's storefront table lists all ten for India; Slovenian is listed for Slovenia, and Urdu for Pakistan too.

We re-parsed Apple's App Store localizations table on September 28, 2026. It still has 175 storefronts and 311 storefront-localization pairs. India lists English (U.K.) as its default, plus Hindi and the ten new languages. In February 2026 it listed two. Every new field except Urdu is listed in exactly one storefront: India. The table has no Bangladesh storefront, and Sri Lanka and Nepal list only English (U.K.).

Apple says you can localize "your app name, description, screenshots, and more" in the new languages, adding them "with your next version submission" (Apple Developer News). A new localization copies the primary's screenshots and properties "except for the description and keywords" (Apple, Localize app information). A fresh Tamil localization starts with no keywords at all.

Two naming quirks trip up checklists. App Store Connect Help says "Bangla" and "Odia," while Apple's API docs say "Bengali" and "Oriya" instead. They're the same languages. And Hindi isn't new: it was India's only secondary localization before March. To check other markets as you read, look up any storefront's list in the Cross-Localization Explorer.

How big is the India App Store opportunity in 2026?

Small in share, fast in growth. In 2025, Apple shipped about 14 million iPhones in India, a record 9% of a flat 152 to 153 million-unit market (Counterpoint via TechCrunch, January 2026). The iOS share of India's mobile web traffic more than doubled, from 3.10% in September 2025 to 7.17% in August 2026 (StatCounter).

Downloads tell the same story. From November 2024 to November 2025, India led both stores combined with 19.1 billion installs. On the App Store alone it ranked sixth, with 1.1 billion installs, up 22%: the fastest growth in the iOS top 10 (AppTweak, December 2025). By our arithmetic on the same dataset, iOS was about 6% of India's downloads.

Spending is catching up. Sensor Tower data put India's in-app purchase revenue across both stores at $520 million in 2021 and over $1 billion in 2025, with $1.25 billion projected for 2026 (Business Standard, April 2026). In Q2 2026, India set a record $345 million in consumer spending, up 35% (Sensor Tower via TechCrunch).

Apple commissioned a study from IIM Ahmedabad. It credits the App Store ecosystem in India with ₹44,447 crore ($5.31 billion) in 2024 billings and sales. But $4.65 billion of that was physical goods and services. Only $302 million was digital (Apple Newsroom India, April 2025). The headline figure measures reach. Very little of it is app revenue.

Low revenue per install, high demand for Indian languages

The catch is revenue per install. RevenueCat's 2026 medians put India and Southeast Asia at $0.08 by day 14 and $0.11 by day 60, against $0.38 and $0.55 in North America (RevenueCat, State of Subscription Apps 2026). We've worked out what India's revenue per install means for payback. In short, cheap metadata work comes first.

Online demand for Indian languages is clear. IAMAI and Kantar counted 886 million active internet users in India in 2024. Of those, 98% access Indic-language content. Among urban users, 57% prefer regional-language content (IAMAI–Kantar via IBEF, January 2025). Those figures describe all internet users, and iPhone owners may differ, so size a market before you localize for it using your own App Analytics data.

Which locale codes does App Store Connect accept for the new languages?

Apple's 2026 API docs list region-tagged shortcodes for all eleven new languages (Apple, Managing metadata by using locale shortcodes). They run from bn-BD and ta-IN to ur-PK and sl-SI. "The language specified is not listed for localization" is the error developers reported for bare codes such as bn or ta.

The trail is public. It runs through fastlane pull request #29959, opened on April 5, 2026. The API "may not yet accept these new locale codes," its author noted. It returned that error "even though the web UI supports them," the author added. On April 29, a contributor reported that bare codes were rejected and that swapping in regional suffixes "pushed all 50 locales" (GitHub, fastlane PR #29959). These are developer reports, not Apple statements.

Where the "39, not 50" claim comes from

It traces to the table's last row. Bluffle says App Store Connect "accepts 39 app-metadata locales" (Bluffle, July 29, 2026). It names seven languages that fail with the same error: Bangla, Marathi, Slovenian, Punjabi, Tamil, Telugu and Urdu. Bluffle doesn't give the codes it used. And 50 minus seven is 43, not 39. The error matches the one developers traced to bare codes. A code mismatch is a plausible explanation, but it isn't proven.

Two traps in the codes, and one in the character count

The first trap is the region tag. Bangla's shortcode carries a Bangladesh tag (bn-BD), though Apple's table has no Bangladesh storefront, and Urdu's carries Pakistan (ur-PK), though India lists Urdu too. Don't read the tag as a territory: the storefront table says where a field is read. The second is tooling: fastlane releases before 2.234.0 don't know the new locales at all.

Then count characters before you save. Treat the keyword field as 100 characters, not 100 bytes. Tamil letters take three bytes each in UTF-8. Every vowel sign also costs its own code point, which is why you should count Indic keyword fields by code point. The protocol below includes a 100- versus 101-character save check.

Does the India App Store index Tamil, Telugu and the other new keyword fields?

Not proven yet. As of September 28, 2026, we haven't found a public test showing that India's search reads the ten new fields. We haven't run one either. Apple's help implies it should. It says users "can search for your app using localized keywords in all countries or regions where the App Store supports" a language (Apple, Localize app information).

That line sits in Apple's French example. India lists all ten languages, so by Apple's rule a Tamil keyword should be searchable there. But Apple doesn't document how it weights fields. Nor does it say whether device language affects search, or how it handles each script. Our cross-localization analysis marked the new fields "listed by Apple" and stopped short of "proven." Nothing public has changed that.

A second question hides inside the first. People often type Indian languages in Latin letters as well as native script, so someone might type "vanakkam" or "வணக்கம்" for the same Tamil word. If India's search doesn't match a romanized query to a native-script keyword, a Tamil field written only in Tamil could index and still miss much of the search. That's a hypothesis, not a finding. It's why the protocol below tests both scripts.

We haven't run this test yet. The protocol below lets you run it on your own app. We'll add our results here when we have them. Until then, treat each new field as an experiment, and keep the 175-storefront localization map handy for the markets that share your other fields.

How can you test whether India's storefront indexes each language?

Put one unique "canary" term in each keyword field and change nothing else. Ship one version. Then search for every canary from India-storefront iPhones on days 1, 3, 7, 14 and 28. Controls around India's twelve fields mean a "no" tells you the field isn't indexed. It can't simply mean the test broke. We haven't run it yet, but you can, on your own app.

1. Apps. Two or three live iOS apps you control, in different categories, with an English (U.S.) primary.
2. Acceptance (day −7). Add all eleven locales in the web UI and through the API, with bare codes and with Apple's shortcodes. Save 100- and 101-character Tamil and Malayalam keyword fields. Log every error and App Review response.
3. Baseline (day −7 to 0). Confirm each canary sits outside the top 200 everywhere you'll check, and record India impressions and conversion rate in App Analytics.
4. Canaries. Two per field: your brand name transliterated into that script (use different words for Hindi and Marathi, which share Devanagari), and a relevant English term you don't yet rank for. The Latin arm separates "does India read this field?" from "can India's search handle this script?"
5. Controls. Positive: English (U.K.) and Hindi, India's pre-March fields. Negative: Japanese, which India doesn't list.
6. Comparison arm. Report these alongside, but don't use them to validate the run: your English (U.S.) primary checked in India, which India's table doesn't list, plus Urdu in Pakistan and Slovenian in Slovenia.
7. Leakage. Check the Tamil canary in Sri Lanka, Singapore and Malaysia, Punjabi in Pakistan, and Urdu and Punjabi in the UAE. None of those storefronts lists the language.
8. Devices and queries. Use India Apple IDs on iPhones set to English (India), English (U.K.), Hindi, Tamil and Telugu. Search each canary in native script, romanized, and by its first three characters.
9. Display check. At each checkpoint, screenshot the India product page under each device language and note whose name, subtitle and screenshots appear.
10. Checkpoints and instruments. Days 1, 3, 7, 14 and 28, on physical iPhones with screen recordings, a tracker that accepts native-script queries for India, and our free Keyword Rank Checker. The checker reads Apple's public iTunes Search API rather than the App Store app's own ranking, so it never decides a result alone.
11. Coding rule. Indexed: top 200 on at least two instruments at two consecutive checkpoints. Not indexed: absent everywhere through day 28 while the positive controls pass. Inconclusive: anything else.
12. Freeze. No other metadata, creative or price changes, and no Apple Ads on any canary term, since an ad would surface the app regardless.

Why a brand-name canary stays within Apple's rules

Apple's Guideline 2.3.7 bars packing metadata with "irrelevant phrases just to game the system" (Apple, App Review Guidelines). Your own name in another script is relevant, unique and uncontested. A rank change can then only come from the field under test.

What the test can't tell you

A few apps aren't a panel, Apple can change keyword indexing without notice, and the test measures indexing only, saying nothing about ranking strength. Watch your positive controls, too. Third-party monitors flagged an unconfirmed shift in India's search in late July 2026, and we covered the July 2026 ranking anomaly in India separately. And learn how long keyword changes take to settle before you judge day 3.

Who actually sees a Tamil or Telugu listing, and how many top apps have one?

Display follows the device language. Apple shows a localization to "users whose language setting" matches it and otherwise uses "the next most relevant localization" (Apple, Localize app information). In our September 27, 2026 snapshot, only 9 of India's top 173 iPhone apps (5.2%) had a listing in any new language. Hindi had 52 (30.1%).

All ten are iOS system languages (Apple, iOS feature availability, retrieved September 28, 2026). Hindi and English (India) are too. A shopper can set an iPhone to Tamil, though no one publishes how many actually do. An iPhone set to English (India) matches none of India's twelve localizations, so we expect the fallback to be English (U.K.), which the display check in the protocol above would confirm.

How many of India's top apps list a new language?

Very few do. On September 27, 2026, we pulled India's top-100 free and top-100 grossing iPhone charts (173 unique apps) and fetched each app's India product page in all twelve languages. An app counts as having a listing when its description differs from the English (U.K.) one and carries that language's script. This method can't see keyword-only localizations, so every number is a floor.

The adopters are mostly global giants with company-wide localization pipelines: Google Gemini and Truecaller had all ten new languages, Instagram nine, Meta AI eight and Duolingo four. PhonePe had only Gujarati. Chaupal, a regional streaming app, had three. Tamil is the fifth-largest mother tongue in India's 2011 census (69 million speakers), yet it appeared on 4 of 173 listings. If its field indexes, that's close to an empty keyword space.

Don't mix this with our earlier look at binary language support among India's top grossers. That one measured languages inside the app (Hindi 47%); this snapshot measures store listings. If you add a language, localize screenshots for the users who will see them. A new localization inherits your primary's images.

Should you localize for India's new languages, and in what order?

Start with English (U.K.) and Hindi. In Apple's 2026 table, English (U.K.) is India's default, and Hindi was the mother tongue of 43.6% of India's population in 2011 (Census of India). Add a new language when your users come mainly from its states, and treat it as a test until its field is shown to index.

By our arithmetic on the 2011 census, the ten new languages are the mother tongues of about 586 million people, 48.4% of the 1.21 billion counted, more than Hindi's 528 million. But national totals mislead. Weight each language by the states your users come from, whatever its national size. Revenue per install matters too: $0.11 by day 60 (RevenueCat, 2026). At that level, metadata is usually the only tier that pays back quickly in India.

1. Check the demand. In App Analytics, filter to India and read impressions and conversion rate. If you run Apple Ads there (it's available in India), read the search-terms report for native-script and romanized queries.
2. Pick by speakers and footprint. Bangla, Marathi, Telugu and Tamil lead by 2011 mother-tongue count; your users' states decide.
3. Research, don't translate. Find native-script terms and the romanized spellings people type. Our guide on how to research keywords instead of translating them covers the method.
4. Fill each field without duplicates. 100 characters per field, and every Indic vowel sign costs a code point.
5. Write readable visible copy. Name and subtitle in the language, checked by a native speaker.
6. Ship through the right codes. Use the web UI, or the API and fastlane 2.234.0 or later with Apple's shortcodes.
7. Verify. Check your brand transliteration at days 3, 7 and 14, as in the protocol above.

Data appendix: India's top apps with a store listing in each language

This is the snapshot behind the adoption chart. It covers India's top-100 free and top-100 grossing iPhone apps from Apple's iTunes RSS feeds (173 unique), collected on September 27, 2026, with 2,076 product-page fetches and no failures. A listing counts when the page's structured description differs from English (U.K.). It must also add at least 20 characters of the language's script. Marathi has to differ from Hindi as well, and Urdu needs Urdu-specific letters.

Limits: one day's charts and visible listings only. The web product page also stands in for what the App Store app shows. To cite this data: ASO Agency, "App Store Connect's New Indian Languages: What Changed and How to Test Them (2026)," asoagency.io, September 28, 2026.

The bottom line

India's twelve fields are real keyword space on paper. Most of it sits empty. Whether all of it is searchable is still an open question.

• The list: 10 new languages for India, so 12 fields and 1,200 keyword characters.
• The codes: region-tagged shortcodes (bn-BD, ur-PK), per Apple's docs and developer reports.
• Indexing: not publicly proven, and we haven't tested it yet. The protocol above lets you.
• Display: per Apple's help, a Tamil listing shows only on iPhones set to Tamil.
• Competition: 9 of India's top 173 iPhone apps had any new-language listing on September 27, 2026.

Look up India, and every storefront you sell in, in the free Cross-Localization Explorer. Then book a free 30-minute call. We'll map which of India's twelve fields your app should fill, then verify each one rank by rank as part of our localization service; the fixed-price ASO audit is the usual starting point.