Guides· 8 min read

Product Video Localization: Voice, Captions and Timing

Which videos deserve a native voiceover, how to build a master that survives translation, and why German captions need cutting, not just translating

By disha Sharma

ShareXLinkedIn
Product video localization cover: a 'One video, many languages' card listing four steps (master, script, voice, re-time) and subtitle limits of 20 characters per second in English and 17 in German

Most "localized" product videos are an English voiceover with translated captions underneath. That works for some videos and fails for others. The skill is knowing which is which, then building the video so each new language costs a script and a voice track, not a new project.

The short answer: to localize a product video, pick which videos get a native voiceover and which get captions only. Then build one locale-ready master: no text baked into the frames, a glossary of terms you never translate, and some slack at the end of each scene. For each language, a native speaker reviews the script, you generate the voice from that script, and you re-time scenes and captions to the new track. Then publish each version where speakers of that language will actually find it.

Two numbers explain why timing is the step that breaks:

  • Text grows when it leaves English. IBM's figures, republished by the W3C, put the average expansion into European languages at 130% for text over 70 characters, and 200–300% for strings under 10 characters.
  • Caption limits shrink. Netflix allows up to 20 characters per second for English subtitles in adult programs, but 17 for German.

So a German caption track has more characters to show and less room per second to show them. Literal translation can't fit. Here's the full workflow.

VideoNative voiceoverCaptions onlyLeave in English
Homepage or pricing demoYes, in your top marketsOther markets—
Onboarding and help videosYes, where you support the languageWhere you don't—
Paid adsYes, per market you buy——
Social clipsOptionalYes—
Changelog and internal updates—OptionalYes

Decide which videos earn a native voice

Captions are cheap and fast. A voiceover costs more review time, and it gets watched with the sound on, at the moment someone is deciding whether to trust you.

The demand is real. In CSA Research's 2020 survey of 8,709 consumers in 29 countries, 76% preferred to buy products with information in their own language, and 40% said they never buy from websites in other languages. The same survey found 65% prefer content in their language even if it's poor quality.

That last number is a floor, not a target. Poor quality will still get watched, but your product video is also making a claim about how carefully you build things.

A practical rule:

  • Voice it when the video is sound-on and a buyer or new user is deciding something: demos, onboarding, paid ads.
  • Caption it when it's watched muted or skimmed: social clips, short feature teasers.
  • Leave it when it goes stale within weeks: changelog videos, internal updates.

Takeaway: start with the two or three videos that decide a purchase or a first success, in the one or two markets where you already have paying users.

Build a locale-ready master first

Every language version inherits the master's problems. Fix them once, before translation starts.

  1. Keep text out of the pixels. Titles, callouts and lower thirds should be editable layers, not text burned into a screenshot. Otherwise each language means redesigning frames.
  2. Show the localized interface. If your product ships in German, record the German UI for the German video. German narration over an English screen undercuts the whole point.
  3. Write a do-not-translate glossary. Product name, plan names, feature names and any UI label that appears on screen. Give it to every translator and reviewer.
  4. Leave room at scene ends. A scene that ends exactly as the English sentence ends has no space for a longer sentence. Hold the final frame a little longer than English needs.
  5. Avoid idioms and wordplay. "Ship it" and "a no-brainer" either translate badly or need rewriting. Plain sentences travel.

Takeaway: if a change to the master would need repeating in every language, make it now.

Why translated scripts and captions run long

The W3C's article on text size in translation reproduces IBM's guidelines for text going from English into European languages:

English source lengthAverage expansion
Up to 10 characters200–300%
11–20 characters180–200%
21–30 characters160–180%
31–50 characters140–160%
51–70 characters151–170%
Over 70 characters130%

Short strings expand the most. That's exactly what callouts, button labels and lower thirds are. Expect your on-screen text to need the most rework.

Spoken language is different. A 2019 study in Science Advances by Coupé and colleagues measured 17 languages and found they carry similar amounts of information per second, about 39 bits. Faster languages pack less information into each syllable, and slower ones pack more. Speaking rates still varied widely between individual speakers, from about 4.3 to 9.1 syllables per second.

So the language alone doesn't decide how long a voiceover runs. When a translated track runs long, check two things first: did the translation carry over every English word, and does the voice read at a different pace? Both can be fixed in the script and the voice settings.

Captions are a separate budget. Netflix's English (USA) style guide allows up to 20 characters per second for adult programs. The German guide allows 17. Both cap lines at 42 characters.

Takeaway: ask translators to adapt to a time budget, not to translate every word. Give them the scene durations along with the script.

Generate the voice from the translated script

The voiceover should come from a script written in the target language, not from dubbing over English audio. That's where the natural rhythm comes from.

