Subtitles and Captions: The Complete SRT Guide for 2026

Let's talk about subtitles. Not the automatic YouTube garbage that thinks "their" and "they're" are the same word, but real, properly-timed, human-readable subtitles that make your videos accessible and watchable.

Whether you're a YouTuber trying to reach international audiences, a course creator making content accessible, or just someone who wants to add captions to family videos (because Uncle Bob mumbles), you need to understand subtitle files. And in 2026, SRT is still king.

What exactly is an SRT file?

SRT stands for SubRip Subtitle. It's a plain text file with a .srt extension that contains your subtitles in a specific format. Here's what one looks like:

1
00:00:01,000 --> 00:00:03,500
Welcome to the world of subtitles.

2
00:00:03,750 --> 00:00:06,200
This is how they work.

3
00:00:06,500 --> 00:00:09,000
Simple, right?

Each subtitle entry has four parts:

• Sequence number — just counts up (1, 2, 3...)
• Timecodes — when the subtitle appears and disappears
• The actual text — what viewers read
• A blank line — separates each entry

That's it. No XML markup, no proprietary format, no bloat. Just text and timestamps. That's why SRT files are so popular — they work everywhere, they're easy to edit, and they're tiny (a 2-hour movie's subtitles are usually under 100 KB).

Subtitles vs. closed captions (yes, they're different)

People use these terms interchangeably, but they're not the same thing.

Subtitles are meant for viewers who can hear the audio but don't understand the language. They translate dialogue. That's it. You're watching a French film? Subtitles give you English translations of what the actors are saying.

Closed captions (CC) are for viewers who can't hear the audio at all. They include dialogue, sure, but also sound effects, speaker identification, and music descriptions. "[door creaks]" and "[ominous music playing]" — that's CC territory.

So if you're making accessible content (which you should be), you want closed captions, not just subtitles. And yes, SRT files can do both — it's about what you write in them, not the file format itself.

How to create SRT files (the practical guide)

You've got a few options here, depending on your patience and budget.

Option 1: Write them by hand

Open Notepad (Windows), TextEdit (Mac), or any plain text editor. Watch your video, pause at key moments, and write out the timecodes and text. Save the file with a .srt extension.

This works. It's tedious. But if you've got a short video (under 5 minutes), it's doable. Just make sure you save as UTF-8 encoding, not some weird legacy format.

Option 2: Use a subtitle editor

Tools like Subtitle Edit (free, Windows), Aegisub (free, cross-platform), or Subtitle Workshop make this way easier. You load your video, type captions, and the software handles timecode formatting. You can adjust timing visually instead of typing 00:04:32,750 manually.

If you're doing more than one video, this is the way.

Option 3: Auto-generate and fix

YouTube, Descript, and tools like Otter.ai or Simon Says can auto-generate subtitles from your video's audio. The accuracy is... variable. If your audio is clean and you speak clearly, you might get 90% accuracy. If there's background noise, accents, or technical jargon, expect to spend time fixing errors.

But even with corrections, it's faster than starting from scratch. Generate, export as SRT, then clean it up in a subtitle editor.

Embedding subtitles: soft subs vs. hard subs

Here's where people get confused.

Soft subtitles (external files) are separate SRT files that sit next to your video. The video player loads them when needed. Viewers can toggle them on/off, switch languages, and customize appearance. Most platforms (YouTube, Vimeo, streaming services) use soft subs.

Hard subtitles (burned in) are permanently embedded into the video itself. You can't turn them off. You can't change the font. They're part of the video image. This is what you see on most social media videos (TikTok, Instagram Reels) where captions are always visible.

So which should you use?

Use soft subs when you want flexibility. Multiple languages? Soft subs. Accessibility options? Soft subs. Professional streaming? Soft subs.

Use hard subs when you need guaranteed visibility. Social media videos where people scroll with sound off? Hard subs. Videos you're sending to someone who might not know how to enable captions? Hard subs.

To burn subtitles into video, you can use tools like FFmpeg, HandBrake, or online services. If you need to convert video formats with embedded subtitles, make sure your converter supports subtitle burning.

Subtitle format wars (SRT vs. VTT vs. ASS)

SRT isn't the only subtitle format out there. Let's compare:

SRT (SubRip) — The standard. Works everywhere. Simple. Limited styling options (basically just text).

WebVTT (.vtt) — HTML5 standard for web video. Supports styling, positioning, and metadata. Used by YouTube, Vimeo, and most web players. Very similar to SRT but with extra features.

ASS/SSA (Advanced SubStation Alpha) — The power user format. Full control over fonts, colors, positioning, animations. Anime fansubbers love this format. Overkill for most use cases.

TTML (Timed Text Markup Language) — XML-based. Used in broadcast and streaming. Complex. You probably don't need this unless you're working with Netflix or TV networks.

For 99% of use cases, stick with SRT or WebVTT. They're simple, widely supported, and good enough.

Platform-specific subtitle requirements

Different platforms have different rules. Here's the quick guide:

YouTube — Accepts SRT, VTT, and a few others. Auto-sync feature can fix timing if your file is slightly off. Supports multiple languages. Max 5,000 characters per caption.

Vimeo — Prefers VTT but accepts SRT. Clean interface for uploading and editing. Can auto-generate captions on paid plans.

Facebook/Instagram — Accepts SRT files. Auto-captions available but you should review them. Many creators just burn captions directly into video for guaranteed visibility.

TikTok — Auto-generates captions. You can't upload SRT files directly, but you can edit the auto-generated text. Most TikTokers burn custom-styled captions into video before uploading.

LinkedIn — Supports SRT files for video posts. Good for professional content. Not many people know this feature exists.

If you're preparing videos for multiple platforms, you might need to convert between video formats and adjust subtitle embedding based on each platform's quirks.

Troubleshooting common subtitle problems

Subtitles don't show up at all

Check the file name. If your video is movie.mp4, your subtitle file should be movie.srt — exact same name, different extension. Some players require this.

Also check encoding. SRT files should be saved as UTF-8 without BOM. If you see weird characters or nothing at all, encoding is probably wrong.

Subtitles are out of sync

Open the SRT file in a subtitle editor and adjust the timing. Most editors have a "shift all subtitles" feature that moves everything forward or backward by X seconds. Way easier than manually fixing every timecode.

Strange characters appear (é, ’, etc.)

Encoding issue again. Open the file in a proper text editor (not Word), save as UTF-8, and the problem should disappear.

Subtitles overlap or disappear too fast

Check your timecodes. Make sure the end time of one subtitle doesn't overlap with the start time of the next. And make sure captions display long enough to actually read (rule of thumb: at least 1 second per line of text, longer for complex sentences).

Best practices for readable subtitles

• Max 2 lines per caption — 3 lines looks cramped and blocks too much of the screen
• 40-42 characters per line max — longer than that and people can't read it in time
• Display time matters — minimum 1 second, maximum 7 seconds per caption
• Break at natural pauses — don't split mid-sentence unless necessary
• Use proper punctuation — periods, commas, question marks help readability
• Avoid ALL CAPS — unless someone is yelling. Lowercase is easier to read.
• Use [brackets] for sound effects — [thunder rumbling], [phone vibrates], etc.

And please, for the love of accessibility, don't use yellow text on white backgrounds or white text on light scenes. If you're burning in hard subs, use a semi-transparent black box behind the text so it's readable on any background.

The future of subtitles: AI and auto-translation

Auto-generated captions have gotten way better in the past few years. YouTube's auto-captions are now genuinely usable (most of the time). AI transcription tools like Whisper (OpenAI) can generate near-perfect transcripts from clean audio.

And auto-translation is starting to work. Not perfectly — you'll still get awkward phrasing and cultural mismatches — but we're at the point where auto-translated subtitles are better than nothing.

But here's the thing: auto-generated subtitles still need human review. AI doesn't understand context, sarcasm, or when someone is making a joke. It doesn't know that "their," "there," and "they're" are different words. It doesn't catch homophones.

So yeah, use AI to speed up the process. But don't publish auto-generated subtitles without reviewing them. Your audience deserves better.

Look, subtitles aren't glamorous. Nobody watches your video and says "wow, those subtitles were amazing." But bad subtitles? People notice. Missing subtitles? People who need them can't watch at all.

If you're making videos in 2026, subtitles aren't optional. They're part of the baseline. They make your content accessible, searchable, and watchable in more contexts (sound-off scrolling, noisy environments, non-native speakers).

And now you know how to make them. Go forth and subtitle.