Set a direct translation
Pair a source term or phrase with the wording your team wants in the target language. Make the decision once and keep it easy to find.
Set the wording that must stay predictable. A Vitra TMS glossary holds direct source-to-target translations and do-not-translate rules, so product names, recurring phrases, and approved labels do not change from one asset to the next.
Free to start · 120 languages · No credit card required
Capabilities
Pair a source term or phrase with the wording your team wants in the target language. Make the decision once and keep it easy to find.
Use do-not-translate rules for product names, identifiers, and branded phrases. A familiar name should not become a new name in the next market.
Bring glossary lists through supported CSV and Excel imports. Check language columns and special characters with a small sample first.
Organize glossaries by the product or client they belong to, then attach the right list to the relevant memory.
Give translators and reviewers the same wording list. Resolve disagreements against an explicit rule instead of an old email.
Export glossary entries as CSV or Excel when another team needs the approved language list.
What changes for your team
Start with the jobs your team already needs to finish.
Product and brand names
Preserve the names customers recognize across campaign copy, packaging designs, videos, and help content.
Interface labels
Keep repeated navigation and action labels consistent across the website, app, and onboarding material.
Recurring approved phrases
Give important labels and short phrases a predictable treatment, with specialist review where needed.
Confirm the wording in context, including the visual, subtitle, interface, or document where it appears.
Start with names, labels, recurring phrases, and words reviewers repeatedly correct.
Set a direct translation
Pair a source term or phrase with the wording your team wants in the target language. Make the decision once and keep it easy to find.
Protect names that should not change
Use do-not-translate rules for product names, identifiers, and branded phrases. A familiar name should not become a new name in the next market.
Import a working spreadsheet
Bring glossary lists through supported CSV and Excel imports. Check language columns and special characters with a small sample first.
How it works
Keep the brief, language resources, and review decisions connected. Use the finished result in Universe or export it for the next step.
Start with names, labels, recurring phrases, and words reviewers repeatedly correct.
Add a target translation or mark the source wording as do not translate.
Attach the glossary to the translation memory for that product, client, or language workflow.
Confirm the wording in context, including the visual, subtitle, interface, or document where it appears.
Who it is for
Preserve the names customers recognize across campaign copy, packaging designs, videos, and help content.
Keep repeated navigation and action labels consistent across the website, app, and onboarding material.
Give important labels and short phrases a predictable treatment, with specialist review where needed.
FAQ
A translation glossary lists source words or phrases and their approved target wording. It can also mark names that should not be translated. In Vitra TMS, glossaries connect to translation resources alongside memory, terminology, and style guides.
Use Vitra TB when you need concept definitions, several terms or synonyms per language, and terminology approval. Use a glossary when the job is a direct wording rule or a do-not-translate instruction.
Yes. Vitra TMS supports CSV and Excel glossary imports and exports. Verify the language mapping and sample entries before a large import.
Everything in Vitra Universe shares one translation memory, one brand kit, and one quality bar — so the work you do here makes everything you do next faster.