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.
1
00:00:00,000 --> 00:00:02,500
Welcome to Novus Examples.
2
00:00:02,500 --> 00:00:05,000
These are free sample subtitle files.
3
00:00:05,000 --> 00:00:08,000
Use them to test parsers, players, and converters.
Specifications
- Format
- SubRip (SRT)
- Cues
- 3
- Timing
- HH:MM:SS,mmm
What is a .srt file?
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 this file
Use an example SRT to test subtitle parsing, timecode handling, and converters that translate between SRT and WebVTT or other caption formats.
How to use this file for testing
“SubRip Subtitles (SRT)” is a deterministic Novus Examples fixture for Subtitle testing, Conversion testing. SubRip and WebVTT sidecars plus multi-track containers — forced-narrative, SDH and styled tracks in one file — for testing track selection, default flags and caption rendering in players.
Documented properties for this file: 3 cues · SubRip (SRT). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.
Parse the cues and check timings against the documented count; the same captions ship across subtitle formats so you can diff a converter against a known target.
Code examples
<video controls src="clip.mp4">
<track kind="captions" srclang="en" label="English" src="captions.srt" default>
</video>Related files
- adocAsciiDoc Guide (ADOC source)An AsciiDoc getting-started guide with source blocks, an admonition, and a table — for testing AsciiDoc renderers (Asciidoctor), editors, and conversion to HTML/PDF.
- docDOC — Legacy Word 97The formatted Word document saved as legacy binary .doc (Word 97-2003, OLE compound file) via LibreOffice. For testing legacy-Office parsers and DOC→DOCX conversion.
- docxDOCX with CommentsA Word document with two anchored reviewer comments — for testing comment extraction and whether converters preserve or drop review annotations.
- docxDOCX with Core and Custom PropertiesA valid DOCX package with fixed core properties and two custom properties surrounding an unchanged word/document.xml part.
- docxDOCX with Metadata StrippedThe same DOCX document part without core or custom property parts, suitable for checking OOXML metadata removal without content loss.
- docxDOCX with Tracked ChangesA Word document with real tracked changes — insertions and deletions attributed to two reviewers with timestamps — for testing how tools read, accept, reject, or preserve revisions.
Generated by generation/data_dev_fixtures.py. Free for any use, no attribution required — license.