Language guide

Translate App Store Screenshots to Chinese (Simplified)

Upload Simplified Chinese screenshots to the zh-Hans localization in App Store Connect and to zh-CN in Google Play Console. Translate both captions and the in-app UI, use full-width Chinese punctuation, keep Simplified and Traditional sets apart, and have a native reader check line breaks and glyph shapes before you publish.

Last updated:

Which store locale codes should you use?

App Store Connect
CodeLanguageNotes
zh-HansChinese (Simplified)Shown as Chinese (Simplified) in App Store Connect (opens in a new tab); zh-Hans is a script code, not a region, per Apple's locale shortcodes (opens in a new tab).
Google Play Console
CodeLanguageNotes
zh-CNChinese (Simplified)Region code. Traditional Chinese is separate (zh-TW, zh-HK) in Play Console (opens in a new tab).

Why do the two stores use different codes for the same language?

Apple names Chinese by writing system, so the App Store Connect shortcode is zh-Hans for Simplified and zh-Hant for Traditional (Apple: locale shortcodes (opens in a new tab)). Google Play names it by region: zh-CN for Simplified, with zh-TW and zh-HK as separate Traditional listings (Play Console Help (opens in a new tab)).

The practical consequence is a mapping step at upload time. One exported Simplified set goes to zh-Hans on iOS and zh-CN on Android; nothing in it should be reused for the Traditional listings.

Which typography problems show up in Chinese screenshots?

Most issues come from treating Han text like Latin text. The W3C Chinese layout requirements (CLREQ (opens in a new tab)) describe the conventions a native reader expects; these are the ones that surface most often in store visuals.

  • Half-width punctuation. Chinese uses full-width marks such as ,。:“” and 《》. An ASCII comma or period next to Han characters looks like a copy-paste slip.
  • Punctuation position. In mainland typography, pause and stop marks sit in the lower-left of their square in horizontal text, while Taiwan and Hong Kong center them (CLREQ §2.1.2 (opens in a new tab)). A font tuned for Traditional text can place them wrong for a zh-CN audience.
  • Forbidden line starts and ends. Closing marks like ,and 。 should not begin a line, and opening quotes or brackets should not end one (CLREQ §6.1.1 (opens in a new tab)). Automatic wrapping in a narrow caption box breaks this rule easily.
  • Mixed Han and Latin. In horizontal text, CLREQ describes a gap of up to a quarter of a Han character between Han characters and Western letters or numerals, or a regular word space, applied consistently and never at the start or end of a line (CLREQ §6.3.3 (opens in a new tab)). Pick one approach for product names like "iPhone" and figures like "4K" and use it in every caption.
  • No word spaces. Chinese has no spaces between words, so a translator's stray spaces show up as uneven gaps in a headline.

How do fonts affect Simplified Chinese screenshots?

Many characters share a code point across Chinese, Japanese and Korean but are drawn differently in each region's fonts. A Japanese or Traditional-oriented typeface can render familiar Simplified characters with shapes that look slightly off to mainland readers.

The eight caption fonts in the StoreLocale editor (Inter, Poppins and others) are Latin typefaces, so Han characters in caption layers are drawn with a fallback font from the operating system and browser. That fallback can differ between computers, so export every Chinese set from the same machine and review the PNGs; a clean sans-serif (Hei style) look suits short marketing lines.

Will Chinese captions be shorter than English?

Often in character count, but not reliably in width. The W3C article on text size in translation (opens in a new tab) counts each Chinese character as two English characters in width and notes that non-Latin scripts often need taller lines. In its single-word example from a Traditional Chinese interface, "views" translates at a ratio of 1.2, slightly longer than English.

Dense characters also lose detail at small sizes. A six-character headline that fits easily can still be hard to read at phone thumbnail size if it is set at the same point size as the English caption, so size Han text up rather than down.

What does StoreLocale produce for Simplified Chinese?

StoreLocale translates detected in-app UI text and caption layers into its zh target, which is Simplified Chinese (简体中文). Traditional Chinese is a separate target, zh-TW (繁體中文), so you can build both sets from the same English project without mixing characters.

Where each StoreLocale output goes
StoreLocale codeScriptApp Store ConnectGoogle Play Console
zhSimplifiedzh-Hanszh-CN
zh-TWTraditionalzh-Hantzh-TW (and zh-HK if you use it)

Exports are PNG files in a ZIP, with a locale folder named zh. StoreLocale does not upload to either console, so drag that folder's files into the zh-Hans and zh-CN listings yourself. Text detection and translation cost no credits; the AI repaint of each screenshot uses 1, 2 or 4 credits depending on the Standard, Pro or Ultra tier.

The repaint is generative, so treat every Chinese image as a draft for review. Brand names and marks such as 4K, HD or PRO stay untranslated by default, and the compare view puts the English source next to the Chinese result.

What should a native reviewer check before upload?

  1. Every character is Simplified. Search for Traditional forms of very common characters (such as those for "this", "say" and "will", or the plural marker) that slipped in from mixed sources.
  2. Punctuation is full-width and sits in the lower-left of its square, and no line starts with ,。!? or a closing quote.
  3. Product names, prices and numbers keep their Latin form with a narrow, consistent gap next to Han text.
  4. Glyphs look mainland-standard, with no Japanese-style or Traditional-style shapes from a fallback font.
  5. Headlines read naturally to a mainland user rather than as a word-for-word rendering of the English.
  6. Repainted UI text matches the original font weight and color, and nothing outside the text regions changed.

Frequently asked questions

Is zh-Hans the same as zh-CN?

Both mean Simplified Chinese in store listings. App Store Connect uses the script code zh-Hans and Google Play Console uses the region code zh-CN, so upload the same Simplified set to each.

Can one Chinese screenshot set serve Taiwan and Hong Kong?

No. Taiwan and Hong Kong readers use Traditional characters and center their punctuation. Create a separate Traditional set with StoreLocale's zh-TW target and upload it to zh-Hant on Apple and zh-TW or zh-HK on Google Play.

Why does Chinese text look different when exported on another computer?

StoreLocale's caption fonts are Latin typefaces, so Chinese characters use a fallback font chosen by the operating system and browser doing the export. Export from one consistent machine, review the PNGs, and have a native reader confirm the glyph shapes.

Should Chinese captions use a smaller font to match the English line length?

Usually not. Han characters are dense and lose legibility quickly at thumbnail size. Keep the caption shorter instead and give each character at least the size you used for English.

Does translating Chinese screenshots cost credits?

Text detection and translation are free. Repainting a screenshot with the translated UI costs 1, 2 or 4 credits per image depending on the quality tier, or no platform credits with your own API key.

Sources

  1. Apple: Managing metadata by using locale shortcodes
  2. Apple: App Store localizations
  3. Apple: Localize app information
  4. Google Play Console Help: Translate and localize your app
  5. W3C: Requirements for Chinese Text Layout (CLREQ)
  6. W3C: Text size in translation

Related pages

Translate your next screenshot set with StoreLocale

Upload your screenshots, pick target languages, and review every localized version before you export.