Localizing your app listing into Hebrew

Storefronts and localization names read from Apple’s App Store localizations reference; language codes and field limits from Google Play’s translation language list and each store’s field reference. Checked August 29, 2026.

Play still identifies Hebrew by the legacy code iw-IL rather than he-IL — a 1980s ISO relic that survives in Android to this day. If a tool or a spreadsheet of yours expects "he", this is the mismatch that loses the translation.

On the App Store, Israel’s storefront defaults to English (U.K.) with Hebrew as an additional supported language, so the Hebrew listing is opt-in.

Where a Hebrew listing appears

Apple publishes the default language of all 173 App Store storefronts, and Hebrew is the default in none of them — it is an additional supported language in 1. Those markets see English unless you add the Hebrew localization yourself.

Additionally supported in

What you translate, and what it costs you

Both stores cap the same fields, and neither cap changes by language — but the amount of meaning you fit inside them does. Apple’s keyword field is the one that surprises people: it is measured in bytes, so Hebrew at about 2 bytes per character leaves roughly 50 characters. Google Play counts characters instead, and says so explicitly: its limits “apply to both full-width and half-width characters”.

The screenshots are part of the localization

Both stores let you upload a separate screenshot set per localization, and in practice the captions are what sells — a translated description under English screenshots converts like an English listing. Design the frames once, then export the same layout per language rather than rebuilding it: that is the difference between localizing into Hebrew in an afternoon and not doing it at all.