What Is an SRT File?

An SRT file is a plain text subtitle file. It stores subtitle text, start and end times, and sequence order so a video player knows what to show and when.

SRT stands for SubRip Subtitle. The file extension is .srt.

In one sentence: an SRT file is used to add timed subtitles to a video, either as a separate subtitle track or as the source file for burned-in subtitles.

SRT is popular because it is simple and widely supported. You can open it in a text editor, upload it to video platforms, edit it in subtitle software, or use it to create a video with permanent subtitles.

What Is Inside an SRT File

An SRT file is made from subtitle blocks. Each block contains a number, a timecode line, the subtitle text, and a blank line before the next block.

1
00:00:04,200 --> 00:00:07,100
This is the first subtitle.

2
00:00:08,500 --> 00:00:11,000
This is the second subtitle.
It can have more than one line.

The structure is:

1. A sequence number
2. A timecode in the format hours:minutes:seconds,milliseconds --> hours:minutes:seconds,milliseconds
3. The subtitle text
4. A blank line to separate entries

That is the whole format. There is no styling layer, font setting, position setting, or embedded video. An SRT file only says what text appears and when.

This simplicity is useful. It also means quality depends on text, timing, and structure. Correct words are only part of the result. The blocks still need readable line breaks, sensible timing, and enough display time for the viewer to follow. See subtitle timing and subtitle line length for the practical standards behind that.

Why SRT Is So Widely Used

SRT became common because it solved a practical problem with little complexity. A subtitle file needed to be easy to create, edit, and parse. SRT does that with plain text.

It is supported by YouTube, Vimeo, VLC, many media players, video editing tools, learning platforms, and social publishing workflows. If a platform accepts subtitles, SRT is usually supported.

SRT also works well across teams. A creator can generate a file, an editor can revise it, a translator can use it as a source, and a platform manager can upload it with the final video.

The tradeoff is that SRT is limited. It does not carry rich styling, speaker positioning, karaoke effects, or advanced accessibility metadata. For most ordinary workflows, it remains the safest default.

SRT vs WebVTT vs ASS

SRT is not the only subtitle format. The three formats most people encounter are SRT, WebVTT, and ASS.

SRT

Use SRT when you need a widely compatible subtitle file. It is best for ordinary video subtitles, platform uploads, basic editing, and workflows where portability matters more than styling.

An SRT file usually looks like this:

1
00:00:04,200 --> 00:00:07,100
This is the first subtitle.

SRT uses comma-based milliseconds and a --> arrow between start and end times.

WebVTT

WebVTT stands for Web Video Text Tracks. It is common on the web, especially with HTML5 video. WebVTT files usually use the .vtt extension and start with a WEBVTT header. They can support extra cues, comments, positioning, and web-specific track behavior.

If you are uploading subtitles to a general video platform, SRT is often accepted. If you are building a web video experience, WebVTT may fit better.

ASS

ASS stands for Advanced SubStation Alpha. It is a more complex format used when styling and placement matter. It can store fonts, colors, positions, effects, and detailed formatting rules. It is common in fansubbing, anime workflows, and karaoke-style captions.

The practical rule:

• Choose SRT for broad compatibility and ordinary subtitle delivery
• Choose WebVTT for web video tracks
• Choose ASS when detailed styling and positioning are required

For most professional video workflows, SRT is the first file to create and keep.

How to Open an SRT File

Because SRT is plain text, you do not need special software to open it. You can use a text editor, subtitle editor, video editor, or media player.

On Mac

On macOS, open an SRT file with TextEdit, Visual Studio Code, Sublime Text, BBEdit, or another plain text editor. If TextEdit opens the file in rich text mode, switch it to plain text before saving.

On Windows

On Windows, open an SRT file with Notepad, Notepad++, Visual Studio Code, or another plain text editor. A code editor is easier for larger files because it shows the structure more clearly.

If you change the file, keep the .srt extension. Do not save it as .txt. Also make sure the file stays in plain text and uses UTF-8 encoding if the subtitles contain accents, non-English characters, or special punctuation.

In Video Editors and Players

Many video editors let you import an SRT file as a subtitle or caption track. The wording varies by tool, but the workflow is usually import, captions, subtitles, or text track.

Media players such as VLC can also load SRT files. Many load the file automatically if it has the same name as the video and sits in the same folder:

training-video.mp4
training-video.srt

If the player does not find the subtitles automatically, use the subtitle menu to add the file manually.

Common SRT Problems and How to Fix Them

SRT files are simple, but small formatting errors can still cause playback or upload problems. The most common issues are encoding, broken timecodes, numbering, line length, and platform compatibility.

