How to localize a product demo video without confusing the workflow

Choose one audience and one workflow for the first version. Check the language available in their product account, the feature they can access, and the page they'll reach after watching. A translated invitation to use a feature is confusing if the next screen sends them somewhere else.

For this guide, imagine a fictional appointment tool with a demo showing how to move a booking to a different time. Suppose the product interface is available only in English, while the audience needs the explanation in another language. That constraint should shape the video: explain the action in the audience's language while making the actual English control recognizable.

The appointment tool is a hypothetical example, not a customer case study or a translated video we've produced. Use your own verified product behavior to decide what stays on screen. If a localized interface really is available, capture that version instead of inventing translated labels in an image.

Translated subtitles let you keep the existing narration while giving the audience text in another language. Consider this route when preserving the original speaker matters or the demonstration leaves enough room to read. Try one scene with both the interface and proposed subtitles visible before committing to the whole video.

In the appointment example, someone may need to compare two time slots while reading the explanation. If those details disappear before they can do both, give the scene more time or simplify the explanation. Making the subtitle text smaller only moves the problem into readability.

Be precise about what you're commissioning. W3C distinguishes translated subtitles from captions, which include speech and meaningful non-speech audio for people who can't hear it. Terminology varies by region, so tell your provider what information the text should contain rather than assuming the word 'subtitles' covers everything you need.

W3C: captions and translated subtitles

Plan caption text, timing and placement

A translated voiceover can let viewers concentrate on the product interaction instead of following a separate text explanation. It still needs to line up with the action: when the narration says to choose another time, the relevant control should be visible long enough to understand.

Try a short section containing a product term and a complete action, rather than judging the voice from a greeting. Ask a fluent reviewer to check the meaning and pronunciation, then watch that section against the screen. Don't assume a natural-sounding voice proves the translation is accurate.

If a presenter is visible, decide whether matching their mouth movement is part of the deliverable. That's a different requirement from replacing off-screen narration. For either approach, ask how you'll correct the script and timing before final export. HeyGen's primary documentation, for example, describes reviewing and editing the translated script before generating the final video. Check access to the needed controls in whichever workflow you choose.

HeyGen: video translation and script review

Brief pronunciation and narration corrections

For the fictional appointment tool, suppose the button says 'Reschedule' and the final state says 'Confirmed.' The explanation needs to help viewers recognize those labels. It also needs to preserve the difference between requesting a change and successfully confirming it.

Create a small terminology sheet before generating multiple versions. Record the exact interface label, what it means in this workflow, whether it stays unchanged on screen, and the approved wording for narration and subtitles. Leave translated wording blank until someone qualified has reviewed it; guessing a translation here would defeat the point.

Also check the example data. A changed time format can make an appointment ambiguous, and a different time zone can change the appointment itself. Decide what the example is meant to represent and keep the screen, narration and captions consistent. Don't casually replace dates or numbers just to make the scene look localized.

Here's an example worksheet for the fictional booking change. It deliberately contains no proposed foreign-language wording. The useful work is agreeing on the meaning and the product state before asking someone to approve a translation.

Audience and target language:
Product interface language available to that audience:
Source video version:

Scene: Move an existing appointment.
Visible control: Reschedule.
Meaning to preserve: Choose a different appointment time.
Visible result: Confirmed, only after the change succeeds.
Wording that would be wrong: Cancel the appointment.

Approved spoken wording:
Approved subtitle wording:
Interface labels that remain unchanged:
Dates, times and time zone checked:

Language reviewer:
Product reviewer:
Timing or layout changes required:
Final file reviewed and approval date:

Have the language reviewer check meaning and natural wording, and the product reviewer check the behavior being described. Those responsibilities can belong to the same person if they know both. The important thing is that someone owns each check instead of everyone assuming another person handled it.

Watch the final file with the approved text beside it. Check that the spoken instruction, subtitle and product state agree throughout the scene. Look for captions covering a control or a translated line continuing after the video has moved to another step. A correct script can still become a confusing finished sequence.

Keep the source version and the approved terminology with each language version. When a button changes name, you can identify which screens, spoken lines and subtitles need review. Otherwise, you risk updating the original demo while leaving another audience with instructions for the old product.

Start with a version your team can review properly before expanding to more languages. The practical limit isn't just how many files a tool can generate; it's whether you can confidently publish and maintain the explanation each audience receives.