What an SRT file actually is
An .srt file is plain text: a cue number, a timecode line such as 00:01:02,500 --> 00:01:05,000, one or two lines of dialogue, then a blank line. Nothing else. That simplicity is why every player, YouTube, Vimeo and Premiere accept it — and why it is so easy to corrupt while translating.
Translation should change only the dialogue lines. If a tool touches the numbers, the arrows, the comma-millisecond format or the blank lines, the file either stops loading or drifts out of sync.
Option 1 — an AI subtitle translator (recommended)
Tools built for subtitle files parse the cues, send only the text for translation, and write the result back into the original structure. The good ones also feed the previous cues as context, so a sentence split across two cues is translated as one thought, and they keep lines under about 42 characters so nothing overflows on screen.
SubFlip does this in the browser: the file is parsed locally, only cue text goes to the model, and you get the same .srt back with identical timecodes. The first file each day is free, so you can check the quality on your own file before paying anything.
Option 2 — Google Translate the whole file
Google Translate's document mode accepts .txt but not .srt; renaming the file works, but the output often merges lines, translates the arrow line or drops blank lines. It also translates cue by cue with no context, so pronouns and half-sentences come out wrong. Fine for a quick gist, not for publishing.
Option 3 — paste into a chatbot
ChatGPT-style tools produce good prose but are unreliable with structure: they renumber cues, reflow long files, and stop halfway on files over a few hundred cues. If you go this route, paste in small batches, tell it explicitly not to touch timecodes, and diff the result. For a 30-minute video that is an hour of work.
Option 4 — Subtitle Edit with auto-translate
Subtitle Edit (Windows) has an auto-translate menu using Google or DeepL. It preserves structure well, but translation quality is machine-translation level, and you need a desktop install and, for DeepL, your own API key. Good for professionals who already live in Subtitle Edit.
Checklist before you upload
Open the translated file in a text editor: cue count identical, first and last timecodes identical, no line longer than ~42 characters, encoding UTF-8. Then load it in VLC or YouTube Studio and scrub to the last minute — if it is still in sync there, it is in sync everywhere.
Tools mentioned
Questions
- Does translating change the subtitle timing?
- It should not. Timecodes describe when a cue shows, not what it says. A proper subtitle translator rewrites only the text; if your timing changed, the tool re-serialized the file badly.
- Which languages can an SRT be translated into?
- Any language the translation model supports — SubFlip handles 36, including right-to-left Arabic and CJK languages with shorter line limits.
- How much does it cost?
- SubFlip: first file free daily, then 10 credits for $4.99. One credit is one file up to 1,000 cues in one language.