How to Translate an SRT File Without Breaking the Timing (2026)

Three ways to translate an SRT subtitle file, what goes wrong with each, and how to keep timecodes, line length and reading speed intact.

An SRT file looks simple: numbered lines of text with timestamps. Translating one seems like a copy and paste job. Then you load the result into a player and half the subtitles are missing, out of order, or too long to read.

This guide explains how to translate an SRT file properly: what the format needs, three ways to do it, and how to check the result before you publish.

What is inside an SRT file

An SRT file is plain text. Each subtitle, called a cue, has three parts and is followed by an empty line.

1
00:00:01,200 --> 00:00:03,800
Thanks for joining us today.

2
00:00:04,000 --> 00:00:06,500
Let's start with the numbers
from last quarter.

The first line is the cue number. The second is the start and end time. The rest is the text, on one or two lines.

Only the text should change when you translate. If the numbers, the timestamps, the arrow or the empty lines are altered, players either skip the cue or refuse the file.

Method 1: Paste it into a general translator

The quickest approach is to paste the whole file into a general translation tool.

It sometimes works for short files. The problems appear fast:

  • Timestamps get edited. Translators may change the comma to a period, add spaces around the colons, or translate the arrow.

  • Empty lines disappear. Without them, cues merge into each other.

  • Each line is translated alone. A sentence split across two cues becomes two fragments that do not connect.

  • Length is ignored. The translation can be much longer than the original and no longer fits on screen for the time available.

Use this only for a quick personal look at a short file, and check the structure afterwards.

Method 2: A subtitle editor with built-in translation

Desktop subtitle editors such as Subtitle Edit open the file as a table, keep the timing locked, and send only the text to a translation engine.

This solves the structure problem. Timestamps and numbering stay intact, and you can fix lines by hand next to the original.

What it does not solve is quality. The text is still translated cue by cue, so split sentences, tone and names are handled poorly. Expect to edit a lot. It is a good option if you are comfortable with desktop software and plan to review every line anyway.

Method 3: An AI subtitle translator

An AI subtitle translator reads the file as a conversation instead of a list of separate lines. It keeps the timing, and it translates each cue knowing what was said before and after.

With our subtitle translator, the steps are:

  1. Upload your .srt or .vtt file.

  2. Choose the target language. More than 20 are supported.

  3. Add a glossary if the video has names or product terms that must stay the same.

  4. Download the translated file.

The free preview translates the first three minutes of the file, with no credit card. After that you pay by the minute, based on the runtime of the subtitles. Details are on the pricing page.

If you have a video but no subtitle file yet, the subtitle generator creates one from the audio, and you can paste a YouTube link instead of uploading.

Why line-by-line translation reads badly

Subtitles are cut for timing, not for grammar. A single sentence is often spread over two or three cues:

14
00:01:10,000 --> 00:01:12,400
What we found, after testing

15
00:01:12,500 --> 00:01:15,000
for almost six months, was surprising.

Translated separately, the first cue has no verb and the second has no subject. In languages with a different word order, such as Japanese, German or Korean, the pieces come out in the wrong places.

Good subtitle translation works on the full sentence and then divides the result back across the same cues. We wrote more about this difference in Why Subtitle Translation Isn't Video Translation.

Rules for subtitles people can actually read

A correct translation can still fail as a subtitle. These are the common guidelines used in professional subtitling:

  • Two lines at most per cue.

  • About 42 characters per line for languages written in Latin script. Fewer for Chinese, Japanese and Korean.

  • A comfortable reading speed. Roughly 17 to 20 characters per second for adult viewers. If a cue is on screen for two seconds, about 40 characters is the limit.

  • Break lines at natural points. After punctuation or before a conjunction, not in the middle of a name.

  • Do not change the timing. If the translation is too long, shorten the wording.

Translations into Spanish, French or German are often 15 to 30 percent longer than English. That is the most common reason a translated file feels rushed. The same effect causes problems in dubbing, which we cover in Why AI Dubs Run Long.

SRT or VTT?

Both carry the same information. The differences are small:

  • SRT uses a comma in timestamps and has no header. It is accepted almost everywhere, including YouTube and most editors.

  • VTT starts with a WEBVTT line, uses a period in timestamps, and supports styling and positioning. It is the standard for web players.

If you are unsure, use SRT. If your web player asks for VTT, convert at the end. The text and timing are the same.

How to check a translated file

You can catch most problems without speaking the target language.

  1. Open it in a text editor. Confirm that every cue still has a number, a timestamp line and an empty line after it.

  2. Compare the cue count. The translated file should have the same number of cues as the original.

  3. Check the encoding. Save as UTF-8. If accented letters or Asian characters show up as question marks or odd symbols, the encoding is wrong.

  4. Play it with the video. Load both in a player such as VLC and watch a few minutes from the start, the middle and the end. Timing drift usually shows up late in the file.

  5. Look for long cues. Anything with three lines, or two full lines on screen for under two seconds, needs shortening.

  6. Check names and numbers. These are where automatic translation makes the errors that matter most.

For a fuller review process, see How to Review and Edit AI Dubbing Translations.

Adding the translated file to YouTube

In YouTube Studio, open the video, go to Subtitles, add the language, choose to upload a file, and select the option that includes timing. Do this for each language. Viewers then see the language in the captions menu.

If you want audio in that language as well, the same translation can be turned into a dub. See AI dubbing or, for YouTube videos, the YouTube video translator.

FAQ

Can I translate an SRT file for free?
General translators and desktop editors are free. Our subtitle translator gives 5 free previews, each covering the first three minutes of a file, then charges by the minute.

Will the timing change after translation?
It should not. Only the text changes. If timing shifted, the tool edited the timestamp lines and the file needs fixing.

Why are some subtitles missing after I translated the file?
Usually an empty line between cues was removed, or a timestamp was altered. Players skip cues they cannot read.

Can I translate a VTT file the same way?
Yes. The structure is nearly identical, and our tool accepts both.

How do I translate subtitles if I only have the video?
Generate the subtitles from the audio first, then translate them. Both steps can be done from the video file or a YouTube link.

Which languages can I translate into?
More than 20, including Spanish, Portuguese, Japanese, Korean, Chinese, French and German.