App Store hit 50 languages. Localize these first.

In March, Apple added 11 more languages to App Store Connect — Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu, and Urdu — bringing the total to 50. Most solo devs read that news and did nothing, because "translate your listing into 50 languages" isn't a task, it's a joke. Here's the actual math on which ones pay for themselves, and which you can skip.

The number that should change your mind

Apple's own product page optimization data puts the average conversion rate on a default, untailored product page at 1.6%. Developers who ship a tailored product page — including localized ones — see a 2.5 percentage point lift on average, a 156% relative increase. CBS Sports measured a 20% conversion bump from a tailored page; State of Survival measured 33%, plus a 14% drop in cost per install. Separately, Storemaven's widely cited localization research found translated listings lift conversion by roughly 26% on average, with some culturally-adapted case studies reporting gains as high as 80%.

None of that requires 50 languages. It requires picking the right handful and doing them properly — real translation and localized screenshots, not machine-translated keywords pasted into the metadata field.

Why "English only" is a bigger leak than it looks

If your listing is English-only, every non-English-speaking visitor who lands on it — from search, from a share link, from a review site — is reading a page that wasn't written for them, in a store where a fully localized competitor sits right next to you in the results. You're not just losing conversion on those visits; in many territories you're not ranking for local-language search terms at all, because Apple's search indexing gives real weight to metadata written in the storefront's language.

What "localize" actually covers

Apple's localization fields go well beyond the description. Per locale, you can set the app name, subtitle, promotional text, the full description, the 100-character keyword field, screenshots, app preview videos, and even in-app purchase display names. Most teams that "localize" only touch the description and leave the rest in English — which means the keyword field, arguably the highest-leverage 100 characters in the whole listing (we've written about that separately), stays untranslated and invisible to local-language search entirely. If you're going to do a locale, do the whole set: name through screenshots. A half-localized page reads as more careless than an English one, because it signals you started and didn't finish.

The five languages worth doing before the other 45

Skip the "translate everything" instinct and prioritize by App Store revenue share, not population. This is the order most indie apps should work through:

1. Spanish (Mexico + Spain). Two of the highest-volume App Store locales outside English, and one translation covers both storefronts with minor regional tweaks.
2. Japanese. Consistently one of the top-grossing App Store territories worldwide, and Japanese users convert notably worse on English listings than almost any other major market — the gap between doing this and skipping it is large.
3. German. A dense, high-spend European market where localized listings are the norm, not the exception; an English-only page reads as unfinished.
4. French. Covers France plus meaningful reach in Canada, Belgium, and francophone Africa with one translation.
5. Simplified Chinese or Portuguese (Brazil), depending on your category. Chinese if you're in productivity, games, or utilities with global reach; Brazilian Portuguese if your app has any social, finance, or lifestyle angle — Brazil is one of the fastest-growing install markets on both stores.

That's five languages, not fifty, and it's the set most likely to clear Apple's 2.5-point conversion bar on volume alone. The March expansion into Indian regional languages (Hindi, Tamil, Telugu, Marathi, Bangla, and friends) is worth revisiting once you have real install data showing India as a growth territory — for most apps that's a second wave, not the first.

The back-of-envelope math for a solo dev

Translation for a modest app listing — name, subtitle, keywords, description, five to eight screenshot headlines — runs somewhere in the range of a good freelance translator's hourly rate times two or three hours per language, or a flat per-locale fee if you use a localization service. Call it a few hours of work or a small fixed cost per language, however you're sourcing it. Against that: even the conservative end of Apple's own numbers, a 20% conversion lift on a tailored page, means one install in five that used to bounce now converts. If your English listing gets any meaningful volume of visits from a target country already — check App Store Connect's territory breakdown before you pick languages, don't guess — the payback period is usually weeks, not months. The math gets worse only if you localize a language with near-zero existing traffic and hope translation alone generates demand. It won't; localization multiplies existing interest, it doesn't create it. That's why territory data should drive the language list, not a hunch about which market "seems big."

Translate the metadata. Don't forget the screenshots.

This is the step most teams skip, and it's the one that actually moves the conversion numbers above — those studies measure tailored pages, not just translated text fields. A Japanese user who taps into a listing with a Japanese title and description, then sees English-language screenshot headlines, gets the same "this wasn't made for me" signal as an English-only page. The screenshots are doing most of the persuasion work; if they're not localized, the translation budget above the fold was wasted.

The catch: App Store Connect wants each locale's screenshots uploaded to that locale's own folder — it's not one flat image set, it's a nested structure per language per device size. Building that by hand in an image editor is the actual reason most indies stop at metadata and never localize the screenshots themselves.

Doing this without a translation budget

This is exactly the gap ShotCanvas closes: design your screenshot set once, let AI translate the headlines into each target locale, and export straight into the per-language, per-device folder structure App Store Connect and Google Play expect — no manual re-typesetting per language. Start with the five above; add more once you can see which territories are actually installing.