Key Takeaways
If the video plays in a browser, you want WebVTT. Almost everywhere else, SubRip (.srt) is the safe answer, because it is the plainest format and the most widely accepted. SubViewer (.sbv) is what YouTube Studio hands you, and it is usually a starting point rather than a destination. ASS and SSA exist for styled, positioned subtitles. Converting a rich format down to SRT keeps the timings and the text and throws everything else away for good. SRT to WebVTT costs you nothing.
Most people arrive at this question sideways. You have a subtitle file, you tried to use it, and something refused it. Now you need to know what the thing on the other end wants, and you would rather not learn a file format to find out.
So this is organized by destination, not by format. Find where the file is going, take the format listed, and only read the rest if you want to know what you are giving up when you convert. That part matters more than it sounds, because conversion is not symmetrical: some directions are free, and some quietly delete things you cannot get back.
Start from where the file is going
The format is not a preference. It is decided by whatever has to read the file, and that thing usually has exactly one answer. Work backward from it.
- A video on a web page. WebVTT. This is the format the web uses, and a browser player generally will not take anything else.
- A desktop or set-top media player, or a subtitle file sitting next to a video file. SubRip. It is the plainest format and the one most likely to be understood without argument.
- An upload form on a platform. SubRip unless the page tells you otherwise. Platforms differ, and the upload page or its help link is the only reliable source for what that particular one takes.
- A styled or positioned look you want preserved. ASS or SSA. Nothing simpler can carry it.
- Anything at all, starting from a file YouTube Studio gave you. That file is SubViewer, and converting it to SubRip first is usually the shortest path to it being accepted.
If your destination is not on that list and gives you no guidance, default to SubRip. The cost of that default is real but small: SRT cannot express styling or positioning, so subtitles will appear wherever the player normally puts them, in whatever the player’s own font is. For dialogue captions, that is usually what you wanted anyway.
SubRip and WebVTT, the two you will actually use
SubRip is about as simple as a text file gets. Each cue is a number on its own line, then a timing line with a start and an end, then one or two lines of text, then a blank line before the next cue. The milliseconds are separated from the seconds by a comma. That blank line between cues is load-bearing, which is why hand-editing an SRT sometimes breaks it in a way that looks like nothing is wrong.
Its virtue is that it asks nothing of the software reading it. There is no styling to interpret, no positioning to honor, no header to parse. If you want the structure spelled out cue by cue, there is a breakdown of the SRT format that goes line by line.
WebVTT is the web’s format and looks like a close cousin. The file opens with the word WEBVTT on its own line, and that line is not decoration; it is how a player identifies the file. Milliseconds are separated by a period rather than a comma. Cue numbers are optional, so a valid VTT file may have them or may not, and both are correct. Beyond that, WebVTT can carry positioning and styling, which is why captions on a web page can sit somewhere other than the bottom center.
The practical difference between the two is small enough to fit in a sentence and consequential enough to break playback. If you want the full picture before you pick, there is a side-by-side comparison of WebVTT and SubRip.
SubViewer and ASS, the two that show up for a reason
SubViewer, with the .sbv extension, is what YouTube Studio exports. You did not choose it; you clicked download and this is what came out. It has no cue numbers at all, the two timestamps on a timing line are separated by a comma rather than an arrow, and the hours are written without padding. It is perfectly readable, and comparatively few things outside its origin want to read it.
That makes SBV a transit format more than a destination. If you pulled captions out of YouTube Studio to use somewhere else, the conversion to SubRip is short and safe, and there is an SBV to SRT converter that does exactly that one job.
When you actually need ASS or SSA
SubStation Alpha, in its .ssa and .ass forms, is the format for subtitles that are meant to look like something. It carries styling, positioning and karaoke effects, all held in a structured Events section. One detail is worth knowing even if you never open the file: the Events section declares its own column order inside the file, so anything reading it has to read that declaration first rather than assume where the timings and text sit.
You need ASS or SSA when the appearance is part of the content: signs translated in place, two speakers in different colors, text timed to land on a specific part of the frame. If your subtitles are just dialogue at the bottom of the screen, you do not need it, and using it will only make the file harder to accept elsewhere.
The one rule that decides whether converting costs you anything
Formats differ in what they can express. Conversion is only free when the destination format can hold everything the source format was carrying. When it cannot, the extra information does not degrade or compress. It disappears.
Converting into SubRip from a richer format is lossy by definition. Styling, positioning and effects have nowhere to go in a format that has no way to describe them, so a converter drops them. What survives is the timings and the text, which for most purposes is the whole point of the file. But the loss is permanent in the converted copy, and converting back later will not bring the styling home. It will produce an unstyled file with a different extension.
Going the other way, SubRip to WebVTT is lossless. The conversion adds the WEBVTT header line and changes the millisecond separator from a comma to a period. Cue numbers get dropped, because WebVTT treats them as optional and they carry no information anyone needs; the order of the cues already says everything the numbers said. Nothing meaningful is lost, which is why this particular conversion is one you can do without thinking about it.
The habit that follows from this: keep the original file. Convert a copy. If the styled ASS file is the only place your positioning exists, overwriting it with an SRT is a decision you make once.
For the conversions themselves, the free subtitle converter on this site runs entirely in your browser, so nothing gets uploaded and there is no account. Those browser tools convert text files and do not transcribe audio; if what you have is a video with no subtitle file at all, SozAI’s transcription app for iOS, Android and macOS turns files, recordings and YouTube links into text with speaker labels, summaries and translation across 99+ languages.
Finding out what your file actually is
The extension is not proof of the contents. A file renamed from .vtt to .srt is still WebVTT; all you changed is the label. This matters because renaming is the first thing people try when a player rejects a file, and it is the one approach guaranteed not to work. The player is not reading the name. It is reading the first few lines, finding a header or a separator it did not expect, and giving up.
Open the file in any plain text editor and look at the top. It tells you immediately:
- First line reads WEBVTT: it is WebVTT, whatever the extension says.
- A number on its own line, then a timing line with a comma before the milliseconds: SubRip.
- No numbers, two timestamps separated by a comma, hours without padding: SubViewer.
- An Events section with a line declaring the column order: SubStation Alpha, in one of its forms.
Thirty seconds of looking replaces a lot of guessing, and it also catches the case where a download gave you something other than what the button promised.
What converting will not fix
Conversion changes the container, not the contents. If the timings drift against the video, they will drift the same way in the new format, because the converter copies the numbers it was given and has no idea what the video looks like. Misspelled names, missing lines and cues that run too long all come through intact.
It also will not talk a player into accepting a format it does not support. If a browser player wants WebVTT, converting your SBV to SRT gets you a format that is more widely accepted in general and still wrong for that specific destination. Convert toward what the destination asks for, not toward what is popular.
And a reverse conversion never restores what a lossy one removed. Once styling and positioning are gone from a file, the only copy of them is in the original, if you kept it. When you are working with styled subtitles, treat the ASS or SSA file as the master and everything you export from it as disposable. That way a bad conversion costs you a minute rather than an afternoon.
