ASO Localization: The 60% of App Revenue Most Indie Devs Leave on the Table

Updated June 2026.

If you ship an English-only app, industry data suggests you are walking past roughly 60% of the global app revenue available to you. That is the uncomfortable math behind aso localization, and it is the single biggest reason indie developers stay stuck at flat MRR while competitors with weaker products pull ahead in Japan, Germany, and Brazil. This post is the pillar guide we wish we had when we started Shotlingo: what aso localization actually means, why it compounds across discoverability and conversion, and the minimum viable stack to capture revenue you are currently leaving on the table.

TL;DR: The Indie ASO Localization Reality

• Industry data (data.ai, Sensor Tower annual reports) suggests roughly 60% of global app revenue comes from non-English markets. The split varies by category, but the direction is consistent.
• Most indie apps ship English-only or with token translation in two or three markets. Even when localized, screenshots are rarely translated.
• Apple has publicly noted that fully localized listings can lift downloads 2 to 3x in non-English markets versus English-only listings.
• Real aso localization is metadata, screenshots, preview videos, per-locale keyword research, and cultural adaptation. Not just Google Translate on a title.
• The minimum viable setup for Tier 1 plus Tier 2 markets is roughly $100 to $200 one-off plus a screenshot tool. The expected lift dwarfs the cost.

Why ASO Localization Determines 60% of Your App Revenue

Let us be honest about the number. The "60% of revenue is non-English" figure is not a single audited statistic. It is a directional estimate that shows up year after year in mobile marketing industry reports from data.ai and similar sources. The actual percentage moves by category: games skew more international, productivity tools skew more US, and finance varies wildly by region. The honest framing is this: the majority of global app revenue is generated outside English-speaking markets, and indie developers who ignore aso localization are auto-excluded from that majority.

The reason this matters more for indie devs than for large studios is structural. Big publishers can buy their way into local markets with paid UA. Indies cannot. Organic discoverability through the App Store is the only affordable acquisition channel left, and the App Store is locale-specific by design. Apple shows users results in their device language first. If your title and keywords are English, you simply do not appear for the queries that drive most of the world's downloads.

For more context on how ASO works as a whole, see our pillar post on what ASO is in 2026, and the indie-cost angle in cost-effective ASO tools for indie developers.

What Real ASO Localization Includes

One of the reasons indie devs underinvest in aso localization is that they think it means "translate the title." Real localization is a stack of work, not a single task.

1. Metadata localization

Title, subtitle, promotional text, keyword field, and description for each locale in App Store Connect. Apple gives you 30 plus locales for free; the limiting factor is whether you fill them in.

2. Screenshot localization

Translating the on-image text in your screenshots. This is the step most indies skip, and it is the step that drives conversion. A Japanese user landing on an English screenshot bounces at a much higher rate than a Japanese user landing on a Japanese screenshot. See our data piece on Japanese screenshot translation fails for why this matters and how it breaks.

3. App preview video localization

Captioned or voiced previews in the local language. Optional but high-leverage in markets like Japan and Korea where preview videos are heavily watched.

4. Per-locale keyword research

This is the part that breaks "Google Translate your keywords" workflows. The Japanese term for "habit tracker" is not the literal translation. German users search with compound words your English research never surfaces. Arabic users search RTL phrases with different segmentation. See German listings and vertical space and Arabic RTL mirror data for concrete examples.

5. Custom Product Pages per locale

CPPs let you test different value propositions per market. Combined with aso localization, they compound. Our CPP localization guide covers the mechanics.

6. Cultural adaptation, not translation

Color meaning, imagery, examples in screenshots, and tone shift by culture. A blunt US-style benefit headline reads pushy in Japan and underwhelming in Brazil. Cultural adaptation is the part you cannot outsource to an API.

The Minimum Viable ASO Localization Stack

You do not need to localize 40 markets. You need to localize the right markets in the right order. Here is the Minimum Viable Localization (MVL) tier system we use with Shotlingo customers.

  | Market tier 
  | Why now 
  | Setup effort 




  | Tier 1: Japan, Germany, China 
  | Largest non-US markets by revenue. Each can double an indie's MRR alone. 
  | Roughly 1 to 2 days per market for metadata plus screenshots. 


  | Tier 2: France, UK, Brazil, Korea, Spain 
  | High-ROI markets where English partly works but localized listings convert much better. 
  | Roughly half a day per market once Tier 1 templates exist. 


  | Tier 3: Italy, Mexico, Russia, India 
  | Long-tail volume. Cheap to add once your template system is in place. 
  | A few hours per market using your Tier 1 and 2 assets as a base. 

