What Is a Translation Glossary and Why Does Your Product Need One?

When you translate an app or website without a glossary, you get inconsistency. The English word "checkout" might become three different French words depending on when it was translated and by whom. Your product name might be transliterated differently across different pages. Feature names that should stay in English get translated into confusing local approximations.

A translation glossary is the solution: a curated list of terms and their approved translations that all translators — human and AI — must follow.

What Is a Translation Glossary?

A translation glossary is a reference document that defines how specific terms should be translated in your product. It maps source terms to their approved target translations, optionally with context notes explaining when and why to use each translation.

A glossary entry looks like:

• Source term: Workspace
• Target (French): Espace de travail
• Note: Always use this term, never "environnement" or "projet".

Multiply this across 50–200 key terms and every language your product supports, and you have a comprehensive terminology database that ensures consistency across all your content.

Why Inconsistent Terminology Is a Real Problem

User Confusion

If your app's navigation says "Sign In" in one place and "Log In" in another (and their translations are different too), users who encounter both versions don't know if they're the same action. This is especially confusing for new users trying to understand your product's structure.

Support Burden

Inconsistent terminology generates support tickets. Users describe what they see on screen, but if your support team is looking at a different translation of the same element, they can't identify what the user is referring to. A unified glossary means everyone — users, support, and the product itself — speaks the same language.

Brand Degradation

Product names, feature names, and marketing copy that are inconsistently translated feel unpolished and unprofessional. It signals to international users that the localized version is an afterthought, not a first-class product experience.

What Goes in a Translation Glossary

Not every word needs to be in a glossary. Focus on terms where consistency is critical:

• Product and feature names — Should they be translated or kept in English? If translated, what's the approved form?
• UI actions — Submit, Cancel, Save, Confirm, Continue, Sign In, Sign Out.
• Technical terms specific to your domain — These often have multiple possible translations; your glossary picks one.
• Terms with ambiguous translations — Words that could be translated multiple ways depending on context.
• Terms that should NOT be translated — Brand names, proper nouns, specific API terms that should remain in English.

Using a Glossary with AI Translation

One of the key advantages of AI translation over traditional MT (machine translation) is that you can inject glossary constraints into the translation prompt. The model is instructed to use specific translations for glossary terms, and it respects those constraints throughout the output.

This means your AI translations are consistent from the first run — without requiring post-processing or find-and-replace passes to fix terminology.

Building and Managing Your Glossary

Building a glossary is an iterative process. Start with your most important terms — UI actions, feature names, brand terms — and expand over time as you encounter new translation decisions.

Glossary management tools let you:

• Create glossaries for specific language pairs (English → French, English → Japanese)
• Add, edit, and delete terms individually
• Import existing terminology from CSV or JSON
• Export to share with human translators
• Enable/disable specific glossaries per project

Manage Your Translation Glossaries in Glot

Glot's Glossary Manager lets you create and manage terminology databases per language pair. Once you've built a glossary, you can attach it to any AI translation — single key, batch file, or document — and all translations will respect your approved terminology.

You can import existing terminology from CSV or JSON, and export your glossary to share with your human translation team. Up to 20 glossaries per account, 500 entries per glossary.

A glossary is a one-time investment that pays dividends across every future translation. The earlier you build it in your localization workflow, the more consistent your product will be across all languages from the start.