AppScreenshots DocsLocalize screenshot sets
Turn one approved master set into reviewed screenshots for every target market.
Localize screenshot sets
Localize after the master-language design is approved. This keeps every market tied to the same product story while giving each language enough room to read naturally.
Before you begin, separate the website interface locale from the screenshot-project locale. The website uses zh, zh-hk, and pt-br, while project content uses zh-CN, zh-TW, and pt; they are related, but they are not interchangeable. Use the full language support and locale mapping when you create the release brief and export package.
Recommended order
- Complete and approve the master-language frames with real product screens.
- Open the language selector in the editor header and choose Manage Languages.
- Set the master language, then enable only the delivery languages required for this release.
- Translate and review the text in every frame.
- Switch through each language on the canvas, fix overflow and visual balance, then export.
Do not translate a design that is still changing. Finish the message hierarchy and screen order first; otherwise every visual change becomes repeated localization work.
Set up the language plan
Use the language manager to set a default language and add target locales. The editor supports English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish, French, German, Portuguese, Russian, Arabic, Hindi, Thai, and Vietnamese where available. Select the screenshot-project locale, not merely the language shown in the website URL.
Before enabling a locale, decide these four things with the product or marketing owner:
| Decision | What to record |
|---|---|
| Market | The storefront or audience receiving this set. |
| Source language | The approved master copy that translators should interpret. |
| Reviewer | The person who can approve meaning, terminology, and screenshots for that market. |
| Delivery name | A short locale code or folder name that will be recognizable after export. |
Translate text in the editor
Select a text element, then use its content settings to edit the current language. You can also define a suitable font per language when the default typeface does not support the script or makes the hierarchy hard to read.
There are two useful working modes:
| Mode | Best for |
|---|---|
| Edit one text element | Approved marketing copy, legal terms, product names, or a small correction. |
| Batch Translate | A fast first draft across enabled languages, followed by human review. This option is marked for Pro/Lifetime access in the product. |
AI translation can speed up a first pass, but it cannot verify your product’s actual terminology, regional claims, or line breaks. Keep approved copy in the project brief or a shared source document, then paste it into the relevant language fields.
Perform a visual review for every locale
Change the active language from the editor header. Review all frames as both an editor view and a small thumbnail, because users encounter the set in a compact storefront context.
| Check | What to look for |
|---|---|
| Completeness | Every headline, subhead, label, and relevant badge has deliberate text for the selected locale. |
| Meaning | The translated statement makes the same promise as the master; it is not merely word-for-word. |
| Layout | Longer copy has not collided with the device, been clipped, or reduced to an unreadable size. |
| Script support | The chosen font renders all characters correctly, especially CJK, Arabic, Hindi, Thai, and Vietnamese. |
| Product proof | The app screen, date, price, currency, and market-specific content are correct for the locale. |
| Direction | Arabic copy and visual alignment feel intentional; confirm right-to-left treatment with a native reviewer. |
If text appears in the default language after switching locales, treat it as a missing-translation warning. The editor may fall back to default content, but an export is only ready when that fallback is deliberate and approved.
Keep translation changes manageable
- Use the same frame order and core benefit across locales unless research or local policy requires a distinct story.
- Keep the master project intact. Duplicate it before testing a market-specific visual direction.
- Avoid baking text into a raster background or app screenshot; editable text is easier to review and update.
- Name market-specific copies clearly, for example
Habit Planner — Japanese review.
When every language passes review, continue with Export screenshots. For later product changes, see Publish and maintain screenshot sets.