Free online SRT converter. Convert SRT to VTT, ASS, SSA, SUB, TXT and more online — no limits, no watermark.
.srt file, or paste the subtitle text straight into the input box if you only have a snippet to convert.<video> needs for browser captionsSRT (SubRip Text) is the lowest-common-denominator caption format. It came out of SubRip, a free Windows program first released on 3 March 2000 that extracted ("ripped") subtitles and their timings from DVDs into a plain-text file. Each cue is a number, a timecode line in the form HH:MM:SS,mmm --> HH:MM:SS,mmm (note the comma before the milliseconds), and one or more lines of text. There is no header and no real styling system — only unofficial HTML-like <b>, <i>, <u>, and <font color> tags that some players honor and others ignore.
That plainness is why SRT plays almost everywhere — and also why people convert away from it. The format simply cannot describe what some destinations demand:
<track> element only accepts WebVTT, a W3C format that began life as "WebSRT" at the WHATWG in 2010. It starts with a WEBVTT header, uses a period instead of a comma in timecodes (00:00:01.000), and adds CSS styling, cue positioning, and metadata SRT can't carry. Converting SRT to VTT is the most common reason creators land here.| Format | Origin / Standard | Timing model | Styling | Typical use |
|---|---|---|---|---|
| SRT (SubRip) | SubRip tool, 2000 | HH:MM:SS,mmm (comma) |
Basic, unofficial HTML tags | Universal fallback; players, social uploads |
| VTT (WebVTT) | W3C / WHATWG, 2010 | HH:MM:SS.mmm (period) |
CSS styling + cue positioning | HTML5 <video>, web captions |
| ASS / SSA | SubStation Alpha (anime fansub) | Start/end with style refs | Full: fonts, color, position, karaoke | Styled subs, anime, Aegisub |
| TTML / DFXP | W3C XML standard | Frame-accurate, XML elements | Rich, XML-defined styling | Broadcast and streaming captioning |
| SBV (SubViewer) | YouTube / SubViewer | H:MM:SS.mmm,H:MM:SS.mmm |
None | YouTube caption uploads |
| TXT | Plain text | None (timecodes removed) | None | Transcripts, translation, indexing |
No. The cue timings are preserved — the converter rewrites them into WebVTT's format rather than altering them. The most visible change is the separator: SRT writes milliseconds after a comma (00:00:01,000) while VTT uses a period (00:00:01.000), and a WEBVTT header is added at the top of the file. The on-screen appearance of when each line shows and hides stays the same.
Basic markup usually carries over, but it depends on the target. SRT supports unofficial <b>, <i>, <u>, and <font color> tags, and formats like VTT and ASS have equivalents. Converting to a richer format such as ASS gives you far more styling control than SRT ever had, while converting to a styling-free format like SBV or TXT drops formatting entirely, leaving plain text.
Both are basic, unstyled caption formats YouTube accepts, but the structure differs. SRT numbers each cue and uses --> between start and end times with a comma before the milliseconds. SBV (SubViewer) has no sequence numbers and puts the start and end timecodes on one comma-separated line using periods. If a tool or uploader specifically asks for SubViewer, convert SRT to SBV; otherwise SRT works directly on most of YouTube.
If your delivery spec names TTML or DFXP, yes. TTML is the XML-based W3C standard widely mandated across broadcast and streaming, and DFXP is a profile of it — many professional caption-ingest systems reject plain SRT and require one of these. Check the exact profile your distributor asks for, since "TTML" and "DFXP" are often used interchangeably but a pipeline may want one specifically.
Yes — convert SRT to TXT. That strips the cue numbers and timecodes and leaves just the spoken lines as continuous text, which is what you want for editing a transcript, feeding a translation tool, or making the content searchable. If you later need timed captions again, you'd re-sync the text to a subtitle format.
In our testing, a standard SRT exported from common subtitle editors converts to VTT and SBV with the cue text and start/end times intact, since all three share the same millisecond timing model. The trickier conversions are into and out of richly styled formats like ASS: timing always survives, but styling that has no equivalent in the target format is simplified or dropped. Always glance at the output pane to confirm your cues look right before downloading.
SRT is still the most widely supported subtitle format and is far from outdated — its simplicity is exactly why nearly every media player, editor, and social platform reads it. You convert away from SRT only when a destination needs something SRT can't express: CSS styling and positioning (VTT), karaoke and rich layout (ASS), or an XML broadcast profile (TTML/DFXP). For everyday playback, SRT remains the safest format to keep.