Localize App Store Screenshots to Chinese (Traditional)
繁體中文
Taiwan + Hong Kong + Macao = ~30M users. High ARPU, strong premium app market.
Why Chinese (Traditional) matters
Traditional Chinese serves Taiwan, Hong Kong, and Macao. Small in population (~30M) but high in ARPU and premium-app spend, with demanding localization standards. Users spot Simplified-to-Traditional auto-conversion in seconds, because the two differ in vocabulary and phrasing, not just character shapes.
Book a table at your favorite restaurant
在你最愛的餐廳輕鬆訂位
Localization tips for Chinese (Traditional)
- 1 Use Noto Sans TC (or Noto Sans HK) and PingFang TC. Traditional-specific forms; a Simplified font substitutes wrong or missing glyphs.
- 2 Vocabulary splits between Taiwan and Hong Kong: 軟體/軟件 (software), 網路/網絡 (network), 影片/短片 (video clip). Localize each separately when both markets matter.
- 3 Traditional characters carry more strokes; test readability at 14-16px screenshot sizes, where dense characters like 觀, 籲, 鑰 can turn to mush.
- 4 Taiwan (MOE standard) and Hong Kong (HKSCS) even differ in glyph shapes for some characters (骨, 內, 直). Match the font build to the target region.
- 5 Hong Kong users are English-fluent and comfortable with mixed English/Chinese UI; Taiwan expects fuller Chinese localization.
- 6 Text contracts ~50% vs English; use full-width punctuation and Traditional-style「」quotation brackets rather than straight "".
Fonts for Chinese (Traditional)
Noto Sans TC (Taiwan MOE forms) or Noto Sans HK (Hong Kong HKSCS forms), plus PingFang TC on iOS. The TW and HK builds differ on characters like 骨, 內, 直; never reuse a Simplified font, which lacks or wrongly maps traditional characters.
Most common mistake
Running a Simplified-to-Traditional character conversion and calling it done. The vocabulary and phrasing differ (软件 mechanically becomes 軟件, but Taiwan actually says 軟體), so the result reads as mainland text in traditional clothing.
Chinese (Traditional) localization FAQ
What App Store Connect locale code should I use for Chinese (Traditional)?
Use zh-Hant (iOS) / zh-TW (Google Play) when adding Chinese (Traditional) (繁體中文) screenshots in App Store Connect or Google Play Console. Using the wrong code means your localized screenshots never reach Chinese (Traditional) users.
Does text expansion affect Chinese (Traditional) screenshot design?
Chinese (Traditional) runs -50% vs English on average character count. You should design buttons and headlines with explicit overflow headroom, because text that fits in English will break in Chinese (Traditional).
Does Shotlingo automatically localize screenshots to Chinese (Traditional)?
Yes. Shotlingo auto-translates your App Store screenshot text to Chinese (Traditional) (繁體中文) with AI that respects text expansion, and platform-appropriate fonts. Export the localized bundle ready for App Store Connect locale zh-Hant (iOS) / zh-TW (Google Play).
Do I have to translate my App Store screenshots to Chinese (Traditional)?
If Chinese (Traditional) is a major market for your app, yes. Unlocalized screenshots significantly reduce conversion, because users scroll past copy they cannot read. Even partial localization (headlines only) typically beats English-only.
Localize your screenshots to Chinese (Traditional) automatically
Shotlingo handles expansion, fonts, and App Store Connect locale codes for you. Free to try.
Try Shotlingo free →