Whichever tool reads it, the narration should be the reviewed target-language script. A workable loop in Poko:

  1. Translate the script with the glossary and scene durations attached.
  2. Have a native speaker read it aloud before any voice is generated. Reading aloud catches stiff phrasing that silent review misses.
  3. Pick a voice for that language. Poko has a built-in voice catalog. If you connect your own ElevenLabs or Cartesia key in Voice Settings, those providers' voices appear in the same picker, billed to your own account.
  4. Decide on a cloned voice carefully. Poko's voice cloning recorder supports over 40 languages. A founder's cloned voice speaking German is still the founder's voice, so check it with a native listener before you ship it.
  5. Fix lines by asking for them. If one sentence lands wrong, ask for the change in Poko's chat editor, which edits the video through plain-language chat, rather than rebuilding it. For why editing by text beats a timeline, see how to edit a demo video just by typing.

Takeaway: treat each language as the same video with three inputs swapped: script, voice and on-screen text.

Re-time scenes and captions to each track

Once the new voice track exists, the English timing is just a starting point.

  • Scene cuts: move each cut to where the new sentence ends, not where the English one did.
  • Callouts: make sure each callout appears while the narration is talking about it.
  • Captions: write them from the new narration, then condense to fit the reading-speed limit. Don't translate the English caption file line by line.
  • End card: give the call to action the same amount of time in every language.

Then run three checks. Watch it on mute, to test the captions alone. Watch it on a phone, to test that expanded text still fits. Have a native speaker watch the whole thing once without the script.

Takeaway: a localized video passes review when a native speaker can't tell which version was made first.

Publish each version where its audience looks

A finished video in the wrong place does nothing.

  • YouTube: YouTube's multi-language audio feature lets you upload audio tracks in different languages to a single video, from YouTube Studio on desktop. Check whether the option appears in YouTube Studio for your channel before you plan around it.
  • Your website: put each language's video on that language's page. If you have separate localized pages, tell Google about them with hreflang annotations.
  • Caption files: upload a caption file per language rather than burning one language into the picture. That keeps the video usable in every market. See how to add captions to videos for the basics.

Takeaway: one video with several audio tracks suits YouTube. Separate files on separate language pages suit your own site.

What localization won't fix

Be honest about the limits before you commit budget.

  • A product that isn't localized. If the app, docs and support stay English-only, a German video sets an expectation the next screen breaks.
  • Claims that differ by market. Pricing, currency, date formats, legal terms and compliance claims can change by country. Check each one, not just the translation.
  • Videos you can't maintain. Every language multiplies the update work when your interface changes. Only localize videos you'll keep current.

Takeaway: localize the video after the product is ready for that market, not instead of it.

Your next step

Pick one video that decides a purchase, usually the homepage demo. Pick one market where you already have customers. Build the locale-ready master, get the script adapted to a time budget, generate the voice, re-time, and have a native speaker watch it before it goes live.

If you're starting from your code, a website or a screen recording, Poko can build the master video. Then each language version only needs its reviewed script and a voice.

Disha Sharma
About the author

Disha Sharma

Marketing, Poko Motion

Writes about AI video workflows, product storytelling, and motion video.

Questions, answered.

How do you localize a product demo video?

Start with a locale-ready master: no text burned into frames, a glossary of terms you never translate, and a little slack at the end of each scene. Have the script adapted into the target language to fit each scene's duration, and have a native speaker read it aloud. Generate the voiceover from that script, re-time scenes and captions to the new track, then publish it on the page or channel where speakers of that language will find it.

Should I use a translated voiceover or just subtitles?

Use a native voiceover for videos watched with the sound on while someone is deciding something, such as homepage demos, onboarding videos and paid ads. Use translated captions for videos usually watched muted or skimmed, such as social clips and short teasers. Videos that go stale within weeks, like changelog updates, can often stay in English. Start with the two or three videos that matter most in one or two markets where you already have customers.

Why does my translated video run longer than the English version?

Often because the translation carried over every English word. IBM's figures, republished by the W3C, show text into European languages expanding by about 130% for longer passages and far more for short labels. Research in Science Advances found spoken languages carry similar information per second, so the fix is in the script: ask translators to adapt to each scene's time budget instead of translating word for word, then re-time cuts to the new track.

How many characters per second should subtitles have?

It depends on the language and audience. Netflix's style guides allow up to 20 characters per second for English subtitles in adult programs and 17 for German, with a maximum of 42 characters per line in both. Because German text also tends to run longer than English, translated captions usually need condensing to fit. Write captions from the new narration and shorten them, rather than translating the English caption file line by line.

Can one YouTube video have voiceovers in several languages?

Yes. YouTube's multi-language audio feature lets creators upload audio tracks in different languages to a single video, from YouTube Studio on desktop, and viewers then choose the track they want. Check whether the option appears in YouTube Studio for your channel before planning around it. On your own website, the simpler approach is a separate video file on each language's page, with hreflang annotations so Google knows which page serves which language.

Keep reading

#video localization#product video#multilingual voiceover#captions#ai voiceover#translation#demo video

Poko Motion · the fastest AI motion video generator

Make your first video
in 5 minutes.

Paste a link, a doc or a deck. A swarm of AI agents builds the video while you watch.