Game Localization · All Services
What Is Translation Memory? — TM for Game Localization Explained
Native translators. Translation Memory. In-build LocQA. Get a free quote →
Translation Memory (TM) is a database of previously translated string pairs — source text and its approved translation — that a localization system can search to automatically suggest or apply existing translations when the same or similar text appears in a new project. For game developers, Translation Memory is the mechanism that makes localization of patches, DLC, and updates significantly cheaper than initial localization: strings that already exist in the TM are translated instantly, only new and changed strings require fresh translation. Your Translation Memory is a valuable business asset — you should own it, and any localization provider you work with should deliver it to you at project completion.
How Translation Memory Works
When a translator completes a translation, the source string and its translation are stored in the Translation Memory as a ‘segment pair.’ When future translation is needed, the TM is searched for identical or similar source segments: 100% matches (identical source text) are applied automatically at zero marginal cost; fuzzy matches (similar but not identical source text, typically 75–99% similarity) are suggested to the translator as a starting point, reducing translation effort; and no-matches require full translation from scratch. In a typical game update or patch, a large percentage of strings are unchanged from the previous version — these are 100% TM matches and cost nothing to ‘translate.’ Only new content and changed content requires new work.
TM Savings on Game Updates
Translation Memory leverage is the primary mechanism for reducing localization cost over a game’s lifetime. Initial release: 100% of content is new, no TM available, full per-word cost for all content. Patch 1.1: UI and menu text unchanged (0% cost), reused dialogue unchanged (0% cost), new quest text (100% of cost). The effect compounds over time — a game’s TM accumulates across all updates, making each subsequent update cheaper than the last. For live-service games with frequent content updates, Translation Memory is essential cost management. Some studios report 40–60% TM leverage ratios on major DLC releases after a full game has been localized.
TM Ownership — What to Ask Your Localization Provider
Your Translation Memory is your property and represents significant value. When working with a localization provider, you should: request explicit TM ownership — the TM should be yours, not the provider’s; receive TM delivery at project completion in TMX format (Translation Memory eXchange — the open standard compatible with all major CAT tools); receive updated TM delivery after each project; and confirm that the TM will be accessible if you change providers. TMX is the standard exchange format — any professional CAT tool (memoQ, SDL Trados, Phrase TMS, Smartcat) can import TMX. Do not accept a provider who refuses to deliver your TM or treats it as their proprietary asset.
TM Quality and Maintenance
A Translation Memory is only valuable if it contains accurate, current translations. TM quality issues that reduce its value: outdated translations (if your game has undergone significant revision, older TM entries may reflect superseded content), inconsistent terminology (if different translators or providers have added entries using different terms for the same concept, the TM may have conflicting entries), and low-quality entries (if MT output or uncorrected translations were added to the TM, the suggested matches will be poor quality). Good TM maintenance practices: use a consistent CAT tool and provider for ongoing projects, periodically review and clean outdated TM entries, and maintain a separate project glossary that overrides TM suggestions for key terminology.
Frequently Asked Questions
What file format is a Translation Memory?
The standard format is TMX (Translation Memory eXchange), an XML-based open standard. TMX files contain source and target language text pairs with metadata (language pair, date, translator). TMX is supported by all major CAT tools — memoQ, SDL Trados, Phrase TMS, Smartcat, OmegaT, and others. You should receive your TM as a TMX file at project completion.
Does SandVox deliver Translation Memory to clients?
Yes. Every SandVox project builds Translation Memory in memoQ, and the complete TMX is delivered to the client at project completion. This TMX is yours to keep, import into other tools, and use with other providers if you change localization partners. We also maintain the TM between projects — if you return for an update or DLC, your existing TM is applied to reduce costs.
How much does TM leverage reduce localization cost?
It depends on how much of your new content matches existing TM entries. Typical scenarios: game patch with bug fixes and minor content adjustments — 60–80% TM leverage, cost is 20–40% of original rate. Major DLC with mostly new content — 20–40% TM leverage. Complete sequel using the same game setting and similar UI — 30–50% TM leverage. We provide a TM analysis with match percentages before quoting any update project, so you can see exactly what leverage is available.
Start Your What Is Translation Memory? 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.