

Apple expands App Store Connect to 50 localisations with 11 new languages including 9 Indian languages. Learn how to update for organic growth through expert ASO localisation tactics.

Apple has opened the door to hundreds of millions of new users. With App Store Connect now supporting 50 localisations — including nine Indian languages — developers who act swiftly on localisation will capture outsized organic growth before competitors catch up.
On 31 March 2026, Apple announced that App Store Connect now supports localised metadata for 11 new languages, expanding the total number of supported localisations from 39 to 50. This marks one of the most significant localisation expansions in App Store history.
The update means developers can now provide localised app names, subtitles, descriptions, keywords, screenshots, and preview videos in each of the new languages directly through App Store Connect. When users browse the App Store in one of these languages, they will see your localised product page — a substantial advantage for discoverability and conversion.
Apple has also released new localised App Store download badges for each language, which developers can use in external marketing materials, websites, and advertising campaigns.
๐ KEY TAKEAWAY
This is not merely a translation update — it is a market expansion signal. Apple is investing in making the App Store more accessible across India and other high-growth regions. Developers who localise early will benefit from reduced competition in these new keyword spaces. For a deeper understanding of how localisation drives ASO, read our complete guide to app localisation.
Nine of the eleven new languages are Indian languages. This is no coincidence. India represents one of the world's fastest-growing mobile markets, with over 650 million smartphone users and app download volumes that rival any market globally.
Yet, the majority of India's population does not use English as their primary language. According to the Census of India, only about 10% of Indians speak English as a first or second language. The remaining 90% interact with their devices in regional languages — Hindi, Bengali, Tamil, Telugu, Marathi, and others.
๐ก EXPERT TIP
India's app market grew to 8.45 billion downloads in FY 2024-25. Yet most App Store listings targeting India remain English-only. Developers who localise into regional Indian languages now will face dramatically less keyword competition compared to English — giving you a first-mover advantage in search rankings.
Read our analysis: How to Promote Your App and Monetise App Store Traffic from India.
The update also includes Slovenian, addressing the EU market where localisation compliance and user preference for native-language content continue to grow. And Urdu opens doors to Pakistan's 100M+ mobile users as well as Urdu-speaking communities worldwide.
Combined, the speakers of these 11 languages represent nearly a billion people. Even accounting for overlap with existing English localisations, this is a transformational expansion in addressable audience.

