Game localization costs vary significantly based on word count, language count, language pairs, and service scope. Most game developers encounter localization cost as a surprise — either higher than expected or structured differently than budgeted. This guide explains the components of game localization cost, typical price ranges for different project types, and the factors that most influence budget.

Per-Word Rates by Language Pair

Game localization pricing is typically quoted in per-source-word rates — cost per word in the source language (usually English) regardless of translation length. Typical professional agency rates for game localization (2024 reference ranges): Major European languages (German, French, Spanish, Italian, Dutch, Portuguese): $0.12–0.20 per word. Northern European languages (Norwegian, Swedish, Danish, Finnish): $0.14–0.22 per word. Eastern European languages (Polish, Czech, Hungarian, Romanian): $0.10–0.18 per word. CJK (Chinese Simplified, Chinese Traditional, Japanese, Korean): $0.15–0.28 per word. Arabic: $0.15–0.25 per word. Southeast Asian languages (Thai, Vietnamese, Indonesian): $0.12–0.20 per word. Note: these are professional agency rates including project management and basic QA. Lower rates are available from freelancers and smaller agencies, but typically without the TM infrastructure, project management, and LQA included in agency rates.

What Drives Localization Cost

The main cost drivers in game localization: (1) Word count — the single largest driver; total translation cost scales directly with words to translate. (2) Language count — adding languages multiplies base translation cost; however, project management, glossary, and LocQA have some economies of scale. (3) Language pair — Japanese and Korean cost more than German and French due to higher complexity of translation from English and translator supply/demand. (4) Content type — narrative dialogue and creative content cost more per word than UI strings; MTPE (machine translation post-editing) can reduce cost for appropriate content types. (5) LocQA scope — first-time CJK or RTL implementation requires significantly more LocQA than languages already supported. (6) TM leverage — games with previous translated content have TM matches that reduce translation cost; highly repetitive content (UI patterns, formulaic quest text) benefits most from TM. (7) Turnaround time — rush fees (typically 20–50% premium) apply to expedited timelines.

Cost Estimates by Game Type

Reference cost ranges for typical game localization projects (professional agency, including translation + LQA + LocQA, major European language per language): Small indie game (5,000–15,000 words, minimal UI): $800–2,500 per language. Mid-size game (20,000–50,000 words, moderate UI): $2,500–8,000 per language. Large game (75,000–150,000 words, complex UI): $8,000–20,000 per language. Narrative-heavy game (200,000+ words, extensive dialogue): $20,000–50,000+ per language. Asian language pair premium adds approximately 20–40% to these ranges. LocQA costs typically add 15–30% of translation cost depending on build complexity. These are reference ranges — actual quotes depend on specific word counts, content types, and language pairs.

How to Reduce Localization Cost

Legitimate cost reduction strategies for game localization: (1) String freeze before project start — late string changes compound cost significantly; getting to string freeze before localization begins eliminates re-work cost. (2) Build and maintain TM — the first localization is the most expensive; subsequent updates with TM leverage are substantially cheaper. (3) Content triage — prioritize full human translation for high-visibility content; consider MTPE for high-volume, lower-visibility UI strings. (4) Scope LocQA appropriately — a first LocQA pass with clear bug documentation is more efficient than multiple rounds of incomplete testing. (5) Provide a complete loc kit — missing context, glossary, and reference build slow the project and increase cost through avoidable errors. (6) Plan language expansion over time — launching with 3–5 languages and adding more in updates is more budget-manageable than launching 12 languages simultaneously.

Frequently Asked Questions