OnlineDocTranslatorGuides

Running your practice

Video Game Localization: What Translators and Agencies Need to Know

Video game localization adapts a game's text, voice, UI, and cultural references for a target locale — produced by translators, LQA testers, and localizers

Video game localization sits at the intersection of software localization and performance direction, and the people producing it are translators, LQA testers, and localization engineers working from a studio-supplied loc kit. This guide is written from the producer's side of the desk: the artifacts that land in your inbox, the tools that open them, the rates US agencies quote, and the career routes into paid game work.

What is video game localization from the translator's side of the desk?

Video game localization is the end-to-end adaptation of a game's in-game text, UI strings, voiceover, art assets, and cultural references for one target locale, produced by translators, LQA testers, and localizers working inside a loc kit the studio hands over — not by rewriting a Word document. The producer sits inside a CAT tool, a staging build, and a bug tracker, not inside a bilingual document view.

Three seats produce the work:

  • Translator — opens string files in Trados, memoQ, or Phrase; writes target copy against a term base and style guide.
  • LQA tester — plays the localized build on target hardware; logs truncations, overlapping UI, and cultural errors as bugs.
  • Localization engineer — assembles the loc kit, runs pseudo-loc, and merges translated resources back into the build.

How does video game localization differ from game translation?

Game translation moves text from source to target language. Video game localization is one of roughly eight workstreams that also adapts cultural references, re-records voiceover, re-lays UI for text expansion, mirrors interfaces for RTL locales, and swaps art assets. Translation is the linguistic core; localization is the full pipeline around it.

Which eight artifacts land on a game localizer's desk?

A game loc kit contains eight artifacts: the resource bundle (.po, .xliff, or Excel string tables), translation memory, term base, style guide, pseudo-loc or staging build, character bible, voiceover script with timecodes, and the LQA bug tracker — three more than a standard app loc kit.

ArtifactFormat / toolAlso in app loc kit?
Resource bundle.po, .xliff, .resx, .json, ExcelYes
Translation memory.tmx inside Trados/memoQYes
Term base.tbx or glossary exportYes
Style guidePDF or wiki pageYes
Pseudo-loc or staging buildPlayable binary on target hardwareYes
Character biblePDF — names, voices, speech registersNo
VO script with timecodesExcel or AAF with in/out pointsNo
LQA bug trackerJira or studio trackerNo

Our published Application Localization: The Translator's and Agency's Guide covers the five-artifact app loc kit (resource bundle, TM, term base, style guide, staging build). Games add character bible, timecoded VO script, and the LQA bug tracker.

How it works

What are the key elements of the video game localization process?

1

How does i18n and pseudo-localization set up the translator's work?

Internationalization externalizes every string from the game engine's code, and pseudo-localization replaces source strings with accented, expanded characters so engineers catch hard-coded strings, concatenation, and layout breaks before translators receive the files. Skipping this step forces translators into query loops that triple editing time.

Rather than re-explain those two stages here, read our dedicated pages: i18n: What Internationalization Means for Translators Producing Localized Builds and Pseudo Localization: What Translators Need to Know About i18n Test Builds.

2

Which file formats do game translators actually open?

Game translators open .po, .xliff, .resx, .json, Unity ScriptableObject exports, Unreal .uasset string tables, and vendor-specific Excel string tables — all consumed inside CAT tools such as SDL Trados, memoQ, and Phrase, with QA passes run through Xbench.

  • .po / .xliff — open-standard string files, native in every major CAT tool.
  • .resx / .json — common in C# and JavaScript-based engines.
  • Unity ScriptableObject exports — flattened to CSV or XLIFF before translation.
  • Unreal .uasset string tables — exported via the Unreal localization dashboard.
  • Excel string tables — vendor-specific; filter rules protect tags and placeholders.

3

What does voiceover and lip-sync localization add to the workflow?

Voiceover localization adds a recorded dialogue stage: translators write time-constrained target scripts, voice directors cast and record in a booth, and audio engineers lip-sync lines to character animation — a workstream absent from app and document localization, billed per studio hour rather than per word.

Script writing for VO is a transcreation task. The translator writes to a timecode in/out window, matches syllable count to animated mouth shapes, and preserves character register from the bible. US studios bill voiceover direction at $150–$300 per studio hour.

