Both stores let you publish a different listing per territory, and both index that localised text for search in that market. An English-only listing is invisible to a shopper searching in Japanese, and unconvincing to one who finds it — which is why localisation is usually the highest-return work left on a finished listing.
✓Apple publishes the default and additional languages of all 173 App Store storefronts — see the language pages for what each one adds
✓Play accepts three languages Apple has no localization for: Persian, Filipino, Swahili
✓Both stores index the localised text for search in that territory
Track every workout
9:41
Thursday, 12 June
Today
MR
6
Week streak
2 days to beat your record of 8 weeks.
612kcal
Burned
48min
Move
132bpm
Avg HR
Workout of the day
Upper body push
42 min · 6 exercises · Strength
Up next
FriLower body · legs38 min
SatZone 2 run45 min
TodayProgressPlansYou
Englishen-US
すべての運動を記録
9:41
Thursday, 12 June
Today
MR
6
Week streak
2 days to beat your record of 8 weeks.
612kcal
Burned
48min
Move
132bpm
Avg HR
Workout of the day
Upper body push
42 min · 6 exercises · Strength
Up next
FriLower body · legs38 min
SatZone 2 run45 min
TodayProgressPlansYou
日本語ja-JP
Registra cada entrenamiento
9:41
Thursday, 12 June
Today
MR
6
Week streak
2 days to beat your record of 8 weeks.
612kcal
Burned
48min
Move
132bpm
Avg HR
Workout of the day
Upper body push
42 min · 6 exercises · Strength
Up next
FriLower body · legs38 min
SatZone 2 run45 min
TodayProgressPlansYou
Españoles-ES
Deutschde-DE“Jedes Workout erfassen”6 shots
Portuguêspt-BR“Acompanhe cada treino”6 shots
+28 more languages
Copy
Translate the listing, not the fields
The title, subtitle, description and keyword field have to work together: the subtitle completes the title, and the keywords have to match the words the description uses. Translating them one at a time breaks those relationships. Here the whole listing is translated in one pass, and every field remains editable afterwards.
✓The copy comes from the ASO tool, or from whatever you already wrote
✓Apple’s keyword field is 100 bytes — a CJK character costs three of them, so the field holds ~33 characters in those languages
Captions are the first thing a shopper reads, and the part most teams skip because redrawing a set per language is a day of work. A locale variant reuses the design — same layout, same device frames, same backgrounds — and replaces only the caption text, so adding a language costs a translation, not a redesign.
✓Each locale gets its own set at the same store resolutions
✓What you upload to App Store Connect for Japan is a complete, correctly sized set — not the English images with a translated description
✓German and Finnish are the usual overflow offenders; check those two first
More than 30, covering the App Store and Google Play territories most apps sell into — the major European, East Asian, South Asian, Middle Eastern and Latin American locales.
Does localising a listing actually help downloads?
In non-English markets, consistently. Both stores index your localised text for search in that territory, and shoppers convert better on a listing in their own language — the screenshots matter as much as the description, because that is what they see first.
Do I have to redesign screenshots for every language?
No. Design one set, then generate a locale variant: the layout and device frames stay put and only the caption text is replaced with the translation, so twelve languages is one design, not twelve.
Can I edit a translation?
Yes, every translated field is editable. Machine translation gets you a complete listing in minutes; a native speaker reading it afterwards is still the difference between good and excellent.
