Subtitles, captions, voice-over, dubbing
Video translation services
Scope video translation services with outputs, platform, and timing settled first.
Move a video into target languages with the output mix (subtitles, captions, voice-over, dubbing), platform format, on-screen text handling, and reading-speed limits confirmed before any work begins.
Upload files for a quote
Short form: name, work email, runtime, platform, target languages, and media files or links if ready.
Target-language coverage reviewed per request
Standard subtitle-only package, 30-min video, single target
Plus TTML and platform-specific exports
Dynamic Dialects supports requests across 250+ languages with ISO 9001/27001 operating controls, ISO 17100 applied to translation scopes, 40,000+ vetted linguists, named project coordination, and written confirmation before production work begins.
Evidence for review
What DD can show before a buyer commits.
This is not a public case study claim. It is DD-owned evidence a buyer can request when the work needs vendor review before a scope is approved.
Ask for proof details- Buyer type
- Video translation services buyer, vendor manager, or operations lead qualifying DD before sending a live requirement.
- Problem
- The buyer needs scope video translation services with outputs, platform, and timing settled first. scoped by files, audience, language pair, deadline, recipient rules, and review process before quote approval.
- Scope
- Video translation services work coordinated by DD with written request review, named PM ownership, and review records matched to the request type.
- Constraint
- This page cannot rely on a public case study yet; it must point to DD-owned proof artifacts and disclosure-safe process evidence.
- DD action
- DD confirms the inputs, missing details, staffing option, quality check, and delivery record before production work begins.
- Evidence available
- Private proof can include a request-specific checklist, redacted QA summary format, delivery record format, and sourcing or reviewer notes.
- Outcome
- The buyer can judge whether DD fits the requirement before sending production files or adding this service to a vendor shortlist.
- Disclosure status
- DD-owned proof only. Public outcomes require client approval; redacted process artifacts can be shared when terms allow.
How the work runs
-
Scope outputs
Output mix (subtitles, captions, voice-over, dubbing), target languages, platform, and deadline recorded in writing before any work begins.
-
Translate against timing
Target-language script written to reading-speed and characters-per-line limits per language pair, with source timing preserved unless retiming is part of the scope.
-
Record voice-over or dub
When audio output is in scope, voice-over or dubbing is recorded against the source video and the adapted script, with the agreed voice direction.
-
Spec-check the timing
Reading speed, characters-per-line, line count, and on-screen text handling validated against the target platform's spec before delivery.
-
Deliver platform-ready files
Final files in the agreed format ready for upload to the target platform, with translator notes attached for any flagged segments.
Each video translation project starts with a written request check confirming source video, target languages, output mix, platform format, on-screen text handling, and reading-speed expectations. The mix is chosen against the actual goal: subtitles for fast international rollout, captions for accessibility, voice-over for narration, dubbing for scene-tight performance. Standard turnaround for a 30-minute video into one target language is 5–7 working days for a subtitle-only package, longer for dubbing or multi-language voice-over. Every project is quoted with a confirmed delivery date in writing.
For media work, DD checks source quality, timing, platform format, speaker treatment, and output files before quoting.
What this page helps you send
- Marketing, brand, and product video translated for international launch.
- Training, onboarding, and internal learning video for multilingual teams.
- Education, MOOC, and explainer video with platform-spec captions.
- OTT, streaming, and broadcast video with subtitle and dubbing options.
- Multilingual subtitle packages built from one source video with separate target-language files.
- Voice-over recording for narrated content where audio is the lead.
- Dubbing for scene-tight target-language performance.
- On-screen text, signs, forced narratives, and lower thirds handled with a recorded decision.
What you receive
- Translated subtitle file per target language, with timing preserved (SRT, VTT, TTML, or platform-specific export).
- Closed caption file when accessibility is in scope, with speaker labels and sound cues.
- Voice-over or dubbing audio per target language when audio output is in scope.
- On-screen text track or burn-in instructions per the project's recorded decision.
- Reading-speed, characters-per-line, and line-count check against the target platform's spec.
Questions teams ask first
What output mix should we ask for?
It depends on the goal. Subtitles are the fastest, cheapest way into international rollout and work on every platform. Closed captions add accessibility access (speaker labels, sound cues) in the source language. Voice-over works for narrated content where the original speaker is off-screen. Dubbing fits scene-tight content where lip-sync and performance matter. Many projects ship a subtitle package first, then add dub or voice-over for higher-value markets.
What file formats are delivered?
SRT and VTT cover most web, social, LMS, and streaming workflows. TTML, DFXP, STL, and platform-specific exports (YouTube SBV, Netflix-spec timed text, broadcast STL) are available on request. The platform you are delivering to drives the format choice and the spec rules that the file must pass.
How are reading speed and characters-per-line handled?
Reading speed (characters per second, CPS) and characters per line (CPL) are checked per language pair, because expansion factor varies. German, Russian, and Finnish typically run longer than English. Mandarin and Japanese pack more meaning into fewer characters but face their own per-line limits. The defaults follow Netflix TTSG and BBC Subtitle Guidelines unless the platform you are delivering to publishes its own spec.
How is on-screen text handled?
Each project records a decision: translate on-screen text in line with dialogue, deliver a separate forced-narrative track, or leave source on-screen text untranslated. Forced-narrative tracks are common for OTT and broadcast delivery where signage and short non-dialogue text needs translation but should appear only when needed.
How long does video translation take?
Standard turnaround for a 30-minute video into one target language is 5–7 working days for a subtitle-only package. Voice-over adds recording time. Dubbing adds adaptation, casting, recording, and review. Multilingual packages are quoted with a confirmed delivery date per language. Expedited turnaround is available for launch and campaign schedules.
Can a single source video produce multiple language outputs?
Yes. A multilingual package is built from one source video with separate target-language files per language and per output type (subtitle, caption, voice-over, dubbing). Timing is preserved from the source unless retiming is part of the scope for a specific language.
What about accessibility (captions and audio description)?
Same-language closed captions for accessibility, target-language subtitles for international viewers, and SDH (subtitles for the deaf and hard of hearing) are different outputs. A single project can produce all three when the audiences and requirements are confirmed up front.
Can existing SRT or VTT files be translated into more languages?
Yes. Send the source subtitle file plus the source video for context. Each target-language file is delivered with timing preserved, reading-speed limits applied, and line breaks adjusted to fit the target language's natural cadence.