Localizing your app listing into Persian

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.

Persian is the clearest case of the two stores diverging: Google Play accepts Persian store listings in four variants, and Apple has no Persian App Store localization at all. There is no field to put it in.

If Persian-speaking users matter to you, the listing work happens on Play, and on iOS the practical route is in-app localization plus an English listing.

Where a Persian listing appears

Only on Google Play. Apple’s App Store localization list has no entry for Persian, so there is no Persian field in App Store Connect — the storefronts where Persian is spoken default to another language, usually English (U.K.). On Play the listing is available under fa, fa-AE, fa-AF, fa-IR.

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 Perso-Arabic at about 2 bytes per character leaves roughly 50 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 Persian in an afternoon and not doing it at all.