AppScreenshots DocsLanguage support and locale mapping
Choose the correct website, help-center, and screenshot-project language for every market.
Language support and locale mapping
AppScreenshots has three language layers. Keep them separate when planning a release: changing the website interface does not translate a screenshot project, and a screenshot-project locale does not change the help article you are reading.
| Layer | Purpose | Where you choose it |
|---|---|---|
| Website interface | Navigation, product controls, and account pages | The website language menu and locale URL. |
| Help-center article | The language of documentation source content | The help-center language route. |
| Screenshot project | Headlines, labels, and per-frame copy that will be exported | Manage Languages in the Screenshot Editor. |
Website interface languages
The website supports these interface locales. The value in the first column is the locale used in the website URL and language selector.
| Website locale | Display language |
|---|---|
en | English |
zh | 简体中文 (Simplified Chinese) |
zh-hk | 繁體中文 (Traditional Chinese) |
ja | 日本語 (Japanese) |
ko | 한국어 (Korean) |
es | Español (Spanish) |
pt-br | Português (Brazilian Portuguese) |
de | Deutsch (German) |
fr | Français (French) |
ru | Русский (Russian) |
ar | العربية (Arabic) |
hi | हिन्दी (Hindi) |
th | ไทย (Thai) |
vi | Tiếng Việt (Vietnamese) |
Use the correct project locale
The Screenshot Editor supports the same market coverage, but uses content-oriented locale codes. Use this mapping in release briefs, export folders, and QA checklists.
| Website locale | Screenshot-project locale | Notes |
|---|---|---|
en | en | English master or delivery version. |
zh | zh-CN | Simplified Chinese. |
zh-hk | zh-TW | Traditional Chinese. Confirm regional terminology with the market reviewer. |
ja | ja | Japanese. Allow room for dense CJK copy. |
ko | ko | Korean. Check font support and line breaks. |
es | es | Spanish. Confirm regional terminology for the target market. |
pt-br | pt | Portuguese project content; confirm Brazilian wording for a Brazilian release. |
de | de | German. Plan for longer compound words. |
fr | fr | French. Review punctuation and expanded text length. |
ru | ru | Russian. Confirm Cyrillic font support. |
ar | ar | Arabic. Review right-to-left wording and alignment with a native reviewer. |
hi | hi | Hindi. Confirm Devanagari font rendering. |
th | th | Thai. Check character shaping and line height. |
vi | vi | Vietnamese. Ensure the selected font supports all diacritics. |
Important: A website locale is not an export-language setting. Set the project language explicitly in the editor, then verify the active language again before each export.
Help-center language availability
The product interface is available in all 14 website locales above. Help articles are currently authored and maintained in English and Simplified Chinese so terminology and product steps remain reviewed. For a website locale without a separately authored help article, the help center uses the maintained source language:
zh-hkuses the Chinese help-center route.- All other non-authored website locales use the English help-center route.
This is intentional: it prevents an untranslated page from appearing as though it were native content. The language matrix above still applies to the Screenshot Editor and exported assets in every supported market.
Apply this to a release
- Pick the website interface language that makes the product easiest for the working team to use.
- Set the master language in Manage Languages based on the approved source copy.
- Enable only the screenshot-project locales needed for the release.
- Assign a native reviewer for every target locale, especially Arabic and market-specific Chinese or Portuguese content.
- Export using an unambiguous locale folder or filename suffix, then verify language, screen content, and target store together.
Continue with Localize screenshot sets for the complete review and export process.