Last updated August 11, 2026
Subtitle Translator — Translate SRT, VTT & More to Any Language
Upload any subtitle file — SRT, VTT, WebVTT, ASS, SUB, SBV, or SCC — and translate to 133 target languages while timestamps and cue numbers stay identical byte-for-byte. Only the text changes. Free 30-minute quota, no signup.
TL;DR
Upload any subtitle file — SRT, VTT, WebVTT, SUB, ASS, SBV, or SCC — and get it translated to 133 target languages while preserving timestamps and cue numbers exactly. Free 30-minute quota, no signup. For starting from video instead of a subtitle file, upload the video and we'll extract, translate, and export subtitles in one step.
What is a subtitle translator (and what should it do)
A subtitle translator takes a text-based subtitle file (SRT, VTT, ASS, etc.) and produces the same file in a different language. The scaffolding — cue indices, start/end timestamps, positional markers — must stay untouched. Only the dialogue text is translated.
A serious subtitle translator does three things a naive text tool cannot:
- Preserves timestamps. Byte-identical
HH:MM:SS,mmmacross source and target. No drift, no re-sync work in the video editor. - Preserves cue numbers and structure. Cue 47 in source is cue 47 in target. ASS style headers, WebVTT positional cues, and SCC control codes are kept intact.
- Handles target-language length expansion. Spanish, French, and German translations run 15-35% longer than English. A good tool flags overflow against CPS (characters-per-second) reading-speed limits so you know which cues to review.
Which subtitle formats we translate
Full support for the seven formats real workflows produce. If you have something exotic (CEA-708, IMSC1, TTML2), export to SRT first.
| Format | Extension | Common in | Our support |
|---|---|---|---|
| SubRip | .srt | Video editors, YouTube, Vimeo, Netflix ingest | Full |
| WebVTT | .vtt / .webvtt | HTML5 <track>, browser video, HLS streaming | Full |
| SubStation Alpha | .ass / .ssa | Anime fansubs, karaoke, styled subtitles | Full (styles + positional markers preserved) |
| MicroDVD | .sub | Legacy DivX / older desktop players | Full |
| YouTube SubViewer | .sbv | YouTube Studio auto-caption downloads | Full |
| Scenarist CC | .scc | US broadcast, CEA-608 closed captions | Full |
| Broadcast captions | .cap / .stl / .dfxp | EBU-STL, DFXP/TTML, Cheetah CAP | Limited — export to SRT first |
How to translate subtitles — 3 steps
Upload → pick target language → download. Same format out, timestamps untouched.
- 1
Upload subtitle file or paste text
Drag .srt/.vtt/.ass/.sub/.sbv/.scc into the tool. Source language auto-detected; raw paste also works.
- 2
Select target language
Pick from 133 target languages. Regional variants (pt-BR, pt-PT, zh-Hans, zh-Hant) available.
- 3
Download translated file in same format
Same extension out. Cue numbers, timestamps, and structural markers preserved exactly.
Original SRT (English)
1
00:00:03,120 --> 00:00:06,480
The quick brown fox jumps
over the lazy dog.
2
00:00:06,720 --> 00:00:09,900
It was a bright cold day
in April.Translated SRT (Spanish)
1
00:00:03,120 --> 00:00:06,480
El rápido zorro marrón salta
sobre el perro perezoso.
2
00:00:06,720 --> 00:00:09,900
Era un día luminoso y frío
de abril.Notice: timestamps identical, only text changed.
Don't have a subtitle file? Start from video instead
If you only have the video (or audio), skip the manual transcription step. VexaScribe handles the full pipeline in one job:
- Upload the video — MP4, MOV, MKV, WebM, up to 5 GB / 10 hours.
- Whisper Large-v3 transcription — 99 source languages, auto-detected.
- Select target language — 133 options.
- Export .srt or .vtt — timestamps aligned to the original audio.
For dedicated video and audio workflows, see Video translator and Audio translator.
AI subtitle translation vs human subtitler — the honest tradeoffs
AI translation is a category. Professional subtitling is a different category. Both are legitimate; the right choice depends on the content.
| Concern | AI (VexaScribe) | Professional subtitler |
|---|---|---|
| Speed | 30 seconds for a 30-minute file | 4-8 hours per finished hour of video |
| Cost | $0-2 for typical creator content | $8-15 per source minute (subtitler rates) |
| Idioms & wordplay | Literal translation; wordplay lost | Cultural adaptation, equivalent idioms |
| Timing accuracy | Byte-identical timestamps preserved | May re-time for CPS compliance |
| CPS adjustment | Flags overflow; does not auto-rewrite | Rewrites long cues to fit reading speed |
| Best for | YouTube, e-learning, internal, drafts | Broadcast, festival, legally-regulated content |
Honest positioning: for YouTube creators, e-learning, internal comms, and first-draft workflows, AI subtitle translation is production-ready today — the timestamp preservation alone saves hours of re-sync work. For broadcast television, streaming platform ingest (Netflix, Prime), legally regulated content, or festival submission, use AI as the base draft and hire a certified subtitler for cultural adaptation and CPS compliance. Both approaches beat rebuilding from scratch.
The CPS trap — why target-language subtitles feel too fast
CPS (characters per second) is the reading-speed budget for each cue. Standard limits:
- • ~17 CPS — comfortable adult reading speed (BBC, Netflix guidelines)
- • ~15 CPS — accessibility standard (children, learners, cognitive access)
- • ~20 CPS — hard ceiling; anything above feels rushed
A 3-second English cue at 15 CPS holds ~45 characters. Translate it to German and you may need 60 characters in the same 3 seconds — that's 20 CPS, over the comfortable limit. The cue displays fine on screen but viewers can't finish reading it before it disappears.
Typical length expansion from English
| Language pair | Length change | Why |
|---|---|---|
| English → Spanish | +25-30% | Longer words, articulos definidos, verb conjugations |
| English → French | +15-20% | Compound tenses, formality markers |
| English → German | +30-35% | Compound nouns, case endings — worst offender |
| English → Portuguese | +20-25% | Similar to Spanish; BR and PT vary slightly |
| English → Italian | +15-20% | Article contractions moderate this |
| English → Japanese | -30% | Kanji compression; particles compact |
| English → Chinese (Simplified) | -40% | Character density is very high |
| English → Korean | -15% | Hangul compact but honorifics add length |
What VexaScribe does
- • Preserves all timestamps byte-identically
- • Flags cues that exceed 20 CPS after translation
- • Marks overflow so you can review in a subtitle editor
What VexaScribe doesn't do
- • Automatically rewrite cues to fit CPS budget
- • Split long cues across new timing boundaries
- • Silently drop text to meet character limits
Advice: for EN → DE, ES, PT translations of dialogue-heavy content, plan to review 5-15% of cues after translation. For EN → JA, ZH, KO, the target is naturally shorter and CPS is rarely a problem. For broadcast delivery, hire a subtitler for the CPS pass; for YouTube and internal use, the flagged-cue review is usually enough.
Translating closed captions (CC vs regular subtitles)
Closed captions include non-dialogue information that regular subtitles omit: sound descriptions, speaker labels, and non-verbal cues. VexaScribe treats all of them as translatable text.
- Bracket contents translated.
[music]→[música],[applause]→[aplausos],[sirens]→[sirenas]. Bracket punctuation preserved. - Speaker labels preserved and translated.
JOHN:stays; the dialogue after the colon is translated. For gendered honorific languages (Japanese, Korean), speaker labels help the model pick the right register. - Positional markers preserved. ASS
\pos()tags, WebVTTline:andposition:settings, and SCC control codes are kept byte-identical.
Not sure of the distinction? See What is closed captioning and Captions vs subtitles.
Translate YouTube subtitles specifically
YouTube auto-translate uses Google Translate under the hood — fine for tier-1 pairs, weak for anything else. Round-tripping through VexaScribe gives better results for uncommon pairs and for creator content with recurring terminology.
- In YouTube Studio, open the video → Subtitles → enable auto-captions if not already generated.
- Download the auto-generated file as
.sbvor.vtt. - Upload it to VexaScribe and pick your target language.
- Download the translated file (same format).
- Back in YouTube Studio, add a new subtitle track for the target language and upload the translated file.
For pulling transcripts out of YouTube directly, see the YouTube transcript tool.
Free subtitle translator — what "free" actually means
"Free" means different things across tools. Here's the honest breakdown.
| Tool | Free tier | Paid | Note |
|---|---|---|---|
| VexaScribe | 30 min source audio/video, no signup | $2-20/month | 133 target languages, all formats, EU hosting |
| TranslateSubtitles.co | Unlimited (Google Translate API) | N/A | Quality = raw Google Translate; no post-edit |
| Kapwing | 4 min video free | $16-24/month | Video-first editor; subtitle translation is a sub-feature |
| Google Translate | Text-only | N/A | No timing metadata; you rebuild SRT structure manually |
| Amara | Free for volunteer / nonprofit projects | Enterprise plans | Community-driven; hybrid AI + volunteer editing |
When to pay: if you translate more than 30 minutes of content per month, need batch processing, want a target language beyond the top 20, or need EU data residency and no-retention guarantees, the $2-10/month tiers cover it. If you translate a single YouTube video once a quarter, the free tier is genuinely enough.
Batch subtitle translation (for teams)
On the Pro tier, upload up to 50 subtitle files in one job. The chosen source-target language pair persists across the batch, you get a single ZIP download with per-file naming preserved, and developer API access is available for programmatic pipelines.
For bulk transcription workflows that feed into translation, see Bulk transcription.
Accessibility & compliance — WCAG, ADA, EAA
Subtitle translation intersects several accessibility regulations. Short reference:
- WCAG 2.1 Level A (SC 1.2.2) — captions required for all prerecorded audio in synchronized media.
- WCAG 2.1 Level AA (SC 1.2.4) — captions required for live audio content.
- EAA (European Accessibility Act, in force June 2025) — extends accessibility requirements to private-sector digital services and video content across the EU.
- ADA Title III — US courts have applied the ADA to public-facing websites and video; captions are treated as reasonable accommodation.
Multilingual requirements vary by jurisdiction and content type. Machine-translated subtitles are generally sufficient for internal training, corporate communications, and non-regulated commercial content. For public-sector broadcasting, educational content in regulated markets, and legally sensitive material, most compliance frameworks expect human review of translated captions.
Frequently asked questions
Does subtitle translation preserve timestamps exactly?
Yes. VexaScribe preserves every timestamp byte-identically — the translated file has the same cue numbers, same start/end times, same structure. Only the dialogue text changes. This is critical for video editors: you can swap in the translated .srt without re-timing anything.
What subtitle formats do you support?
SRT (SubRip), VTT and WebVTT, SubStation Alpha (.ass/.ssa), MicroDVD (.sub), YouTube SubViewer (.sbv), and Scenarist Closed Caption (.scc). For broadcast formats (.cap, .stl, .dfxp), we recommend exporting to SRT first — support is limited on those.
How many target languages are available?
133 target languages, from Afrikaans to Zulu. Source detection auto-covers 99 languages (Whisper Large-v3). If you can't find your target language, contact us — some regional variants may need manual selection.
Is subtitle translation free?
Yes, up to 30 minutes of source video-equivalent per month with no signup. For pre-made subtitle files, character/line count applies. Paid plans start at $2/month equivalent for larger volumes.
Can I translate YouTube subtitles directly?
Yes. Download YouTube's auto-captions as .sbv or .vtt from YouTube Studio, upload to VexaScribe, select target language, download translated file, and upload as a new subtitle track in YouTube Studio. Better quality than YouTube's built-in auto-translate for uncommon language pairs.
How does AI subtitle translation compare to a professional subtitler?
AI wins on speed (30 seconds vs 4-8 hours) and cost ($0-2 vs $8-15/minute) and preserves timestamps exactly. Professional subtitlers win on idiom handling, cultural nuance, and CPS adjustment for target-language length. For most creator/e-learning content, AI is production-ready. For broadcast or legally sensitive content, use AI as the base draft and hire a human for review.
Do you translate closed captions with sound descriptions?
Yes. Closed captions include descriptions in brackets ([music], [applause], [sirens]) — VexaScribe translates the bracket contents too ([música], [aplausos], [sirenas] for Spanish). Speaker labels (JOHN: hello) are preserved and translated. Positional markers in ASS/WebVTT are kept intact.
Can I batch-translate multiple subtitle files?
Yes, on the Pro tier. Upload up to 50 subtitle files per job, select one target language for all, receive a ZIP download of translated files. For higher volumes, developer API access is available.
Ready to translate your subtitles?
Any format in, same format out. Timestamps preserved. 133 target languages. Free 30 minutes, no signup, EU hosting.