
How game localisation works becomes clearer when you follow the language beyond a translated sentence. A game also has screens, voices and context that shape what a player understands. This guide explains the production stages and the practical language-support checks readers can make. It draws on published developer accounts, engine documentation and practitioner guidance. Keywords Studios’ own description of linguistic testing, localised audio and presentation checks illustrates the range of work involved. Source.

1. Treat localisation as a production process
Text, audio and interfaces belong together
Game localisation connects language work with the systems that deliver a game to its audience. In Ubisoft’s May 2022 interview, localisation project manager Myriam Forbes described translation, recording and testing alongside planning, documentation and risk management. Her examples also included fonts and the right-to-left orientation of Arabic interfaces. That account helps explain why a finished translation file is only one part of the job. The language still has to function within a screen, a performance and an implemented game. Source.
For readers exploring how game localisation works, this is a useful starting distinction. A question about an awkward sentence may belong to translation or editing; a missing character may concern font support; a misplaced interface element may require implementation work. These are different questions within the same production. Forbes’ interview documents one professional perspective from 2022, rather than a universal staffing model. It illustrates why coordination matters when a language change reaches several departments. Source.
Follow the issue
- Identify the affected text, sound or interface.

2. Give translators the context behind a line
A localisation brief explains the situation
A translator needs to know what a line is doing. Jennifer O’Donnell’s 2021 IGDA guide recommends reference material, a localisation kit, style guidance, comments and a channel for questions. Character descriptions, story information and explanations of game systems help make a text file understandable. Context can include who is speaking, whom they address, the intended emotion and where the words appear. These details give a language specialist a basis for making choices rather than guessing from an isolated string. Source.
Consider an invented instruction such as “Hold.” Without context, it might describe keeping a button pressed, waiting in place or defending a location. This is an editorial example, not a translation taken from a shipped game. A useful brief would explain the action and the interface constraint before requesting a target-language version. The same principle applies to names and repeated expressions: apparent repetition in a spreadsheet does not establish that every occurrence serves the same purpose. Source.
Useful context
- Record the speaker, action and screen location.

3. Separate understanding, translation and editing
Natural dialogue can involve several roles
Nintendo’s historical Iwata Asks discussion of The Legend of Zelda: Twilight Princess describes overseas localisation teams working with the developers in Japan. The account distinguishes people interpreting nuances in the Japanese text, people converting it into English and others refining the English so it sounded natural. It should not be read as a statement about every Nintendo project or its current staffing. Source.
The distinction is useful when discussing whether a line is accurate or enjoyable to read. Understanding an intended meaning and expressing it naturally are connected decisions, but they are not identical tasks. A reader can ask which meaning, character relationship or story purpose a wording is meant to preserve before judging it solely by word order. Nintendo’s account supports that collaborative view. It does not give outside readers access to every draft, editorial discussion or rejected alternative behind the finished game. Source.
Read the credit carefully
- Distinguish translation from subsequent editing.


4. Make language assets work in the engine
Fonts and audio need implementation choices
Epic’s Unreal Engine asset-localisation documentation explains that a project can replace assets for a particular culture. Its font guidance distinguishes a composite font covering cultures from separate font assets for individual cultures. The documentation also discusses language-specific audio and circumstances in which changing culture can require a restart to reload assets. These are engine-specific implementation details, not a promise that every game exposes the same language menu or switches all content immediately while it runs. Source.
The game may also need a different font or audio asset. For a production team, the corresponding question is which assets follow the selected culture and which settings can be chosen separately. Epic documents an example of assigning audio a different culture from other content. Whether a particular released game offers that option must still be checked in that game’s own documentation. Source.
Check the actual game
- Do not infer its settings from engine capabilities.

5. Test layout assumptions before translation is final
Pseudo-localisation serves a different purpose
Unity’s localisation package overview for Editor 6000.0 describes locale-based strings and assets, together with pseudo-localisation for checking how a project adapts before translations are added. It also lists Smart Strings for logic involving placeholders and plurals, and import or export through formats including XLIFF and CSV. The cited overview identifies package 1.5.14 for that editor version; it does not describe every Unity release. Source.
Pseudo-localisation should therefore be understood as an early development check, rather than evidence that a language has been translated or reviewed. A team can use that stage to question assumptions about how localised content will fit before treating final wording as settled. The useful distinction is between a tool that helps arrange and exercise content and the editorial judgement needed to decide whether the resulting language communicates correctly. Source.
Keep the stages distinct
- A technical check does not certify a translation.

6. Rebuild a character’s performance in another language
Localised voice acting has its own production
Riot’s November 2023 account of Hwei’s voice describes work across narrative, audio and voice production. Character materials informed casting and performance, while scripts passed through development stages before final recording. The article then explains that localisation teams undertook their own casting, script translation, recording and post-processing, with contextual notes from the originating team. This is a named character’s production history, rather than a standard schedule or a guarantee about how another studio records dialogue. Source.
That example makes a useful distinction between translating a script and producing a localised performance. A written line carries meaning, but a recorded delivery also expresses mood, energy and character. The regional production has decisions to make after receiving the source material. When comparing language versions, readers can recognise that additional creative work without assuming the actors copied one another’s delivery. This guide has not auditioned performers, listened to unreleased sessions or independently reviewed the final recordings; the workflow description comes from Riot’s published account. Source.
Follow the full workflow
- Include casting, recording and post-processing.


