srt
What is a .srt file?
application/x-subrip
SRT (SubRip) is a plain-text subtitle format listing numbered cues, each with a start and end timecode and one or more lines of text. It is simple, human-readable, and extremely widely supported by players. It carries no styling metadata beyond basic inline tags.
How to use a .srt file
Use an example SRT to test subtitle parsing, timecode handling, and converters that translate between SRT and WebVTT or other caption formats.
Download example .srt files
- SubRip Subtitles (SRT)A SubRip (SRT) subtitle track with three timed cues — the most common subtitle format. Paired with the WebVTT twin for testing subtitle parsers and SRT↔VTT conversion.
- SRT — Soft-Sub CompanionCompanion SRT for the soft-sub MP4 — same SAMPLE cue timings.
- SRT — Video QC Note 01Video QC companion SAMPLE (desync-caption.srt) for Wave G suites.
- SRT — Video QC Note 03Video QC companion SAMPLE (bars-caption.srt) for Wave G suites.
- SRT — Video QC Note 05Video QC companion SAMPLE (portrait-caption.srt) for Wave G suites.
- SRT — Video QC Note 07Video QC companion SAMPLE (square-caption.srt) for Wave G suites.
- SRT — UTF-8, LFPlain UTF-8, no byte-order mark, Unix LF line endings. The reference member of this set — every other file here carries the same five cues, so a parser's output can be diffed against this one. Identical cue content across the whole set, so any difference in a parser's output is an encoding bug and nothing else.
- SRT — UTF-8 with BOM, LFUTF-8 with a leading U+FEFF byte-order mark. Windows caption tools emit this constantly, and a parser that does not strip it sees the BOM as part of the first cue number and fails to match its index. Identical cue content across the whole set, so any difference in a parser's output is an encoding bug and nothing else.
and 25 more in the library.