Verified July 2026

SRT Translator — Free, Preserves Timings

Upload an SRT file, pick one or more target languages, download the translated SRT with cue numbers and timings preserved exactly. 99 supported languages, batch export up to 10 target languages as a ZIP, character-overflow flagging for standard 2-line subtitles. Free for short files, EU hosting.

Translate an SRT in 3 steps

Upload → pick target languages → download. Cue numbers and timings never change.

  1. 1

    Upload your SRT file

    Drag your .srt into the widget above. Auto-detection identifies the source language; override manually if needed.

  2. 2

    Pick target languages

    Choose 1 language (free) or up to 10 languages (signed-in batch). 99 supported languages total.

  3. 3

    Download translated SRT(s)

    Single file or ZIP with per-language filenames (video_es.srt, video_ja.srt). Overflow-flagged cues marked in output.

What gets preserved, what changes

Translation is a text-only operation on your SRT. The scaffolding (cue numbers, timecodes) stays untouched. That is what makes SRT translation faster and more reliable than re-transcribing.

AttributeStateDetail
Cue numbers (1, 2, 3, …)PreservedIdentical index across source and translation
Start timecodes (HH:MM:SS,mmm)PreservedExact match — sync stays perfect
End timecodes (HH:MM:SS,mmm)PreservedExact match — no drift
Cue textChangedReplaced with target-language translation
Language of the fileChangedYou picked the target — obvious
Character count per cueChangedOften longer in EN→DE, ES, FI; shorter in EN→JA, ZH
Line breaks within cue textChangedRe-flowed for readability; overflow flagged

Character overflow — the 42-char / 2-line rule

Subtitle standards (BBC, Netflix, EBU-STL) recommend ≤42 characters per line and ≤2 lines per cue for readability at standard reading speeds. That is 84 characters per cue as a soft ceiling.

Languages have different character counts for the same meaning. English "I'll be right back" (20 chars) becomes:

  • • Spanish "Vuelvo enseguida" (16 chars — shorter)
  • • French "Je reviens tout de suite" (24 chars)
  • • German "Ich bin gleich wieder da" (24 chars)
  • • Finnish "Palaan hetken kuluttua" (22 chars)
  • • Russian "Я скоро вернусь" (15 chars — depends on script)
  • • Japanese "すぐ戻ります" (7 chars — dramatically shorter)

For longer source cues, EN→DE / FI / RU can push past 84 characters. Our tool flags overflowing cues in the output so you can review them in a subtitle editor. We do not silently split or drop text — that decision is yours.

Batch translation — 1 upload, up to 10 target languages

For signed-in users, one SRT upload can produce translations into up to 10 target languages simultaneously. You get a single ZIP with clear per-language filenames:

video_translations.zip
├── video_es.srt   (Spanish)
├── video_fr.srt   (French)
├── video_de.srt   (German)
├── video_it.srt   (Italian)
├── video_pt.srt   (Portuguese)
├── video_ja.srt   (Japanese)
├── video_zh.srt   (Mandarin)
├── video_ko.srt   (Korean)
├── video_ar.srt   (Arabic)
└── video_hi.srt   (Hindi)

Faster than translating one at a time, and consistent — the same source cue splits are respected across all target languages, so timing sync stays perfect no matter which track a viewer picks.

Translate SRT vs re-transcribe target-language audio — which is right?

Translate SRT — when the video stays in the original language and you want subtitles in another. Timing stays perfect (same cues), fastest workflow, cheapest.

Re-transcribe target-language audio — when you have a dubbed version of the video in the target language. The dubbed audio uses different phrasing, pacing, and word order than a translation would; re-transcribing captures what the dubber actually said. Use transcribe-and-translate for that path.

Rule of thumb: if the video's audio track is the same, translate the SRT. If the audio track changes (dubbing, voice-over, native retake), transcribe the new audio.

Translation quality by language pair

Honest expectation-setting. BLEU scores below are typical for general content; specialized domains (medical, legal, tech) benefit from human review across all tiers.

Tier 1 (90-95% BLEU on general content)

Pairs: EN ↔ ES, FR, DE, IT, PT (BR + PT), NL, RU, PL

Note: Most languages have decades of parallel corpus data. Broadcast-quality baseline.

Tier 2 (80-88%)

Pairs: EN ↔ JA, ZH (Simplified + Traditional), KO, AR, HI, TR, VI, TH, ID, UK, CS, HU, RO

Note: Solid for general content; specialized domains (medical, legal) benefit from human review.

Tier 3 (65-80%)

Pairs: EN ↔ SW, BN, TA, PA, WEL, and lower-resource pairs

Note: Usable starting point; human review strongly recommended for publish-quality output.

4 workflows for translated SRT

YouTube creator adding multilingual subtitles

Workflow: Upload English SRT → pick ES, FR, DE, PT, JA → download ZIP → upload each language track in YouTube Studio

Tip: YouTube auto-detects language from the file; naming them foo_es.srt / foo_fr.srt keeps them organized.

Course creator localizing lectures

Workflow: Upload English lecture SRT → pick target markets → review Tier 2 languages (JA/ZH/KO) with a native speaker → publish

Tip: For educational content with technical vocabulary (physics, medicine, CS), Tier 2 language pairs benefit most from native review.

Indie filmmaker for festival submission

Workflow: Upload original-language SRT → translate to festival languages → hand off to festival technical review

