SRT is the best default subtitle format for most everyday use: it is simple and widely supported. Choose WebVTT (.vtt) for native web video, or ASS (.ass) when you need detailed styling and positioning in a compatible player. The right choice depends on where the subtitles will play. If your current subtitles already work, there may be no reason to change them.

I've always just used SRT. It generally worked, so I had never seriously looked into the alternatives. But seeing VTT, ASS, and SDH alongside it made me wonder whether I was missing something. Should you even care about the format, as long as it works?

Usually, you can leave it alone. Here is when the differences become useful.

Which subtitle format should you use?

Choose a subtitle format for what you want to do
Your situationStart withWhy
Ordinary movie playback or sharing a subtitle fileSRT (.srt)Simple and widely supported; check your particular player or device
Uploading subtitles to YouTubeSRT; WebVTT is also acceptedSRT is a straightforward upload choice; styling support is limited
Adding subtitles to native HTML video on a websiteWebVTT (.vtt)The format used by the browser's native text tracks
Precise placement, styled signs, or karaoke effectsASS (.ass), if supportedMore control over appearance, positioning, and effects
Keeping an existing DVD or Blu-ray image trackIts original supported image formatSaving subtitle pictures as editable text requires text recognition

VLC does not use just one subtitle format. VideoLAN's desktop documentation lists SRT, ASS, SSA, and VobSub among its supported formats, as well as embedded subtitle tracks in MKV and DVD media. For a basic external file, SRT remains a sensible choice; you do not need to convert a supported track simply because you use VLC. [1]

For YouTube, start with a plain UTF-8 SRT file. YouTube recommends SRT or SBV for beginners and accepts WebVTT too. It ignores styling markup in SRT uploads and supports only limited styling in WebVTT. A file's capabilities and the features YouTube preserves are different things. [2]

Does the subtitle format actually matter?

For ordinary viewing, what matters is whether the words are readable, accurate, and in time with the dialogue. A more feature-rich file format does not automatically improve any of those things.

The format starts to matter when a player cannot load the file, an upload service rejects it, or formatting disappears. You might also need a particular format to keep a translation beside an on-screen sign or prevent subtitles from covering something important. In those situations, check what the destination supports before choosing your export.

Does one format look better or sharper?

SRT and WebVTT do not have inherently different text sharpness. The player renders the text, and its font, size, outline, background, and display settings affect readability. WebVTT provides web-oriented layout and styling controls; ASS offers more elaborate styling in compatible players. Neither guarantees a better-looking result.

Image-based subtitles are different because the letters are already pictures. They can look softer or more pixelated when enlarged. That does not mean every image track looks poor, only that changing a font setting cannot redraw it the way a player can redraw text.

SRT, WebVTT, and ASS: what is different?

SRT: the everyday default

An SRT subtitle file, also called SubRip, is a plain text file containing numbered entries, the time range for each entry, and the words to display. In effect, it tells the player: show this sentence from this moment until that moment.

It is easy to edit and a convenient choice for dialogue subtitles. Basic formatting works in some players, but you should not rely on elaborate styles or precise placement surviving across apps. SRT is often the most practical format because you need little more than words and timing.

WebVTT: a natural fit for web video

WebVTT means Web Video Text Tracks. It uses the .vtt extension and, like SRT, stores timed text. It is the format used for external subtitle and caption files with the native HTML video track element. It also supports cue positioning and styling, although the player determines which features are available. [3]

For example, if you are adding a caption file to a video on your own website, WebVTT is the natural starting point. If you are uploading to a hosted video service, follow that service's requirements instead.

That is the useful distinction in SRT vs. VTT: SRT is a convenient general-purpose file; VTT fits native web video. There is no universal winner.

ASS: when styling is part of the subtitles

ASS, or Advanced SubStation Alpha, supports detailed fonts, colors, outlines, positioning, and effects such as movement and karaoke highlighting. It can be useful when a translation needs to sit beside a sign or several speakers need distinct styles.