For each tier, the workflow is the same: translate title and subtitle (free with Apple's tools), translate screenshot text (Shotlingo or manual), do keyword research in the local language, then iterate based on Search Match data. The full localization hub walks through the assets and templates we provide for each.

Why Most Indies Skip ASO Localization and Lose the Money

The pattern is consistent. Indie devs skip aso localization for four predictable reasons.

"Japan seems hard"

It is not hard. It is unfamiliar. The Japanese App Store rewards localized listings disproportionately because most Western indies skip it. The competitive bar is lower than in the US.

"My app is global, English is fine"

This is the most expensive mistake. Even users who speak English search in their native language by default. Discoverability is the first filter, and English titles fail the filter before conversion is even relevant.

"I will localize later when I have revenue"

The math runs backward. Localization is what unlocks the revenue. Waiting for revenue before localizing is waiting for the lift before doing the thing that creates the lift.

"Translation is good enough"

Translation without screenshot localization is the most common half-measure. Discoverability improves a little. Conversion does not, because the user lands on English screenshots and bounces. This is the single biggest leak we see in indie ASO audits.

Step-by-Step: Localize Your First Market

Pick one Tier 1 market. Japan, Germany, or France are the safest first choices. The workflow is the same regardless.

Step 1: Keyword research in the local language

Do not translate your English keywords. Start fresh. Use Apple Search Match data to discover what local users actually type. Apple Search Match is free and catches local-language queries you would never guess.

Step 2: Translate title and subtitle for the local market

Use a native speaker or a high-quality service. Google Translate is a starting point, not a finishing point. Pay attention to character limits and to text expansion, which can blow out your title in German and squeeze it in CJK.

Step 3: Fill the keyword field with locale-specific terms

100 characters per locale. Do not reuse English keywords. Each locale is its own ranking surface.

Step 4: Localize screenshot text

This is where most indies stop and where Shotlingo earns its keep. Translate every line of on-image copy. Keep the layout. Adjust for text expansion. For German specifically, see our vertical space data piece.

Step 5: Submit and monitor

Submit the localized listing. Watch impressions, taps, and conversion in App Store Connect by locale. Iterate. The first version is rarely the best version.

Common ASO Localization Mistakes

• Translation-only. Metadata translated, screenshots English. Half the work, none of the conversion lift.
• Google Translate on marketing copy. Acceptable for description, dangerous for title and subtitle where every character matters.
• Skipping Tier 1 because it feels intimidating. Japan and China feel hard until you do them once. They are the highest-leverage markets for indies.
• Localizing 20 markets too early. Three well-localized markets beat twenty half-localized ones. Quality compounds, breadth does not.
• No iteration loop. Ship and forget is the default. Local users give you data through Search Match. Use it.
• Forgetting RTL markets. Arabic and Hebrew feel exotic but they are worth the effort. The competitive bar is even lower than in CJK. See our Arabic RTL data piece.
• CJK font fallback issues. Japanese characters render in fallback fonts when your screenshot template uses Latin-only fonts. The result looks unprofessional and tanks conversion.

The Cost vs Revenue Math

The honest math on aso localization for an indie is forgiving.

• DIY translation with native review: roughly $10 to $50 per locale for title, subtitle, and description.
• Screenshot localization with Shotlingo: $9 per month unlimited across all locales.
• Total one-off setup for Tier 1 plus Tier 2 (eight markets): roughly $100 to $200.
• Expected revenue lift: industry data suggests fully localized apps see 2 to 3x the downloads of single-market peers. The actual multiple varies, but the direction is consistent.

A $200 one-off investment against a 2x revenue trajectory is the kind of math indies should never skip. The reason it gets skipped is that the work feels intimidating, not because the math is unfavorable.

For more on Apple's official guidance, see Apple's developer localization documentation and the App Store Connect localization workflows.

FAQ

How is ASO localization different from translation?

Translation converts words from one language to another. ASO localization adapts your entire App Store listing including keywords, screenshots, preview videos, and cultural framing for a specific market. Translation is one ingredient. Localization is the whole recipe. See our ASO glossary for related terms.

Which market should I localize first?

For most indie apps, the answer is Japan, Germany, or France. Japan has the highest revenue ceiling but the steepest learning curve. Germany is the easiest culturally for Western devs. France is a strong middle ground. Pick the one closest to your existing user base or the one with the highest revenue category for your app type.

Do I need to localize my screenshots, or is metadata enough?

Metadata-only localization improves discoverability but not conversion. Users who find you through localized keywords still bounce when they land on English screenshots. Screenshot localization is the step that converts the discoverability into installs. If you only do one thing beyond metadata, localize your screenshots.

The Bottom Line

Industry data suggests roughly 60% of global app revenue is non-English. Most indies ship English-only or token translation and walk past that majority. The fix is not a 40-market launch. It is a focused Tier 1 plus Tier 2 push with real screenshot localization and per-locale keyword research. The cost is roughly $100 to $200 one-off plus a screenshot tool. The expected lift is multiples, not percentages.

Ready to capture the 60%? Create a free Shotlingo account and start localizing your screenshots in minutes. Or explore our localization hub for templates, language guides, and the per-market data series referenced throughout this post.

Originally published on Shotlingo