Localizing your app listing into Spanish

Storefronts and localization names read from Apple’s App Store localizations reference; language codes and field limits from Google Play’s translation language list and each store’s field reference. Checked August 29, 2026.

Spanish is the highest-leverage second language on the App Store, and the reason is structural: Spanish (Mexico) is the default language of 16 storefronts across Latin America, while Spanish (Spain) is the default of exactly one. If you add only one Spanish localization, add the Mexican one.

Play splits it differently again — es-419 for Latin America, es-ES for Spain, es-US for the United States — so a single Spanish translation covers far more of Play than of the App Store.

Where a Spanish listing appears

Apple publishes the default language of all 173 App Store storefronts. Spanish is the default in 17 of them, and an additional supported language in 3 more.

Default language in

Additionally supported in

What you translate, and what it costs you

Both stores cap the same fields, and neither cap changes by language — but the amount of meaning you fit inside them does. Apple’s keyword field is the one that surprises people: it is measured in bytes, so Latin at about 1 byte per character leaves roughly 100 characters. Google Play counts characters instead, and says so explicitly: its limits “apply to both full-width and half-width characters”.

The screenshots are part of the localization

Both stores let you upload a separate screenshot set per localization, and in practice the captions are what sells — a translated description under English screenshots converts like an English listing. Design the frames once, then export the same layout per language rather than rebuilding it: that is the difference between localizing into Spanish in an afternoon and not doing it at all.