Hebrew App Store Screenshot Localization
עברית (he-IL)
Israel is a small market by population — about 9.5 million people — but it punches way above its weight in app spending per user. This is a country where basically everyone has a smartphone, tech adoption is aggressive, and users are willing to pay for apps that are genuinely good. The "Startup Nation" reputation is real: Israeli users are sophisticated, they've seen everything, and they have high expectations. Here's the developer calculus: Hebrew localization requires dealing with right-to-left layout, which is a genuine technical challenge. But unlike Arabic — where you're dealing with...
Translation Challenges
The headline challenge with Hebrew screenshots is right-to-left layout. Your entire UI flow mirrors — navigation goes right-to-left, text aligns right, and UI elements swap sides. If you've only ever designed for LTR, this is a mental shift. The good news: Hebrew RTL is simpler than Arabic RTL. Hebrew letters don't connect to each other (no ligatures), there are no multiple letter forms based on...
Typography Guide
Hebrew requires dedicated Hebrew fonts — you can't just use any Latin font and expect it to work. Good options: Heebo (Google Fonts, very popular), Noto Sans Hebrew, Assistant, and Rubik. These all handle Hebrew characters well and include Latin character sets for mixed-language text. Hebrew letters are relatively uniform in height — no true ascenders or descenders except for five "final forms"...
Screenshot Tips for Hebrew
- Full RTL layout mirroring is non-negotiable. Everything flips: text alignment, navigation flow, progress indicators, swipe direction. Half-RTL (just translating text but keeping LTR layout) looks broken and amateurish
- Hebrew contracts 10-20% from English — use the extra space to create cleaner, less cluttered layouts rather than just letting elements shrink
- Display prices in new Israeli shekel: ₪49.90 (symbol before number, period for decimals). Israeli users expect to see local currency
- Test bidirectional text rendering obsessively. Your app name in Latin characters mixed with Hebrew description text is where bidi bugs always surface. If this is garbled, nothing else matters
- Write copy that's direct, informal, and confident. Israeli users scroll past anything that reads like it was written by a marketing committee. Short, punchy Hebrew headlines win
- Don't include vowel marks (nikud) in your text. Standard modern Hebrew for adults never uses them. Including them makes your screenshots look like a children's book
- If your app has any security or privacy features, call them out explicitly. Israeli users are more security-conscious than most markets and it's a genuine differentiator
Cultural Notes
- Israeli culture is famously direct and informal. Corporate-speak and polished marketing language falls flat — Israelis respond to straightforward, no-BS communication. Write your screenshot copy the way you'd explain your app to someone at a coffee shop
- Humor and wit work exceptionally well. Israelis appreciate clever, slightly irreverent copy. If your brand voice allows it, a witty Hebrew headline will outperform a safe, generic one every time
- Israeli users are aggressive early adopters. They actively hunt for new apps and are willing to try things. But they're equally quick to abandon anything that doesn't deliver — first impressions matter enormously
- Shabbat (Friday evening to Saturday evening) genuinely affects usage patterns. Don't schedule campaigns or expect engagement during this window. Plan around it, not through it
- Jewish holidays — Rosh Hashanah, Passover, Hanukkah — create real seasonal opportunities. Themed screenshots or promotions around these dates can drive significant spikes
- Security and privacy awareness is extremely high in Israel, partly due to the country's cybersecurity culture. If your app handles any personal data, highlighting security features is a meaningful trust signal
- Israel has high revenue per user compared to markets with similar population sizes. Don't let the 9.5M population fool you — per-capita app spending is among the highest globally
Frequently Asked Questions
How hard is RTL layout for Hebrew screenshots really?
It's a real technical challenge but not as bad as you might fear. The key mental shift: everything mirrors. Text aligns right, UI flows right-to-left, back buttons go on the right. Hebrew letters don't connect like Arabic, so the script itself is simpler to render. The hardest part is bidirectional text — when Hebrew and Latin characters appear together (your app name, English terms, numbers). If your screenshot tool supports RTL natively, you're mostly fine. If it doesn't, you'll be manually positioning text, which is tedious but doable.
Is Israel worth localizing for with only 9.5 million people?
Look at revenue per user, not population. Israel has some of the highest app spending per capita in the world, driven by near-universal smartphone adoption, high disposable income, and a culture that enthusiastically embraces technology. A well-localized app in Israel can generate more revenue than in countries with ten times the population but lower spending. Plus, Israeli users talk to each other — word-of-mouth in a small market can scale your install base quickly.
What's different about Hebrew RTL compared to Arabic RTL?
Hebrew is significantly simpler. Hebrew letters are standalone — they don't connect to each other or change shape based on position in a word. Arabic has initial, medial, final, and isolated forms for most letters, plus complex ligatures. Hebrew is just 22 discrete characters plus five final forms. If you're considering your first RTL market, Hebrew is the easier starting point. The bidirectional text handling challenges are the same, but the script rendering is far more straightforward.
Should I include vowel marks (nikud) in Hebrew screenshots?
Absolutely not. Modern Hebrew for adults never includes vowel marks. Nikud is used in children's books, religious texts, poetry, and language learning materials. Including them in your app screenshots would look as strange as putting pronunciation guides on every English word. Native Hebrew readers infer vowels from context automatically. Any localization that includes nikud is signaling 'we don't know how Hebrew actually works.'
What tone works for Israeli users?
Direct, informal, and confident. Israeli culture values dugri — straight talk without filters. Corporate marketing speak that might work in other markets comes across as inauthentic in Israel. Write your headlines like you're talking to a friend who asked what your app does. Humor and cleverness are rewarded. Formality is punished. This is one of the few markets where being a bit cheeky in your screenshot copy is actually the professional choice.
How do I handle my app name and English terms in Hebrew text?
Keep them in Latin characters. Modern Hebrew naturally mixes in English for brand names, tech terms, and product names. The technical challenge is making sure your rendering engine handles the direction switch correctly — Hebrew text flows right-to-left, but embedded English words render left-to-right within that flow. This is called bidirectional (bidi) text, and it's the number one source of Hebrew rendering bugs. Always test with real Hebrew text, not placeholder strings, because bidi issues only surface with actual mixed-direction content.