Your app is localised. Your screenshots are not.
Generate the same gallery in up to 5 languages per batch, with headlines written natively for each storefront and right-to-left layouts mirrored rather than right-aligned.
Every supported storefront language
Pick any 5 per batch. Right-to-left languages are marked.
- English (US)
- English (UK)
- Spanish (ES)
- Spanish (LATAM)
- French (FR)
- German (DE)
- Japanese (JP)
- Chinese Simplified
- Chinese Traditional
- Portuguese (BR)
- Portuguese (PT)
- Italian (IT)
- Korean (KR)
- Hindi (HI)
- Arabic (AR)RTL
- Russian (RU)
- Turkish (TR)
- Dutch (NL)
- Polish (PL)
- Swedish (SE)
- Indonesian (ID)
- Vietnamese (VN)
- Thai (TH)
- Ukrainian (UA)
- Czech (CZ)
- Romanian (RO)
- Greek (GR)
- Hungarian (HU)
- Danish (DK)
- Finnish (FI)
- Norwegian (NO)
- Hebrew (IL)RTL
- Malay (MY)
- Filipino (Tagalog)
- Bengali (BD)
- Urdu (PK)
- Swahili (KE)
- Persian (IR)RTL
- Tamil (IN)
- Telugu (IN)
Why the gallery is the part worth localising first
Localised listings convert measurably better
Store users browsing a non-English storefront read an English headline as "not built for me". Translating the app but leaving the gallery in English is the most common half-finished localisation.
Screenshots are indexed differently from metadata
Apple and Google index your title, subtitle and keywords per storefront. Your screenshots are not indexed — but they are the reason a person who found you actually installs, which is what feeds ranking.
Machine translation shows
A word-for-word rendering of "Track every rupee, effortlessly" is not how a native speaker writes marketing copy. Each locale here is written natively from the meaning, not converted from the English string.
Numbers and currency live inside the frame
A German listing showing $ amounts and MM/DD dates undercuts the translation around it. Localised copy covers the promotional layer; keep your uploaded screens locale-appropriate too.
Plan for text expansion, not just translation
A headline that fits on one line in English will not fit on one line in German. These are the shifts that break a layout, measured against English at 100.
| Language | Length vs English | What it does to the layout |
|---|---|---|
| German | +20 to 35% | Compound nouns wrap to a second line and shrink the headline. |
| French | +15 to 20% | Longer connectives; four-word English lines become six. |
| Spanish | +15 to 25% | Similar to French, plus longer verb forms. |
| Russian | +10 to 20% | Long words with few break points, so wrapping is unforgiving. |
| Japanese | −30 to 50% | Much shorter, but needs larger type to stay legible at thumbnail size. |
| Chinese | −40 to 50% | Shortest of all; a short line can look under-set unless the type grows. |
| Arabic | +20 to 25% | Expands and reverses direction — the whole layout mirrors, not just the text. |
Right-to-left: Arabic, Hebrew, Persian mirror the whole promotional composition — headline alignment, badge position and reading order — rather than right-aligning a layout that was designed left to right.
How a localised batch runs
- 1
Pick up to five languages per batch
The generator accepts 5 locales in one run. Run additional batches for further storefronts — the theme analysis is shared, so set eleven looks like set one.
- 2
Copy is written, not converted
The model is instructed to write idiomatic marketing copy a native speaker would write, using typography and weights that render the script legibly.
- 3
Your UI is left alone
Only the promotional copy around the device is localised. The interface inside the frame stays exactly as you uploaded it.
- 4
RTL layouts mirror properly
Arabic, Hebrew and Persian mirror the whole promotional composition so alignment and reading flow run right to left, rather than just right-aligning the text.
- 5
Export is foldered per language
The ZIP splits by store and by locale, so uploading to eleven storefronts is eleven drag-and-drops rather than an afternoon of renaming.
Localisation questions
How many languages are supported?+
40 store languages, covering every major App Store and Google Play storefront including both Chinese scripts, both Portuguese variants, Latin American and European Spanish, and the three right-to-left languages.
Can I generate all languages at once?+
A single batch takes up to 5 locales. That cap keeps one generation predictable; run several batches back to back for a wider rollout. Because every batch shares the same theme analysis, the sets stay visually identical across languages.
Which languages should I start with?+
Your top five install markets, taken from your own store analytics rather than a generic list. For most apps that means English plus some combination of German, Japanese, Simplified Chinese, Brazilian Portuguese, Spanish and Korean — but your data beats that guess.
Does it translate text inside my app screenshots?+
No, and deliberately. The interface inside the device frame is your product; changing it would misrepresent the app. Upload localised app screens if you want the UI localised too — the promotional copy around them is generated in the target language either way.
How does right-to-left work?+
For Arabic, Hebrew and Persian the promotional layout is mirrored: headline alignment, badge placement and visual flow all run right to left. A right-aligned English layout is not the same thing and reads as a translation bolted onto a Western composition.
The strategy side — which markets to enter and in what order — is covered in the app store localisation guide.