Why did correcting my ElevenLabs pronunciation dictionary not change the existing product voiceover?

Trace the rule to the project and the recording

Start by recording whether the project is in Studio or Audiobooks, the selected speech model, and the exact term to correct. Keep the approved written product name and spoken form separate; a pronunciation fix does not authorize a different product claim.

In Studio, open the Pronunciations Editor, select the intended existing dictionary and choose Connect. Adding a rule to an existing dictionary through the documented editor flow also connects it automatically. Within a dictionary, matching proceeds from start to end and uses the first replacement; inspect the actual matching entry rather than inventing a priority across dictionaries.

Audiobooks documentation explicitly says dictionary edits apply only to newly generated audio and require paragraph regeneration to hear the update. Keep that product-specific statement separate from Studio's connection instructions; an editor displaying a corrected rule is not evidence that an existing recording changed.

1. Record the project, dictionary name/version or revision note, term, approved output and affected paragraph identifiers.
2. Confirm the dictionary connection and matching entry in the actual product. Check other shared uses before changing a shared brand rule.
3. Use the actual paragraph generation controls and inspect the displayed eligibility or credit information; do not assume the rule edit grants free regeneration.
4. Listen to the new take in its full sentence, compare it with the approved reading, and record the take identifier or generation time and any unresolved issue.

Use the Studio Pronunciations Editor instructions for the documented rule-creation and connection behavior.

The new-audio-only and paragraph-regeneration statement appears in Audiobooks pronunciation-dictionary guidance; check the product you are actually using.

After producing a new take, check product names and units in the actual narration before approving it.

Illustrative exercise A: one reading across a product family

A fictional merchant uses the same family name in several campaign paragraphs. Its owner has approved one reading. Before revising a shared dictionary, identify who maintains it and which other projects may rely on the entry. Do not silently turn a local correction into a shared brand change.

Confirm the intended dictionary and active entry order in the current project. Generate the affected paragraphs only after checking the actual button and eligibility information; a rule edit is not a promise of free regeneration.

Review the resulting name inside each sentence, including its transition into model numbers. A convincing isolated replacement is not enough if the full sentence becomes ambiguous. Record the accepted new take rather than labeling the old recording corrected merely because the editor now displays the desired rule.

Illustrative exercise B: isolate a campaign exception

Fictional campaign exception: an abbreviation needs a special spoken expansion while the shared brand reading must remain unchanged. Prepare a separate campaign dictionary, deliberately connect it to the intended project, and inspect matching entries before generation.

A separate dictionary is not an automatic priority override, paragraph-level control or cloning feature. Record the exception's owner and project, resolve incompatible readings, then review a newly generated take. This branch was not executed.

Distinguish pronunciation controls from voice labels

A pronunciation alias supplies a spoken replacement; the voice Alias setting labels a voice within the project. Renaming that label does not repair a product reading. Studio help identifies Flash v2 for phoneme tags: check the selected Studio model and available rule type rather than transferring broader API assumptions.

Compare the accepted recording with the approved script and captions. Record which dictionary and take produced the result, then recheck timing if the reading changed. Neither a connected dictionary nor a written phonetic form replaces listening.

These illustrative branches were not executed. No Studio account operation, speech generation, paid generation, export or actual file listening occurred, and no Itemlume integration is claimed.

Pronunciation change and new-take record — complete with actual observations

Save a copy of this record and enter actual inputs, actions and observations. Keep incomplete checks pending; do not prefill success.

Download review worksheet (CSV)