HeyGen Brand Glossary: control pronunciation and translation terms before production

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Separate how a term sounds from how it translates

HeyGen's Brand Glossary can hold pronunciation rules and translation rules. A product name may need a specific spoken form while remaining unchanged in writing across languages. Another term may require an approved local translation. Record these as separate decisions so a pronunciation fix does not accidentally become a translation instruction.

Create a high-risk term list

Start with brand names, abbreviations, personal names, product tiers, technical phrases and legal wording. Add the source term, source language, target locale, approved written form, intended spoken form and an owner. Do not add every common word; focus on terms whose error would materially change meaning or brand identity.

Use a synthetic acceptance script

Prepare a short script that contains each term once in an ordinary sentence and once next to a potentially confusing word. Apply the glossary and generate only the smallest useful preview. Review pronunciation, on-screen text and translated wording with an approved speaker or reviewer for each target language.

1. Confirm the intended glossary is selected in the editor.
2. Check which pronunciation rules appear active in the script.
3. Verify forced translations and terms marked not to translate.
4. Correct the glossary, then regenerate the acceptance script.
5. Record the approved result before using the terms in a full project.

A worked terminology example

A fictional company named NomaQ sells a module called Flow 2. The company name must keep its spelling, while the spoken form needs guidance. “Flow 2” must remain unchanged in French and German. Add both rules, generate one test sentence per locale and have the reviewer sign off. This example illustrates the method and is not a product benchmark.

Control updates

HeyGen allows entries to be added in the editor and reflected in the selected glossary. Treat each addition as a shared change: capture who requested it, which languages it affects and whether older videos need review. Test the glossary again after a bulk CSV upload or a change to a high-risk term.