4

How does Localization Quality Assurance (LQA) work inside a staging build?

LQA testers play the localized staging build on target hardware, logging truncations, overlapping UI, untranslated strings, broken placeholders, and cultural errors as bugs in Jira or a studio tracker — scored per 1000 words against a weighted rubric at release, the same QA cadence used across our certified translation production.

A standard LQA bug record carries severity (A/B/C), category (linguistic, cosmetic, functional), screenshot, repro steps, and suggested fix. Xbench is the industry QA pass between translation and LQA for catching inconsistencies, number mismatches, and empty targets before the build is cut.

How does cultural adaptation differ by target region in game localization?

Cultural adaptation changes jokes, character names, historical references, religious iconography, weapons, gestures, and UI color conventions by region — Japan, China, Germany, Saudi Arabia, and Brazil each impose different content rules, and localizers who miss them trigger age-rating failures, store rejections, or player backlash.

  • Japan — honorific registers, double-byte fonts, character-name re-naming for phonetic readability.
  • China — content review against regional publishing rules, skeleton and skull iconography restrictions.
  • Germany — USK age-rating sensitivity around historical symbols; text expansion of 25–30%.
  • Saudi Arabia — RTL mirroring, religious iconography review, dialect decision.
  • Brazil — Brazilian Portuguese (not European), football references, informal register.

What makes Japanese and Chinese game localization different from Western locales?

Japanese and Chinese game localization require character-name re-naming for phonetic readability, honorific registers absent in English, double-byte font support, and content review against regional publishing rules. Nintendo's historical Western releases rewrote humor and iconography wholesale rather than translating line-by-line, and the reverse is also true for English-to-Japanese inbound work.

For a deeper CJK producer-side walkthrough, see our sibling guide i18n: What Internationalization Means for Translators Producing Localized Builds, which covers double-byte handling and bidirectional engine support.

What makes Arabic game localization harder than most target languages?

Arabic game localization is harder because it requires right-to-left (RTL) UI mirroring, Arabic script shaping with contextual letter forms, 25–30% text expansion inside hard-coded HUDs, and a dialect decision between Modern Standard Arabic (MSA) and regional variants. Demand is growing, competition is thin, and Unity and Unreal only partially support RTL out of the box.

The worked example: a studio ships an action RPG into Gulf markets. Four producer-side decisions follow:

  1. Dialect — MSA for narrative text and UI; Gulf dialect optional for incidental VO barks.
  2. UI mirroring — menus, inventory grids, progress bars flip; HUD compass does not.
  3. Script shaping — the engine must render contextual letter forms; stock Unity text components do not.
  4. Text expansion — Arabic strings run 25–30% longer than English; hard-coded HUD widgets truncate without a rebuild.

Pricing

How much do agencies and freelancers charge for video game localization?

US agencies price video game localization in six line items per locale: translation $0.08–$0.20 per source word, review $0.04–$0.08 per word, LQA $40–$90 per 1000 words, voiceover direction $150–$300 per studio hour, project management 10–15% of job, and loc-kit engineering setup $300–$1,500 flat — placeholder-dense and timecoded segments carry a 15–25% surcharge.

ServiceDetails
Junior$0.05–$0.10/word; UI strings, item descriptions, patch notes.
Mid-career$0.10–$0.15/word; narrative dialogue, quest text, review passes.
Senior / specialist$0.15–$0.25+/word; transcreation, song lyrics, marketing copy, VO script adaptation.
Get a quote

How does a translator break into video game localization as a career?

Translators break into video game localization through four documented routes: contributing to a fan-translation project to build a portfolio, taking an LQA tester seat at a Language Service Provider, applying to game-specialist LSPs before approaching studios directly, and networking through IGDA chapters and LocWorld — a translation degree is useful but not required.

Do fan translations build a usable portfolio for paid game localization work?

Fan translations build a usable portfolio when the project is a completed, publicly playable patch of an abandoned or clearly non-commercial title. LSPs will not credit fan work on live Steam, PlayStation, or Nintendo titles because distributing modified binaries of commercial games violates publisher EULAs and risks legal exposure.

