Video localization

Video Localization with AI

Localisation makes a video feel made for its audience. mydubly automates the biggest part — the spoken language — with voice tracks, subtitles and transcripts, so your team can focus on what still needs human judgement.

01 Upload

Your video

Full translation outputVideo, translated audio, and transcripts in the result panel.
Server assistOff by default. When on, this job uploads your media file so our servers can decode it (helpful on phones). Uploads this file (max 500 MB). Same credit cost as a normal run. Max length still 2 hours.

By default the video file stays in this browser (only audio chunks go to the cloud). Language is required for full translation.

02 Result

Your translated video

Your translated video will appear here.

Waiting for upload

25 languages available

What this looks like in mydubly

mydubly YouTube subtitle style with white text on a dark box
mydubly choice between cloned speaker voice and stock male or female voice
mydubly Social Media subtitle style big centred captions for vertical video
Burn styled mydubly captions into an MP4 from the subtitle editor

What's automated — and what isn't

Automated
Transcription, translation into 21 languages, AI voice track in 19 of them, subtitle files, timestamped transcripts
Still manual
On-screen text and graphics, cultural references, units and currencies, final native-speaker review

How teams use it

  • Marketing: test explainers and product videos in new markets.
  • Training: give every site the same onboarding and safety content.
  • Courses: sell existing courses to new audiences.
  • Webinars: turn live events into on-demand content per region.

A simple localisation workflow

  1. Pick evergreen videos and the markets that matter.
  2. Translate one video per language and have a native speaker review it.
  3. Fix your glossary, then process the rest.
  4. Translate titles, descriptions and thumbnails, and publish with subtitles.

The full list is in the video localization checklist.

Pricing

Transcript and subtitles
5 credits per minute (0.5¢), minimum 25 credits per file
YouTube link transcript
15 credits per minute (1.5¢), minimum 75 credits per link
Translated voice (includes everything above)
120 credits per minute (12¢), minimum 2 minutes per file
Text to audio
120 credits per minute (12¢), minimum 2 minutes per file
Corrections in the dub editor
free for timing, levels, background, leftover-speech cleanup, ducking, loudness and subtitles; re-voiced lines cost 120 credits per minute of those lines, minimum 60 credits per re-process
Credits
$1 buys 1,000 credits; each top-up lasts 30 days
Free credits
240 credits when you sign in with Google

Privacy

By default your video is not uploaded — only its audio is, over HTTPS in small chunks. Optional Server assist uploads the media for a job when you turn it on. A dub's audio, script and voice files stay on our servers for 120 minutes after it finishes or after you last use the editor, so you can fine-tune it, and are then deleted; the editor's "Delete files" button removes them at once. Nothing is used to train models. Your account keeps only the file name, length, languages and credits used. Details in the privacy policy.

Good to know

  • Each person is dubbed in a copy of their own voice (up to 8 people per file), with natural pronunciation for the new language. Telling people apart is automatic, so crosstalk, very short interjections or two very similar voices can end up in the wrong voice, and overlapping speech overlaps in the dub by at most about two seconds. Someone with too little clean speech to copy gets the copied voice of a similar-sounding person in the file, or otherwise a stock voice matching their voice (female or male). There is no lip-sync.
  • Music and sound effects are kept by AI vocal separation, which isn't perfect: in dense mixes faint traces of the original voice can remain, and sung lyrics are removed along with the speech.
  • The dub editor corrects the dub mydubly made: it doesn't import your own SRT or script, and a dub can be re-processed up to 40 times while its files are kept.
  • No speaker labels — transcripts don't say who is speaking.
  • File uploads stay file-based: no Instagram or TikTok links, and no live audio. For a YouTube link transcript only, use the YouTube transcript tool — and only for videos you have the right to transcribe.
  • Subtitles come as SRT/VTT files; to burn them into the picture, use the free subtitle editor.

Who runs localization with a tool like this

The typical user is a small team without a localization vendor: a marketing manager taking product videos into two new markets, an L&D lead with onboarding content for sites abroad, a course creator testing demand in another language. They need the spoken layer handled and can find one fluent reviewer per market. Larger teams use the same output to draft and test a market before committing studio budget.

