Forced Subtitles Explained: Translating Only the Lines Viewers Can't Follow

What forced subtitles are for

Picture an English-language thriller where two characters briefly argue in Russian. English-speaking viewers watching without subtitles still need to know what was said, so the film shows English text for that scene only. Those lines are forced subtitles: they are part of the intended viewing experience, not an optional accessibility or translation layer.

The same idea applies far outside cinema. A travel vlog in English that includes a conversation with a market vendor in Spanish, a documentary interview with a witness speaking Arabic, or a corporate video where a regional manager speaks in Japanese all have stretches that most of the audience cannot follow. A forced track covers just those stretches.

Forced subtitles are always written in the main language of the version being watched. If the thriller is dubbed into German, the German version needs its own forced track in German for the Russian scene, unless the dub has a different plan for that dialogue.

What belongs in a forced track, and what doesn't

Include:

• Dialogue in a language other than the main language of the version.
• On-screen text that carries meaning and is in another language: a letter, a sign the plot depends on, a text message shown in close-up.
• Lines the story intends the audience to understand, even if characters on screen do not.

Leave out:

• Ordinary dialogue in the main language. That belongs in the full subtitle or caption track.
• Foreign speech the film deliberately leaves untranslated, for example to put the viewer in a character's confused position. That is an editorial decision, not an omission.
• Sound descriptions and speaker labels, which belong in caption tracks for deaf and hard-of-hearing viewers.

The full subtitle track for the same language should also contain the forced lines, so a viewer who turns on full subtitles does not lose them.

How forced subtitles are flagged in MKV, MP4 and streaming

There is no forced flag inside an SRT or VTT file. Forcing is a property of the track in the container or the playlist, not of the cues.

MKV

Each track header has a forced flag alongside the default flag; tools such as MKVToolNix set it when muxing

MP4 and MOV

No single, universally honoured equivalent. Apple's timed-text tracks support forced subtitles, and tools such as ffmpeg can mark a forced disposition, but player support varies

Blu-ray and DVD

Disc subtitle formats carry their own forced-display flags, which is why disc rips sometimes produce a separate forced track

HLS streaming

Subtitle renditions in the master playlist can be marked as forced

Sidecar files

Many media servers and players recognize a forced marker in the file name, such as film.en.forced.srt

Video platforms are less consistent. Many upload flows have no forced option at all, so a forced track either becomes the only subtitle track for that language or the lines are burned into the picture as open subtitles. The trade-offs of burned-in text are covered in open vs closed captions.

How players decide when to show them

Player behaviour is the weak link. Typical logic in desktop players and media servers is: if the viewer has not chosen a subtitle track, and a forced track exists in the language of the selected audio, show it. Some players honour the forced flag only on embedded tracks, some only on file-name markers, and some ignore it unless a setting is enabled. Televisions and streaming sticks vary again.

That means you cannot assume a forced track will appear. Test with subtitles off on every player your audience is likely to use, and decide in advance what happens where forcing is not supported: burn in the forced lines, or accept that some viewers will need to switch the track on.

Building a forced track from a full translated SRT

For a mixed-language video, the least error-prone method is to produce a complete translated subtitle file in the viewer's language and then remove everything that does not need forcing. Timing for the foreign lines is already done, and you only delete.

1. Produce a full subtitle file in the viewer's language for the whole video. Lines that were already in that language will come through essentially unchanged.
2. Identify the foreign-language stretches. A timestamped transcript in the spoken language makes this quick: scan for passages in the other language and note their start and end times.
3. In a subtitle editor, delete every cue outside those stretches. Most editors renumber the remaining cues automatically; the mechanics of editing cues are covered in how to edit an SRT file.
4. Review each remaining line with a fluent speaker of the foreign language, since these few lines carry the whole meaning of the scene.
5. Add cues by hand for any foreign on-screen text that matters, timed to when it is visible.
6. Watch the video with only the forced track enabled and confirm every foreign line is covered and nothing else appears.

Speech recognition tools that detect the spoken language automatically can handle code-switching inconsistently, so short foreign phrases may be transcribed in the wrong language or skipped. Why that happens, and workarounds such as splitting the file, are explained in translating videos with mixed languages.

Naming, muxing and delivering a forced track

• Name sidecar files clearly, for example episode-04.en.forced.srt next to episode-04.en.srt, if your player or media server recognizes that convention.
• For MKV, mux the forced track with its language set and the forced flag on, and keep the full subtitle track as a separate, non-forced track.
• For MP4, test the exact players you care about; if they do not honour forcing, consider burning in the forced lines in an editor.
• For streaming delivery, follow the distributor's spec, which may call the track a forced narrative and set its own rules for language tags and on-screen text.
• For platforms without forced support, decide between burned-in forced lines and a clearly named optional track. Attaching files to common platforms is covered in how to add subtitles to a video.

Common mistakes and limits

• Leaving forced lines out of the full subtitle track, so viewers with subtitles on miss the foreign dialogue.
• Forgetting on-screen text, especially signs and messages that the plot depends on.
• Flagging the full subtitle track as forced, which forces every line on viewers who wanted none.
• Relying on the forced flag without testing; many players handle it differently or not at all.
• Trusting machine translation of the few foreign lines without review. They are short, which makes errors stand out.
• Building forced tracks for every language version at once before the source version is locked. Edits to the picture shift cue times in every file.

How mydubly fits into a forced-subtitle workflow

mydubly can supply the raw material: a full SRT or VTT in the target language, with one numbered, single-line cue per recognized segment, and a translated transcript job gives the transcript in both languages, including a timestamped version with [m:ss] labels for finding the foreign stretches. The spoken language is detected automatically, so check the foreign passages carefully in mixed audio.

The rest happens elsewhere. mydubly does not flag tracks as forced, does not mux subtitles into the video, and does not burn text into the picture; the translated video it assembles contains no subtitle track. It also translates speech only, not on-screen text, so the cues for signs or letters must be written by hand, as described in translating on-screen text in videos. If you dub a mixed-language video, every recognized line is voiced in the target language by one stock voice and the original voices are removed, so the contrast of a foreign-language scene is lost; subtitles keep it.

Next step: try it on one scene

Pick a video with a short foreign-language passage, generate a full translated subtitle file with the subtitle generator, and trim it to that passage. Test the result with subtitles switched off in the player your audience uses most; that single test tells you whether to rely on a forced flag or burn the lines in.