How to Localize an iOS App in 14 Languages (2026)

Localization is the highest-leverage App Store move most indie iOS developers never make. A well-executed localization into one strategic locale lifts installs 30–60% for a typical indie app; five locales done right can 3–5x total install volume. Yet most indies ship English-only and stay that way because the path from “I should translate my app” to “I have a Japanese listing that ranks” is longer than most guides admit.

This post is the 2026 reference for how to translate an app for App Store distribution across 14 languages — the metadata, the in-app strings, the screenshots, and the App Store Connect workflow to ship all three. It ranks the highest-ROI starter locales, walks the App Store Connect UI step by step, and explains the one non-obvious rule that separates listings that rank from listings that just exist in another language.

Pair this with the ASO playbook for indie developers for the broader strategy context, or jump straight to the step-by-step section if you already know which locales you want to ship.

The three layers of iOS localization

Localization is not one task — it is three parallel workstreams, each with its own tooling, its own review path, and its own ROI curve.

Layer 1: Metadata

App name, subtitle, keywords field, description, promotional text, What’s New, support URL, and privacy policy URL. All filled in App Store Connect, per locale. Metadata localization can ship without a new binary — you submit it with your next version as part of the normal review cycle.

Layer 2: In-app content

UI strings, system alerts, error messages, push notification copy, and share-sheet titles. Handled via String Catalog (Xcode 15+, the recommended format since 2023) or legacy Localizable.strings / Localizable.stringsdict. Exported from Xcode as an .xcloc or XLIFF file for your translator, imported back, and rebuilt into your binary. In-app localization requires a new binary submission.

Layer 3: Visual assets

Localized screenshots, app preview videos, and (rarely) a localized app icon. Uploaded per locale in App Store Connect under each localization’s screenshot section. Shipped with the same review cycle as metadata — no binary change required.

Why keyword re-optimization per locale is the whole game

This is the one non-obvious rule that determines whether a localized listing ranks or just exists.

Apple’s App Store keywords field is hidden, comma-separated, and per-locale independent. Every localization you add gets its own 100-character field. The instinct most indies follow is to run the English keywords through Google Translate and paste the output into the Japanese, German, or Portuguese field. This produces a grammatically correct string that almost never ranks.

Here is why. Keywords in a locale are not translations — they are what users in that locale actually type into App Store search. Those terms emerge from the local linguistic and cultural context, not from the English-to-locale dictionary.

The same pattern holds across locales:

• German productivity users search for notizen but also notiz (singular base form), and often mix English loanwords like todo and task.
• Brazilian Portuguese users search for produtividade but also afazeres, which has no direct English equivalent.
• Simplified Chinese users often search using Pinyin or a mix of Latin and Chinese characters that a mechanical translation would never surface.

The fix: every locale gets its own keyword research pass. See the full Apple App Store keywords field deep-dive for the mechanics of the 100-character field.

The 5 highest-ROI starter locales

For an English-first indie app, these are the five locales that consistently return the highest install uplift per hour of localization work. Ordered by ROI, not population.

1. Japanese

Highest per-install revenue in the App Store globally. Premium market that rewards polished localization. Thin indie competition because most indie devs assume Japanese is too hard. Watch for Japanese cultural conventions: politeness levels matter in UI copy, and emojis in descriptions read as informal in a market where formality sells.

2. Simplified Chinese

The largest iOS install base by country. Pairs with the separate Traditional Chinese locale for Taiwan and Hong Kong. Requires an ICP registration if the app includes user-generated content or online services — check App Store China requirements before submitting. App Review in the China storefront is a separate review from the global one.

3. German

Strong purchasing power, ASO-aware user base that notices quality localization. German keyword behaviour is interesting: users commonly mix German and English terms. Keyword research here rewards the extra hour.

4. Brazilian Portuguese

Large and growing market, historically underserved by indie localizations. Strong Google Play penetration but growing iOS user base. Distinct from European Portuguese — use the Brazilian locale (pt-BR), not European (pt-PT), unless you have specific reason to target Portugal.

