Game Localization · Glossary
What is Localization QA (LQA)?
Localization QA (LQA) is the quality assurance process applied specifically to localized game content — verifying that translated text displays correctly in-game, fits UI constraints, reads naturally in the target language, and is free of encoding errors, truncation, and cultural inconsistencies.
What LQA Tests
Localization QA covers two distinct types of issues: linguistic issues (mistranslations, inconsistent terminology, awkward phrasing, missing strings) and functional/display issues (text truncation, UI overflow, font rendering errors, encoding problems, incorrect character sets, broken special characters). Both require in-context review — checking the localized text as it actually appears in the game, not just in a spreadsheet.
Why In-Context LQA Is Essential
A translation can be linguistically accurate but functionally broken. A German tooltip that translates perfectly may overflow its button container by 12 characters. A Japanese string may render as garbled characters if the font doesn’t include the full Unicode CJK range. Arabic text may flow incorrectly if RTL rendering isn’t properly implemented. These issues only appear in-context — in the actual game build.
LQA vs. General QA
General QA (gameplay testing, bug finding) is distinct from LQA. LQA testers are linguists and localization specialists, not gameplay testers. They review specifically for localization-related issues: is the translation accurate? Does it display correctly? Does it maintain the intended tone? Is terminology consistent with the style guide? General QA catches gameplay bugs; LQA catches localization bugs.
The Cost of Skipping LQA
Games released without proper LQA routinely launch with visible display errors, broken characters, or mistranslated critical UI elements. In markets like Japan and Germany, players are highly critical of localization quality — negative reviews citing poor translation spread quickly in community forums. The cost of post-launch localization fixes (patching, community management, rating damage) far exceeds the cost of pre-launch LQA.
SandVox and Localization QA (LQA)
SandVox’s LocQA service covers both linguistic and functional review — checking translated content in-context for display errors, encoding issues, truncation, and linguistic quality. LocQA is included as standard in all SandVox localization projects and is also available as a standalone service for teams that handle their own translation.
Related terms: Game Localization · Linguistic Testing · Functional Testing Localization · Pseudo Localization
Frequently Asked Questions
What is the difference between LQA and general game QA?
General QA tests gameplay mechanics, bugs, and performance. LQA tests localization specifically — translation accuracy, terminology consistency, display rendering, encoding, and cultural fit. Both are necessary; neither substitutes for the other.
Do I need LQA if I use professional translators?
Yes. Even high-quality translation can produce display issues that are invisible outside the game context — truncation, overflow, encoding errors, RTL rendering problems. LQA is the step that catches what translation review misses.
Can LQA be done without a playable build?
Partial LQA (linguistic review in a spreadsheet or CAT tool) is possible without a build, but functional LQA — checking display, truncation, encoding, and rendering — requires an actual game build or screenshot-based review at minimum.
What does SandVox’s LocQA service cover?
SandVox LocQA covers: linguistic accuracy review, terminology consistency check, display rendering verification (truncation, overflow, font), encoding validation, and cultural fit review. We provide an annotated issue report with severity ratings and suggested fixes.
Need Expert Game Localization?
SandVox provides end-to-end game localization including localization qa (lqa) — for narrative games, mobile titles, webtoons, and interactive fiction.