How to Compare Two Subtitle Translations and Pick the Best Lines

Two translations of the same film can differ in surprising ways. They may agree on the plot but disagree on tone, on what a joke means, on how formal a character is, or even on who is speaking. If you have both files, you have a rare opportunity: you can read them side by side and build a better version than either one. But comparing translations well is a skill, and doing it without a method quickly turns into a muddle of personal preferences.

This guide gives you a practical approach. It is written for translators and proofreaders, for fans who maintain subtitle releases, and for anyone who simply wants to watch a film with the best possible text. You can follow along with the free browser tool, which shows the two files aligned by time, but the method works with any tool, and even with printouts and a pen.

Start with a clear goal

Before you read a single line, decide what the final subtitle is for. The answer changes which version wins.

• Personal viewing. You care most about natural, enjoyable reading.
• A release for others. Accuracy and consistency matter more, and you need to respect the original translators' rights.
• Language learning. You may prefer a literal translation, or you may want both versions on screen.
• Professional delivery. Follow the client's style guide exactly, including line length, reading speed, and terminology lists.

Write the goal at the top of your notes. When two versions seem equally good, the goal breaks the tie.

Choose a primary file

Pick one file as your base. This is the file you would keep if you had to choose only one, usually the more complete and more accurate of the two. In the merger it goes in the File 1 slot. Starting from a strong base means you only change lines where the other version is clearly better, which keeps the result coherent. If you start from neither, you end up with a patchwork where the voice of the subtitles changes every few minutes.

The five criteria

When two lines differ, evaluate them against the same checklist every time.

1. Accuracy

Does the line say what the character says? Check for dropped negatives, wrong numbers, mistaken names, reversed subject and object, and confusion between similar words. If you do not speak the source language, you can still spot trouble: when one translation is much shorter or longer than the other, one of them has probably added or omitted something. Look for a third source of truth, such as an official release or a transcript, if the stakes are high.

Accuracy does not mean literalness. A line that follows the words but misses the meaning is less accurate than a free rendering that carries the meaning across.

2. Naturalness

Read each candidate aloud. Would a real person say it? Unnatural phrasing usually comes from translating word by word, keeping the source language's sentence order, or using a register that does not fit the situation, like a formal phrase in a casual argument. The natural version almost always wins when accuracy is equal.

3. Register and character voice

A teenager, a judge, and a street vendor do not speak alike. Check whether each translation keeps the differences. Look at contractions, slang, swearing, honorifics, and forms of address. Be consistent within a character: if a character says "mate" in one scene, they should not turn into "my friend" in the next without a reason.

4. Terminology and names

Names of people, places, organisations, and invented terms should be spelled the same way every time. When two files disagree, pick the spelling that matches the official release, or the one you have used elsewhere, and keep a short glossary. It is surprisingly easy to introduce a second spelling by choosing the better line from each file without noticing. For a long project, searching the merged file for each key term at the end is worth the five minutes.

5. Readability and timing

A subtitle is read in a limited time. Even a perfect translation fails if viewers cannot finish it. Compare the length of each candidate with how long it stays on screen. A common professional guideline is around 17 characters per second for adult content, with lines up to about 42 characters. The more detailed rules are in our article on subtitle formatting best practices. When two versions are equally accurate, choose the shorter one if the time is tight.

A simple workflow, step by step

Here is a method that works for a feature-length film and takes a few hours at most.

1. Prepare the files. Make sure both are in sync and saved as UTF-8.
2. Load them side by side. Put the primary file first, and look at the summary of identical, differing, and unmatched rows.
3. Ignore the identical rows. There is nothing to decide. In many cases they make up a large share of the file.
4. Handle the unmatched rows next. A row that exists in only one file means the other translator skipped or merged that speech. Decide whether it is real dialogue that should be kept, or an interjection, a sound description, or a duplicate that the other translator was right to omit.
5. Work through the differing rows. Apply the five criteria in order. If a row is a toss-up, keep the primary file's version.
6. Edit where neither is right. Sometimes the best subtitle is a blend. Use the edit button to combine the best phrase from each, and fix typos while you are there.
7. Save and watch. Play the merged file against the film. Mistakes that are invisible on a table become obvious in motion.

Decision rules for common conflicts

Having a standing rule for repeated situations prevents arguing with yourself on every line.

One version is much longer. Prefer the shorter one unless it loses meaning.

Humor and wordplay. Prefer the version that creates a joke in the target language, even if it departs from the literal text. A literal translation of a pun that no longer works is a dead line.

Cultural references. Prefer the version that the audience can understand without a footnote. If a reference cannot be carried over, a brief explanation or an equivalent is better than leaving it untouched, as long as it does not take too long to read.

Profanity. Keep the intensity of the original. Softening or sharpening it changes the character.

Songs and on-screen text. These are often skipped by one translator and included by another. Decide once whether your project subtitles them, then apply the decision everywhere.

Sound descriptions. If you are producing subtitles for deaf and hard-of-hearing viewers, keep them. Otherwise, remove them for consistency.

Using both versions deliberately

Sometimes the correct answer is to keep both. For language learners, showing two translations at once, or a translation with the original language, helps with comprehension. In the merger you hold Shift while clicking to keep both versions of a row. Remember that two subtitles with overlapping times appear stacked on screen, so check that the combined text does not cover too much of the picture. For long dialogue scenes it can become overwhelming, so many learners reserve it for particular scenes.

Reviewing as a team

If two or more people work on the same file, small procedures prevent conflict.

• Assign one owner for the final merge. Others suggest changes, but one person applies them.
• Record the reasoning for hard calls. A short note such as "kept File 2: matches official name spelling" saves a repeat discussion.
• Share the glossary first. Agree on names and terms before anyone starts comparing.
• Review in two passes. First pass for content, second for timing and formatting. Mixing both leads to missed errors.
• Keep the originals. Store both source files unchanged with the merged result, so you can trace any decision back.

Respect the translators' work

Subtitle translations are creative work. Even free fan translations have authors, and many carry a licence or a request about how they may be shared. For private use you can combine whatever you like. If you plan to publish a merged file, obtain permission when needed, credit the original translators, and follow any conditions attached to the source files. If a file is based on a commercial release, remember that the underlying translation may be protected by copyright, and avoid redistributing it without the rights holder's consent.

Common mistakes to avoid

• Choosing by sound, not by sense. A lovely phrase that is wrong is still wrong.
• Switching styles midstream. Constantly alternating between a formal file and a casual file produces a confusing voice.
• Forgetting timing. A great line shown for half a second will not be read.
• Not testing. Always watch a sample of the final file in a real player.
• Overwriting originals. Always save the merged result under a new name.

Summary

Comparing translations is a series of small, repeated decisions, so having the same criteria for every line matters more than any single choice. Choose a primary file, check accuracy, naturalness, voice, terminology, and readability in that order, resolve repeated situations with standing rules, and test the result in motion. With a good side-by-side view and a consistent method, merging two translations can raise the quality of the subtitles well above either source file.

Ready to try it? Open the merge tool, load your two files, and work through the rows that differ. Or read the step-by-step merge guide first for a full walkthrough of the tool.