Translation is an input. Localization is a production workflow.
Video localization can involve on-screen text, subtitles, voiceover, product imagery, offers and market-specific end cards. A translated headline may need more space. A voiceover may need different timing. A local reviewer may need to approve a claim before the asset can ship.
Decide who supplies and approves each language. Keep creative adaptation separate from translation approval: a producer can check that a title fits while a qualified language reviewer checks that it says the right thing. Neither check replaces the other.
Build a localization brief that editors can use.
Give every copy element a stable identifier and a clearly approved source. Include context for translators, pronunciation notes for voice talent, the intended market and any elements that must stay unchanged. Keep the revision history with the approved language set.
Combine that language set with the delivery matrix. Some markets need a different offer or duration; others may share a language but need different end cards. Avoid assuming that one translation corresponds to exactly one deliverable.
- Approved source script and on-screen copy.
- Language and market owners, with review deadlines.
- Fonts and character coverage for the required languages.
- Subtitle, voiceover and timing requirements.
- Market-specific product, offer and end-card changes.
- Required output formats and editable source handoff.
Test the longest line and the tightest timing.
When evaluating a video localization platform, use a representative translated line that challenges the design. Check text wrapping, reading time, punctuation, font support and whether the product remains visible. If right-to-left layouts are required, demonstrate them explicitly rather than inferring support.
Compare the localized output with the approved script and listen to the complete audio track. Inspect subtitles in the final frame, not only in a spreadsheet. Keep linguistic approval and technical quality control visible as separate steps.
Scope the production work with Revolv.
Bring an approved master, source-file details and a small approved language set. We will evaluate the editable production workflow in Composer and the review requirements around the job. Confirm supported languages, font behaviour, voiceover inputs and export formats during scoping.
This is a campaign production conversation, not a promise of automatic translation or dubbing in every language. Agree which materials you supply, which steps are automated, and who signs off the market-ready result before expanding the pilot.
Before you start
Common questions
Does this include translation or automatic dubbing?
Do not assume either is included. Translation, voiceover, language support and review responsibilities are confirmed as part of the campaign scope.
Who approves the localized version?
Assign a market or language reviewer alongside the creative owner. Agree who can approve copy, imagery, audio and final delivery before production begins.