How to Merge Two SRT Subtitle Files: A Step-by-Step Guide

Sooner or later almost everyone who watches foreign films or works with subtitles ends up with two versions of the same subtitle track. One translation has beautiful phrasing but misses a few lines. Another is complete but stiff. A fan release fixes the jokes, while the official release gets the names right. You do not want to choose one file and live with its flaws. You want the best line from each.

This guide explains how to merge two SRT subtitle files properly: how to prepare them, how to compare them line by line, how to decide which version to keep, and how to check the finished file. You can follow every step with the free SRT Merger tool, which runs entirely in your browser, but the principles apply no matter what software you use.

What "merging" subtitles actually means

The word merge is used for two quite different jobs, and it helps to separate them before you start.

The first job is cherry-picking. You have two translations of the same dialogue. For each line or group of lines, you choose one version and drop the other. The result is a single subtitle track with exactly one line on screen at any moment. This is what translators, reviewers, and careful viewers usually want.

The second job is stacking. You keep both versions at once so that two languages appear together, for example English on top and Spanish underneath. This is popular with language learners. It is a different workflow because the result deliberately contains overlapping lines.

The SRT Merger handles both. A normal click on a checkbox selects one version and clears the other. A Shift+click selects a version without clearing the opposite side, so you can keep both for the lines where you want them.

Before you start: check that the files are in sync

Merging only makes sense when both files describe the same video at the same timing. If one subtitle file is two seconds late, or was made for a different cut of the film, no merging tool can line the two up correctly because the timecodes will never match.

Open both files in your player and compare three moments: the first line of dialogue, a line somewhere in the middle, and one near the end. If all three appear at the correct moment in both files, they are in sync. If one of them drifts, fix it first. Our guide on fixing subtitle sync problems walks through the common causes, from a simple constant delay to a frame rate mismatch.

Also check the encoding. The merger reads files as UTF-8, which is what most modern subtitle files use. If a file shows garbled characters instead of accents or non-Latin letters, convert it to UTF-8 before loading it. The subtitle encoding guide explains how.

Step 1: Load your two files

Open the online merge tool and choose your primary file as File 1. This is the file you trust more, the one you would use if you had to pick only one. Then load the alternative translation as File 2. You can use the file picker buttons or drag each file onto its box.

If you want to see how the tool behaves before using your own files, press the sample button. It loads two short made-up translations that include every situation you will meet: identical lines, lines that differ, a line that exists in only one file, and so on.

Nothing is uploaded when you load a file. The browser reads it locally, and the page never sends its contents anywhere. You can confirm this yourself by switching off your internet connection after the page has loaded. Everything will keep working.

Step 2: Understand how the files are aligned

Once both files are loaded, the tool aligns them by timecode, not by line number. This matters because two translations of the same scene rarely have the same number of lines. One translator might split a long sentence in two while another keeps it as one subtitle. Comparing line 40 to line 40 would quickly fall out of step.

Instead, the tool groups lines that overlap in time into a single row. A row can contain one subtitle on each side, several subtitles on one side against one on the other, or a subtitle on only one side. Each row gets a pair of checkboxes in the middle, one for each file.

Above the table you will see a short summary with four counts:

• Identical rows have the same timing and the same text in both files. They are greyed out and you only need to keep one copy, which the tool does for you.
• Differ rows exist in both files but the text or timing is not the same. These are the rows where you make decisions.
• Only in File 1 and Only in File 2 rows contain lines that the other file does not cover at that time.

On a typical film, the identical count is often surprisingly high, especially when both subtitles started from the same source. That is good news because it shrinks the review work to the rows that differ.

Step 3: Decide which version to keep

By default, every row that exists in File 1 is selected, so if you saved right now you would get File 1 back unchanged. Your job is to go through the rows that differ and switch to File 2 wherever it is better.

A consistent set of rules makes this much faster and keeps the result from sounding like two different people wrote it. These are the questions experienced reviewers ask:

1. Is it accurate? A mistranslated line should lose, however nicely it reads.
2. Does it sound natural? Read the line aloud. Dialogue that no person would say is a sign of word-for-word translation.
3. Is it consistent? Character names, titles, and recurring terms should be spelled the same throughout. If File 1 uses one spelling for a name and File 2 another, pick one and stay with it.
4. Is it readable in time? A long line shown for only a second is hard to read. Prefer the version that fits the time available.
5. Does it keep the tone? Humor, formality, and slang are easy to flatten. Keep the version that preserves how the character speaks.

