App Store Screenshot Localization: 7-Market Priority [2026]

Localize App Store screenshots for these 7 markets first, in this order: US English (the global baseline), Japanese (Japan), Simplified Chinese (China, regulatory permitting), German (Germany), Korean (South Korea), Brazilian Portuguese (Brazil), and Arabic (Saudi Arabia, UAE, and the broader Gulf). Apple now supports 50 App Store Connect metadata localizations as of March 31, 2026 [1], but revenue, ARPU, and screenshot adaptation cost all concentrate in the top 7. Each market needs different visual adaptation, not just a translated caption.

This is the App Store localization cluster's screenshot-priority deep dive. The broader localization workflow guide covers metadata fields, keyword research, and App Store Connect upload mechanics; this post covers which markets to enter first and what each one needs from your screenshots beyond text translation.

TL;DR:

• Top 7 by ARPU and screenshot-adaptation ROI: US (with regional variants), Japan, China, Germany, Korea, Brazil, Arabic-speaking GCC.
• Apple App Store Connect supports 50 localizations as of March 31, 2026 (up from 39); the 11 newest are mostly Indian regional languages plus Slovenian [1][2]. The list is at developer.apple.com [2].
• Each market has different screenshot rules. German captions run roughly 30-35% longer than English [4], so a layout that fits in English can clip in German. Arabic and Hebrew mirror layout direction. Japanese readers tolerate higher information density than Western readers. Brazilian Portuguese expands roughly 25-30%.
• The 50-language matrix is a trap. Picking 5 to 7 markets where ARPU times user base times your category fit beats spraying 50 mediocre localizations.
• China requires an ICP filing for App Store distribution since 2023 [7]. Don't budget Chinese screenshots until the filing is clear.
• AppScreenshotStudio's translation flow regenerates the screenshot set in 15 target languages from one English design, applying RTL flip for Arabic and font fallback for CJK automatically.

Table of Contents

• Why isn't the answer "localize for all 50 languages"?
• How do you pick the right 7 markets for your app?
• What does each market actually need from screenshots?
• What technical screenshot adaptations apply per market?
• When should you skip a market on this list?
• How does Apple's March 2026 50-language expansion change priorities?
• Takeaways

Why isn't the answer "localize for all 50 languages"?