Those features require a compatible player and renderer, the software that draws the subtitles. If you only want readable dialogue at the bottom of a movie, ASS usually gives you more controls than you need. If an existing ASS track uses placement to make a scene understandable, preserving that track can matter.

Can you convert SRT to VTT?

Yes. Ordinary text and timestamps can generally be converted between SRT and VTT with a subtitle editor. Use its export or conversion function; changing the filename extension does not change the file's structure.

Keep the original and check the result in the destination player. WebVTT positioning or styles may be lost when exporting to SRT, and ASS effects do not transfer faithfully to simpler formats. Conversion also preserves existing timing errors unless you separately adjust the timestamps.

What are the different types of subtitles?

Format names get confusing because they sit alongside labels describing other things. There are two useful distinctions.

What the subtitles consist of:

  • Text-based subtitles, such as SRT, WebVTT, and ASS, contain text that the player draws at specified times.
  • Image-based subtitles, such as DVD VobSub and Blu-ray PGS tracks, contain pictures of the words. Turning those pictures into editable text requires optical character recognition (OCR) or transcription.

How the subtitles are carried or displayed:

  • A separate file, sometimes called a sidecar, sits alongside the video. An .srt next to an .mp4 is a familiar example.
  • An embedded track is stored inside a video container such as MKV. A compatible player lets you select or disable it.
  • Burned-in, or hardcoded, subtitles are part of the video picture. You cannot switch them off as a separate track.

These categories overlap: an MKV can contain an embedded image-based subtitle track that you can still turn off. Image-based does not mean burned-in.

Subtitles, captions, and SDH

Ordinary dialogue or translation subtitles may include just the spoken words. Captions also convey important audio information, such as sound effects, music, and who is speaking when that is unclear from the picture. Terminology varies across regions and services, so you will sometimes see “subtitles” used for both. Closed captions can be switched on or off; open captions stay visible. [4]

SDH means Subtitles for the Deaf and Hard of Hearing. It describes accessibility-focused content, rather than a separate file extension. An SRT file can contain SDH subtitles, including cues such as [door slams] or a speaker's name.

I had seen descriptions like those in movie subtitles without understanding their purpose. They supply information that dialogue alone cannot give someone who cannot hear the soundtrack. A sound coming from off screen, for example, may explain why a character suddenly turns around.

Are SDH subtitles better? They are better suited to viewers who need or prefer that extra audio context. If you want only translated dialogue, a standard subtitle track may suit you. Choose the content you need as well as a format your player accepts.

What if the subtitles do not work as expected?

If the file will not load, check format support first. A player or TV may accept the video but reject its subtitle format. Try loading the file manually and check the device's supported subtitle types. A supported alternative can help; renaming the extension cannot.

If styling disappears, check the app's limitations. Accepting a file does not mean preserving all of its fonts, colors, or positions. Keep the original styled track if those details matter.

If the words are out of sync, check the movie release. I have downloaded valid subtitle files that did not match the particular release I was watching. Another cut, an extra opening sequence, or a version running at a different speed can put the timing out. That is a separate problem from choosing SRT or VTT.

My usual preference is to find subtitles that match the release rather than manually retime them. A player's subtitle-delay control can help with a constant offset, but a mismatch that changes through the film may need more work. Converting the same timestamps to another format will not solve it.

If the subtitles are already inside the video, you may need extraction. You can extract an existing subtitle track from supported MKV, MP4, M4V, and MOV files. Text tracks can be saved as plain SRT or VTT; supported PGS and VobSub tracks in MKV keep their image format. This does not turn subtitle images into text or recover captions burned into the picture.

References

  1. VideoLAN. Subtitles — VLC Desktop User Documentation 3.0.
  2. YouTube Help. Supported subtitle and closed caption files.
  3. W3C. WebVTT: The Web Video Text Tracks Format.
  4. W3C Web Accessibility Initiative. Captions/Subtitles.