About SRT Files
SubRip Subtitle
SRT is the most widely used subtitle format with simple timestamps and text.
Family
Documents & Text
Extension
.srt
MIME Type
application/x-subrip
Can Use As
HOW SRT
CAME TO BE.
SRT — SubRip Text — was created by a developer known only as "Zuggy" in 2001 as the output format of his Windows OCR tool SubRip, which ripped subtitles from DVDs. The format was so gloriously simple — a number, a timecode range, text, blank line, repeat — that every subtitle pirate, fansubbing group, and DVD ripper adopted it almost overnight.
By 2005 .srt was the universal subtitle format. Every media player (VLC, MPC, KMPlayer, later mpv) loaded them automatically from a sidecar file next to the video. Today Netflix, YouTube captions, Amazon Prime subtitles, and every torrent release all ship SRT as the baseline subtitle format. It has never been formally standardized — but convention has made it as solid as any ISO spec.
CURIOSITIES &
TRIVIA.
SRT has never been formally standardized — every implementation follows a convention established by convention alone.
The entire format can be parsed with a ~15-line regex.
Netflix uses a stricter subset internally; their authoring tools convert to WebVTT or their own TTML for streaming.
SubRip's original author "Zuggy" has never publicly claimed credit — the tool was distributed anonymously on DVD forums.
Adding italic or bold text in SRT uses HTML tags (<i>, <b>) — an informal extension that every player supports.
STRENGTHS &
LIMITATIONS.
Strengths
- Trivially simple — every video player reads SRT sidecar files automatically.
- Plain text — editable in Notepad, grep-able, diff-friendly.
- Universal tooling — OCR, translation, and timing apps all speak SRT natively.
- Tiny file sizes — a 2-hour movie of subtitles is usually under 100 KB.
Limitations
- No formal standard — edge cases (nested tags, encoding, line count) vary.
- No styling beyond basic HTML — no positioning, no colors beyond italic/bold.
- Character encoding ambiguity — some SRTs are Windows-1252, some UTF-8, some UTF-16.
- Cannot represent multiple speakers, sound effects, or precise positioning like SSA/ASS can.
Typical Sizes & Weights
1-hour TV episode (English)
30-80 KB
2-hour movie (English)
50-120 KB
Anime episode with stylized Japanese
80-200 KB
Technical Specifications
- MIME type
- application/x-subrip
- Extension
- .srt
- Structure
- Numbered blocks: index → timecodes → text → blank line
- Timecode format
- HH:MM:SS,mmm --> HH:MM:SS,mmm
- Encoding
- Typically UTF-8 (modern) or CP1252 (legacy)
CONVERT FROM
SRT
Common Use Cases
Video subtitles, captions
Related Formats
Popular comparisons
SRT vs VTT
Differences, file size, and when to choose each format.
SRT vs PDF
Differences, file size, and when to choose each format.
SRT vs DOCX
Differences, file size, and when to choose each format.
SRT vs ODT
Differences, file size, and when to choose each format.
SRT vs TXT
Differences, file size, and when to choose each format.
SRT vs MD
Differences, file size, and when to choose each format.
Popular SRT conversions
The most-requested destinations when starting from SRT.
Frequently Asked Questions about SRT
Frequently Asked Questions
SRT (SubRip Subtitle) is a document format used to store paginated text, with optional formatting, tables, images, hyperlinks, headers and footers. It sits in the documents & text family and is typically associated with a specific office suite or publishing pipeline that defined the format and ships the canonical reader.
Modern office suites — Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages — open most SRT files with reasonable fidelity. If your installed software does not support SRT, convert to DOCX or PDF first using KaijuConverter; both open in virtually every reader, including free online viewers.
Upload the SRT to KaijuConverter and pick DOCX, PDF, ODT, RTF, HTML, Markdown, or plain text. Our pipeline runs LibreOffice headlessly plus pandoc for text formats — the same engines behind professional document pipelines. Styles, tables, images, and hyperlinks survive the conversion intact.
Yes, to a high degree. Standard fonts, headings, lists, tables, images, hyperlinks and page structure transfer cleanly. Custom fonts substitute to the closest match if not embedded; obscure layout features unique to SRT (frames, legacy macros) may flatten to static content in the target format.