A termbase is a structured collection of approved terms and their equivalents, definitions, usage notes, and forbidden variants, used to enforce consistent terminology across a translation project. In localization, it is a reference asset that translators, editors, and QA tools consult to align with client-specific or domain-specific language; a well-maintained termbase reduces ambiguity and supports terminology management throughout the content lifecycle.
Termbases are created and maintained during project preparation, often by terminologists or lead linguists using terminology extraction and client-approved term lists. They are loaded into CAT tools so translators see recognized terms while translating, and QA checks can flag unapproved variants or inconsistent term use across files; updates are controlled through workflows that prevent ad-hoc changes.
A common mistake is treating a termbase as a simple word list and adding entries without definitions, context, or forbidden variants. This leads to inconsistent application because translators cannot tell when a term applies; over-restrictive or outdated entries can also cause false QA flags and unnecessary rework across teams or vendors.
For creative and consumer content the failure mode is flatness, not inaccuracy — and flatness passes an accuracy check. Terms here also carry technical constraints (reading speed, character budgets) that are part of the brief.
Angel Translation locks terms like this into a project terminology base before expert review begins, so the same source term resolves to the same target term across every document in a submission — and stays consistent in the next revision. See the 8-step AI + expert workflow.
Send us the files. Acknowledged in 4 hours, quoted in 24.
Request a Quote →Content Globalization solutions →