Strange Characters or Broken Accents

If your subtitle file contains unreadable characters, boxes, or incorrect accents, it may be saved with the wrong encoding.

Try this:

1. Open the file in a plain text editor
2. Save it again as UTF-8
3. Re-upload the file

This matters for accents, non-Latin scripts, curly quotes, and special punctuation. UTF-8 is the safest default for modern subtitle workflows.

Timecode Errors

Each SRT timecode line needs a start time, an arrow, and an end time:

00:00:04,200 --> 00:00:07,100

Common mistakes include a missing arrow, a malformed timestamp, a period instead of a comma in milliseconds, or an end time that comes before the start time.

Overlapping timecodes can also cause problems. One subtitle should usually end before the next one starts. Some players tolerate overlap, but others may skip cues.

If subtitles feel early, late, rushed, or out of sync after an edit to the video, the SRT may belong to a different cut. Review the first line, a middle section, and the final section before publishing. The subtitle timing standard explains what good timing should feel like.

Sequence Number Issues

Most modern players care more about timecodes than sequence numbers, but broken numbering can still confuse editing tools and validators. Keep numbering simple when possible:

1
2
3

If you delete or merge subtitle blocks, a subtitle editor will usually renumber the file automatically.

Lines That Are Too Long

An SRT file can contain very long subtitle lines, but that does not mean they will be readable. Long lines may run off the screen, wrap awkwardly, or force viewers to read too much text too quickly.

This is where subtitle craft matters. A subtitle should not feel like a transcript chunk pasted onto the video. Good formatting uses readable line lengths, natural phrase breaks, and enough time on screen. For guidance, see subtitle line length.

Why an SRT File Might Not Work in a Player

If a player does not read your SRT file, check these basics first:

• The file extension is .srt
• The file is plain text, not rich text
• The file is saved as UTF-8
• The SRT uses valid timecode lines with the --> arrow
• There is a blank line between subtitle blocks
• The video and SRT names match if you expect automatic loading
• The platform actually supports SRT upload for that video type

Some platforms also have their own rules for language labels, caption track settings, or upload location. If the file opens in a subtitle editor but fails on one platform, the issue may be the platform workflow.

SRT in a Subtitle Workflow

An SRT file is usually not the whole workflow. It is the subtitle file that moves between steps.

A typical workflow looks like this:

1. Generate or create subtitle text and timing
2. Review the SRT for text, timing, line breaks, and readability
3. Upload the SRT as a subtitle track, or use it to render burned-in subtitles

If you are still choosing the right method, start with how to add subtitles to a video. That guide compares generated subtitles, uploaded files, closed captions, and burned-in output.

If the SRT needs corrections, use a subtitle editor or follow the practical steps in how to edit an SRT file. The SRT Editor lets you load a video and an SRT file together, then adjust the text and timing in the browser.

If you want the subtitles to be permanent, use the SRT to create a video with burned-in subtitles. The guide to how to burn subtitles into video explains what to check before rendering. If you already have a video and SRT file, you can use Burn Subtitles Into Video directly.

For accessibility and viewer control, it is useful to understand the difference between subtitles, captions, and soft tracks. The guide to subtitles vs captions explains when a subtitle file is translating or transcribing speech, and when it should include non-speech audio information.

How to Get an SRT File

There are three common ways to get an SRT file.

Generate One from a Video

The fastest option is to generate subtitles from your video with an automatic subtitle tool. Upload the video, let the tool transcribe and time the speech, then export the result as SRT.

The AI Subtitle Generator creates an SRT file from your video and can also produce a burned-in video in the same workflow. For more detail, see how to create subtitles automatically.

Automatic generation is a strong starting point, but review still matters. Transcript accuracy is not the same as subtitle quality. Proper names, numbers, timing, line breaks, and reading speed can still need attention before publishing.

Type One Manually

You can create an SRT file by hand in a text editor. This is possible for short clips, simple videos, and technical tests. For longer videos, it becomes slow because you need to transcribe, time, split, and review every subtitle block.

Receive One from a Professional Subtitler

Professional subtitlers often deliver SRT files because the format is easy for clients to use. If you receive an SRT from someone else, open it with the video before publishing. Check that it matches the final cut, uses the right language, and follows your platform requirements.

Create or Edit Your SRT File

If you need an SRT file from a video, start with the AI Subtitle Generator. It creates timed subtitles and gives you an SRT file you can review, edit, upload, or burn into the video.

If you already have an SRT file, open it in the SRT Editor to review text and timing before publishing. A small fix to timing, encoding, or line breaks can be the difference between a subtitle file that merely loads and subtitles people can comfortably follow.