Localize App Store Screenshots to Japanese
日本語
~100M smartphone users. Japan is Apple's #3 App Store market by revenue.
Why Japanese matters
Japan is a hyper-localized market and Apple's #3 App Store by revenue: Japanese users expect native copy, and machine-translated English is obvious and trust-destroying. The writing system is uniquely forgiving on layout, though, because kanji pack dense meaning into few characters. A translated headline usually ends up shorter than the English it replaces.
Track your sleep and wake up refreshed
睡眠を記録して、すっきり目覚めよう
Localization tips for Japanese
- 1 Use Noto Sans JP or Hiragino Sans. A plain Noto Sans without the JP variant falls back to Chinese glyph shapes (骨, 直, 今 differ subtly) that look wrong to Japanese readers.
- 2 Avoid bold italic. Japanese typography rarely uses italics and it looks cluttered; vary weight instead.
- 3 Mind line-breaking (kinsoku shori): there are no word spaces, so set breaks that never orphan a small kana or start a line with closing punctuation (。、」).
- 4 Keep the product name in Latin ("Shotlingo"), not katakana (ショットリンゴ). Katakana-izing a brand reads as old-fashioned and lowers trust.
- 5 Balance the script mix. An all-kanji headline reads stiff and bureaucratic; native marketing copy leavens kanji with hiragana and katakana.
- 6 Kanji are information-dense, so Japanese headlines run ~45% SHORTER than English. You gain space, but resist the urge to oversize the font to fill it.
Fonts for Japanese
Noto Sans JP, Hiragino Sans (iOS system), Yu Gothic. Use the JP-specific build so shared Han characters (骨, 直, 今) take Japanese glyph shapes rather than Chinese; avoid Mincho (serif) for UI unless you deliberately want an editorial tone.
Most common mistake
Leaving English UI screenshots with only the headline translated. Japanese users read the screenshot as a whole. If the buttons still say "Get Started" while the headline is Japanese, they assume the app is not actually localized and uninstall.
Japanese localization FAQ
What App Store Connect locale code should I use for Japanese?
Use ja when adding Japanese (日本語) screenshots in App Store Connect or Google Play Console. Using the wrong code means your localized screenshots never reach Japanese users.
Does text expansion affect Japanese screenshot design?
Japanese runs -45% 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 Japanese.
Does Shotlingo automatically localize screenshots to Japanese?
Yes. Shotlingo auto-translates your App Store screenshot text to Japanese (日本語) with AI that respects text expansion, and platform-appropriate fonts. Export the localized bundle ready for App Store Connect locale ja.
Do I have to translate my App Store screenshots to Japanese?
If Japanese 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 Japanese automatically
Shotlingo handles expansion, fonts, and App Store Connect locale codes for you. Free to try.
Try Shotlingo free →