Video Subtitle Burner

Burn SRT subtitle text directly into video frames permanently.

Tested tool guide Tested browser tools Checked August 16, 2026

What Video Subtitle Burner does, with a checked example

A subtitle file is a set of instructions; this tool turns those instructions into pixels. You upload a video and an SRT file, and each cue is drawn over its frames before the result is written out as one new video. The output has no subtitle track: the text is part of the picture, so it cannot be toggled off, and a typo means processing again. What surprises people most is that this is not a quick mux - the video must be re-encoded, so the job takes real time and the source file's quality is the ceiling for the result.

Worked example

A concrete input and expected output from the current implementation.

Input

1
00:00:01,000 --> 00:00:04,000
Hello, world.

Expected output

A new video file, same duration as the source, in which the text "Hello, world." is part of the picture from the 1-second mark to the 4-second mark - a 3.000-second window (4.000 - 1.000 = 3.000).

The timecode 00:00:01,000 --> 00:00:04,000 pins the cue to the 1-to-4-second region of the timeline, and burning draws the text into exactly those frames, permanently.

How the result is produced

Reading the SRT timeline

The file is parsed as a series of cues: a number, a timecode line in the form HH:MM:SS,mmm --> HH:MM:SS,mmm, and the text beneath it. The comma is the required decimal separator. Each cue marks a window on the video timeline, and the tool renders that text into the frames whose timestamps fall inside the window.

Why the result is permanent

Burning draws the text into the picture data of the frames that carry a cue. Compressed video cannot be edited in place, so the affected frames are re-encoded and written to a new file; the source is left untouched. The text is now pixels, not a track, so no player can hide it, and processing time scales with the length of the video.

Good uses

Sending a clip to a TV, set-top box, or web player that ignores sidecar SRT files - burning puts the captions where the player cannot miss them.
Handing someone a single self-contained file: the subtitles travel inside the video, so there is no second file to lose, rename, or let drift out of sync.
Preparing a clip for re-upload or conversion, where soft subtitle tracks are often stripped - burned text survives any container change.

Limits and checks

The burn is permanent in the output. The text cannot be turned off, resized, or corrected, so a typo in the SRT means encoding again from the source, and the picture under the subtitle band is covered for the cue's duration.
SRT timecodes require a comma as the decimal separator, written HH:MM:SS,mmm. Editors sometimes display or export milliseconds with a dot, and a timecode like 00:00:01.500 does not match the format; scan the file for dots before uploading.
A subtitle line wider than the frame cannot be displayed whole: the renderer has to wrap, shrink, or clip it. Break long lines yourself in the SRT, and check one short test burn before encoding a full-length video.

Common questions

Can I still turn the subtitles off after burning?

No - that is what burning is for. The text is painted into the frames, so the output has no subtitle track and no player setting can hide it. If you need subtitles that can be toggled or restyled, keep the SRT as a separate file or attach it as a soft track instead.

Will the output look exactly like my source video?

Not exactly. The video is re-encoded, and every re-encode loses a little detail even at high settings, plus the text covers the picture underneath it. For most clips the difference is hard to spot, but keep the original file as your master copy.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.