Run a full App Store listing through Google Cloud's machine translation and it costs under ten cents. The 2026 list price is $20 per million characters (Google Cloud, Cloud Translation pricing). The same listing from a human translator costs about $110–$215. A full in-app localization can pass $30,000 per language. All three get called "localization," and they sit more than five orders of magnitude apart.
That's why quotes never line up: each vendor prices a different scope, and almost nobody prices the upkeep that arrives with every release. If you haven't picked your markets yet, start with which languages to localize first. This post prices what comes next, tier by tier, and gives you a payback test to run on your own revenue per install.
Translation is now the cheap line. Machine translation costs $20 per million characters (Google Cloud, 2026), and a human-translated App Store listing about $110–$215 per language (Smartling rates, 2026). The money goes to keyword research, screenshots, QA and upkeep; in-app localization runs $2,000–$30,000+ per language (Kanopy Labs vendor estimates, 2026). Buy only the depth your storefront traffic can repay.
Key Findings
- Raw machine translation costs about $0.0001 a word, against $0.15–$0.30 for a human: a gap of more than 1,000×.
- A full App Store text set is about 720 words: $110–$215 by hand, about $86 with post-edited MT, under $0.10 raw.
- In-app localization runs $2,000–$30,000+ per language, plus $5,000–$25,000 of one-time engineering (vendor estimates).
- 91 of the U.S. top-100 grossing iPhone apps updated within 14 days; the median release note ran 27 words (ASO Agency snapshot, Sep 24, 2026).
- Every $1,000 needs about 1,800 extra installs to repay in North America, 3,000 in Western Europe and 9,100 in India and Southeast Asia (RevenueCat, 2026).
How much does app localization cost in 2026?
Per language and per store, it runs from under $1 to more than $30,000 in 2026. The low end is machine-translated metadata. The top end is a large app's full in-app localization, in Kanopy Labs' July 2026 vendor estimates. The range is wide because "localization" names five different jobs. Price each separately.
| Tier | What's included | Cost per language | Driver | Source |
|---|---|---|---|---|
| 1 · Keyword fields | Title, subtitle, keyword field, researched locally | $500–$2,000 ASO research (vendor estimate); under $10 translation | Research hours | Kanopy Labs; Smartling |
| 2 · Store metadata | Tier 1 plus promotional text and description | $110–$215 human; ~$86 MTPE; under $0.10 raw MT | Per-word rate | Smartling; Google Cloud |
| 3 · Creative | Captions, localized imagery, app previews | $300–$2,000 | Design time | Centus; AppFollow |
| 4 · In-app strings | App strings, LQA, internationalization (i18n) | $2,000–$30,000+; LQA $1,000–$5,000; i18n $5,000–$25,000 once | String count, QA | Kanopy Labs (vendor estimates) |
| 5 · Culturalization | Legal, voice, support, payments | Legal review $2,000–$5,000 (vendor estimate); voiceover ~$1,700–$3,600 | People, compliance | Kanopy Labs; Centus |
Third-party bundles land in the same place. AppFollow's 2026 playbook puts one store localization cycle at $1,000–$5,000 per market; tiers 1 to 3 above add up to roughly $900–$4,200. These are third-party figures, not our prices.
What one language costs, tier by tier
Tier 2 is the anchor. A human-translated App Store text set costs about $110–$215 per language in 2026. That's roughly 720 words at Smartling's $0.15–$0.30 per-word rate (Smartling, Translation Rates, Sep 2026). It's the same figure our language ranking uses. Everything above it is priced in hours, assets or string counts, not words.
How we priced it
We used 10 public rate cards and pricing pages, retrieved September 24–25, 2026 and listed in Sources. One language, one store, a small-to-mid app; words equal characters divided by six (4,330 characters is about 720 words). Vendor estimates are labeled. These are ranges, not quotes, and exclude our own prices. Cite as: ASO Agency, "App Localization Cost in 2026," asoagency.io, September 25, 2026.
What does each localization tier include?
Each tier adds a different kind of work: words and research, then design, then engineering and QA, then people. Costs jump at each boundary. In Kanopy Labs' July 2026 estimates, the step from store metadata to a small app's strings is $2,000–$5,000 per language before QA.
Tier 1: keyword and title fields
Title (30), subtitle (30) and keyword field (100) add up to 160 characters, about 27 words: roughly $8 at $0.30 a word. Translated bills a 100-word minimum, though. The keyword limit is 100 characters. App Store Connect Help says bytes, but saved strings show characters are enforced (Apple Developer Forums, 2022; Applyra, 2026).
Translation is the wrong tool here anyway. You need the words that market actually types, which means keyword research in each new locale. The cheapest tier-1 move needs no translation: English (U.K.) is indexed in 172 of 175 storefronts, per our Cross-Localization Explorer.
Tier 2: full store metadata
At maximum length, an App Store text set is about 4,330 characters: name 30, subtitle 30, keywords 100, promotional text 170 and description 4,000 (Apple, 2026). Google Play's three text fields come to about 4,110 characters, or 685 words (Play Console Help). When you add a language, Apple copies most properties from the primary language, "except for the description and keywords" (Apple). Those you write.
Tier 3: screenshots and creative
The words are few; the cost is design. Apple allows one to 10 screenshots and up to three previews per device size and language (Apple). Updating them needs a new app version. Centus budgets about $300–$600 of design per language (2024); AppFollow puts a creative refresh at $500–$2,000. Apple's screenshot specifications now list iPhone Duo sizes too, so there's more creative per locale. To keep this tier lean, localize your screenshots for each market starting with the first three frames.
Tier 4: in-app UI and strings
This is where budgets break. Kanopy Labs' uncited ranges are $2,000–$5,000 per language for small apps (under 2,000 strings), $5,000–$15,000 for medium and $15,000–$30,000+ for large, plus i18n and LQA. Others run lower: Centus's small-app example works out to about $1,100–$1,800 per language (2024), and Alconost's 2026 game scenario to about $2,150. On Android, Play Console has translated app strings with Gemini "at no cost" since October 30, 2025 (Android Developers Blog). Review still costs.
Tier 5: full culturalization
This tier is people: legal review, voice, payments and support. Business of Apps' 2026 benchmarks show conversion rising from 4.3% to 6.5% with a localized payment method. And in 2020, CSA Research found 75% of consumers are likelier to repurchase with customer care in their language. Most apps shouldn't buy this tier first.
Per-word or per-project: how is app localization priced?
Text is priced per word, QA per hour, creative per asset and tools per month. In September 2026, Smartling put human translation at $0.15–$0.30 a word. Alconost's April 2026 rate card, built from 3,200+ projects, runs $0.07–$0.14 by language, and Translated's average is $0.10.
Language sets the rate. Russian costs $0.07 a word at Alconost; Japanese, Danish and Finnish cost double. Among the Tier-1 markets in our ranking, Japanese is the priciest and Italian and Portuguese (Brazil) the cheapest.
Human translation rate per word, by target language
The other units add up. LQA runs $31–$48 an hour at Alconost. Google Play Console's paid vendor charges "as little as USD 0.07 per word" (Play Console Help). Tools matter only at tier 4: Phrase runs $27–$1,245 a month billed annually, Lokalise $149–$1,049. Then the multipliers: a 20–50% rush surcharge under 48 hours (Alconost) and 100-word minimums (Translated).
Human, machine or MT + post-editing: which should you pay for?
Choose the method field by field, not once per project. In 2026, raw machine translation costs about $0.0001 a word at Google Cloud's $20 per million characters, after 500,000 free characters a month. MT plus post-editing (MTPE) costs $0.12 at Smartling or $0.06–$0.12 at Alconost; human translation, $0.15–$0.30.
Quality has caught up on plain text. Intento's State of Translation Automation 2025 covered 46 engines and LLMs across 11 language pairs. Its human evaluators "often couldn't distinguish AI-generated from human translations" (Slator, Oct 2025). But store copy isn't plain text. A 30-character subtitle is a positioning decision.
| Method | Price | Speed | Evidence | Best for | Avoid for |
|---|---|---|---|---|---|
| Raw MT / LLM | $20 per 1M characters; Gemini in Play Console free | Seconds | Intento 2025: often indistinguishable | Drafts, Android strings with review | Title, subtitle, keywords |
| MT + post-editing | $0.06–$0.12 a word | 1–3 days (Centus) | LSP adoption 26% (2022) to ~46% (2024) (Nimdzi) | Description, UI, release notes | Legal copy |
| Human translation | $0.07–$0.30 a word | ~2,500 words a day (Translated) | The baseline | Promotional text, captions | Keyword field |
| Native copy + keyword research | Research hours | Slowest | n/a | Title, subtitle, keywords, first three captions | Bulk UI |
Imperfect local copy still beats English for low-stakes text. In 2020, CSA Research found 65% of consumers prefer their own language even at poor quality (CSA Research). That doesn't rescue the keyword field, where a mistake costs rankings. And since Google I/O on May 19, 2026, Gemini pre-populates Play listings across languages for your review (Android Developers Blog). On Android, the machine layer is free; review is the cost.
Translation is approaching free; judgment isn't. At about $0.0001 a word, raw MT is more than 1,000× cheaper than a $0.15 human rate. So the spend moves to what a model can't do for you: choosing keywords, writing a 30-character subtitle, checking the first three screenshots.
What does localization cost after launch?
You pay again with every release. On September 24, 2026, we took a snapshot of the U.S. top-100 grossing iPhone apps. Of those, 91 had shipped an update in the previous 14 days, and 70 in the previous seven. The median release note ran 27 words. Apple requires "What's New in This Version" for every version after the first, and it's localizable (Apple, Platform version information).
The method: we pulled Apple's U.S. top-grossing iTunes RSS feed, then read each app's releaseNotes, currentVersionReleaseDate and languageCodesISO2A from the iTunes Lookup API. A re-pull on September 25 returned the same apps and figures. Release notes ran a median 27 words (middle half 11–45). Median supported languages: 16, read from the binary, so it's a proxy for store localizations.
Now the illustrative arithmetic. A weekly shipper with 16 languages writes English plus 15 translations: 780 localized release notes a year. Bought one job at a time with a 100-word minimum at $0.15–$0.30 a word, that's $11,700–$23,400 a year for release notes alone. Batch them or run MT with a spot review, and the line drops close to zero.
| Upkeep line | Cost | Source |
|---|---|---|
| New strings each release | Translation memory saves 20–40% | Kanopy Labs (vendor estimate) |
| Continuous localization | Saves 30–50% | Alconost, 2026 |
| Periodic LQA | $3,000–$6,000 a year | Alconost, 2026 |
| Creative refresh | $500–$2,000 per cycle | AppFollow, 2026 |
| Keyword re-research | Quarterly (our practice, not a benchmark) | ASO Agency |
| Rule of thumb | 15–25% of initial cost a year | Kanopy Labs (vendor estimate) |
Market pages add to it. Every localized custom product page is another screenshot set to refresh. That's why we flag the maintenance cost of market pages early.
What hidden costs do localization quotes leave out?
A quote prices the words; the bill covers the work around them. Start with text expansion. IBM's guidelines, published by the W3C, expect English strings of up to 10 characters to reach 200–300% of their length in European languages. Strings over 70 characters reach about 130% (W3C, Text size in translation). Six lines usually go missing:
- Expansion rework. A 30-character German title gets rewritten, not translated. Check every locale against the character limits.
- LQA cycles. $31–$48 an hour (Alconost), plus days for in-context checks.
- Release gating. Screenshots change only with a new version, so creative fixes wait.
- Support and reviews. CSA Research found 73% of consumers want product reviews in their language; new locales mean replying in it.
- Rush fees and minimums. 20–50% surcharges (Alconost); 100-word minimums (Translated).
- Project management. Centus's five-language example carries $200–$400 of it.
Each is billed by someone other than the translator. Ask vendors which of the six they include.
When does app localization pay back? The ROI model
Localization pays back when incremental installs times revenue per install exceed cost plus upkeep. At RevenueCat's 2026 day-60 medians, every $1,000 needs about 1,800 extra installs in North America ($0.55), 3,000 in Western Europe ($0.33) and 9,100 in India and Southeast Asia ($0.11) (RevenueCat, State of Subscription Apps 2026). Those match the regional revenue-per-install table in our language ranking.
| Tier line | Cost per language | North America ($0.55) | Western Europe ($0.33) | India & SE Asia ($0.11) |
|---|---|---|---|---|
| Metadata translation | $110–$215 | 200–390 | 330–650 | 1,000–1,950 |
| Keyword research / ASO | $500–$2,000 | 910–3,640 | 1,520–6,060 | 4,550–18,180 |
| Screenshots and creative | $300–$2,000 | 550–3,640 | 910–6,060 | 2,730–18,180 |
| In-app, small app (strings + LQA) | $3,000–$10,000 | 5,450–18,180 | 9,090–30,300 | 27,270–90,910 |
Extra installs needed to repay each tier, by region
How much traffic does payback need?
Divide the installs you need by a realistic conversion lift, and you get the traffic a market must already send you. In 2020, Storemaven's data from 500M+ users put the potential lift of a localized store page at 5.1–24.6% (Storemaven, 2020). Top gaming apps reached up to 26%. The data is old, so use a mid value. At a 10% lift, the 650 installs that repay $215 of metadata in Western Europe need about 6,500 baseline installs from that language. The $10,000 in-app tier needs about 303,000.
So match depth to the traffic you already have. The exception: where you rank for nothing, localized keywords add visibility a conversion lift can't capture.
And the famous "+128% downloads"? It comes from Distimo's September 2012 report on around 200 iPhone apps that added the native language that August. It compared one week after with one week before. Downloads rose over 128% and revenue about 26%, while iPad apps saw no significant download growth. Distimo itself wrote that crediting the language alone "is hard to tell" (Distimo, 2012). Treat it as direction, not a forecast.
ROI = (incremental installs × revenue per install − cost) ÷ cost. Run it on your own numbers: plug your own revenue per install into our Apple Search Ads Calculator and read the break-even section.
Caveats: RevenueCat's figures are medians for subscription apps by user region, from 115,000+ apps, so games sit outside them. RevenueCat defines RPI as "total revenue earned divided by total installs" without saying whether that's before the store's commission. If it's gross, install counts rise about 18% at a 15% commission and 43% at 30%. Lifetime value beyond day 60 shortens payback.
How should you budget your first new market?
Buy depth in the order your data earns it. Do tiers 1 and 2 first, starting with English (U.K.), indexed in 172 of 175 storefronts with no translation (ASO Agency Cross-Localization Explorer, 2026). Then validate, and fund in-app work only where a market clears the break-even threshold. Our sequence:
- Month 0: keyword research and full metadata for one Tier-1 market.
- Months 1–2: a localized custom product page as a cheap market probe (up to 70 per app, each localizable, per Apple), or test localized treatments with Product Page Optimization.
- Month 3 onward: screenshots for the market whose impressions and conversion moved.
- Month 6 onward: in-app work only where installs × revenue per install clear the tier-4 cost.
If you're weighing whether to run localization in-house or with an agency, price the research and upkeep hours, not just the words. Our app localization service runs in this order, one market at a time.
Frequently asked questions
How much does it cost to localize an app?
It depends on the tier. Translating an App Store listing costs about $110–$215 per language at Smartling's 2026 rates of $0.15–$0.30 a word. In-app localization runs $2,000–$30,000+ per language, plus $5,000–$25,000 of one-time engineering, in Kanopy Labs' 2026 vendor estimates. Most of the gap is QA, design and upkeep, not words.
How much does it cost to translate an App Store listing?
A full App Store text set is about 720 words. That's $110–$215 from a human translator, about $86 with machine translation plus post-editing at Smartling's $0.12 a word, and under $0.10 with raw machine translation at Google Cloud's 2026 price. The keyword field needs research in the new locale, not translation.
Is machine translation good enough for App Store metadata?
For the description and UI strings, yes, if a person post-edits it. In Intento's 2025 evaluation of 46 systems, human evaluators often couldn't tell top AI translations from human ones on standard text. Don't use it for the title, subtitle or keyword field. Those need native keyword research, because a mistake there costs rankings.
How much does localization cost per release?
More than most budgets allow for. In our September 2026 snapshot, 91 of the U.S. top-100 grossing iPhone apps had updated within 14 days, with a median 27-word release note. Bought job by job at a 100-word minimum, a weekly shipper's notes in 15 languages cost $11,700–$23,400 a year. Batch them instead.
How long does localization take to pay back?
It depends on the region's revenue per install. At RevenueCat's 2026 day-60 medians, every $1,000 needs about 1,800 extra installs in North America, 3,000 in Western Europe and 9,100 in India and Southeast Asia. Metadata translation alone repays in about 330–650 extra Western European installs. Deeper tiers need thousands.
The bottom line
- Price five tiers, not one number. The words of a listing cost $110–$215; in-app work, $2,000–$30,000+ per language.
- Machine translation made words nearly free. Research, creative, QA and upkeep are the budget.
- Choose the method by field, and budget for upkeep: 91 of the top 100 U.S. grossers updated within 14 days.
- Match depth to traffic: each $1,000 needs about 1,800, 3,000 or 9,100 installs to repay, by region.
Look up your storefronts in the free Cross-Localization Explorer. For a budget built from your own App Store Connect data, book a free 30-minute call or start with the fixed-price ASO audit.
