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
Testing contract
Expected to pass- Scenario
- Exercise SubRip Subtitles (SRT) in its subtitles workflow. A SubRip (SRT) subtitle track with three timed cues: the most common subtitle format.
- Expected result
- 11 text lines, decoded as UTF-8; first nonempty line is '1'. Declared feature checks: 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 Testaroo 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>Generated by generation/data_dev_fixtures.py. Free for any use, no attribution required, license.
Related files
- ediAlder Table Bistro: ANSI X12 810 invoiceANSI X12 810 invoice for Alder Table Bistro. Version 004010 transaction set 810 for invoice INV-BST-5002, control number 810002. 3 IT1 segments, a TXI segment stating GST of 15.69, and a TDS segment of 32953 in implied-decimal cents, which is 329.53 CAD. SE declares 13 segments and 13 are present.
- ediAlder Table Bistro: ANSI X12 810 invoice with a wrong SE segment countANSI X12 810 invoice with a wrong SE segment count for Alder Table Bistro. Identical to edi-810-invoice.edi except for one element: SE declares 11 segments where 13 are present between ST and SE inclusive. The ISA, GS, GE and IEA control numbers, every data segment and the TDS total of 32953 are unchanged, so a parser that checks only syntax accepts the file and only a parser that recounts segments rejects it.
- ediAlder Table Bistro: ANSI X12 850 purchase orderANSI X12 850 purchase order for Alder Table Bistro. Version 004010 transaction set 850 for PO-BST-1002, control number 850002. 3 PO1 segments carry quantity, X12 unit code, unit price, the supplier item code (VP) and the buyer item code (BP); CTT declares 3 line items and SE declares 14 segments, which is the number actually present between ST and SE inclusive.
- ediAlder Table Bistro: ANSI X12 856 despatch adviceANSI X12 856 despatch advice for Alder Table Bistro. Version 004010 transaction set 856 for supplier delivery note DN-BST-3002 against PO-BST-1002, control number 856002. The shipment, order and item hierarchy uses HL segments, and the SN1 quantities are the quantities actually delivered, so line 2 reports 16 where the 850 ordered 20.
- xmlAlder Table Bistro: Factur-X CII invoice XMLFactur-X CII invoice XML for Alder Table Bistro. UN/CEFACT Cross Industry Invoice for INV-BST-5001 at the Factur-X BASIC guideline, with 3 trade line items, a TaxTotalAmount of 10.38 and a DuePayableAmount of 217.98 CAD. These bytes are the exact bytes embedded as factur-x.xml inside invoice-facturx.pdf.
- pdfAlder Table Bistro: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Alder Table Bistro. Invoice INV-BST-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 207.60, GST 10.38, 217.98 CAD due. This is the only file in the set that carries its data twice in one container.
