Localizing product demos: translated narration over an untranslated interface

The core problem: translated voice, original interface

A SaaS demo is mostly a screen recording with a voice explaining it. Translating the voice is straightforward; the interface is another matter. Unless you record a new demo in a localized build of your product, the viewer hears Japanese while watching menus, buttons and sample data in English. That mismatch is fine for some audiences and confusing for others, and the right approach depends on whether your product itself is localized.

Product UI is localized

The viewer's own app shows translated labels, so a demo with English screens does not match what they see. Re-recording in the localized UI is worth it for key demos.

Product UI is English only

Viewers will use the English interface anyway, so narration in their language that names the English labels is often more useful than a fully localized demo.

Partly localized UI

Some screens are translated and some are not. The narration should follow whatever the viewer will actually see in the product.

How the narration should name interface elements

The most common failure in a translated demo is narration that translates button labels the viewer cannot find on screen. If the button says Export report, a translator naturally renders it into the target language, and the viewer then hunts for a label that does not exist.

Pick a convention per language and record it in the glossary:

• Keep UI labels in the source language inside the translated sentence when the product is not localized. A German narration might say "Klicken Sie auf Export report" with the label unchanged.
• Use the localized label exactly as it appears in the product when the product is localized.
• Describe the element instead of naming it when labels change often: the blue button at the top right.

Machine translation will not apply these conventions by itself. Review the translated transcript specifically for UI terms, and help future recordings by saying labels clearly and exactly in the source script.

Callouts, zooms and on-screen text

Demos lean on callouts: arrows, highlight boxes, step numbers and short captions such as "Step 2: Connect your data". These are part of the picture, so they stay in the source language when only the audio is translated. Options, from cheapest to most expensive:

1. Leave them, and make sure the narration says everything the callout says.
2. Keep callouts visual only (arrows, highlights and numbers without words) in future recordings.
3. Re-export the callout layer from your editing project in each language.
4. Re-record the demo in a localized build of the product.

Option 2 is the cheapest long-term fix, and it costs nothing in the original language.

Recording demos that localize well

If demos will be localized, a few habits at recording time save hours later:

1. Script the demo and say UI labels exactly as they appear, so the translated transcript can keep them intact.
2. Pause briefly after each action; translated narration often runs longer, and pauses give the new voice room to fit.
3. Avoid typing visible sentences into the product; use neutral sample data with names and numbers that work internationally.
4. Keep callouts wordless where possible.
5. Record each feature as its own short video rather than one long tour, so an interface change invalidates one clip, not all of them.
6. Save the project file, so overlays can be re-exported per language.

Keeping localized demos in step with releases

Product demos go stale faster than almost any other video. A redesign in one release can make every localized version wrong at once. Treat demos as versioned assets:

• Tag each demo with the product version or release date it shows.
• When a feature's interface changes, re-record the source clip first, then produce each language version from it again.
• Keep the translated transcripts with the video; comparing old and new source scripts shows which lines changed and need fresh review.
• Retire localized versions you cannot keep current, rather than leaving outdated ones published.

Short, feature-level clips make this manageable; a single 20-minute tour does not.

Example: an onboarding demo in German and Japanese

Where translated demos help, and their limits

They help most when the product is used in English anyway but buyers and new users prefer explanations in their own language, when demos are evergreen, and when the narration carries the explanation rather than the visuals. They are also a quick way to test interest in a market before committing to localizing the product itself.

They fall short when the product UI is localized and the demo shows a different language from the viewer's screen, when callouts carry most of the information, and when an on-camera presenter dominates, since there is no lip-sync. Frequent releases are the other weakness: without a plan for updates, localized demos turn into a liability.

Producing demo versions with mydubly

mydubly translates the narration of a demo you have already recorded and exported as MP4, MOV, WebM, MKV or M4V, up to 2 hours per file. The output is a translated MP4 with a new AI voice track over your unchanged screen recording, the translated audio file, SRT and VTT subtitles, and transcripts in both languages for review. The picture is never altered, so interface text and callouts stay as recorded, and the original narration is replaced by the new voice while any background music stays underneath. The video file stays on your device and only the audio is processed, which helps when a demo shows unreleased features. See screen recording translation for recording tips and the video localization page for the full workflow.

Next step

Pick your most-watched demo and one target market, decide the UI-label convention for that language, and produce a translated version. Have someone who uses the product in that language review it with the glossary open. Start from the video localization page; if you also produce marketing explainers, marketing video translation covers that format.