Our longer article on comparing subtitle translations goes deeper into these criteria and includes a workflow for teams.

Using the bulk buttons

If you already know that File 2 is better overall, you do not have to tick every box by hand. The bulk buttons let you prefer File 2 everywhere, go back to File 1 everywhere, or keep both versions in every row that has both. Then you only need to correct the exceptions. Starting from the better file and fixing the exceptions is usually quicker than building up a choice row by row.

When to keep both lines

Keeping both versions of a row is useful in two cases. The first is stacking languages, as described earlier. The second is when you cannot decide and want to mark the row for later. After saving, you can search the file for the rows that appear twice and resolve them in a text editor. If you do plan to play the result with both lines showing, remember that the player will draw them on top of each other if they overlap in time, so test the look before relying on it.

Step 4: Fix small problems as you go

You will often notice a typo, a missing italic tag, or a timecode that is a few hundred milliseconds off. You do not need to leave the page. Press the Edit button in any cell, or double-click the cell, and the lines in that row turn into editable text showing the index, the timecodes, and the subtitle text. Change what you need and click outside the box to apply it. Press Escape if you change your mind.

Formatting tags such as italics are preserved. The tool displays the tags <i>, <b>, <u>, and <font> as formatting in the preview and writes them back to the file exactly as they appeared, so your styling survives the merge.

Edits apply to the merged result only. Your original files on disk are never modified.

Step 5: Save the merged file

When you are happy with the selection, press the save button. Browsers that support the File System Access API, such as Chrome and Edge, open a save dialog so you can choose the folder and name. Other browsers download a file called merged.srt to your usual downloads folder.

Behind the scenes, the tool collects every selected line, sorts them by start time, renumbers them from 1, and writes them out in standard SRT format with a blank line between entries. Renumbering matters because many players are fussy about gaps or duplicates in the index numbers.

Step 6: Test the result

Never trust a merged file until you have watched part of it. Load it in your player next to the video and check the following:

• The first and last lines appear at the right time.
• Rows where you changed from one file to the other do not show any jump in tone or spelling.
• No line is stuck on screen too long. This can happen if a row from one file with a long duration was kept next to a row from the other file with an overlapping duration.
• Special characters, accents, and non-Latin scripts display correctly.

If something looks wrong, reopen the two original files in the merger and adjust the selection. Because the originals are untouched, it costs nothing to start again.

Common problems and how to solve them

Nothing appears after loading the files. The tool could not find any subtitles in one of the files. Open the file in a text editor and check that it contains timecode lines such as 00:01:02,500 --> 00:01:05,000. Files in other formats, such as WebVTT or ASS, need to be converted to SRT first. See our comparison of subtitle formats for how.

Almost every row is marked as different. This usually means the two files are not in sync, or one of them uses a different frame rate. Fix the timing first.

The rows are huge. If one file was split into very long subtitles and the other into very short ones, the tool groups them into large rows to keep the alignment correct. That is expected. You can still choose one side or the other for the whole group.

Text looks garbled. The file is probably not UTF-8. Convert it and load it again.

A quick checklist

Before you merge: confirm both files are in sync, confirm both are UTF-8, and decide which file is your primary.

While you merge: work through the rows that differ, apply the same decision rules everywhere, and use bulk buttons to save time.

After you merge: save, play the file against the video, and keep your original files in case you want to revisit a decision.

Merging subtitles is mostly careful reading. A good tool takes care of alignment, numbering, and formatting so you can spend your attention on the part that really needs a human: choosing the words that serve the story best.

Frequently asked questions

Can I merge more than two subtitle files? Merge two at a time. Merge the first two, save the result, and then load that result as File 1 with the third file as File 2.

Will merging change the timing of my subtitles? No. Each line keeps the start and end time it had in the file you took it from, unless you edit it.

Is it legal to combine subtitles? For personal viewing, combining files you already have is generally fine. If you plan to share or publish the result, check the licence or terms attached to each original translation and credit the authors where required.