Game Localization and Internationalization for Global Markets

When The Witcher 3: Wild Hunt launched in 2015, CD Projekt Red released it simultaneously in 15 languages, including fully voiced dialogue in Polish, English, and 4 other languages, with subtitles covering the rest. That wasn't an afterthought — it was a deliberate infrastructure decision baked in from early development. The gap between a game that sells in one market and one that sells in 40 comes down, in large part, to how seriously a studio treats localization and internationalization as engineering and creative disciplines, not just translation tasks.

This page covers the distinction between localization and internationalization, how the process actually operates in a production pipeline, where it applies across different game types and markets, and how studios decide when the investment is warranted.

Definition and Scope

Internationalization (commonly abbreviated i18n — 18 letters between the "i" and the "n") is the engineering work that makes a game capable of being localized. Localization (l10n) is the creative and linguistic work that actually adapts it for a specific locale. These are related but distinct disciplines, and conflating them is how studios end up with expensive retrofits.

Internationalization includes decisions like: storing all display text in external string files rather than hardcoding it into source code, designing UI layouts with text expansion budgets (German text routinely runs 30–40% longer than English equivalents), supporting Unicode character encoding for languages that don't use the Latin alphabet, and building date, time, currency, and numeral formatting as locale-aware variables rather than fixed strings.

Localization scope varies significantly by market and budget. A full localization pass typically includes:

  1. Text translation — menus, subtitles, dialogue, tutorials, in-game item descriptions, achievement text
  2. Voice-over (VO) localization — re-recording dialogue with native actors, which multiplies cost substantially
  3. Cultural adaptation — adjusting imagery, symbols, character design, or narrative content that may be offensive or legally restricted in specific regions
  4. Legal and rating compliance — content ratings bodies in Germany (USK), Australia (ACB), China (NRTA), and South Korea (GRAC) each have distinct content standards that may require asset changes
  5. Audio and video assets — updating marketing trailers, tutorial videos, and splash screens
  6. QA localization testing — verifying that translated strings display correctly, don't break UI containers, and read as intended by native speakers

The International Game Developers Association (IGDA) has published localization guidelines treating this process as a production discipline with dedicated resourcing, not a post-production task.

How It Works

Localization in practice is a pipeline problem. The earlier a team builds localization-aware infrastructure, the cheaper it is. The industry standard approach follows a rough sequence:

String externalization happens during engine setup — all player-facing text is written to resource files (commonly .xml, .json, or .po format) that translation teams can edit without touching source code. Engines like Unity and Unreal Engine both offer built-in or asset-store localization toolkits that manage string tables, pseudolocalization testing, and font rendering for non-Latin scripts.

Pseudolocalization is a technique worth knowing: before real translations exist, tools replace Latin characters with accented or extended equivalents to simulate how longer translated text will behave in UI containers. This catches layout failures before a single translator is hired.

Translation memory (TM) systems — used by most professional localization vendors — store previously translated strings and flag matches when the same or similar text appears again, reducing per-word costs on sequels or content updates.

Voice-over localization adds a different order of complexity. It requires translation that fits lip-sync timing windows, casting and studio sessions in each target language, audio file management across potentially thousands of dialogue lines, and implementation back into the audio engine. Studios frequently partner with localization service providers (LSPs) who specialize in game content — companies like Babel Media, Keywords Studios, and Binari Sonori operate in this space, though specific vendor relationships vary by project.

Common Scenarios

Indie titles going multiplatform — A small studio launching on Steam to a primarily English-speaking audience may ship with English only. But if Steam analytics show significant wishlist activity from Brazil, Germany, or Japan, adding even text-only localization for those 3 markets can meaningfully shift conversion rates.

Mobile games targeting Asian markets — Mobile games publishing in China requires approval from the National Radio and Television Administration (NRTA), which mandates content review and, for foreign titles, a Chinese publishing partner. Japan and South Korea each have their own rating systems and cultural expectations around UI density, monetization phrasing, and character aesthetics that affect whether a game reads as polished or foreign.

AAA simultaneous global launches — Major publishers like Nintendo, Sony, and Ubisoft build localization into milestone schedules from pre-production. The goal is "sim-ship" — shipping all language versions on the same date — which requires coordinating translation, VO recording, and cert submissions across platforms in parallel. Console certification and submission processes at Sony, Microsoft, and Nintendo all include localization verification requirements.

Decision Boundaries

The core question studios face: which languages, and at what depth?

A useful framework separates markets by return profile:

The right cutoff depends on genre, platform, and price point. A narrative-heavy RPG where dialogue is central to the experience warrants VO investment in Japanese in a way that a physics puzzle game may not. Understanding where a given project sits in the broader video game development production pipeline shapes these decisions — localization costs baked into a milestone budget behave very differently than localization bolted on at submission.

The IGDA and Localization Industry Standards Association (LISA) — now largely absorbed into GALA, the Globalization and Localization Association — have both produced standards documentation for game localization workflows. The Game Localization and Internationalization topic connects directly to game publishing and distribution considerations, since platform submission requirements vary by region and language coverage affects certification eligibility.

For studios exploring where localization fits into the full development picture, the Video Game Development Authority index maps the complete landscape of production, publishing, and platform decisions.

References