Localisation is more than translation. A robust localisation strategy involves adapting your entire product page — metadata, keywords, visuals, and messaging — to resonate with each target audience. Here is a structured approach.
Before adding new languages, review your existing localised listings. Check which markets are driving the most installs, what your conversion rates look like per locale, and where there are gaps in keyword coverage.
โ ACTION STEP
Go to App Store Connect > App Analytics > Metrics. Filter by territory and storefront. Identify which Indian states or regions already show meaningful install volume — these are your priority languages.
Keyword behaviour varies dramatically between languages. A direct translation of your English keywords will rarely capture actual search intent in languages like Tamil or Telugu. You need native-language keyword research.
๐ก EXPERT TIP
Don't translate keywords — discover them. Use native speakers or local ASO consultants to identify how users in each language actually search for apps in your category. The same concept (e.g., "budget tracker") may use entirely different phrasing in Bangla versus Marathi. Treat each language as a fresh keyword research project.
For keyword research methodology, see: How to Do App Store Keyword Research.
With your keyword research complete, localise the following fields in App Store Connect for each new language:
|
Metadata Field |
Character Limit |
Localisation Priority |
|
App Name |
30 characters |
Critical — directly impacts search ranking |
|
Subtitle |
30 characters |
Critical — visible in search results |
|
Keywords Field |
100 characters |
Critical — hidden but indexed for search |
|
Description |
4,000 characters |
High — affects conversion rate |
|
Promotional Text |
170 characters |
Medium — updatable without new submission |
|
Screenshots |
Up to 10 per size |
High — primary conversion driver |
|
App Preview Video |
Up to 3 |
Medium — strong for engagement |
๐ก EXPERT TIP
Character limits work differently with non-Latin scripts. Many Indic scripts use conjunct characters and ligatures. A 30-character limit in Tamil or Malayalam may yield far fewer visible "words" than in English. Draft your app name and subtitle, then test how they render on actual devices before submitting.
For a detailed comparison of how localisation works across platforms, read: Comparing App Localisation on Google Play and App Store.
Apple requires that localised metadata be added with a new version submission. Plan your localisation work to align with your next release cycle. You can localise one language at a time — you need not localise all 11 simultaneously.
Adding a new localisation is only the beginning. To maximise impact, treat each localisation as a distinct product page optimisation project.
The iOS keyword field gives you 100 characters — a particularly valuable space since it is indexed by Apple's search algorithm but not visible to users. For Indic languages, consider:
๐ก EXPERT TIP
Use the 100-character keyword field strategically. Since the app name (30 chars) and subtitle (30 chars) are also indexed, avoid duplicating keywords across these three fields. That gives you an effective 160 characters of keyword real estate per language. Learn more in our guide: How to Optimise the iOS Keyword Field.
Whilst the App Store description is not directly indexed for search on iOS, it plays a crucial role in conversion. A well-localised description signals to users that your app genuinely supports their language and cultural context — not merely a machine-translated afterthought.
โ COMMON MISTAKE
Machine translation alone is not localisation. Google Translate or AI-generated translations of Indic languages frequently produce awkward or inaccurate phrasing. Users notice immediately, and it damages trust. Always have native speakers review and refine your descriptions. Budget for professional localisation — the ROI on conversion rate improvements alone typically justifies the cost.
Screenshots are the single most influential conversion element on the App Store product page. Localising them is not optional — it is essential.
For a deep dive on creative optimisation, see: Creative Optimisation & Creative Strategy.
๐ก EXPERT TIP
Create a modular screenshot template system. Design screenshot frames with swappable text layers and interchangeable UI mockups. This lets you produce localised screenshots at scale without redesigning from scratch for each language. Tools like Figma variables or Sketch overrides make this efficient.
See how creative optimisation drives real results: How to Boost Conversion by 35% with Product Page Optimisation.
Apple has released new App Store download badges in all 11 languages. Use these in your marketing materials:
If you cannot localise for all 11 languages at once, use this framework to prioritise based on market size, strategic value, and effort required:
| HIGH | Bangla, Tamil, Telugu, Marathi | Largest speaker populations among the new languages. High smartphone penetration in West Bengal, Tamil Nadu, Andhra Pradesh/Telangana, and Maharashtra. Strong existing app demand with limited localised competition. |
| MED | Gujarati, Kannada, Malayalam, Urdu | Significant user bases with growing digital adoption. Gujarat and Karnataka are major economic hubs. Urdu opens the Pakistan market alongside Indian Urdu speakers. |
| LOW | Odia, Punjabi, Slovenian | Smaller addressable markets but still valuable for apps with existing traction or specific category relevance in these regions. Slovenian is relevant for EU compliance and Slovenian-market apps. |
๐ก EXPERT TIP
Check your existing analytics first. If your app already sees meaningful traffic from Karnataka, prioritise Kannada — regardless of the general framework. Your own data should always override generic prioritisation.
For a practical approach to market expansion, our guide on utilising app localisation to enlarge your app market walks through the decision framework in detail.
Apple's expansion to 50 supported localisations is a clear signal: the future of mobile app growth is multilingual and multi-regional. The developers and marketers who treat this as a strategic opportunity — rather than a checkbox exercise — will see compounding returns in organic visibility, conversion rates, and user retention.
India, in particular, represents a market where the gap between opportunity and optimisation is massive. Nine new Indian languages mean nine new keyword ecosystems with minimal competition. The window of low competition will not remain open indefinitely.
Start with the languages that align with your existing user base, invest in genuine localisation (not translation), and build a systematic approach to managing multilingual product pages at scale. For developers new to ASO strategy, our App Store Optimisation resource hub and advanced ASO localisation services are strong starting points.
Mobile App Growth,App Store Optimisation,
Get FREE Optimization Consultation
Let's Grow Your App & Get Massive Traffic!
All content, layout and frame code of all ASOWorld blog sections belong to the original content and technical team, all reproduction and references need to indicate the source and link in the obvious position, otherwise legal responsibility will be pursued.