SRT Translator — Free, Preserves Timings

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.

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.

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.

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.

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.

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.

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.

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.

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.

SRT translator (this page) handles .srt files specifically — the most universal subtitle format. Our subtitle translator (/subtitle-translator) handles broader formats (VTT, WebVTT, SUB, ASS, SBV, SCC). If your file is .srt, either tool works — this page is optimized for SRT workflow. For non-SRT formats, use subtitle translator.

Google Translate is text-only — you'd copy-paste each subtitle line manually and lose timestamps in the process. AI SRT translator preserves timestamps exactly, handles cue structure, and processes entire files in seconds. For English↔Spanish/French/German, translation quality is comparable. For non-Latin scripts (Arabic, Hindi, Chinese, Japanese), LLM-based translation (VexaScribe) typically outperforms Google Translate on contextual accuracy.

Yes, up to 30 minutes of source-video-equivalent duration under our free tier — no signup, no credit card. For SRT files generated from longer videos, character/line count applies. Fully-free alternatives (TranslateSubtitles.co, GitHub batch tools) use Google Translate under the hood and give lower quality on uncommon language pairs.

Yes. The output is a standard .srt file with identical structure to the input — just translated text. Upload to YouTube Studio as a subtitle track, import into Premiere Pro (File → Import → your SRT), DaVinci Resolve (Media Pool → Import), or VLC (drag onto video). No format conversion needed.