Skip to main content

Localization reference

App Store and Google Play screenshots, language by language

Every language row states the code App Store Connect expects, the code Play Console expects, the text direction the layout has to follow and how much the translated copy changes length — read from the same locale modules the editor and the export worker render with.

Languages ScreenCraft can localize screenshots into
LanguageApp StorePlay
Japanesejaja-JP
Germandede-DE
Koreankoko-KR
Portuguese (BR)pt-BRpt-BR
Chinese (Simplified)zh-Hanszh-CN
Arabicarar-SA

6 languages documented so far — the table grows as more language pages ship. ScreenCraft itself covers 44 languages in the editor and the export worker.

Two consoles, two code systems

App Store Connect and Play Console do not always agree on a locale code. ScreenCraft normalizes between the two on upload, so the language you pick in the editor is the language both consoles receive. These are the differences across the languages documented here:

  • Japanese App Store ja · Play ja-JP
  • German App Store de · Play de-DE
  • Korean App Store ko · Play ko-KR
  • Chinese (Simplified) App Store zh-Hans · Play zh-CN
  • Arabic App Store ar · Play ar-SA

A language missing from this list uses the same code in both consoles.

Check a headline before it ships

The free text-fit checker answers the question these ranges only approximate: paste the translation you got back and see whether it fits the headline box with the editor's own auto-fit rules. It needs no account and nothing leaves your browser.

Open the free text-fit checker

Design once, export every language

ScreenCraft lays out the screens once, applies the translation per language, mirrors the right-to-left scripts and exports each store's folder structure as one ZIP.

Try ScreenCraft free