The clean line is this: ROM patches for abandoned 16-bit titles are a credit-worthy portfolio piece. A fan patch of a currently-selling PC game is a liability on a CV.

Is the LSP route or the direct-to-studio route faster for a junior localizer?

The LSP route is faster for a junior localizer because vendors hire LQA testers and junior translators continuously, while in-house studio localization seats open only around major title cycles. Most senior in-house localizers started on an LSP contract.

The LQA-first path is the entry route most working localizers describe: a junior lands an LQA tester seat, learns the Xbench and bug-report workflow on live projects, and is promoted into translation after one or two titles.

Which tools and credentials do game-localization employers actually ask for?

Game-localization employers ask for working fluency in SDL Trados or memoQ, QA fluency in Xbench, familiarity with .po/.xliff/Excel string tables, demonstrable gaming literacy, and native-level target-language fluency — a translation or linguistics degree matters less than a shipped-title credit or a reviewed fan-translation portfolio.

  • CAT tool — SDL Trados Studio or memoQ (one of the two is non-negotiable).
  • QA tool — Xbench for consistency, number, and tag checks.
  • File formats — ability to open and filter .po, .xliff, .resx, Excel string tables.
  • Gaming literacy — platforms played and genres understood; terminology spoken natively.
  • Target fluency — native-level in the target language, strong source comprehension.

What are the common engineering pitfalls that break video game localization?

The costliest engineering pitfalls in video game localization are hard-coded strings in UI widgets, concatenated sentences that cannot be reordered for Japanese or German, missing plural categories, placeholder format drift mid-project, no screenshots for short HUD strings, broken RTL mirroring, and retrofitting i18n after launch — each pitfall multiplies translator query loops and LQA bug count.

Our dedicated guide i18n: What Internationalization Means for Translators Producing Localized Builds covers these pitfalls from the engineering side. From the translator's side, the practical defense is to flag every one of them during the first 200 strings and send a batch query before translating further.

Text expansion is the pitfall every producer meets first. English into German, Russian, and Arabic typically expands 15–30%. A HUD widget sized to "Health" cannot render "Lebenspunkte" without re-layout, and a hard-coded container crops the Arabic string entirely.

How does video game localization compare to application and web localization?

Video game localization shares the resource-bundle, TM, and style-guide spine of application localization but adds voiceover, lip-sync, cinematic subtitling, character-name canon, and on-hardware LQA — pricing per word runs 10–20% lower than apps on raw UI strings and 2–3× higher on timecoded dialogue segments.

The baseline comparison is our Application Localization: The Translator's and Agency's Guide, which prices app translation at $0.10–$0.25/word, review at $0.04–$0.08/word, and LQA at $40–$90/1000 words. Games match the review and LQA bands, discount translation on short UI, and add voiceover direction at $150–$300/hour.

StageApp localizationGame localization
Resource bundle.resx, .json, .po, .xliffSame + Unity/Unreal exports, Excel string tables
VoiceoverRareStandard on AAA, common on mid-tier
Lip-syncNeverRequired for cinematic and in-engine dialogue
LQA environmentStaging web/mobile buildOn-hardware build (console, PC, handheld)
Character bibleNot applicableMandatory for narrative titles
Framework handoffsReact, Angular, Vue i18n librariesUnity Localization package, Unreal localization dashboard

Video game localization FAQs cover career entry, Arabic-specific demand, legal status of fan translations, cost benchmarks, and the difference between LQA and translation seats — the questions working translators and agencies most often raise before taking on game work.

Frequently asked questions

What is localization in video games?

Video game localization is the process of adapting a game's text, audio, UI, and cultural references so it feels native to a target market — not just translated, but culturally appropriate. This goes well beyond swapping words: translators rework jokes, rename characters, resize text boxes for languages like German or Arabic, re-record voice lines, and adjust imagery to meet regional regulations. For professional translators and agencies, game localization is a specialized discipline that sits between literary translation and software/UI localization, demanding both linguistic precision and an understanding of gameplay context.

What is the process of localization in games?

