LOCALIZATION GUIDE · hr

Localize App Store Screenshots to Croatian

Hrvatski

Croatia = ~4M people, plus Croatian-speaking diaspora.

Text expansion
+25%
vs English
Layout risk
Medium
overflow severity
Locale code
hr
App Store Connect

Why Croatian matters

Croatian reaches ~4M speakers plus a sizeable diaspora, and it is a small but premium, high-ARPU market. Written in Latin, its trap is a set of look-alike diacritics: č (caron) and ć (acute) are different letters and sounds, and đ is a single crossed-D letter, never 'dj'. It is also close to Serbian but must be localized separately. Croatian is Latin-only in practice and uses distinct vocabulary (e.g. 'zaslon' for screen).

English (source)

Plan your trip and discover hidden gems

39 chars

Isplanirajte putovanje i otkrijte skrivene dragulje

51 chars

Localization tips for Croatian

  1. 1 Distinguish č (caron, hard 'ch') from ć (acute, soft 'ch'). Different letters and sounds; a font that blurs caron vs acute, or a translator that swaps them, is an outright error.
  2. 2 đ (lowercase d with stroke) is a single letter, not 'dj'. Verify the font renders the crossbar; substituting dj is the classic tell of a lazy localization.
  3. 3 Budget ~25% more width; Croatian has seven cases that change word endings.
  4. 4 dž, lj and nj are digraph letters written as two characters. Fine to type normally, but don't let a line break hyphenate inside them.
  5. 5 Never reuse Serbian copy: Croatian is Latin-only in practice and differs in vocabulary and phrasing, so a converted Serbian text reads wrong.
  6. 6 Use formal 'Vi' for business apps, informal 'ti' for consumer apps.

Fonts for Croatian

Inter, Noto Sans, Roboto and Source Sans 3 cover Croatian. Verify č (caron) and ć (acute) are visually distinct, that š/ž carons render, and that đ/Đ show the crossbar rather than falling back to a plain d.

Most common mistake

Substituting đ with 'dj' or collapsing ć and č. Both look 'close enough' to outsiders but are spelling errors to Croatian readers, and đ→dj in particular instantly marks the localization as machine-made.

Croatian localization FAQ

What App Store Connect locale code should I use for Croatian?

Use hr when adding Croatian (Hrvatski) screenshots in App Store Connect or Google Play Console. Using the wrong code means your localized screenshots never reach Croatian users.

Does text expansion affect Croatian screenshot design?

Croatian runs +25% 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 Croatian.

Does Shotlingo automatically localize screenshots to Croatian?

Yes. Shotlingo auto-translates your App Store screenshot text to Croatian (Hrvatski) with AI that respects text expansion, and platform-appropriate fonts. Export the localized bundle ready for App Store Connect locale hr.

Do I have to translate my App Store screenshots to Croatian?

If Croatian 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 Croatian automatically

Shotlingo handles expansion, fonts, and App Store Connect locale codes for you. Free to try.

Try Shotlingo free →
Other localization guides