Localize App Store Screenshots to Turkish
Türkçe
Turkey = ~85M people, emerging high-growth app market.
Why Turkish matters
Turkey is a large, young, Android-first market (~85M people) where lira volatility keeps users intensely price-sensitive, so free/discount framing in screenshots converts. Turkish is agglutinative: suffixes stack onto the root, so a tidy English 'Settings' can balloon into one long word. Vowel harmony then reshapes those suffixes to match the root's vowels, so you can't just glue strings together.
See where your money goes each month
Paranızın her ay nereye gittiğini görün
Localization tips for Turkish
- 1 Budget ~20% more width AND expect unusually long single words, because case/possessive suffixes attach to the root (e.g. 'görüntülerinizi' = 'your images' + accusative in one word).
- 2 Turkish has a dotted/dotless i distinction (İ/i and I/ı are four separate letters), so uppercasing must use the Turkish locale or 'giriş' wrongly becomes 'GIRIS' instead of 'GİRİŞ'.
- 3 Include ğ (soft g), ı (dotless i), ş, ö, ü, ç; a font that drops the dot distinction or the ğ breve makes correct words read as typos.
- 4 Default to formal 'siz' in marketing copy; informal 'sen' reads as talking down to adults and is reserved for teen or entertainment apps.
- 5 Vowel harmony forces suffixes to echo the root's vowels (-lar vs -ler, -ı/-i/-u/-ü); machine output that breaks harmony sounds robotic to natives.
- 6 Localize the currency to Turkish lira and lean on free/trial/discount messaging. Inflation makes price the dominant install trigger here.
Fonts for Turkish
Inter, Roboto, and Noto Sans all carry the full Turkish set (ğ ı İ ş ö ü ç), so glyph coverage is rarely the problem. The real risk is locale-aware casing: uppercase headlines with the 'tr' locale so 'i'→'İ' and 'ı'→'I' render correctly instead of the English 'i'→'I'.
Most common mistake
Uppercasing a headline with a default (English) locale so the dotted i is lost: 'İletişim'/'giriş' become 'ILETISIM'/'GIRIS'. Turkish readers parse the missing dot as a spelling error, and the whole screenshot looks machine-made.
Turkish localization FAQ
What App Store Connect locale code should I use for Turkish?
Use tr when adding Turkish (Türkçe) screenshots in App Store Connect or Google Play Console. Using the wrong code means your localized screenshots never reach Turkish users.
Does text expansion affect Turkish screenshot design?
Turkish runs +20% 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 Turkish.
Does Shotlingo automatically localize screenshots to Turkish?
Yes. Shotlingo auto-translates your App Store screenshot text to Turkish (Türkçe) with AI that respects text expansion, and platform-appropriate fonts. Export the localized bundle ready for App Store Connect locale tr.
Do I have to translate my App Store screenshots to Turkish?
If Turkish 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 Turkish automatically
Shotlingo handles expansion, fonts, and App Store Connect locale codes for you. Free to try.
Try Shotlingo free →