Apple's localization page reads like a permission slip: 50 languages, infinite ambition, go global. The math doesn't agree. Each new localization costs you a translated screenshot set per device class (currently iPhone 6.9-inch and iPad Pro 13-inch are required), localized metadata (title, subtitle, keywords, description, promotional text, what's new), and ongoing maintenance every time you ship a new feature. Doing 50 localizations means redoing all of that 50 times, every release. Most indie teams have one person.

The revenue distribution is also skewed. App Store revenue concentrates in a small set of high-ARPU markets. The US is the largest single market by spend, Japan ranks among the top three by App Store revenue with some of the highest ARPU globally, and China and the UK and Germany round out the top five [6]. Beyond the top 10 markets, the marginal ROI of an additional localization drops sharply because download volume grows but per-user revenue drops faster. Spending the same effort on a deeper localization of fewer markets beats spreading thin.

The screenshot layer specifically compounds this. Translating a description is cheap (one paragraph, one round of native-speaker review). Adapting a screenshot is expensive: the caption text length changes per language, the visual hierarchy needs to survive that change, the device frame stays but the inner UI may need a different content example, and for RTL languages the entire layout flips. A 50-language matrix means 50 of those adaptations, not 50 paragraph translations.

The right move is to pick 5 to 7 markets where the math works and execute each one as a real localization. The 7 below are where the screenshot-adaptation ROI consistently beats the cost for indie apps in 2026.

How do you pick the right 7 markets for your app?

The 7-market default assumes a category-agnostic ranking. Your category may shift the order. Pick using these three filters in sequence:

1. Available revenue per user in the market (ARPU). Markets like the US, Japan, South Korea, and Germany consistently produce the highest ARPU on the App Store [6]. Markets like India and Indonesia have huge user bases but lower per-user spend; localize them for download volume and ad-supported monetization, not for direct revenue.
2. Category fit with the market. Gaming and entertainment over-index in Japan and Korea. Fintech and productivity over-index in Germany and the UK. Health and fitness over-index in the US, UK, and Germany. Don't rank Japan above Germany for a B2B productivity tool just because Japan has higher mobile ARPU overall.
3. Adaptation cost vs. screenshot complexity. If your screenshots are text-heavy with multiple captions per frame, German and Brazilian Portuguese cost more (text expansion of 25-35%). If you have RTL-incompatible layouts (text flowing across product mockups, asymmetric framing), Arabic costs more. Cheap-to-adapt screenshots can stretch further down the priority list.

The 7-market default below is what works for the median indie app: a product targeting consumer or prosumer users, monetized through subscriptions or one-time purchases, with English as the source language. Adjust if your category has known regional skews.

What does each market actually need from screenshots?

This is the per-market field manual. Each entry covers ARPU and category fit, what the screenshot caption layer needs, what the visual layer needs, and the adaptation cost relative to a baseline US-English set.

1. US English (with regional variants for Canada, UK, Australia)

The default. If you have only one screenshot set, it's this one. The wedge here isn't whether to localize; it's whether to use regional English variants.

• Caption layer: US English is fine for Canada and Australia for most apps. The UK variant matters more than indie teams assume. Currency symbols ($ vs. £), spelling (color vs. colour, optimize vs. optimise), and idiom differences ("trash" vs. "rubbish") all read as foreign when wrong. Apple distinguishes English (U.S.), English (U.K.), English (Canada), and English (Australia) as four separate App Store Connect localizations [2]. If your screenshots show prices, dates, or units, a UK-specific set converts measurably better than US screenshots served to UK users.
• Visual layer: Minimalist composition. Single value proposition per frame. Plenty of negative space. Western readers scan left-to-right and expect the visual hook in the top-left quadrant.
• Cost relative to baseline: Zero (this is the baseline). UK variant adds roughly 10-15% production overhead for one extra screenshot set per device class.

2. Japanese (Japan)

The third-largest App Store market by consumer spend, with the highest per-capita mobile app spending globally [6]. Japanese mobile UI tolerates higher information density than US norms; a Japan-targeted screenshot can stack 2 to 3 callouts where the US version shows one. The hard parts are tone (polite-friendly teineigo is the safe default) and font rendering (iOS uses Hiragino Sans as the Japanese system font, so custom English fonts without CJK weights produce visible mixed-font captions).

Full breakdown on the cultural-adaptation pass (information density layout by layout, keigo register per app type, anime conversion limits, CJK font fallback rules): Japanese screenshot cultural-adaptation guide.

3. Simplified Chinese (China)

China is the largest non-US App Store market by revenue, but distribution requires a Mainland China ICP filing. Since September 2023, China's Ministry of Industry and Information Technology requires all apps distributed in Mainland China to have an Internet Content Provider filing number; from April 2024 onward, apps without the filing can't ship updates and face mandatory removal [7]. Without the filing, your Chinese screenshots ship nowhere.

• Caption layer: Simplified Chinese compresses tightly compared to English. A 30-character English caption typically becomes 12 to 16 Chinese characters. The opposite problem from German: your layout will have a lot of empty space where English needed every pixel. Resist the urge to fill it; restraint reads as quality.
• Visual layer: Red signifies luck and prosperity in China, the opposite of the Western "danger" signal. If your accent color is red, this is a win, not a problem. Color saturation runs higher in successful Chinese app screenshots than in equivalents for Western markets. Apple Review Guideline 5.1.1(ix) on highly regulated fields applies more strictly in Mainland China for finance, health, and crypto [3].
• Cost relative to baseline: High (regulatory more than visual). Don't budget Chinese screenshot production until the ICP filing is approved.

4. German (Germany)

The largest European App Store market. German body copy runs 30-35% longer than English [4], but short headline strings expand 60-80% (IBM's expansion data, reproduced by the W3C), so the screenshot layer takes the brunt. German users also weight regulator and certification signals heavily over user-count social proof.

Full breakdown on the screenshot layout pass (layout-by-layout failure modes, compound-word width, font and trust-signal rules): German screenshot text-expansion layout rules.

5. Korean (South Korea)

Extremely high engagement and spending in gaming, productivity, and fintech categories. Korean ARPU consistently ranks among the top globally, particularly for in-app purchases and subscriptions.

• Caption layer: Korean (Hangul) is a phonetic script that compresses well, similar to Japanese. Captions are typically shorter than English equivalents. Be careful with formality level; Korean has distinct formal and informal registers and using the wrong one for your category (formal for casual games, informal for fintech) signals "non-native team."
• Visual layer: Information density tolerance is high, between US and Japanese norms. Anime and character illustration convert well in gaming and entertainment. K-pop-adjacent visual cues (specific color combinations, soft gradients, glossy product shots) work in lifestyle, beauty, and shopping categories. The category-typical visual conventions in Korea are tight enough that going off-pattern reads as "non-local app" the same way it does in finance.
• Cost relative to baseline: Moderate. The font renders cleanly on iOS; the tone and formality decisions need a native review pass.

6. Brazilian Portuguese (Brazil)

Brazil is one of the largest non-Asian markets by download volume and the dominant market in Latin America. The "Brazilian" qualifier matters: European Portuguese and Brazilian Portuguese differ in vocabulary, idiom, and even some grammar. Using European Portuguese for the Brazilian App Store reads as a foreign listing.

• Caption layer: Brazilian Portuguese typically runs 25-30% longer than English [4]. Plan similar wrap-tolerance as for German, though the issue is more about word count than compound-word width.
• Visual layer: Warmer color palette than US norms. Photography over illustration in lifestyle. High social-proof tolerance; download counts and star ratings convert measurably better when shown explicitly on the screenshot rather than implied. Currency formatting should use R$ (Brazilian real) with comma decimal separator and period thousand separator (R$1.247,90 not $1,247.90).
• Cost relative to baseline: Moderate. The Latin script is shared with English, so font and rendering aren't an issue; the caption-expansion layout pass is the main cost.

7. Arabic (Saudi Arabia, UAE, and the wider GCC)

The Gulf Cooperation Council markets have high ARPU, particularly in gaming, lifestyle, and finance. Arabic is the localization with the biggest structural visual change because it flips layout direction.

• Caption layer: Arabic reads right-to-left. The text flow, the position of caption text relative to the device frame, the alignment of section headers, and the order of carousel slides all mirror. Numbers stay left-to-right (so "1247" reads in the same direction even in an Arabic sentence).
• Visual layer: Mirror layout direction for the overall screenshot composition: if the device frame sits on the left of the caption in English, it sits on the right in Arabic. Do NOT mirror: logos, brand icons, photographs, real-object illustrations, video player controls, clockwise-rotation arrows, map orientations, or chart axes (X-axis labels still read left-to-right unless the chart is itself rebuilt for RTL). Apple's RTL guidance is explicit on what mirrors and what doesn't; following it cleanly is the difference between a credible Arabic listing and one that reads as auto-flipped.
• Cost relative to baseline: High. The layout flip is structural, not cosmetic. Plan a dedicated Arabic design pass; don't auto-mirror an English file and ship it.

What technical screenshot adaptations apply per market?

Beyond the per-market notes above, five cross-cutting technical rules apply.

Text expansion ratios

Plan caption space against the longest target language, not the source. Standard expansion ratios from English [4]:

The practical rule: design your English captions with 35% headroom on the right side of the headline. That headroom absorbs German without requiring a separate layout pass.

RTL layout for Arabic and Hebrew

Arabic and Hebrew are the two App Store-supported RTL languages [2]. The layout, caption flow, and directional icons mirror; logos, photos, numbers, video controls, and clocks do not. Full mirror set, don't-mirror set, and 9-layout RTL difficulty matrix: App Store cultural adaptation pillar.

Currency, date, and number formats in stat panels

If your screenshot shows a price, a date, a balance, a stat, or any numeric value, the format matters. The defaults:

• Currency: $ in US, £ in UK, € in Germany/France/Spain/Italy, ¥ in Japan/China, ₩ in Korea, R$ in Brazil. Position before or after the number depends on the locale (€1,247 in Germany; 1.247€ in some EU contexts).
• Decimal separator: Period in US/UK/Japan/Korea; comma in Germany/France/Spain/Brazil.
• Thousand separator: Comma in US/UK; period in Germany/France/Spain/Brazil; space in some EU contexts.
• Date format: MM/DD/YYYY in US; DD/MM/YYYY in most of Europe and Latin America; YYYY/MM/DD in Japan/Korea/China.

Stats-hero and feature-grid layouts surface these the most. The stats-hero layout breakdown covers how stat panel composition handles the format differences.

Font fallback for CJK scripts

Apple ships system fonts that handle Chinese, Japanese, and Korean (CJK) glyphs on iOS, but your custom screenshot font may not. If you're using a designer font for English captions, check whether the font's CJK fallback ships clean glyphs or substitutes a system fallback at runtime; the substitution often produces a visible weight mismatch that reads as "rendered in two fonts." For CJK target languages, prefer system fonts (San Francisco for English, Hiragino Sans for Japanese, PingFang for Chinese, Apple SD Gothic Neo for Korean) over a single custom font with patchy CJK support.

Cultural imagery and color meaning

Beyond layout and typography, the cultural layer affects screenshot conversion. Color meaning shifts across three regional clusters (East Asia, Gulf, Western); human imagery breaks trust when models, gestures, or symbols don't match the target market; and flag icons used as language indicators conflate country with language. Full color-meaning matrix, imagery rules per category, and the 9-layout sensitivity table: App Store cultural adaptation pillar.

When should you skip a market on this list?

The 7-market default isn't sacred. Skip a market when at least one of these is true:

1. Your category has near-zero traction there. Sports betting apps skip GCC markets entirely (regulatory). Alcohol-adjacent apps skip Saudi Arabia and several GCC states. Crypto apps skip multiple markets at once; check App Store Review Guideline 5.1.1(ix) compliance per market [3] before budgeting screenshots.
2. Regulatory cost outweighs revenue potential. China is the canonical example. The ICP filing process [7] adds months to a launch timeline and ongoing compliance overhead. If your team can't sustain that, the Chinese localization is a wasted asset because nothing ships to Mainland China without the filing.
3. You don't have the operational bandwidth to maintain it. Each localization needs a re-pass every time you ship a feature, change a screenshot, or update a price. If you're a solo developer shipping monthly, doing 7 localized screenshot sets per release is realistic only if the visual layer is automated. If it's manual, drop to 3 to 5 markets and execute those deeply.

Skip is a strategic choice, not a failure. A poorly localized listing converts worse than no localization at all, because the user opens the listing, sees machine-translated copy or a layout that breaks, and bounces with a stronger negative signal than if they'd seen the English version.

How does Apple's March 2026 50-language expansion change priorities?

On March 31, 2026, Apple expanded App Store Connect localization support from 39 languages to 50 [1]. The 11 new languages: Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu, and Urdu [1][2]. Ten of those are Indian regional languages; Slovenian is the European outlier.

What this changes:

• India strategy shifts from one language to many. Before this expansion, India was a single-language localization opportunity (Hindi, plus English variants). Now you can ship to specific Indian regional language markets directly. For mass-market consumer apps with India download exposure, adding Hindi plus 2 to 3 of the new regional languages (Tamil, Telugu, Bengali/Bangla are typical first picks by user base) can pay off; for high-ARPU subscription apps, the per-user revenue math still favors the original top 7 first.
• Slovenian is a niche unlock. Slovenia is a small market by itself, but the prior absence of Slovenian forced developers to choose between a poor fit (German, Croatian) or skipping. Add this only if you already see Slovenian traffic or you're a regional app.
• The 50-language ceiling doesn't change the top-7 priority. Indian regional languages are high-download, lower-ARPU. They expand the long tail of the localization matrix, not the top of it. The order of priority above still holds.

The strategic takeaway: Apple keeps adding markets faster than indie teams can localize. That makes the "pick a small priority list and execute deeply" approach more valuable each year, not less. The expansion is good news for translation-services pricing (more competition, more tooling) and bad news for teams that try to chase every new addition.

Takeaways

The 7-market priority list works for the median indie app on the App Store in 2026. Localize US English first (with UK as the cheap regional second), then Japanese, then Simplified Chinese only if you can clear the ICP filing, then German with explicit caption-layout headroom, then Korean, then Brazilian Portuguese, then Arabic with a real RTL design pass.

Each market needs different visual adaptation. Translating the caption is the cheap part. Plan for German text expansion of 30-35% [4], Brazilian Portuguese expansion of 25-30%, RTL layout flip for Arabic, higher information density for Japanese readers, and font fallback for CJK scripts. The 50-language matrix [2] is a trap; pick the 5 to 7 markets where the math works and execute each one as a real localization.

If you're running this manually (Photoshop or Figma per language, hand-pasted captions, manual RTL flipping), the cost per market is high enough that 7 markets stays aspirational. A chat-based screenshot builder can regenerate the full set per language from one source design, dropping the per-market cost to a chat command rather than a design pass.

The next decision after picking markets is which screenshot frames to localize first within each set. The first three screenshots conversion playbook covers that question; frames 1 to 3 carry most of the conversion weight per market, so the localization budget concentrates there too. The indie developer launch checklist and the App Store featured nominations guide both reference market-specific timing and can sit upstream of the localization decision.