# Should I subtitle or dub an existing customer testimonial? By Wideframe Editorial Use translated subtitles when preserving the original voice matters and the audience can comfortably read the text. Consider dubbing when spoken access in the target language is important and the customer has agreed to that use. Wideframe documents both caption and localization workflows, but the choice should start with the audience and the representation of the speaker. ## What you’ll take away - Choose the viewing experience before choosing the localization method. - Review meaning and product terminology with someone competent in the target language. - Plan titles and graphics separately from translated speech. ## Decide how the audience will watch A short clip viewed silently may be well served by translated captions. A longer explanation that competes with detailed product visuals may benefit from spoken translation, because reading and studying the screen at the same time can be difficult. In an illustrative sales use, a local team sends a customer story before a meeting. They need the prospect to understand the experience without a live presenter. Ask whether that audience expects subtitles, dubbed audio, or a clearly narrated translation. Do not assume one method is inherently more professional in every context. ## Preserve the customer's meaning and agreed representation A testimonial is someone's account of their experience. Translation should preserve the claim, its scope, and its tone. Confirm the intended localized use through the appropriate approval process, especially when the speaker's voice or mouth movement will be synthesized. Do not use localization to strengthen an endorsement or add a statement. Keep product names, numbers, and qualifications explicit in the translation brief. A fluent sentence that changes the claim is not a successful customer story. ## Use subtitles when the original performance matters Subtitles let viewers hear the customer's actual voice while reading the translated meaning. Choose readable timing and line breaks for the target language, which may occupy different space from the source. Review how the text interacts with identity graphics and product details. Wideframe's [caption recipe](https://try.wideframe.com/skills/captions/) is a useful starting point for caption delivery. Add the public recipe in a chat with the intended video and provide the reviewed target-language text and delivery needs. Do not assume a source-language caption file is already a verified translation. For the delivery pass, add and save [caption-this](https://try.wideframe.com/skills/caption-this/) in a blank Wideframe chat, then invoke it with the video and your reviewed language requirements. Explicitly request translation when needed—the recipe otherwise captions the spoken language—and choose the required SRT, Premiere track, or burned-in format. Its cue checks help with readable timing; they do not replace a target-language review of the customer's meaning. ## Use dubbing deliberately, not as a cosmetic default Wideframe's [lipsync-localize page](https://try.wideframe.com/skills/lipsync-localize/) describes a HeyGen-based translation and dubbing workflow, including suitability review. It also makes clear that speech localization does not translate on-screen text and that automated checks do not replace professional language review. Start with the approved source and one target language. Choose a representative passage to assess voice, meaning, and visual suitability before expanding to a full series. This is a practical production step, especially when the recording includes side profiles, overlapping speech, or expressive delivery. ## Translate the whole viewing experience Names, roles, headings, product labels, and supporting graphics may need separate attention. A dubbed answer beneath an untranslated claim card can remain confusing. Decide which terms should stay in the original language and which need an approved localized form. Keep the source project available so text changes can be made cleanly. If a graphic is baked into the only available video, allow for rebuilding or covering it appropriately. Do not promise a complete localized deliverable merely because the speech has changed languages. ## Have a target-language reviewer watch the final version Give the reviewer the intended meaning and relevant product vocabulary, not only a transcript. They should hear or read the final delivery with its imagery and timing. An accurate translation on paper can become hard to follow when squeezed into the original duration. Resolve awkward phrasing without changing the customer's claim. Keep any updated captions synchronized with the approved version. If the voice or visual result is unsuitable, choose subtitles or another clearly presented translation method rather than publishing a distracting imitation. ## Keep language versions maintainable Name each version by language and source revision, and retain the approved wording. When the original story changes, identify which localized versions need updates. Do not let an old translation remain attached to a new edit without review. For the next customer story, decide localization needs before final graphics are baked in. Reuse the terminology and delivery preferences that remain valid, while reviewing the new speaker and statement on their own merits. ## Try this request Help localize this approved customer story for [language and audience]. Compare a subtitle delivery with dubbing based on the viewing context, preserve the customer's meaning, and identify on-screen text that needs separate translation. Begin with one representative passage. ## Questions ### Does dubbing also translate titles and graphics? The documented Wideframe localization workflow handles speech; on-screen text needs separate attention. ### Can we rely only on an automatic transcript comparison? Use a competent target-language reviewer for meaning, terminology, tone, and the final viewing experience. ### Should every language version use the same method? Not necessarily. Audience expectations, available review, and the visual demands of the video may justify different choices. ## Sources - [Wideframe: lipsync-localize](https://try.wideframe.com/skills/lipsync-localize/) — consulted 2026-09-18 - [Wideframe: captions](https://try.wideframe.com/skills/captions/) — consulted 2026-09-18 - [Wideframe caption-this recipe](https://try.wideframe.com/skills/caption-this/) — consulted 2026-09-18 Published by Wideframe. Examples are not customer results or benchmarks. ## Choose the right language version for your audience Bring an approved customer story and one target language into Wideframe, then prepare the caption or localization workflow that fits its audience. [Start free trial](https://try.wideframe.com/onboarding?start=trial). Seven days; card required; $100/month afterward unless canceled. Apple Silicon Mac and Premiere Pro required. [Current terms](https://try.wideframe.com/pricing/).