Game localization typically follows five stages: internationalization (i18n), string extraction, translation and adaptation, linguistic quality assurance (LQA), and in-game testing. Internationalization is handled by developers first — hardcoding is removed and the engine is made locale-aware. Translators then receive string files (often in XML, JSON, or Excel) with context notes, translate them, and return them for integration. LQA reviewers check for truncated text, missing glyphs, and cultural issues. Final in-game testing confirms everything renders correctly in the live build. For agencies, managing this pipeline efficiently — with clear handoff protocols and version control — is as important as translation quality itself.

How much does it cost to localize a game?

Localizing a mid-size game into one language typically costs between $15,000 and $75,000+ depending on word count, voice-over requirements, and language pair. A casual mobile game with 10,000 words might run $1,500–$5,000 per language at standard rates, while a AAA RPG with 500,000+ words and full voice acting can reach seven figures across multiple locales. Translation alone is priced by the word — commonly $0.10–$0.25 per word for specialist game translators in European languages, higher for rarer pairs. Agencies should budget separately for LQA, desktop publishing, and project management overhead.

How do I get into game localization/translation as a career?

Start by building a foundation in translation (a relevant degree or demonstrated fluency in two or more languages) and then specializing in gaming content. Play games extensively in both your source and target languages to internalize terminology, tone, and genre conventions. Seek junior roles at localization vendors — companies like Lionbridge, Keywords Studios, or Pole To Win regularly hire game translators and LQA testers. Contributing to open-source or indie game translations builds early portfolio pieces. Professional associations like IGDA's Localization SIG and LocWorld events are practical networking entry points.

What skills do I need to break into the game localization industry?

Core skills are native-level fluency in your target language, strong source-language reading comprehension, and cultural knowledge of both markets. Beyond linguistics, game localizers need familiarity with CAT tools (SDL Trados, memoQ, Phrase), basic knowledge of file formats like JSON or XLIFF, and an understanding of UI constraints such as character limits and text expansion. Gaming literacy — knowing genre conventions, understanding game mechanics, and reading context from screenshots — is essential for accurate translation. Soft skills like meeting tight deadlines and communicating with engineers matter equally in a fast-paced development environment.

How to get into video game localization?

The most direct path into game localization is through linguistic quality assurance (LQA) testing, which requires strong bilingual skills and is an entry-level role at many vendors. From there, translators move into junior translator or editor roles. Building a niche — such as expertise in JRPGs, mobile games, or a high-demand language like Arabic or Korean — accelerates career progression. Agencies also look for candidates who can pass timed translation tests and demonstrate gaming knowledge. Attending industry events like GDC or LocWorld and joining the IGDA Localization SIG helps candidates connect with hiring managers directly.

How much do game localizers make?

Freelance game translators typically earn $0.10–$0.25 per source word, with experienced specialists commanding the higher end of that range. Full-time localization project managers at agencies earn roughly $45,000–$75,000 annually in North America, while senior linguists and localization directors can earn $80,000–$110,000+. Rates vary significantly by language pair — rare pairs or languages requiring complex script handling (Arabic, Thai, Japanese) often command premiums. LQA testers at entry level may earn hourly rates of $15–$22, making it a common but lower-paid entry point. Freelancers who specialize in high-volume gaming clients can build stable, well-paying workloads over time.

What qualifications do you need to become a translator?

Professional translators typically hold a bachelor's or master's degree in translation, linguistics, or a related field, though demonstrated bilingual proficiency and subject-matter expertise can substitute in practice. For game localization specifically, certifications from bodies like the ATA (American Translators Association) signal credibility to agencies, though they are not universally required. What agencies consistently prioritize is a strong, relevant portfolio, familiarity with CAT tools, and the ability to pass in-house translation tests. In regulated fields like legal or medical translation, formal credentials and certification carry more weight than they typically do in game localization.

Is there demand for Arabic game localization?

Yes — demand for Arabic game localization has grown substantially as the MENA gaming market has expanded into one of the fastest-growing regional markets globally. Saudi Arabia, UAE, and Egypt represent large, young, mobile-first gaming populations, and major publishers increasingly prioritize Arabic as a launch language rather than an afterthought. Arabic localization is technically complex — it requires right-to-left UI implementation, Arabic numeral decisions, and dialect choices (Modern Standard Arabic vs. regional variants) — which means skilled Arabic game translators command a premium. For agencies, Arabic is a high-value specialization with a relatively limited pool of qualified game-specialist translators.

Related