The smallest file in localization: how subtitle tracks take one video into many markets
The master file of a ten-minute product video can weigh several gigabytes. Its Spanish subtitle file is a few dozen kilobytes of plain text. That gap in size is also a gap in cost, in turnaround and in risk, and it explains why so many localization teams now treat the subtitle file as the default way to carry a company's video into a new market.
The text file is only half the job, though. A translated SRT sitting in a shared folder helps nobody. It has to reach the viewer inside a player that lets them choose their language, on a page the company controls, without the video leaking to the open web. That last step is where translators are increasingly asked for advice, and where tools like vodspot.tv have made the publishing side as simple as the translation side is skilled.
Why subtitles win the budget argument
Dubbing a video means casting voices, booking studio time, directing performances and mixing new audio tracks. Every revision to the source cut sends the whole chain back to the studio. A new on-screen voice also changes the brand: the CEO who speaks in the original suddenly sounds like someone else in Lisbon and someone else again in Seoul.
Subtitles keep the original voice and swap only the words. A translator works from a transcript and a timecode, a reviewer checks the result against the picture, and an edit to the cut usually means retiming a handful of cues rather than re-recording a performance. For training videos, product demos, investor updates and conference talks, the material most companies actually produce, that trade is hard to beat.
The audience demand is real. CSA Research, working with the survey firm Kantar, asked 8,709 consumers in 29 countries how language affects what they buy online. Seventy-six percent said they prefer to buy products with information in their native language, and 40% said they will never buy from websites in other languages. A product video in English only is, for a large share of those buyers, a closed door. A subtitle track is the cheapest key.
There is a second payoff that budget owners often miss: subtitles help people understand the video better, not just access it. Morton Ann Gernsbacher, a psychologist at the University of Wisconsin–Madison, reviewed more than 100 empirical studies for a paper in Policy Insights from the Behavioral and Brain Sciences. Her conclusion was that captions improve comprehension of, attention to and memory for a video, and that viewers watching in a language that is not their first are among the groups who gain the most. For a translator, that is a strong argument to bring to a client meeting: the subtitle file is not a compromise version of the content. For many viewers it is the better version.
SRT or WebVTT: what to hand over
Both formats are plain text, and both pair a time range with a block of words. The differences matter when the file reaches a web player.
SRT is the older and more universal format. Each cue has a sequence number, a timestamp line written with commas before the milliseconds (00:01:12,400 --> 00:01:15,900) and the text. Almost every editing tool and subtitling suite exports it, which makes it the safe choice for handoffs between vendors.
WebVTT was designed for the web. The file opens with the word WEBVTT, timestamps use a period instead of a comma, and cues can carry positioning and basic styling. If a client's video will play in a browser, WebVTT is the format the browser understands natively.
A practical rule for localization teams: deliver both. Keep SRT as the archival master and generate WebVTT for publishing. Name the files with the language code and a clear label, such as onboarding_es-MX.vtt and onboarding_fr-CA.vtt, so nobody uploads Canadian French where European French was promised.
How the viewer chooses a language
On the viewer's side, the experience is simple when it is set up well. The player shows a captions button, usually marked CC. Tapping it opens a list of available tracks, and the viewer picks one. The track list is where small decisions add up.
Label tracks in their own language. A Japanese viewer scanning the menu looks for 日本語, not "Japanese." A Brazilian viewer looks for Português (Brasil).
Separate regional variants. Latin American Spanish and Castilian Spanish are different deliverables with different vocabulary, and the menu should say so.
Keep captions and translations distinct. Same-language captions for the deaf and hard of hearing include sound cues like [door slams]. Translated subtitles usually do not. If both exist, list both.
Check reading speed against the cut. A line that reads comfortably on paper can flash past in a fast-paced edit. Watching every track at full speed, on a phone, before handoff catches most problems.
Publishing one video with many tracks, privately
Here is where many localization projects stall. The translations are approved, but the company's options for publishing feel wrong. A public video platform puts the clip next to recommendations and ads. A file-sharing link makes partners in other countries download gigabytes before they can watch a single frame, and the subtitles end up as separate attachments nobody opens.
A private video platform solves this in one place. In VodSpot, a team uploads the master once and attaches up to 20 subtitle tracks in SRT or WebVTT. The video streams in up to 4K with adaptive playback, so it starts at once on a laptop in Frankfurt or a phone in Mexico City and adjusts to the connection. The player carries no ads, no recommendations and no third-party branding, and the viewer chooses a language from the captions menu.
The publishing model fits how localized content is actually distributed. One project can have many delivery pages, each with its own link, password and expiry date. A company can send its distributor in Madrid a page that opens in Spanish, with the interface itself shown in the viewer's language (VodSpot pages come in six), and send its partner in Montreal a separate page with its own password and its own stats. If a page should stop working when a campaign ends, it expires on schedule; if a link goes somewhere it shouldn't, access can be revoked instantly. Delivery pages are kept out of search engines, and streams run through signed URLs that expire within minutes.
Pages carry the company's own logo, colors and fonts, so a regional team sees the brand rather than a hosting service. And the project owner gets an email the first time a page is opened, plus views, watch time and completion for each page, which tells a localization manager something no delivery receipt can: whether the market actually watched.
For a team that publishes regularly, the Studio plan costs 1,490 USD a year with 10 seats and 1.5 TB of storage, which is 3,310 USD (69%) less than the 4,800 USD a year that Vimeo's published Studio price comes to. And because VodSpot charges no bandwidth fees, a video that takes off in a new market does not turn into a surprise invoice.
Where translators fit in
Localization professionals already own the hardest part of this workflow: the words, the timing and the cultural judgment. Advising clients on the last mile, which format to publish, how to label tracks and where the video should live, is a natural extension of that expertise and an easy way to make a project land well.
The subtitle file stays the smallest thing in the delivery. Published properly, it can carry a video further than anything else in the package.
VodSpot can be tried free for seven days without a credit card, which is enough to publish one video with all of its subtitle tracks.