How to Merge Two SRT Subtitle Files: A Step-by-Step Guide
Learn how to merge two SRT subtitle files: compare them by timecode, pick the best line from each, and test the result in your player.
A single person translating a short video can keep everything in their head. Add a second translator, a reviewer, a deadline, and several languages, and the project quickly gets messy. Files named final, final2, and really-final-v3 pile up. Two people fix the same line in different ways. A name is spelled three ways across the film. Nobody is sure which version went to the client.
This guide describes a calm, repeatable workflow for subtitle projects with more than one person involved. It covers the roles, the stages, the documents you need, how to name and track versions, which checks to automate, and how to reconcile different people's changes without losing good work. It complements our article on comparing subtitle translations, which focuses on choosing between two versions of a line. Here the subject is the whole pipeline.
Professional subtitle work usually passes through the same stages, whatever the size of the team.
Even a two-person project benefits from keeping these stages separate. The most common quality failure is to merge translation and review into one pass, so that the same eyes that wrote a mistake also check it.
Different projects use different job titles, but these functions need an owner.
Project owner. Decides priorities, keeps the schedule, and holds the master files. In a small team, this is whoever answers the client.
Translator. Produces the first target-language version.
Reviewer. Checks the translation against the source and the picture, and proposes changes. A reviewer should be a different person from the translator.
QC specialist. Performs the technical and consistency checks and the final playback review. In a small team, this can be the reviewer, but it should be a separate pass.
Terminology keeper. Maintains the glossary. Often the project owner or the lead translator.
One person can hold several roles on small jobs. What matters is that every function is performed on purpose, and that the final merge of changes has a single decision-maker.
A short written style guide settles hundreds of small disagreements before they happen. It does not need to be long. Cover:
If a client supplies its own guide, follow that one, and add a note about anything it leaves open.
List names, places, titles, product names, and recurring terms with the approved translation of each. Add notes such as "do not translate" or "use formal address". A glossary shared before translation starts prevents most consistency errors, and it saves the reviewer from repeating the same correction fifty times.
Give the translators everything that helps: a script, previous seasons or episodes, a description of characters and their relationships, and any prior subtitles. Context improves quality more than any tool.
Most confusion comes from files, so name them with care.
A simple pattern is: project_episode_language_stage_version.srt, for example series_s01e03_es_review_v2.srt. Always include the language, stage, and a version number that only goes up. Never edit a delivered file in place; save a new version.
A few more habits:
A review pass produces a second version of the file. Sometimes two reviewers each return their own. The question is how to merge them without losing good changes or accepting bad ones.
A side-by-side comparison does this efficiently. Load the base translation in the SRT Merger as File 1 and the reviewer's version as File 2. The tool aligns the two by timecode and shows you three kinds of rows: identical, different, and present only in one version. You skip the identical rows entirely, and go through the differences one by one, choosing the better line or editing it directly. Then save the result as a new version. To add a second reviewer, repeat with the saved file as File 1.
Some rules keep that process fair:
The same approach works to combine a human edit with an automatic first draft, as described in our guide to translating an SRT file.
A computer is better than a person at counting characters. Automate what you can, and leave the human attention for meaning.
Check for:
Subtitle editors include many of these checks, and a small script can do the rest. Run them after every merge, not only at the end.
Technical checks do not tell you whether a joke works. The reviewer's job is to compare the translation with the source and the picture.
A good review pass looks at:
Ask reviewers to give a reason for each change when it is not an obvious error. That feedback teaches the translator and prevents the same edits recurring in every episode.
Do the last check in the same kind of player your audience uses, with the final video:
Fix anything found, re-run the automated checks, and only then deliver.
Clients and viewers will find things. Treat feedback as a short, simple loop.
Everyone edits the same file. Use separate files per stage and merge deliberately.
No shared terminology. Create the glossary first, and update it during review.
Review done by the translator. Use a second person whenever you can.
Quality checks only at the end. Run them after every stage.
Lost decisions. Keep the change log.
Overwritten files. Version numbers only go up, and delivered files are never edited.
A good subtitle workflow separates preparation, translation, review, quality control, and delivery, and gives each function a clear owner. A short style guide, a shared glossary, and consistent file names prevent most disputes. Automate the mechanical checks, reserve human review for meaning and tone, and use a side-by-side merge to reconcile reviewers' versions while the project owner keeps final say. With those pieces in place, a team can deliver consistent subtitles in many languages without the chaos.
Merge your own subtitle files
Compare two .srt files side by side and save the best lines as one file. It runs in your browser, so nothing is uploaded.