How to compare two subtitle drafts before publishing

You have two subtitle drafts and need to decide what changed before one goes live. A quick scan can miss a shifted timestamp, a dropped cue, or a small wording change that affects meaning.

Use Text Compare to spot differences, then check the subtitle structure and watch the changed sections with the video. The comparison is a review aid, not a substitute for checking how the captions appear on screen.

Compare the drafts

Open Text Compare. Put the earlier approved draft on one side and the candidate for publication on the other. Keep the original files unchanged so you can return to them if needed.
Use the same subtitle format for both drafts when possible. If the files are SRT or WebVTT, compare the exported text without removing timestamps, cue numbers, blank lines, or markup. Those details can affect playback.
Review the marked differences from the beginning to the end. For each change, decide whether it is an intentional edit, a timing adjustment, a formatting change, or an unexplained difference.
Check each changed cue against the audio and picture. Confirm that the words match what is spoken, the caption appears at the right moment, and a speaker label or sound description has not been lost.
Preview the candidate in the publishing platform or the player used for final quality checks. Look at the changed passages, plus the cue before and after each one, then save the approved file with a clear version name.

For a useful comparison, make sure both drafts cover the same section and use the same line breaks where practical. If one version has been rewrapped or exported in a different format, the comparison may show many changes that do not alter the spoken text. Keep that in mind before treating every marked line as an editorial revision.

What the differences mean

Words or punctuation changed

A changed word may correct a name, improve grammar, or alter the meaning. Compare it with the audio and the approved script where available. Check punctuation in context: a comma, question mark, or speaker label can change how a line reads even when the words are the same.

Timestamps changed

A timestamp change may be a deliberate cue adjustment, or it may move a subtitle too early or late. Check the start and end against the spoken phrase. Also look for a cue that now overlaps the next one or stays on screen after the speaker finishes.

Many lines changed at once

A large block of differences can mean someone revised several captions, but it can also mean the drafts use different line breaks or file conventions. Compare a few cues in detail before accepting the whole block. If the text is identical but the wrapping differs, review the final display rather than judging it only by the comparison.

A cue number or formatting line changed

In SRT, cues usually have a number followed by a timestamp line. WebVTT starts with WEBVTT and uses a period before milliseconds in its timestamps. A missing number, separator, blank line, or formatting tag can make a cue render incorrectly, depending on the publishing system. Preserve the format the project requires.

How to fix common subtitle differences

Confirm which draft is the source of truth. Check the filenames, revision notes, or approval record before copying a change. Do not assume the newer-looking filename is the approved version.
Correct unexplained wording changes. Compare the disputed phrase with the audio and the project script. Restore the approved wording or get confirmation from the editor if the change affects meaning, names, or claims.
Repair timing in the subtitle editor. Adjust the cue against the spoken audio, then check the cue before and after it. Avoid changing timestamps in bulk unless you know every affected cue needs the same offset.
Restore the required file structure. Export again in the format requested by the publisher if cue numbers, timestamps, blank lines, or markup look damaged. Avoid removing punctuation or formatting through a broad find-and-replace operation.
Check encoding if characters look wrong. If accented letters or symbols appear as question marks or scrambled characters, export a fresh copy from the source project using the delivery format requested by the publisher. Recheck the exported file before replacing the approved version.
Run a final playback check. Preview the complete file if possible. At minimum, review every changed passage and scan the start and end of the subtitle track for missing or extra cues.

Why a clean comparison is not final approval

Text comparison can reveal that two files differ, but it cannot tell you whether a line is accurate, easy to read, or synchronized well with the scene. A timestamp can be valid in the file and still feel late to a viewer. A line can match the script but be too long to read comfortably before it disappears.

Check the platform's subtitle requirements before delivery. These may specify SRT or WebVTT, character limits, line counts, speaker labels, or how sound descriptions should appear. Keep one approved master file, record the version you reviewed, and make later edits in a copy so the publishing handoff stays traceable.