What it doesn't replace is the rest of a vendor's service: project management across many files, translation memory that reuses approved wording, casting voice actors, or adapting graphics. If your project depends on those, use this for the speech layer and plan the rest separately.

Tiering a video library

Not every video deserves the same treatment. Sorting the library first keeps cost and review effort where viewers will notice.

Tier 1: flagship brand films and paid ads
AI version to test the market; professional review or voice-over before full spend
Tier 2: product explainers, onboarding, training
Dub mode plus a fluent reviewer's pass
Tier 3: webinars, event recordings, internal updates
Translated subtitles from transcript mode; add a dub only if viewers ask for it
Tier 4: archive and low-traffic videos
A transcript for search, or leave as is

Building a localization strategy covers auditing a library and choosing markets.

Budgeting per market

Six onboarding videos of 7 minutes each, into Spanish (Latin America), Portuguese (Brazil) and Polish

42 minutes in three languages is 126 dubbed minutes: 6,300 credits ($6.30). Each video is a separate run per language.

The same library as translated subtitles only is 126 credits (12.6¢). At these rates the processing cost is rarely what limits a project; reviewer time is. Plan roughly one reviewer session per language per batch, and process the rest only after the first video's feedback is in. Running one video through several languages covers file naming and release order.

What sits outside the speech layer

  • Text in the picture: lower thirds, slides and interface labels stay in the original language. Exporting textless versions of your videos makes replacing them far easier; see textless masters.
  • Metadata: titles, descriptions, thumbnails and landing pages aren't translated by mydubly.
  • Prices, units and dates spoken in narration: machine translation renders them rather than adapting them, so a price in dollars stays in dollars. Reviewers should flag every one.
  • Product demos: the narration changes language while the interface on screen doesn't; localizing product demos covers how to handle UI terms.
  • Cultural fit: humour, examples and references may need rewriting at the source, not fixing in translation.

Review and upkeep across languages

  1. Write a one-page style guide per language: formality, terms to leave untranslated, how to handle names. Writing a translation style guide has a template.
  2. Send each reviewer the SRT and the video. They note problems with timestamps, which makes fixes quick to locate.
  3. Fix subtitle text directly in the SRT. For a mistranslated line in the dub, replace that line in an editor using the translated audio, or decide the error is minor enough to accept.
  4. When the source video changes, re-run it for every language that carries it, and keep a list of which version each market has; updating translated videos covers patching versus re-running.

Deciding whether a market is worth continuing

Treat the first batch in a new language as a pilot with a fixed review date. Publish a handful of Tier 2 videos, then compare them with the same videos in the original language: watch time, how far viewers get, comments in the new language, sign-ups or support tickets from that region. Subtitles are the cheaper first test; if viewers in that market stay longer and ask for audio, add the dub later from the same source files.

Set the decision rule before you look at the numbers, such as "expand if the translated versions hold viewers about as well as the originals", so a slow first month doesn't end a market that needed time. Measuring localization success lists metrics by goal.

Where to go from here

Use-case pages show the workflow for specific content: marketing videos, training and online courses. The target-language pages, for example German or Portuguese, list what reviewers in that language should check.

Localisation by use case

Learn more

Articles that go deeper on the technology and workflows behind this tool.

Frequently asked questions

What is video localization?

Video localization means adapting a video so it feels made for another language or market — not only translating words, but fitting speech, subtitles, and often titles and on-screen text. mydubly automates transcription, translation, AI voice and subtitle files; graphics, cultural references and final native review stay with your team.

Is AI localisation good enough for customer-facing video?

Often, especially for explainers and training. For flagship campaigns, use the AI version to validate a market and add professional review or voice-over where it matters.

Does mydubly translate thumbnails, titles or slides?

No. It translates speech: the voice track, subtitles and transcripts. Titles, descriptions, thumbnails and text in the picture are separate work for your team or a designer.

How many languages should we start with?

One or two, chosen from your own audience data: where viewers already come from, what support tickets or comments ask for. Choosing languages covers how to read that data.

Can we keep terminology consistent across dozens of videos?

There's no glossary feature, so consistency comes from review. Keep a term list in your style guide and search each transcript for those terms before the reviewer starts.