Skip to main content

Translation Styles & Glossary

Learn how Translation Styles and your Glossary lock brand terms, do-not-translate words, and pronunciation per language pair for consistent dubs.

Every brand has words that need to stay consistent across languages — product names, slogans, technical terms, the way you address your audience. Dubly.AI's Translation Styles are how you lock those in. A Translation Style is a reusable bundle of rules for one source-to-target language pair, applied per language at dub creation time. This article explains how to set them up, what they can do, and how to use them to enforce brand guidelines across a series of videos.


Where to find Translation Styles

Open Translation Style from the sidebar.

Translation Style

Translation Styles live at the organization level. Every member of your organization sees the same list, and any style you create here is available to every dub in the organization. There's no per-project copy to keep in sync.


What a Translation Style contains

A Translation Style is a reusable bundle of rules for a specific source-to-target language pair — for example, English → German or English → Spanish (Latin American). Each style covers two kinds of rules:

Terminology rules — locking specific words and phrases:

  • Don't Translate — words the translator must leave as they are. Perfect for brand names, product names, trademarked terms, SKUs, URLs. You can add several at once, separated by commas.

  • Define Translations (your Glossary) — exact source-to-target translations. Use these when the default translation of a term is wrong or off-brand (e.g. always translate subscriber as Abonnent in German, not Abonnement).

  • Pronunciations — how tricky names or acronyms should be spoken (e.g. AWS ⇒ ay-double-yoo-ess, or Nike ⇒ Naikee). On the left, write the word as it appears in the translation; on the right, spell it the way it should sound in that language. Use the play button to test a spelling before you add it.

Characteristics — controlling how the translation sounds overall:

  • Writing style — Simple, Business, Academic or Casual. If you leave it empty, the translation follows the style of your original video.

  • Tone — the emotional register your brand wants on camera: Enthusiastic, Friendly, Confident or Diplomatic.

  • Formality — Informal or Formal. Matters for languages where it changes the grammar (e.g. German du vs. Sie, French tu vs. vous).

Plus:

  • Name — whatever name helps your team pick the right one later.

  • Source and target language — the pair this style applies to.


Creating a Translation Style

  1. Go to Translation Style in the sidebar.

  2. Click Add another translation style (or Add your first translation style if you don't have one yet).

  3. Enter a name and pick the source and target language — exactly the languages you'll dub with.

  4. Fill in only the tabs that matter for this pair — leave anything you don't need empty.

  5. Click Save. It becomes clickable once the name and both languages are set.

You can create as many styles as you need: one per market, one per product line, one per brand, or just one catch-all. To change a style later, click it in the list; to delete it, use the bin icon.


Importing and exporting entries

Instead of adding entries one by one, you can import them from a file. You can also export a style's lists to share them with your translators or use them in another organization. Import and Export are at the top of the Translation Style window, on the Translation Style page and when you add a style while creating a dub.

Export

Click Export and choose Excel (.xlsx), CSV (.csv) or Text (.txt). The file contains the three lists, Don't Translate, Define Translations and Pronunciations, exactly as they stand in the window, unsaved changes included. Writing style, tone, formality and the languages are not part of the file.

Import

  1. Click Import. The Import entries window shows how the file has to be structured for each format.

  2. Click Download template and choose a format. Excel (.xlsx) is recommended: the template has one sheet each for words you don't translate, fixed translations and pronunciations. Keep the header row and replace the example rows with your own entries.

  3. Click Choose file and select your file: .xlsx, .csv or .txt, up to 5 MB.

  4. Check the preview. It shows how many entries are new, already present, in conflict or skipped, and lists each skipped row with its row number and the reason.

  5. Click Apply to add the new entries to the lists in the window, then click Save. Nothing is stored until you save.

An import only adds entries. It never changes or removes the ones already in the style:

  • Duplicates — an entry that's already in the style, or further up in the file, is added only once.

  • Conflicts — if a source term already has a different translation or pronunciation, the existing entry stays and the row is not imported.

  • Skipped rows — rows that can't be used, for example with an empty field, an unchanged example row from the template or a value longer than 500 characters, are skipped and the preview says why. Long values are never shortened.

The file holds no language information. Entries go into the style you have open, so make sure its language pair matches.


Applying a style to a dub

When you create a new dub:

  1. Open the dub creation modal and choose your languages in Details.

  2. Switch to the Translation Styles tab.

    Translation Styles

  3. For each target language, check the selected Translation Style. If a style matches the dub's source and target language exactly, it's already selected (the oldest one, if several match).

    Target languages

  4. To use a different style, open the list: matching styles come first, all others follow under All styles. Clear the field to dub without a style.

  5. No style yet? Choose Add Custom Translation Style in the list to create one right there — the languages are filled in for you.

Styles apply per target language. The same English source can use one style for German and a different one for French in the same dub. The automatic match is exact: a style for Spanish (Latin American) isn't preselected for a dub into Spanish. Without a style, the translation follows the tone and style of your original video.

Using a Translation Style doesn't cost anything extra.


Enforcing brand guidelines across a series

If you publish a series of videos, you want every dub to sound like the same brand. Translation Styles are how you make that happen without hand-tuning every dub.

Recommended workflow:

  • First dub in a series — experiment to find the right tone, formality, and terminology.

  • Second dub onward — apply the same Translation Style for the same language pair. New translations come out matching the rules without per-segment tweaking.

  • As soon as a brand-specific term appears in two different translations — add it to the style's Define Translations or Don't Translate list. That's the cue to lock it in.

  • Before launching a multi-video campaign — configure once, then run all videos against the same style.

For a recurring series, this is the difference between hand-tuning every dub and getting consistent output without intervention.


What Translation Styles can't do

  • They don't override segment-level edits. When you edit a translation yourself, your wording is kept exactly as you typed it — only the pronunciations are applied to it.

  • They don't replace human review. For high-stakes content (legal, medical, regulatory), a native-speaker review is still the safety net.

  • They don't update existing dubs on their own. A dub keeps the style it was created with, and editing the style doesn't re-translate it. Lines that are voiced again pick up new pronunciations; lines that are translated again (after you edit their original text) pick up all updated rules. See Can I change the translation style on an already dubbed video?.


Who can edit styles

  • Owners, Admins and Members can view, create, edit and delete Translation Styles.

  • Reviewers don't see Translation Style in the sidebar.


Best practices

  • Start with Don't Translate. Brand names, product names, UI labels that must stay as they are — lock these first. It's the fastest win.

  • Add brand names to Pronunciations too. Don't Translate only keeps the spelling; a pronunciation entry controls how the word sounds.

  • Keep custom translations short and unambiguous. If a term needs a paragraph of context, it's a bad custom translation — split it into multiple entries or handle it in the transcript editor.

  • Add pronunciations for acronyms and proper nouns. The voice model usually guesses right but will struggle with novel or domain-specific names. A quick phonetic hint saves a re-record.

  • Audit quarterly. Pick one target language, spot-check a recent dub with a native reviewer, and update the style based on what you find.


Limits

  • Each individual entry (custom translation, pronunciation, don't-translate term) is capped at 500 characters.

  • Style names are capped at 255 characters.

  • No upper limit on how many styles or entries you can create.

  • In the window, Don't Translate accepts several words at once, separated by commas; custom translations and pronunciations are added one at a time. To add many entries at once, use Import (.xlsx, .csv or .txt, up to 5 MB).


Still need help?

If a term keeps being mistranslated even after you've added it, ask Dubby in the chat (bottom right) and include the style name, the source text, and the output you expected.

Did this answer your question?