Free · no signup · browser-local

Burn SRT Subtitles into a Video Locally

Burn validated SRT text into a local video with English/Chinese font support, size and color controls.

Browse all tools →

Local files · native first · WASM when needed · no uploads

Files and settings

Editable sample: 12 seconds from the 2009 U.S. inaugural address, marked public domain under U.S. law. Source and license · Steve Jobs at Stanford ↗ · Jensen Huang speeches ↗

Drop local files here. Up to three clips; source size and duration follow this device’s budget above. Source up to 1080p.

Output frame
Use even dimensions. Native video: up to 1080p; WASM video: up to 720p, including portrait 720×1280. Frame captures can use up to 1080p.
Video format and quality
Bitrate is a target, not an exact file-size promise. Native supports up to 60 FPS, WASM up to 30 FPS; unsupported settings are rejected rather than silently changed.
Audio settings
Opus may require 48 kHz. MP3 at 16/24 kHz is limited to 160 kbps; use 44.1/48 kHz for higher MP3 rates.
SRT captions

Use the original complete clip timeline. 2 MiB UTF-8, 10,000 cues; burned text becomes part of the picture.

Processing method and compatibility

WASM first use loads about 32 MB from this site. Captions and watermarks may load an additional 16 MB local font. Files are never sent for server conversion.

Your video stays on your device

Start with a local file or the attributed speech sample. The preview and actual output appear here.

Supported formats depend on the device. Unsupported or damaged files get an explicit message.

Getting started

Paste or load UTF-8 SRT on the original full-clip timeline, inspect the current cue and export.

Before you use the result

Device-aware sources: 256 MiB–2 GiB per file and 1–4 hours combined, up to three clips, one video and at most one audio track, up to 1080p source. Native long outputs can use local temporary storage; WASM has separate input/output/working-memory budgets and up to 720p/30 FPS. Actual codecs, memory and storage are checked; compression is not guaranteed. UTF-8 SRT: 2 MiB / 10,000 cues on the full source timeline. Subtitles are rendered into pixels, not a removable text track.

Try an example

Use the two-cue English/Chinese example and inspect a frame where each cue is active.

How it works

Browser-native WebCodecs and Mediabunny are preferred; fixed single-thread FFmpeg WASM operations cover missing codecs and other supported tasks. Inputs and outputs are checked for dimensions, duration and expected tracks; long native results use bounded sample checks and can stream to private local temporary storage. No server conversion or arbitrary commands.

Frequently asked questions

Burn validated SRT text into a local video with English/Chinese font support, size and color controls.

How do I use Burn SRT Subtitles into a Video Locally?

Paste or load UTF-8 SRT on the original full-clip timeline, inspect the current cue and export.

Does this tool upload my data?

Inputs and files are processed in your browser. Page-view analytics do not contain your tool input.

What should I check before using the result?

Device-aware sources: 256 MiB–2 GiB per file and 1–4 hours combined, up to three clips, one video and at most one audio track, up to 1080p source. Native long outputs can use local temporary storage; WASM has separate input/output/working-memory budgets and up to 720p/30 FPS. Actual codecs, memory and storage are checked; compression is not guaranteed. UTF-8 SRT: 2 MiB / 10,000 cues on the full source timeline. Subtitles are rendered into pixels, not a removable text track.