How to Show Subtitles in Two Languages at Once

Three ways to get two languages on screen

There are three distinct approaches, and they suit different situations.

One bilingual subtitle file

Each cue contains a line in language A and a line in language B. Works in nearly every player and upload form that accepts SRT, because to the player it is just a two-line subtitle.

Two files shown together

The player loads a primary and a secondary subtitle track and draws both. Flexible, since viewers can turn either off, but only some players support it.

Burned-in bilingual text

Both languages are rendered into the picture with a video editor. Displays everywhere, but cannot be switched off and requires re-encoding the video.

For most people the bilingual file is the practical choice, because it travels: you can upload it to a video platform, load it in a desktop player or attach it in an editor without depending on a special feature. Two separate tracks shown together are better for personal study, where the viewer wants control. Burned-in text belongs to cases where the platform accepts no subtitle files at all; the trade-offs are covered in open vs closed captions.

Who actually benefits from two languages at once

Dual subtitles are a niche tool, and they help most when the audience genuinely needs both languages:

• Bilingual communities, such as a parish, a city council meeting or a cultural association where some viewers read one language and some read another, and a single upload has to serve everyone.
• Families where grandparents and grandchildren watch together but read different languages.
• Language learners at an intermediate stage who want to check a translation without pausing. For most study, though, a side-by-side transcript read at your own pace does more, as explained in learning a language with videos.
• Teachers preparing classroom material where students share a second language but differ in their first.
• Professional review, where a reviewer watches the source and translation together to spot meaning errors in context.

If the audience mainly reads one language, two lines are clutter. Separate subtitle tracks per language, which viewers choose from a menu, serve them better.

Reading load: the limit that decides everything

A single subtitle line already competes with the picture. Two languages per cue double the reading, and viewers usually read only the language they need while the other becomes visual noise. A few rules keep it manageable:

• Keep each language to one line. If either language wraps onto a second line, the cue becomes four lines and covers a large part of the frame.
• Keep cues short in time and text. A long sentence spoken over seven seconds is readable in one language and tiring in two.
• Put the languages in a fixed order and never swap them mid-video. Viewers learn where to look within seconds.
• Distinguish them visually. Italics for one language is supported by most players through the i tag in SRT; color via font tags works in some players and is ignored by others.
• Mind mixed directions. A cue pairing Arabic or Hebrew with a left-to-right language needs extra testing, described in right-to-left video localization.

Fast speech is the hardest case. A presenter who talks quickly produces long segments, and if the translation expands, the bottom line may not finish being read before the cue ends. For fast material, consider a bilingual transcript instead of bilingual subtitles.

Building a bilingual SRT from two subtitle files

The idea is simple: take the timing from one file and stack the text from both. You need two SRT files made from the same video, one in each language, with matching cues.

1. Create subtitles in the spoken language. With the subtitle generator, run the video with the spoken language selected, so the text comes back untranslated.
2. Run the same file again with the second language as the target, so you have a translated SRT.
3. Open both files side by side and compare the number of cues and the first and last timestamps. Files generated from the same recognized speech segments normally line up cue for cue, but confirm it before merging.
4. Build the merged file: for each cue, keep the number and timing line from the first file, then write the first file's text on one line and the second file's text on the next line. Leave a blank line before the next cue.
5. Optionally wrap the second language in i tags so it appears in italics.
6. Save the result as UTF-8 with a .srt extension, then load it in the player your audience will use and watch the busiest minute at full screen and on a phone.

For a short video you can merge by hand in a text editor. For anything longer, a spreadsheet is less error-prone: paste each file's text into its own column, check that row 120 in one column matches row 120 in the other, then join the columns. Some subtitle editors also include a feature for combining two files with the same time codes; check your editor's tools menu for a merge or join option.

What a merged cue looks like

Here is one cue from a hypothetical cooking video, shown line by line as it appears in the file:

Line 1

27

Line 2

00:01:42,300 --> 00:01:45,900

Line 3

Let the onions soften before adding the garlic.

Line 4

Deja que la cebolla se ablande antes de añadir el ajo.

Line 5

(blank line before cue 28)

If the cue counts differ between the two files, do not shift text up or down to make them fit. Match cues by timestamp: for each cue in the first file, take the translated cue whose time range overlaps it most. Where one file has split a sentence into two cues and the other has not, merge those two cues first so both files describe the same stretch of speech.

Showing two separate tracks instead

Some players can draw a second subtitle track at the same time as the first, which avoids merging files and lets viewers turn either language off. mpv supports this with its secondary subtitle setting, and several other desktop players offer a secondary subtitle option in their menus. VLC's stable releases have long shown one subtitle track at a time; check current release notes if you rely on it. Browser extensions for some streaming services add dual subtitles on those sites, but they work only within that service.

On your own website, WebVTT gives you more control than SRT. A custom player can show two VTT tracks and position one near the top of the frame using cue settings such as line:0, keeping the languages apart. Browsers differ in how they render several active tracks, so test in each browser you support. The format differences themselves are covered in SRT vs VTT.

Pitfalls and limits of bilingual subtitles

• Platforms label a subtitle track with one language. A bilingual file uploaded as "English" may confuse viewers and search features, so name it clearly where the platform allows a track title.
• Bilingual subtitles are not captions. Deaf and hard-of-hearing viewers need same-language captions with sound cues, ideally as their own track.
• Machine errors appear twice. A misheard name in the source line usually reappears mistranslated in the second line, so proofread the source before merging.
• Long cues stay long. Merging does not shorten anything; if the original cues are too long to read, split them first.
• Burned-in bilingual text cannot be corrected after publishing without re-exporting the video.
• Merged files are harder to update. If you later fix one language, you must rebuild the bilingual file, so keep the two single-language SRTs as your source files.

What mydubly provides for dual subtitles

Each mydubly job produces one subtitle track, as SRT and VTT, in either the spoken language or the target language you choose. For two languages you run the file twice. At 1 credit per minute with a 5-credit minimum per file, a 12-minute video costs 12 credits (1.2¢) per run, so 24 credits (2.4¢) for both. Each cue is one recognized speech segment written as a single line, and both files come from the same audio, which is what makes cue-by-cue merging practical.

mydubly does not merge the two files, does not position or style subtitles and does not burn text into the picture; the merge, styling and any burn-in happen in your own editor or player. It also cannot import an existing SRT to translate it, so both files must come from the audio. The supported languages are the same 21 for both runs, with Chinese output in Simplified characters.

Start with one short clip

Pick a two-minute clip, generate subtitles in both languages, merge them and watch the result on the smallest screen your viewers use. If two lines feel crowded there, they will feel crowded everywhere, and separate tracks or a bilingual transcript may serve your audience better.