Create multilingual client videos from one approved source: choose subtitles or dubbing, lock terminology, run native review, add captions, and manage versions.
A client watching your onboarding video in their second language is doing extra work you never see. They're translating in their head, rewinding the part about billing, and quietly wondering whether they understood the setup instructions correctly. Most never tell you, and instead they take longer to get started or send the support ticket your video was supposed to prevent.
Multilingual client videos remove that hidden friction. The process that works is simpler than most teams expect: create one approved master video, decide how deeply each video needs to be adapted, protect your product terms and names, review every language version with a fluent speaker, and publish each one where the client will find it. The number of languages matters far less than the quality of each one.
This guide covers the difference between translation and localization, how to choose between subtitles and dubbing, which videos and languages to prioritize, a step-by-step production workflow, a QA checklist, accessibility requirements, and how to keep every version current when the source changes.
TL;DR: The most reliable way to create multilingual client videos is to start from one approved source video, choose the right level of adaptation for each asset (subtitles, audio dubbing, or lip-synced translation), lock your terminology, and have a native speaker review every version before it reaches clients. Produce the language versions in HeyGen, because one existing video can be translated, dubbed in the speaker's own cloned voice, lip-synced, and captioned without a reshoot.
- A professional dubbing agency still wins for high-stakes flagship content where every line needs voice-actor performance.
- Subtitles alone are enough for low-risk videos where viewers read comfortably and the original voice matters most.
- Re-filming with a bilingual presenter makes sense when a market needs its own examples, not only its own language.
Video Localization vs. Video Translation
Video translation converts spoken or written language from one language into another. Video localization goes further: it adapts the whole video for a target-language audience, which can include phrasing, examples, on-screen text, captions, audio, timing, and cultural references.
For client videos, the difference shows up in the details. A translated onboarding video might say "click the gear icon" correctly in Spanish, while a localized version also changes the screenshot showing English menu labels, adjusts the date format in the example invoice, and swaps an American sports metaphor for something that lands. Translation gets the words right, while localization gets the whole experience right.
Choose the Right Level of Adaptation for Each Video
Not every client video needs full dubbing. Match the level of adaptation to the video's purpose, risk, and viewing context.
A practical rule: if a person is talking to the camera and the client needs to trust them, lip-synced translation preserves the relationship best. If the screen is the star, such as a software walkthrough, audio dubbing or subtitles are usually enough.
Which Client Videos and Languages to Localize First
Localizing everything at once is the fastest way to create a library nobody maintains. Prioritize with three practical questions.
Which languages do your clients use? Check your CRM, support tickets, and account records for preferred languages rather than guessing from market-size charts. For many US companies serving diverse client bases, Spanish is the obvious first candidate, but your data may point elsewhere.
Which videos do clients watch at critical moments? Onboarding, setup, billing explanations, and renewal messages usually matter more than a brand story. Start where confusion costs the most.
How long will the video stay accurate? An evergreen welcome video justifies more localization effort than a feature demo that changes next quarter.
Start with two or three high-impact videos in one or two languages, review the results with real clients, then expand.
One Master Video, Many Languages
The traditional approach, a separate shoot or dubbing session for every language, turns each new language into a new production project. That's why most client video libraries stay English-only far longer than they should.
A more sustainable model is to localize one approved master. HeyGen's video localization workflow translates, dubs, subtitles, and synchronizes an existing video into multiple languages from a single source, and localized versions can be regenerated when the content changes. The platform handles the language production; deciding which languages to support, what counts as accurate, and who signs off remains your team's job.
What You Need Before You Start
Gather these items before translating anything. Each has a "good enough" bar so the project keeps moving.
- An approved source video and transcript: The final version, not a draft. If the transcript contains errors, every language inherits them.
- A terminology list: Product names, feature names, client-facing terms, and names that should never be translated. Twenty to forty entries covers most companies.
- A fluent reviewer per language: A bilingual employee, partner, or contractor who understands your product. One reviewer per language is enough to start.
- A list of on-screen text: Titles, labels, URLs, and screenshots that appear in the video and may need localized versions.
- A distribution plan: Where each language version will live, whether a client portal, help center, email sequence, or YouTube.
How to Create Multilingual Client Videos with HeyGen
With the source video and glossary ready, the first language version typically takes under an hour including review, and additional languages go faster.
Step 1: Lock the source script and terminology
Review the transcript line by line before translation, correcting names, numbers, and product terms. Flag idioms and metaphors that won't survive translation, such as "hit it out of the park," and replace them in the source if possible. Build your terminology list at the same time. This takes 20 to 30 minutes for a three-minute video and prevents the same error from appearing in every language.
Step 2: Start the translation and pick the right mode
From the HeyGen dashboard, click Create, then select Translate a Video, and upload the file or paste a YouTube or Google Drive link. Choose Hyperrealistic Translation when the speaker's face is clearly visible, since it includes lip-sync, or Audio Dubbing when the speaker is small, off-screen, or speed matters most. Both routes can use AI dubbing with voice cloning, so the translated audio keeps the presenter's own tone rather than a generic narrator.
Step 3: Configure glossary, pacing, and captions
Before clicking Translate, add your brand glossary so product names and key terms stay consistent across languages. Turn on dynamic duration so pacing sounds natural when a translation runs longer than the English, which is common with Spanish, German, and French. Enable captions, background noise removal, and voice enhancement as needed, and group the languages into a collection so every version of the same video stays together.
Step 4: Review every language with a fluent speaker
Translated videos appear in your library and on the Share page, ready for review. Have each reviewer watch the full video, not only read the script, checking terminology, tone, names, and timing. On Pro plans and above, reviewers can edit and proofread the translation script, then regenerate the corrected version. Enterprise plans add proofreader seats so reviewers can work without full editor access. Budget 15 to 30 minutes per language per video.
Step 5: Localize on-screen text and visuals
Translated audio with English-only graphics still feels half-finished. Update titles, labels, lower-thirds, and any callouts that viewers must read to follow along. For videos with a lot of embedded text, a guide on how to translate text in video covers the options for handling it. Screenshots of software interfaces may need to be re-captured in the target language if clients use a localized version of your product.
Step 6: Publish each version where clients will find it
Label each file with the source video, language, and version number, then publish it in the place that client already goes: the localized section of your help center, the onboarding email for that language, or an in-app language selector. Record which version of the source each translation came from, because you'll need that the next time the English video changes.
A QA Checklist for Translated Client Videos
Automation makes generating language versions fast. Review is what makes them trustworthy. Check each language version for the following:
- Names: Client, company, product, and presenter names pronounced and spelled correctly
- Terminology: Product and feature names consistent with your glossary
- Numbers and formats: Prices, currencies, dates, times, and units correct for the audience
- URLs and contact details: Working links and the right regional support contacts
- Legal and compliance language: Disclaimers and required wording reviewed by the appropriate team
- Tone: Formal or informal address matching how you speak to clients in that language
- Idioms: No literal translations of metaphors or jokes
- Timing and lip-sync: Speech aligned with visuals and mouth movement
- On-screen text: Graphics, labels, and screenshots localized or intentionally left in English
- Captions: Present, accurate, and matching the audio
- Call to action: The next step clear and pointing to a destination in the right language
Translated Subtitles Aren't the Same as Captions
This distinction trips up many teams. Translated subtitles help people who don't speak the video's language. Captions help people who can't hear the audio, and they include meaningful non-speech information, such as a speaker change or an alert sound, not only dialogue.
The W3C's guidance on captions and subtitles explains that captions are needed for accessibility, whereas subtitles in other languages are not directly an accessibility accommodation. Accessibility guidelines call for captions on prerecorded video with meaningful audio, so a Spanish subtitle track on an English video doesn't, by itself, make that video accessible.
The practical answer is to treat both as requirements. Every language version should carry accurate captions in that language, and your review checklist should confirm they include relevant non-speech sounds.
Publishing Localized Versions: One Video or Many
How you publish matters as much as how you translate. For client portals and help centers, a separate, clearly labeled video per language usually works best, with a language selector or a language-specific page. For onboarding emails, send each client a single link in their preferred language rather than a menu of options.
If you publish client education on YouTube, the platform's multi-language audio feature lets eligible creators upload dubbed audio tracks to a single video, and the player defaults to the viewer's preferred language. Translated titles and descriptions also help viewers find the video when they search in their own language. That keeps views and comments consolidated on one video, though access to the feature is currently limited to some creators.
Version Control When the Source Video Changes
Here is the problem most localization guides skip. The moment one English video becomes six language versions, every product update, pricing change, new disclaimer, or renamed feature creates six updates. Without a system, some languages quietly fall out of date, and clients in those languages receive old information.
Treat the source script as the single source of truth and give every asset a version identifier, such as "Onboarding v3.2 ES." Keep a simple tracker with four columns: source version, language, reviewer, and date approved. Define update triggers in advance, such as a pricing change or new required disclaimer, so the team knows when a re-translation is mandatory rather than optional.
Because localized versions can be regenerated from an updated source, the update itself is usually fast. The bottleneck becomes review, so schedule reviewer time whenever a source video changes rather than waiting for a client to notice.
Personalized Multilingual Client Messages
Not every multilingual client video is a library asset. Sometimes the job is sending the same approved message, such as a welcome, a renewal reminder, or a quarterly check-in, to dozens of clients, each in their own language and addressed by name.
A personalized video workflow lets you connect a spreadsheet or CRM, map fields like client name and company to variables in the script, and render every version in one batch. Combined with translated scripts, an account manager's welcome can reach each client in their preferred language without recording anything new. Keep the personalized fields simple and review the translated template once before batching, since every version inherits its wording.
Common Mistakes in Multilingual Client Videos
These mistakes show up across industries, whether the videos cover software setup, financial services, or healthcare onboarding.
Skipping native-language review
Automated translation can be fluent and still wrong about your product. A fluent reviewer catches mistranslated feature names, awkward formality, and phrases that sound machine-made. For regulated or technical content, a review of AI video platforms for regulated industries covers the review and retention questions worth asking before you scale. Never send a client-facing language version nobody on your side has watched.
Translating idioms literally
"Let's get the ball rolling" becomes nonsense in many languages. Remove idioms from the source script when possible, and flag any that remain for the reviewer.
Leaving on-screen text in English
Dubbed audio over English labels and titles forces viewers to switch between languages. Localize anything a viewer must read to follow the instructions.
Localizing without tracking versions
Six language versions with no tracker guarantees that some will go stale. Version identifiers and a simple spreadsheet prevent clients from receiving outdated instructions.
Other Ways to Create Multilingual Client Videos
Hire a professional dubbing agency
Agencies cast voice actors, translate scripts, record in studios, and mix the final audio.
Pros:
- Human voice performance with emotional nuance
- Professional translators and quality control built in
- Strong fit for flagship brand content
- Handles complex projects end to end
Cons:
- Every language requires a separate recording session, so updates to the source video become expensive and slow
- Turnaround is measured in weeks rather than hours
Use translated subtitles only
Keep the original audio and add subtitle tracks in each target language.
Pros:
- Lowest cost and effort per language
- Preserves the presenter's original voice exactly
- Easy to update by editing text files
- Works on nearly every video platform
Cons:
- Viewers must read while watching, which is hard during software walkthroughs or detailed instructions
- Feels less personal for relationship-driven client communication
Re-film with bilingual presenters
Record separate versions of the video with presenters fluent in each language.
Pros:
- Native delivery by a real speaker of the language
- Allows market-specific examples, visuals, and references
- No questions to answer about AI-generated audio
- Strong fit when a market needs its own version entirely
Cons:
- Requires finding and scheduling a presenter for every language, which rarely scales past two or three
- Every source update means multiple new shoots
How the methods compare
The AI route has trade-offs worth knowing: lip-synced translation draws from a monthly credit allowance that takes a billing cycle to learn, and every language version still needs a fluent human reviewer before it reaches clients.
The Bottom Line
Clients rarely complain that a video wasn't in their language. They simply understand less, trust a little less, and need more help than they should. Multilingual client videos close that gap, but only when each version sounds like it was made for the person watching, which comes down to terminology, review, and upkeep far more than the number of languages you support.
The hard part has never been deciding to localize. It's the recording sessions, the dubbing quotes, and the dread of redoing everything when the English version changes. Pick your most important client video and your clients' most common second language, localize it this week, and put it in front of a fluent reviewer. HeyGen's Free plan lets you test translation with up to three one-minute videos a month in 30+ languages.
Creator costs 24 billed annually) and unlocks 177+ languages and dialects with voice cloning, Pro starts at $49 a month and adds editing and proofreading of translation scripts, and Business runs $149 a month plus $20 per added seat for team workspaces and shared review. Compare plans on the HeyGen pricing page and give every client a video that speaks their language.
Frequently Asked Questions
What is video localization?
Video localization adapts a video for viewers who speak another language, going beyond translation to adjust phrasing, captions, audio, on-screen text, timing, and cultural references. For client videos, localization makes the experience feel natural in the viewer's language rather than like a translated copy of an English original.
Should client videos use subtitles or dubbing?
Use dubbing, ideally lip-synced, for presenter-led client videos where trust and clarity matter, such as onboarding or account messages. Use subtitles for low-risk videos or when the original voice matters most. For software walkthroughs, audio dubbing works well because viewers watch the screen, not the speaker.
Can AI translate client videos accurately?
AI can translate client videos quickly and fluently, but accuracy for your specific product, terminology, and tone still requires review. Use a brand glossary to protect key terms, then have a fluent speaker watch each version before publishing. Higher-risk content, such as legal or financial explanations, deserves more careful review.
How many languages should you localize client videos into?
Start with the one or two languages your clients use most, based on CRM data and support requests, not market-size assumptions. Localize your highest-impact videos first, such as onboarding and billing explanations, review results with real clients, then expand to additional languages once your review process works.
Are translated subtitles enough for accessibility?
No, translated subtitles alone aren't enough. Translated subtitles help viewers who don't speak the video's language, while captions serve viewers who can't hear the audio and include meaningful non-speech sounds. Accessibility guidelines call for captions on prerecorded video, so each language version should carry accurate captions in that language.
Can one video have multiple language audio tracks?
Yes, some platforms support multiple tracks. YouTube's multi-language audio feature lets eligible creators add dubbed audio tracks to a single video, and the player defaults to the viewer's preferred language. For client portals and emails, separate clearly labeled language versions are usually simpler for clients to find.
