Subtitle or Dub: Choosing per Market
Dubbing every market feels like the premium choice. The coverage math and the accessibility law both say subtitle broadly and dub selectively instead.
"Should we dub this for other markets?" gets asked as if it's a taste question — does the brand want to sound premium and fully localized, or is subtitling good enough. That framing hides the actual decision, which is really two separate questions wearing one costume: which markets can you even dub into, and which of those actually justify the heavier lift once you can. Answer both honestly and "dub everything" stops being a real option long before budget even enters the conversation.
The coverage math nobody checks first
Versely's captioning system transcribes spoken audio across 165 language codes — practically any language your source video might already be in. Dubbing is a much narrower door: 25 target languages. That's not a rounding difference, it's close to a sevenfold gap, and it means the "should we dub this market" question is frequently moot before you get to weighing cost against benefit. If the market you're chasing speaks a language outside that list of 25, dubbing isn't the harder option — it's not an option, full stop, and subtitling was never the fallback plan. It was the only plan available for that market from the start.
That reframes the whole decision. "Subtitle or dub" isn't a spectrum from cheap to premium where you pick your ambition level. For most of the markets on your list, it's a filter that already made the choice — and the two markets where dubbing is genuinely on the table are the only place a real decision gets made at all.
Subtitles are the floor, not the budget option
It's worth separating what subtitles are actually for, because "we didn't have budget to dub, so we subtitled instead" undersells the format badly. Captions on prerecorded video with synchronized audio are a WCAG 1.2.2 requirement, and that requirement doesn't care what language the audio is in. It's not a market-expansion feature that happens to be cheap — it's the accessibility deliverable your content owes its audience regardless of whether you ever localize into a second spoken language at all. A video with zero foreign-market ambitions still needs captions for the same-language deaf and hard-of-hearing viewers watching it, and for the much larger sound-off-by-default audience scrolling with the volume down.
Put plainly: you owe every video captions before you owe any video a dub. That ordering matters when budget actually is tight, because it tells you which spend is foundational and which is discretionary, instead of treating both as equally optional "nice to have if we get to it" line items.
Dubbing is a specific, narrower bet
Dubbing does something subtitles structurally cannot: it preserves delivery. A founder's actual voice, cloned and resynced, saying the same words in Spanish, carries tone and personality that a caption block at the bottom of the screen loses entirely. That's real value, and it's exactly the value worth paying for — selectively, for the content and the markets where delivery is doing real work, rather than as a blanket policy applied to a whole content library regardless of format. If the goal is simply natural-sounding narration in a new language without cloning a specific person's voice, Versely's voiceover library covers a wide roster of named voices across languages, which is a lighter localization option than a full clone for content where the delivery doesn't need to be one specific, recognizable voice.
Where dubbing earns its cost: founder-led narration, emotional or persuasive reads, anything where the point is a specific person's voice and cadence, not just the information in the sentence. Where it usually doesn't: data-heavy explainers, tutorials, anything a viewer is going to read as much as listen to anyway — captions lose nothing there that dubbing would have recovered.
The actual per-market test
Run every candidate market through this, in order, before deciding anything:
- Is the market's language one of the 25 dub targets? If not, you're subtitling that market by default, and the rest of this list doesn't apply — there's no decision left to make.
- Does the format depend on delivery? A talking-head founder video loses real value to a flat caption; a stats-driven explainer doesn't. Dubbing is worth its cost where the answer is yes, and rarely worth it where the answer is no.
- Does the market's own signal justify the heavier investment? Existing comments, shares and engagement from that language's audience on your already-subtitled content is the honest evidence a market is worth the extra step — not a guess about where you'd like to be popular. get_content_insights reads your own connected accounts' post history for exactly this kind of signal before you commit spend on the strength of a hunch.
A market that clears all three is one of your "two markets that justify it." Most won't clear the first filter alone, which is precisely why subtitling broadly and dubbing selectively isn't a compromise — it's the shape the coverage numbers force regardless of ambition.
A Versely walkthrough: caption the master, dub the shortlist
The practical build order, running subtitles as the default and dubbing as the selective add-on:
- Caption the source video first, in its own spoken language, before any localization decision gets made: "Add subtitles to this video automatically, source language English." This calls
add_veed_captionsagainst the audio as recorded, and it's the deliverable every version of this video needs regardless of what happens next. - Shortlist the one or two markets that clear the three-part test above — inside the 25 dub-target languages, delivery-dependent format, and real audience signal.
- Run the dub on each shortlisted market: "Dub this video into Spanish using the ElevenLabs engine, keep the background audio."
dub_videoclones the speaker's voice into the target language; addengine: 'heygen'instead when the face is prominent on camera and mouth-shape matching matters enough to justify its shorter length cap. For a lighter localization where full voice cloning isn't needed,translate_audio_onlyproduces translated speech without the full clone. - Re-caption the dubbed output, not the original transcript: run
add_veed_captionsagain against the new audio file, with the target language set. Caption timing and wording don't survive translation cleanly — sentence lengths shift — so the dubbed version gets its own fresh transcription rather than a reused one, giving that market both a localized voice and accurate captions for its own sound-off viewers. - Check the actual credit math before committing to the shortlist. What does dubbing one video into 10 languages cost breaks down that dubbing bills as a flat per-job charge that doesn't vary by target language — useful for confirming the real number before treating "two markets" as a budget-driven ceiling rather than a strategy-driven one.
The takeaway
Dubbing every market sounds like the more ambitious choice, but the coverage numbers make the real decision for most of your list before cost ever enters it: 165 languages of caption coverage against 25 of dub coverage means subtitling is the only lever available almost everywhere, and it's owed to every viewer regardless. Spend the heavier localization budget on the one or two markets where a real voice, in a real language, delivering a format that depends on delivery, actually changes the outcome — and let captions carry everything else, because they were never the fallback plan to begin with.