Bilingual Subtitle Splitter

The Bilingual Subtitle Splitter takes a dual-language subtitle file and separates it back into two single-language tracks. You paste the combined file into the Dual-sub SRT Content box and the tool returns one plain-text result containing two complete SRT blocks, labelled "=== Language 1 ===" and "=== Language 2 ===", which you can copy out individually. Because the output holds two files at once it downloads as a .txt rather than a .srt.

The need shows up whenever a bilingual file arrives and only one language is wanted. A vendor delivers a combined Spanish-and-English track but the platform spec calls for separate language files. A learner's dual-sub download needs the target language on its own for a re-watch. A localisation manager wants to send the translated lines alone to a proofreader without the source distracting them. Retyping or manually deleting one line from every cue across an hour-long programme is exactly the kind of work that introduces errors around the cues where one language is missing.

The split is line-based and matches how dual-sub files are actually built. Each cue's text is divided at its line breaks: the first line becomes the language 1 cue, and every remaining line joined back together becomes the language 2 cue. Both output tracks keep the original start and end times for every cue, and both preserve the full cue sequence, so the two files stay in step with each other and with picture. A cue that only ever had one line yields text in language 1 and an empty cue in language 2, which makes gaps in the second language visible instead of shifting everything up by one.

This is the exact inverse of the bilingual merger, and like it, everything runs in your browser with no upload.

• Both languages in one run: A single action produces two complete SRT blocks, clearly headed as Language 1 and Language 2, so you do not have to process the file twice.
• First-line and remainder rule: The top line of each cue goes to language 1 and everything below it is rejoined for language 2, which correctly handles a lower language that wraps onto two lines.
• Timings duplicated intact: Every cue in both outputs carries the original start and end times, so each single-language file is still frame-accurate against the same picture.
• Cue sequence preserved: Both outputs contain the same number of cues in the same order as the input, which keeps them aligned with each other for later comparison.
• Gaps stay visible: A cue with only one line produces an empty cue in language 2 rather than pulling the next cue's text up, so missing translations are easy to spot.
• Single-field operation: The only control is the Dual-sub SRT Content box and a run action, with nothing to configure incorrectly.
• Exact inverse of the merger: Files produced by the bilingual merger split back cleanly into their original two tracks.
• Local processing: The dual-sub file is parsed in your browser and never uploaded.

1. Paste your combined two-language file into the Dual-sub SRT Content box, or click Load sample to see the layout the splitter expects.
2. Check that the language you want as Language 1 really is on the top line of each cue, since the split is positional rather than based on detecting the language.
3. Run the splitter; there are no options, because the first line and the remainder define the two tracks.
4. Scroll to the "=== Language 1 ===" heading and copy everything between it and the "=== Language 2 ===" heading into a new file, saving it with an .srt extension.
5. Copy the block below the "=== Language 2 ===" heading into a second file, and check it for empty cues, which mark places where the source had only one line.
6. Download the combined result as a .txt if you want a record of both tracks together, then load each saved .srt against picture to confirm the timing is right.

Example 1 - separating an English and French dual-sub. One combined cue becomes one cue in each output track, sharing the same timecode.

Input
1
00:00:01,000 --> 00:00:03,000
Hello, how are you?
Bonjour, comment allez-vous ?

Output
=== Language 1 ===

1
00:00:01,000 --> 00:00:03,000
Hello, how are you?

=== Language 2 ===

1
00:00:01,000 --> 00:00:03,000
Bonjour, comment allez-vous ?

Example 2 - a cue where the translation is missing. If cue 14 contained only the English line, language 1 gets that line and language 2 gets cue 14 with the correct timecode but no text. Every later cue keeps its original number in both files, so the two tracks remain directly comparable and you know exactly which cue needs a translator's attention.

• Meets single-language delivery specs: A bilingual file that a platform would reject becomes two compliant tracks in one step.
• Saves hours of manual deletion: Removing one line from every cue of a long programme by hand is slow and error-prone, and this does it exactly.
• Keeps both files in sync: Shared timecodes and matching cue numbers mean the two outputs stay comparable with each other and accurate against picture.
• Highlights missing translations: Empty cues in the second track point straight at the places where a translator skipped a line.
• Cleaner review packets: Proofreaders can be sent only the language they are checking, without the other language competing for attention.
• No upload of client files: The separation happens in your browser, so vendor deliveries and unreleased translations stay confidential.