Tip: Broadcast-quality festivals often require translations reviewed by certified subtitlers — treat the tool output as a strong starting draft.

Accessibility team providing multi-language captions

Workflow: Upload English caption SRT → translate to top 5 non-English viewer languages → batch upload to CMS

Tip: Character overflow flagging is critical for accessibility — visually-impaired users reading captions need standard-compliant 2-line cues.

Working with VTT files

This tool handles SRT specifically. For VTT (WebVTT, used by HTML5 <track> elements), do a two-step round trip:

  1. Convert VTT → SRT using our free VTT to SRT converter (client-side).
  2. Translate the SRT here.
  3. Convert back to VTT if the target platform requires it.

We keep the workflow modular because SRT and VTT have subtly different syntax around styling and positioning — a "universal" converter would silently drop features. Two transparent steps beats one lossy step.

Privacy

  • EU hosting — AWS eu-west-2 (London) infrastructure.
  • No retention after download — SRT files are deleted from our servers after export.
  • Contractual non-reuse — your text is not used for model training.
  • For strictly confidential content — unreleased film scripts, legal transcripts — client-side-only workflows are always more private than any server-side tool. Honest baseline.

See the full privacy policy.

Frequently asked questions

How do I translate an SRT file?

Upload your existing .srt file to the tool above, pick one or more target languages, and download the translated SRT with timings preserved. Timing and cue numbers stay identical to the source — only the text inside each cue is translated. Free for short files (under 500 cues) without signup. For batch translation into 3-10 target languages simultaneously, longer files, or higher volumes, sign in to a free account.

Do timings and cue numbers stay the same?

Yes — that is the whole point of translating an SRT rather than re-transcribing. Each source cue keeps its cue number, start timecode, and end timecode. Only the text is replaced with the target-language translation. This preserves the exact sync with your video and lets you swap subtitle tracks (English → Spanish → French) without touching the video editing timeline. If you re-transcribed from the audio in the target language instead, the cue boundaries would shift.

What happens if the translation is longer than the original?

Common issue — subtitle standards recommend ≤42 characters per line and ≤2 lines per cue for readability. Languages like German, Finnish, and Russian often produce translations 20-40% longer than English. Our tool flags cues where the translated text exceeds 84 characters (2 lines × 42) so you know to review them. We do not automatically split cues or drop text — that decision belongs to you. For hard-limit subtitle standards (Netflix, broadcast), you may need to manually shorten flagged cues in a subtitle editor after export.

Can I translate to multiple languages at once?

Yes, for signed-in users. Upload one SRT file, pick your target languages (up to 10 at once — English, Spanish, French, German, Italian, Portuguese, Japanese, Mandarin, Korean, Arabic, Hindi, and 88 more), and download all translations as a single ZIP with clear naming (video_es.srt, video_fr.srt, video_ja.srt). This is significantly faster than translating one language at a time and keeps the batch consistent — same source cue splits across all languages.

How accurate is the translation?

We use the same translation stack that powers our transcribe-and-translate audio workflow. Accuracy is highest for Tier 1 language pairs (English ↔ Spanish/French/German/Italian/Portuguese/Dutch: 90-95% BLEU on general content, higher for common phrases). Medium for Tier 2 (English ↔ Japanese/Mandarin/Korean/Arabic/Hindi: 80-88% depending on content type). Colloquial idioms, slang, and heavy domain jargon (medical, legal, tech) still need human review. For broadcast-quality subtitles, translated SRT is a strong starting point but not a substitute for professional translation.

SRT translator vs re-transcribing in the target language — which is better?

Depends on whether the target language audio exists. If you already have an English SRT and want Spanish subtitles for the same English video: SRT translator is right — one operation, timing preserved, faster and cheaper than dubbing. If you have a dubbed Spanish audio track alongside the English video: re-transcribe the Spanish audio directly for cleaner results (the SRT translator would just guess at the equivalent Spanish text, whereas the dubbed audio is already in the target language and might use different phrasing). Our transcribe-and-translate audio tool handles the second case.

Does it work with VTT files?

Yes with a small round-trip. Convert VTT to SRT first using our VTT to SRT converter (free, client-side), translate the SRT here, then convert back to VTT if needed. We keep the workflow modular because SRT and VTT have subtly different syntax around styling and positioning — one universal converter would silently drop features. Two steps, transparent behavior.

Is my SRT file private?

Yes. Files are processed on our EU infrastructure (AWS eu-west-2, London), translated, and returned. Nothing is retained after you download the output. The translated text is not used for model training. For strictly sensitive content (unreleased film scripts, confidential legal transcripts), the contractual non-reuse guarantee is the honest baseline — client-side-only workflows will always be more private than any server-side tool. See our privacy policy for details.

What are the supported languages?

99 source languages (auto-detected or picked by you) and 99 target languages. Head list: English, Spanish, French, German, Italian, Portuguese (BR + PT), Dutch, Japanese, Mandarin (Simplified + Traditional), Korean, Russian, Polish, Turkish, Arabic (Modern Standard + regional dialects), Hindi, Bengali, Vietnamese, Thai, Indonesian, Filipino, Swahili, Ukrainian, Czech, Hungarian, Romanian, Greek, Hebrew, Persian, Urdu, Punjabi, Tamil, and many more. Cross-check with the language picker in the tool for the full 99×99 grid.

Ready to translate your SRT?

Free for short files, batch multi-language for signed-in accounts. EU hosting, no retention, timing preserved.