7. Check the words in the running game
Linguistic QA tests implementation and context
O’Donnell’s May 2023 IGDA guide distinguishes localisation quality assurance from translation, editing and proofreading. Testers examine implemented language in context, looking at such matters as meaning, consistency and presentation. The described workflow includes reports, corrections, implementation and another check of the revised build. This matters because a sentence that looks acceptable in a document can acquire a different meaning when a player sees the speaker, the action or the surrounding interface. Source.
A useful way to understand the testing loop is to follow one reported issue through to the version containing its fix. Reporting an error and verifying its correction are separate events. The guide also warns that changes to source text need to reach other languages and be checked again. Its process is not simply a fluent speaker playing casually until the credits. Clear coverage, ways to locate strings and communication between testers and the language team all help explain what the work actually involves. Source.
Track the correction
- Check the revised build, not only the report.

8. Bring regional perspectives into creative decisions
Cultural context belongs in the discussion
Riot’s February 2023 profile of Kat Wong describes localisation extending beyond exchanging words between languages. In its professional-process passages, the company discusses cultural resonance and sensitivity, and the value of involving localisation specialists and regional perspectives earlier in decisions. The article also describes internal groups contributing knowledge about character design. Those passages document Riot’s stated approach at that time; they are not an independent audit of its workplace or a rule followed by all game developers. Source.
For readers, the useful question is which creative issue a regional perspective is helping to clarify. A name, reference or character detail may need discussion before anyone settles on final wording. Asking that question is more precise than assuming every difference between versions has the same explanation. The published profile supports early consultation as a working approach, but it cannot establish the reason for an unrelated game’s change. Such a claim would need evidence about the specific decision and the people responsible for it. Source.
Ask for specific evidence
- Do not invent a reason for a changed line.

9. Read language support one category at a time
Store text and in-game support are different
Steamworks separates store-page localisation from support inside the game. Its documentation also distinguishes interface text, subtitles and full audio for each language. A translated shop description therefore does not, by itself, tell a buyer what language options the game contains. Read the relevant in-game categories before purchase, especially when spoken dialogue is important to the experience. This is a guide to interpreting Steam’s distinctions; other storefronts should be checked against their own labels. Source.
A careful check begins with the language you want, followed by the kinds of support you need. Someone comfortable with original-language voices may mainly need translated subtitles and interface text. Another player may specifically want localised audio. Those preferences lead to different questions even when both people ask whether a game supports the same language. Use the categories as a checklist, then consult the developer’s support information if the available description leaves an important detail unclear. Source.
Read each column
| Category | Check |
|---|---|
| Store page | Shop description |
| Interface | In-game text |
| Subtitles | Dialogue text |
| Full audio | Spoken language |

10. Keep localisation connected to the game’s life cycle
Language work can meet accessibility design
Massive’s account of localisation on The Division 2 describes its localisation team being involved from pre-production through the live phase. The article also discusses subtitle features, including descriptions of sounds, adjustable text size and indicators distinguishing speakers. This historical example connects language work with the way information is presented to players. It does not establish that every later game has the same features, or that one studio’s approach is a complete accessibility standard. Source.
The practical lesson is to examine language support alongside the options that make that language readable and useful. A subtitle language and a subtitle presentation setting answer different questions. When reviewing a game’s official information, look for both rather than assuming one guarantees the other. Massive’s account is also a reminder to identify the particular game and published feature description. A production story explains decisions in that project; it should not become an unsupported claim about every update, sequel or game made with the same engine. Source.
Check the named product
- Verify language and presentation options separately.


FAQ
What does LQA stand for?
Localisation quality assurance covers checks of localised content. Keywords describes linguistic testing alongside localised voice audio and presentation checks. Source.
Can a game have different audio and text languages?
Some can. Epic documents separate culture settings for audio assets, but the available choices depend on the individual game. Source.
Does pseudo-localisation mean a translation is ready?
No. Unity describes it as an early way to test adaptation before translations are added. Source.
Are translation and editing the same task?
They can involve different roles. Nintendo’s Twilight Princess development account distinguishes interpreting the source, translating it and refining the resulting English. Source.

Sources
- Keywords Studios LQA
- Ubisoft: Myriam Forbes, 2022
- IGDA: Localisation context, 2021
- Nintendo: Twilight Princess development
- Epic: Asset localisation
- Unity 6000.0: Localisation
- Riot: Hwei voice production, 2023
- IGDA: LQA workflow, 2023
- Riot: Regional perspectives, 2023
- Steamworks: Languages and localisation
- Massive: Localisation and subtitles
Related reading

How Game Age Ratings Work: ESRB, PEGI and Online Features
Related guide. Thumbnail is an AI-generated representative illustration.

Cross-Play vs Cross-Save: What Carries Across Gaming Platforms?
Related guide. Thumbnail is an AI-generated representative illustration.
PART 19 / 19 · GLOBECURRENT
Gaming & Digital Culture Editor
Game updates, official reward sources, digital communities and player safety.




