App Store Localization Guide for Indie Developers (2026)

Localization is the single biggest ASO lever most indie devs ignore. The math is brutal: a properly localized listing in Japan can outperform your US listing in raw downloads, with a fraction of the competition.

But "translate everything everywhere" is the wrong strategy. It costs $5k+ and most of the languages won't move the needle. Here's how to do this right.

Which countries to localize first

For most consumer apps, the order looks like this:

For B2B / productivity apps:

Skip until later: India (low ARPU despite volume), Russia (sanctions + Yandex.Store), most Southeast Asia (low ARPU + Android-heavy).

English ≠ English

The most common mistake: shipping the US English listing globally.

• UK: "mobile" not "cell"; "favourite" not "favorite"; metric units; UK politeness register.
• Australia: closer to UK English with localized references.
• Canada: closer to US English, but bilingual French in Quebec is required by law for some categories.

Apple/Google treat these as separate localizations. The keywords differ.

Keyword research per market

Don't translate your US keywords. Re-do keyword research per market.

Example: a fitness app

• US: "workout tracker", "fitness app"
• Germany: "Fitness Tracker", "Trainings App" (anglicism), but also "Bewegungstracker"
• Japan: "フィットネス" + English "fitness" both used — bilingual title often outranks pure-Japanese
• Brazil: "exercícios", "treino", "academia"

Workflow:

1. Pull top 20 ranking apps in your category for that country.
2. Run each through Keyword Density Checker on the localized listing.
3. Spot the keywords that appear in every top-ranking listing — those are the must-haves.
4. Cross-reference with Apple Search Ads popularity scores for that country.

How to actually localize (without burning $5k)

Three tiers:

Tier 1: machine translation (free, OK for low-priority markets)

DeepL > Google Translate for most European languages. Free for casual use, ~$20/month for the API.

Use for:

• Tier-3 markets where you just need a listing to exist.
• Description body (keywords matter more than poetry).
• App Store keywords field (just keywords, not sentences).

Don't use for:

• Title and subtitle. These need to read naturally. Hire a native speaker for these — even if it's just $50 on Fiverr/Upwork.
• Screenshot captions. Cultural references break.

Tier 2: freelance native speaker ($100-$500 per language)

Best ROI for indie devs. Find a native speaker who also speaks tech. Brief:

• Your title, subtitle, description, screenshot captions.
• Your top 10 English keywords.
• Your target user persona.

Ask for:

• Localized title + subtitle (multiple options).
• Re-researched keywords (not translated).
• Culturally-adapted screenshot captions.

Cost: $100-$500 per language. Pays back in days if the market converts.

Tier 3: localization agency ($1k-$3k per language)

Worth it only when you're at significant scale (>$50k MRR) and need ongoing localization across many markets. Most indie devs don't reach this tier.

Screenshots: what to actually localize

Common mistake: shipping the same screenshots globally with translated captions.

Better:

• Japan: Localized screenshots are huge — Japanese users penalize foreign-feeling design heavily.
• Korea: Same — localize the visual feel.
• Germany, France: Caption translation is usually enough.
• Brazil, LatAm: Caption translation usually fine. If you have human models in screenshots, swap to reflect the market.

Run localized screenshots through Screenshot Lab to spot readability issues — Japanese text often won't fit the same template as English.

hreflang & store-level configuration

Apple and Google handle this automatically — you don't add hreflang tags like you would on the web. What you control:

• App Store Connect: Add localizations. Each localization can have separate title, subtitle, keywords, description, screenshots, app previews.
• Play Console: "Store listing localizations." Same surface — title, short description, full description, graphic assets.

Both stores then route users by device language (primarily) and country store (secondarily). A US user with their phone in Japanese will see the Japanese listing.

Common mistakes

• Translating instead of localizing. Keywords don't translate.
• Skipping screenshot localization. Caption translation is not enough for visually-discerning markets (JP, KR).
• Forgetting App Store keywords field per market. Each market has its own 100 characters.
• One global price. App Store/Google Play handle currency, but price tier is per-market — sometimes you should price lower in PPP-adjusted markets (Brazil, India) and higher in premium markets (Norway, Switzerland).
• No country-level review tracking. A 4.5 average globally can hide a 3.2 in your most important non-US market.

Measure per-country

Track these per-country in App Store Connect / Play Console:

• Impressions
• Conversion rate (impressions → product page → install)
• Average rating per country
• Top search terms users typed before installing

If your conversion rate in a localized market is lower than US, localization isn't done — diagnose with the ASO audit checklist per market.

Related reading

• The Indie ASO Audit Checklist (2026)
• App Store Keyword Research
• App Store Screenshot Best Practices
• The Complete ASO Guide for Indie Developers
• How to Get More App Reviews in 2026

Try the tools

• Keyword Density Checker — check density per language.
• Screenshot Lab — review localized screenshots.
• Free ASO audit — run per market to spot weak localizations.