Translate an SRT file while preserving its timecodes

Separate editable text from structural lines

An SRT block contains a cue number, a timestamp line, subtitle text, and a blank separator. Translation should change the text, not the sequence number or timestamp punctuation. A comma separates milliseconds in SRT. Replacing it with a decimal point or translating the arrow can make a file unreadable to a player.

The following prepared example shows one valid block. If you translate “Start with a small piece of clay.” into another language, retain the first two lines and the blank line after the block. A multiline caption is still one cue, not a reason to add a new number.

1
00:00:02,000 --> 00:00:06,000
Start with a small piece of clay.

2
00:00:08,000 --> 00:00:10,000
Center the clay.

Use a subtitle editor or a tool that accepts real SRT input

For an existing file, choose software that exposes a text column separately from the timing column. Duplicate the original file before editing and keep a source-language copy for comparison. If a translation tool accepts SRT, confirm that its output is still an SRT file, not a prose summary with timestamps omitted.

When using a text translation system, handle a small group of complete blocks at a time and explicitly preserve cue numbers and timestamp lines. Compare the returned structure against the original before continuing. Do not paste confidential subtitles into a service until you have checked its processing and retention terms.

Validate more than the cue count

An equal number of cues is a useful first check, but it does not establish a correct translation. Confirm that cue identifiers remain in order, each start precedes its end, the timecodes match the original, and blank separators are present. Then compare the actual line text for omissions or accidental duplication.

Look for formatting mistakes around quotation marks, literal arrows, extra markup, or automatically inserted explanations. Save as UTF-8 when the destination supports it. Reopen the file to ensure accented characters and Chinese or Japanese text were not damaged by an encoding conversion.

Test timing and readability with the video

Attach the translated SRT to the same video in a compatible player. Check a cue at the beginning, middle, and end, then watch the longest translated sentence. A translation can be too long for a cue even when every timecode is preserved exactly. Shorten the wording carefully or adjust cue boundaries in the editor if the task permits it.

If the original SRT was already out of sync, translation will preserve that problem. Correct timing against the video separately, and do not attribute the timing change to translation quality. Keep a copy of both files so you can tell which changes were structural and which were linguistic.

When to use ClipLocale instead

Use ClipLocale when your starting material is a video with speech and you need to generate subtitles before translating them. The browser extracts audio, online processing creates and translates cues, and you can edit and export SRT/VTT. English, Chinese, Spanish, and Japanese are the current language choices.

If you only need to translate an existing SRT, use the file workflow above. Re-transcribing a video can change wording, cue boundaries, and timing; it is not a faithful replacement for translating an established subtitle file. For bilingual output, keep both language lines in each cue and test the result on a small screen.