5. French

Covers France, French Canada, and parts of North Africa. Premium market dynamics similar to German. French users prefer fully localized descriptions without English loanwords; a machine translation that leaves English words in place reads as low-effort.

Step-by-step — adding a locale in App Store Connect

The actual App Store Connect workflow, current through 2026.

1. Open App Store Connect, select your app, go to Distribution → App Store → iOS App.
2. At the top right of the Localizable Information section, click the language dropdown and choose Add Language. App Store Connect supports 40+ locales; add one at a time.
3. Apple creates a new localization pre-filled with copies of your primary-language fields as placeholders. Replace each field.
4. Fill fields in this order:
   • Name (30 chars) and Subtitle (30 chars). The subtitle helper ships proven patterns for both.
   • Keywords field (100 chars) — researched per locale, not translated. Validate the 100-char limit with the keyword character counter.
   • Promotional text (170 chars) — evergreen, no time-bound promotions.
   • Description (4,000 chars) — the first three lines are the conversion hook, spend disproportionate review time there.
   • Support URL and Privacy Policy URL — point at localized pages where possible; the same URL is acceptable but a localized page converts better. Apple verifies these URLs are reachable.
   • What’s New (4,000 chars) — for the current version.
5. Upload localized screenshots under the App Previews and Screenshots section for each device class. 6.9-inch iPhone is the required size as of 2026; others auto-scale.
6. Optionally upload a localized app preview video (up to 3 per device class, 15–30 seconds each).
7. Save and submit with your next version. Metadata-only localizations are reviewed as part of the app review; there is no separate metadata-only review queue.

Push My App’s 14-language translator handles steps 4–6 in one pass — translates the description, re-optimizes the keyword field per locale, exports localized screenshot overlays, and submits to App Store Connect.

The three-layer workflow, automated

Manual localization of all three layers across five starter locales typically takes 20–30 hours per app plus translator costs. Automating the metadata and visual layers cuts that to an afternoon; in-app strings still require a translator for quality, but even there machine translation plus native-speaker review is much faster than ground-up translation.

Push My App’s 14-language translator covers the metadata and visual layers in one pass:

• Translates every metadata field into all 14 supported locales, including title, subtitle, description, promotional text, keyword field, and What’s New.
• Re-optimizes the keyword field per locale using local ranking data, not translation.
• Exports localized screenshot overlays from a single English master, per locale, ready to upload to App Store Connect.
• Submits the localized metadata to App Store Connect directly, so you ship the listing without a new binary.

For the in-app string layer, export your Xcode project’s XLIFF or .xcloc bundle via Product → Export Localizations and hand it to a translator. The App Store vs Google Play listing requirements post covers the equivalent flow for Play if you ship to both stores.

Common mistakes that waste a localization budget

Five mistakes that turn a good localization into a wasted one.

Machine translation without a native reviewer. Acceptable as a first pass for the description; never acceptable as the final version. Japanese, German, and French users notice machine-translation cadence immediately and downgrade the listing’s perceived quality.

Translating keywords instead of re-researching them. The single most expensive mistake. A translated keywords field fills the 100 characters without ranking for the queries that matter. Every locale deserves its own keyword research pass.

Half-localized listings. English screenshots paired with localized descriptions — or vice versa — read as low-quality on both dimensions. If you commit to a locale, commit to all three layers or skip the locale entirely.

Ignoring screenshots and app previews. Screenshots drive installs more than description prose does (see the 2.5-second rule in the ASO playbook). Shipping English screenshots into a Japanese listing cuts install rate by 40%+ relative to fully-localized screenshots in most indie-app category benchmarks.

Forgetting to localize the support URL.Apple reviewers verify every URL in your listing. A support URL that returns 404 in the locale’s language is a reject under guideline 1.5. See the full App Store rejection reasons index for the exact rejection phrasing.

Frequently asked questions