Game Localization · All Services
Localization QA — What Is LocQA & Why Your Game Needs It
Native translators. Translation Memory. In-build LocQA. Get a free quote →
Localization QA (LocQA or LQA) is the process of testing a localized game build to find and fix issues that only appear when translated text is displayed inside the running game. Translation review verifies that text is translated correctly. Localization QA verifies that the translated game works correctly — that text fits in UI elements, renders in the correct font, displays without overflow or truncation, and that all translatable content is actually translated. A game that has been translated but not LocQA’d will ship with issues that damage the player experience and your reviews in localized markets.
What LocQA Tests
Localization QA tests a running game build for issues including: text overflow (translated text that is too long for its UI container, overflowing the visible area or cutting off); text truncation (text cut by the game engine with ellipsis or hard cut); missing translations (strings that appear in the source language in the localized build — untranslated strings in UI or dialogue); font rendering failures (characters that display as boxes, squares, or incorrect glyphs because the required font is not loaded or the font does not contain the required Unicode range); layout breaks (UI elements that break when translated text is longer or shorter than source text, causing elements to overlap or misalign); and functional failures (text that should trigger a gameplay event or function correctly but fails when the string is in a different language or encoding).
In-Engine LocQA vs. File-Level Translation Review
File-level translation review (checking exported string files for translation accuracy) and in-engine LocQA are both necessary but test different things. File-level review catches: mistranslations, inconsistent terminology, incorrect grammar, and missing translations. In-engine LocQA catches: text overflow and truncation that only appear in rendered UI, font rendering failures for CJK and special characters, UI layout breaks caused by text length differences, and untranslated strings that appear as source language in the game UI despite appearing translated in the string files. Many significant localization issues are invisible at the file level — they only appear when the game renders.
When LocQA Should Happen
LocQA should happen on the near-final build of your game, after translation is complete and integrated, before submission to platform stores. Earlier LocQA passes on milestone builds help catch systemic issues (like a font that doesn’t support a required character range) before they are expensive to fix. A typical timeline: string export and translation during final development; integration of translated strings into build; LocQA pass on integrated build; bug fixing and re-testing; final build submission. LocQA before platform submission is particularly important for console platforms (Nintendo Switch, PlayStation, Xbox), which have certification requirements around localization and language support that reviewers test.
Console Certification LocQA
Console platform certification — the process of getting a game approved by Nintendo, Sony, or Microsoft for sale on their platforms — includes language and localization testing requirements. Nintendo’s Lotcheck process, PlayStation’s Technical Requirements Checklist (TRC), and Xbox’s Title Requirements all include requirements around language support, text rendering, and localization consistency. A game that fails certification for localization issues must fix the issues and resubmit, extending the time to release and adding cost. SandVox’s console certification LocQA service tests against platform certification requirements before submission, reducing the risk of certification failure.
Frequently Asked Questions
What is the difference between LocQA and functional QA?
Functional QA tests whether a game works correctly — mechanics function, bugs are absent, the game runs without crashes. Localization QA tests whether the localized version of the game works correctly specifically because of localization — text renders correctly, UI doesn’t break from text length changes, all content is translated. Both are necessary for a shipped game. Functional QA finds gameplay bugs; LocQA finds localization-specific visual and functional issues.
How long does LocQA take?
LocQA duration depends on game size and complexity. A small indie game (5–10 hours of content, simple UI) can be LocQA’d in 2–5 days per language. A large RPG with complex UI, extensive dialogue, and multiple platforms may require 2–4 weeks of LocQA per language. Console certification LocQA adds time for testing against specific platform requirements and often requires a dedicated device for each target platform.
Can I do LocQA myself?
Yes, for simple games. Self-LocQA is practical if: the developer speaks the target language (or has a team member who does), the game has a small UI surface area, and the language pair does not involve CJK or RTL text. For games with complex UI, CJK languages, RTL languages, or console platform requirements, professional LocQA catches issues that non-native speakers and non-specialists reliably miss. The cost of a failed platform certification submission typically exceeds the cost of professional LocQA.
Start Your Localization QA Project
Tell us your word count, target languages, and platform. We return translated files ready for import — with Translation Memory and terminology glossary included. Free quote in one business day.