SRT Subtitle Merger

Use the SRT merger to combine caption files for consecutive video parts or pair two already aligned subtitle languages. Sequential mode shifts later files onto the preceding part’s subtitle end time, with an optional gap. Bilingual mode joins the text of matching cues while keeping the first file’s timing. The SRT merger previews the combined cues and downloads one SRT file. These modes solve different problems: choose deliberately, because joining dialogue is not the same as discovering video duration or aligning unrelated translations.

How to use the SRT merger

1. Select the required SRT files in their intended order. Sequential mode needs at least two; bilingual mode needs exactly two.
2. Choose Merge mode: sequential or bilingual.
3. For sequential parts, enter a nonnegative Gap between parts (milliseconds). Set Input encoding when required.
4. Select Process files, inspect the new cue times and download subtitles.srt.

Try an example loads two small samples automatically. For a real merge, check the selected filename order before processing; the first chosen file supplies the first subtitle part or the first language line.

Sequential merging uses caption ends, not video lengths

The SRT merger preserves the first part’s cue times. For each subsequent part, it adds the previous accumulated offset plus the last caption end from the preceding part and the chosen gap. Cue numbering is regenerated in the exported file. The source video is not loaded, so its actual duration is not measured.

This distinction matters when a video continues after its final caption. A 10-minute clip might have its last spoken line at 9 minutes 40 seconds. With no additional gap, the next subtitle part is positioned from that 9-minute-40-second endpoint. Account for uncaptained tails and transitions yourself, then verify the result against the combined video.

Worked example: where the second part starts

Suppose the first file’s last cue ends at 00:00:03,500, and the second file’s first cue starts at 00:00:01,000. With sequential mode and a zero gap, the second cue starts at 00:00:04,500. A gap of 500 milliseconds moves that start to 00:00:05,000.

The built-in example demonstrates this behavior with short matching dialogue samples. It is intentionally small so the offset is easy to inspect. For a longer recording, examine the join and several cues near the end in your player; a mathematically consistent caption merge can still be wrong for the actual edit if the supplied gap is wrong.

Bilingual merging requires existing cue alignment

Bilingual mode expects both files to contain the same number of cues. Each paired cue’s start and end must be within 100 milliseconds of the corresponding cue in the other file. The first file’s timing is retained, and its text is followed by the second language on a new line.

The SRT merger rejects mismatched files instead of guessing which translation corresponds to each line. It does not translate dialogue, perform dynamic alignment, combine unequal cue groups or synchronize subtitles from different video edits. Prepare aligned source files in a subtitle editor when one language splits a sentence across more cues than the other.

Preserve readable text and check overlaps

Supported SRT text and multiline dialogue are retained through the cue export. However, not every player displays all SRT formatting extensions identically. A bilingual result can also be too tall or too dense for comfortable playback even when its timing is valid. Check long cues on the screen size where the subtitles will be watched.

Overlaps are reported as warnings and retained, because simultaneous speakers can legitimately overlap. This SRT merger does not automatically resolve overlap by shortening or deleting dialogue. Use the subtitle repair tool for its supported separator and numbering cleanup, then reconsider timing in the source editor if the overlap is unwanted.

Choose the right task before combining captions

A uniform time offset is better handled by the SRT timing tool, which also supports its documented synchronization controls. If you only need readable dialogue from several files, first decide whether a timed merge is necessary; the SRT to TXT converter produces a different output for transcript review.

Do not mix two independent tasks without checking the intermediate result. For example, repair a malformed cue before merging it, and verify each part’s encoding before combining multilingual text. A merger cannot recover missing accents or infer the recording’s correct frame rate from subtitle text alone.

Troubleshooting and validating the download

Malformed SRT timing, an end before a start, empty files, a negative gap or unsuitable bilingual alignment can stop processing. Check the original cues and controls rather than renaming the file extension. For large collections, respect the displayed per-file limit and the bounded cue count, and test the part order on a small group first.

The source captions remain on your device during processing. Download the combined SRT, keep both originals, and test playback at every join or language pair that matters. Use Clear files and results after confidential work on a shared device. The SRT merger joins a supported timeline; final synchronization still needs the actual video.

Common SRT merger errors and how to fix them

When the SRT merger cannot use a file, it stops with one clear message instead of producing a half-finished download. These are the problems people run into most often, with the fix for each:

• Choose files before processing. Merging needs at least two SRT files.
• Bilingual files must have equal cue counts and timing within 100 ms. Bilingual mode stacks matching cues. If one language was retimed or split differently, use sequential mode or align the files first.
• A subtitle ends before it starts. A cue has an end time earlier than (or equal to) its start time, often from a typo such as 00:01:05 written as 00:00:65 or swapped times. Correct that cue in a text editor and process the file again.
• Enter valid subtitle times or a finite shift. The gap between parts must be zero or a positive number of milliseconds.

Privacy: the SRT merger runs in your browser

SRT merger processing happens with JavaScript in a background worker on this page. Your file is not uploaded to a FileFix server, and the results you download are created in your browser’s memory. Unreleased video scripts and captions stay on your computer. When you finish on a shared computer, clear the selection or close the tab.

For the underlying format rules, see the Library of Congress description of SubRip (SRT). The SRT merger follows the subset described on this page rather than every optional feature in those documents.

Sources

• Library of Congress description of SubRip (SRT)

Questions about this tool