When it comes time to take your app to international markets, it is essential that you consider all areas that can promote your app. Google Play Store localizations are a great opportunity to bring a multi-lingual approach to your app’s online presence by making an SEO friendly listing optimized for new user discovery. Unlike the App Store which offers 39 languages, the Play Store offers a whopping 84 potential language localizations. Plenty of languages to get started!
Do I have to localize my Play Store listings? No, definitely not. The decision to localize your app’s listing comes down to a question of both necessity and opportunity. If you are already an internationally used app then localizing might be a necessity to maintain your diverse users. On the other hand, if your app is developing you may want to consider how much opportunity you actually have outside of your current market. There are a few reasons why you may NOT want to localize as well.
When it comes to SEO, what’s important for the Play Store? When you think of optimizing your Play Store for discoverability, the approach is much more traditional in the website sense of search engines. The App Store has limited areas for keywords, but the Play Store is more diverse or inclusive. The app name, description, and short description can all be factors.
SensorTower illustrates the most to least impactful touch points of your listing with this simple infographic:

Available Play Store Localizations
There are 84 total languages available currently for the Play Store. Below is a list of these as well as their respective ISO locales. It is important to note how Google allows for niche dialects focusing in areas like English, Spanish, and multiple long-tail languages as well.
Language | Locale |
Afrikaans | af |
Amharic | am |
Arabic | ar |
Armenian | hy-AM |
Azerbaijani | az-AZ |
Bangla | bn-BD |
Basque | eu-ES |
Belarussian | be |
Bulgarian | bg |
Burmese | my-MM |
Catalan | ca |
Chinese (Hong Kong) | zh-HK |
Chinese (Simplified) | zh-CN |
Chinese (Traditional) | zh-TW |
Croatian | hr |
Czech | cs-CZ |
Danish | da-DK |
Dutch | nl-NL |
English (Australia) | en-AU |
English (Canada) | en-CA |
English (India) | en-IN |
English (Singapore) | en-SG |
English (UK) | en-GB |
English (US) | en-US |
English (South Africa) | en-ZA |
Estonian | et |
Filipino | fil |
Finnish | fi-FI |
French | fr-FR |
French (Canada) | fr-CA |
Galician | gl-ES |
Georgian | ka-GE |
German | de-DE |
Greek | el-GR |
Hebrew | iw-IL |
Hindi | hi-IN |
Hungarian | hu-HU |
Icelandic | is-IS |
Indonesian | id |
Italian | it-IT |
Japanese | ja-JP |
Kannada | kn-IN |
Kazakh | kk |
Khmer | km-KH |
Korea (South) | ko-KR |
Kyrgyz | ky-KG |
Lao | lo-LA |
Latvian | lv |
Lithuanian | lt |
Macedonian | mk-MK |
Malay | ms |
Malay (Malaysia) | ms-MY |
Malayalam | ml-IN |
Marathi | mr-IN |
Mongolian | mn-MN |
Nepali | ne-NP |
Norwegian | no-NO |
Persian | fa |
Persian (Afghanistan) | fa-AF |
Persian (Iran) | fa-IR |
Persian (UAE) | fa-AE |
Polish | pl-PL |
Portuguese (Brazil) | pt-BR |
Portuguese (Portugal) | pt-PT |
Punjabi | pa |
Romanian | ro |
Romansh | rm |
Russian | ru-RU |
Serbian | sr |
Sinhala | si-LK |
Slovak | sk |
Slovenian | sl |
Spanish (LATAM) | es-419 |
Spanish (Spain) | es-ES |
Spanish (United States) | es-US |
Swahili | sw |
Swedish | sv-SE |
Tamil | ta-IN |
Telugu | te-IN |
Thai | th |
Turkish | tr-TR |
Ukrainian | uk |
Vietnamese | vi |
Zulu | zu |
Example of a localized Play Store listing
Here Skype is seen in Traditional Chinese (zh-TW). Skype has been incredibly successful in its international efforts and is localized into more than 40 languages.

Character Limitations: Why they matter
As you translate your app to and from the source language, keep in mind that the target language can be more or less characters depending on your source language. Let’s say your source language is English (AU) but you are localizing into Korean. You are likely to have additional space for more characters since Korean is typically more descriptive with less space than English. Each language will be different in this circumstance so be considerate to spacing and your priorities.
This table below helps as a quick reference for each section of the Play Store and your character limitations.
Category | Play Store |
Title | 50 |
Subtitle | 80 |
Descriptions | 4,000 |
SKU Titles | 55 |
SKU Descriptions | 80 |
AB Testing
It wouldn’t be right to mention Play Store localizations without at least mentioning the capability to AB test. One of the greatest benefits to the Play Store is that you can actually try multiple variants and see how they perform. This is ideal for visual testing but also for other aspects of localization as well. AB testing deserve a detailed post itself and maybe I will do one in the future.
In Conclusion
It is reassuring that Google lists Play Store localization as part of its Localization checklist and Going Global Playbook, which to me are both indicators of how important this can be for your app. If you’d like to hear more about this topic, feel free to let us know so we know what topics to focus on for future posts.
Have you done any Play Store localization before? Are you planning to soon? Start a discussion with us below.
If you are interested in app store optimization consultant that won’t break the bank, drop us a line here.
Stay tuned for more posts in the future on the Localization Blog.

6 comments
Pingback: iTunes Connect Localizations - Backpacking Diplomacy
Pingback: Arabic and Hebrew added to the App Store - Backpacking Diplomacy
Pingback: App store localization: Intro to ASO localization - Backpacking Diplomacy
Pingback: Localization resources for l10n professionals - Backpacking Diplomacy
Pingback: iTunes Connect Localizations - Backpacking Diplomacy
Pingback: Recursos para Localizacion de Lenguas y Software - Backpacking Diplomacy