You made a video people can't fully understand — different language, noisy environment, muted autoplay, accessibility needs. Subtitles fix all of it: they multiply reach, and on social feeds where sound-off viewing is the norm, they often double watch time. The catch is that "add subtitles" means two very different jobs, and picking the wrong one wastes an afternoon.

The two kinds of subtitling

Soft subtitles (a sidecar file)

The captions live in a separate .srt file next to the video. Players that support it display them on demand; viewers can switch them off. Elegant — but support is fragmented: chat apps ignore .srt entirely, most social platforms strip it, and casual viewers rarely manage the file pairing.

Hard subtitles (burned into the frames)

The captions are rendered onto the video pixels themselves. They travel everywhere the video goes — every player, every platform, every mute-button scenario. For sharing, this is almost always what you actually want. The tradeoff: they cannot be turned off, and viewers who don't need them see them anyway.

Step 1: Get the text with timing

Auto-transcription

Modern speech-to-text handles clear audio well. Editors like CapCut and Descript generate timed captions from the audio track in minutes; YouTube's auto-captions can bootstrap an .srt from an upload. Always proofread — names and jargon are where machines stumble.

Manual timing

For short clips, typing along with a simple editor is faster than fixing bad automation. The .srt format is plain text and human-editable:

1 00:00:01,000 --> 00:00:03,500 Welcome back to the channel.

Step 2: Burn them in with FFmpeg

The universal one-liner for hardcoding:

ffmpeg -i input.mp4 -vf "subtitles=captions.srt" -c:a copy output.mp4

Video re-encodes; audio passes through untouched. Make the subtitles readable with styling options — the two that matter most are font size (14–18pt equivalent at 1080p) and a subtle outline or box so captions survive light backgrounds.

The no-command-line routes

Mobile editors

CapCut (free) auto-captions and burns them in a few taps — the fastest path for phone-shot video.

Online tools

Subtitle-merger sites take video + .srt and return a captioned file. Fine for short, non-sensitive clips; think twice before uploading private footage.

Desktop editors

Shotcut, DaVinci Resolve, and Premiere all import .srt and render it in — with the bonus of visual styling control.

Step 3: Verify before you share

Check the timing on a real watch

Captions that drift half a second late feel broken. Watch the final file end to end once — the last ten seconds especially, where drift accumulates.

Read them at phone size

What looks fine on a 27-inch monitor can crowd a phone screen. Preview at actual mobile size before shipping.

Confirm they survived the platform

If you upload to a video host, check whether the player shows your burned captions (it will — they're pixels). If you relied on soft subs, verify the platform kept the .srt; most don't.

A note on sharing platforms and captions

Uploading to streaming hosts like s.pub preserves whatever is in the frames — hard captions included — across every rendition of the adaptive ladder. That is the safest chain: burn once, share anywhere, captions intact on every screen.

The takeaway

For anything you'll share, burn the captions in. Transcribe (and proofread) with the fastest tool you have, hardcode with FFmpeg or CapCut, verify timing at phone size — and your video becomes watchable by every audience, in every context, sound on or off.