Ten supported choices
The current locale set covers es, pt-BR, fr, de, it, ja, ko, zh-CN, hi, and ar alongside the English base campaign.
Localized app store screenshots
One campaign, adapted for every market.
Choose from ten supported locales and Storeboard adapts the short marketing headlines instead of translating them word for word. Listing copy is localized in the same pass, then each selected language gets its own image renders and export folders.
Low-quality drafts use no credits. Sign up free to try the workflow.
Storeboard
Localization
Supported locale set
Extra locales10 choices
Headlines3-6 words
ExportPer locale
One project keeps the direction, files, and store details together.
How it works
From source to finished asset in three clear steps.
- 01
Finish the base message
Approve the English headlines and listing copy first so every translation starts from the same campaign strategy.
- 02
Choose the locales
Select any combination of Spanish, Brazilian Portuguese, French, German, Italian, Japanese, Korean, Simplified Chinese, Hindi, and Arabic.
- 03
Render and organize
Storeboard generates the localized image variants and places finished screenshots and listing text into folders keyed by locale.
Adapted, then constrained
Short copy stays punchy across languages.
The localization prompt asks for marketing adaptation, not literal translation. It keeps screenshot headlines short and runs the same hard listing limits on every localized result.
One coordinated request
Selected locales are translated together so their headlines remain in the same order and map cleanly to the original screenshot concepts.
Store-safe text fields
Apple and Google character limits are enforced again after localization, when longer translations are most likely to overflow.
Locale-first exports
Standard downloads use one folder per locale. The Fastlane option maps assets and Android listing files into the expected locale structure.
Frequently asked questions
The practical details.
Which languages does Storeboard support?
The English base can be adapted into Spanish, Brazilian Portuguese, French, German, Italian, Japanese, Korean, Simplified Chinese, Hindi, and Arabic.
Are the headlines translated literally?
No. Storeboard asks for punchy marketing adaptations that preserve the message while keeping each screenshot headline to roughly three to six words.
Does listing copy get localized too?
Yes, when a base listing exists. Apple and Google listing fields are translated with their original structure and character limits preserved.
How are localized files organized?
Standard exports use a top-level folder for each locale. Fastlane exports map screenshots and Play listing metadata into locale-specific directories.
Keep building
More ways to finish the listing.
App Store screenshots
Generate cohesive App Store and Google Play screenshot sets at the exact sizes each store expects.
Explore featureListing copy and ASO
Write App Store and Google Play listing copy with hard character limits and competitor-informed keyword suggestions.
Explore featureTeams and agencies
Keep shared projects, pooled monthly credits, team invites, and read-only client previews in one studio.
Explore featureFrom the blog
Notes on getting this right.
Start with a free draft
Take the campaign beyond English.
Adapt the message, render each locale, and keep every market organized in one project.
Localize my store assets