SubRip SRT converter
Convert SubRip SRT subtitles while handling cue numbers, comma timestamps, encodings, line breaks, and WebVTT output.
.srt
Format
About SubRip SRT
SRT, short for SubRip, is the simplest widely exchanged subtitle format. It is plain text organized as numbered cues, start and end timestamps using comma milliseconds, caption lines, and blank separators. It has no formal styling model beyond text conventions and limited markup accepted by some players. That simplicity is why SRT appears in YouTube uploads, editing tools, media archives, translation workflows, and broadcast handoffs that do not need positioning. Our subtitle routes convert SRT to VTT, ASS, TXT, CSV, or JSON. We ran SRT to VTT locally and the output added a WEBVTT header, changed commas to periods, and kept three cue texts.
SRT has no single official version, so files vary by convention. Cue numbers may be missing, duplicated, or out of order. Encodings may be UTF-8, UTF-8 with a byte order mark, Windows-1252, or another legacy charset. Line endings differ by operating system. Some files contain italic tags, speaker labels, music notes, translator comments, or HTML-like markup that a player may or may not honor. Timing can use overlapping cues, very short durations, or frame-derived values rounded to milliseconds. A converter has to normalize enough syntax for the target while preserving the actual captions.
Readers and writers include subtitle editors, video platforms, media players, transcription services, localization vendors, streaming teams, and QA tools. SRT is a good interchange choice when the target only needs readable captions at times. It is weaker for web text tracks that need cue settings, for styled fansubs, and for authoring workflows that need speaker metadata or region placement. CSV or JSON can help translators and scripts review caption text, but those targets are not playback formats. A subtitle conversion should always be checked against the video because syntactically valid captions can still be late, early, or too long.
SRT conversion gotchas come from moving between plain captions and richer timed-text formats. SRT to VTT is common for browsers, but WebVTT may support settings that SRT never had. SRT to ASS can create a styled script shell, yet the source contains little style information. SRT to TXT loses timing, while SRT to CSV or JSON is for editing or analysis. Before converting, validate cue order, fix overlapping timings, normalize encoding to UTF-8, remove comments that players treat as captions, and review line breaks. For accessibility, proof reading speed and synchronization rather than only checking file syntax.
Convert to SubRip SRT from…
Common SubRip SRT problems
Browser video needs a text track file.
Use /convert/srt-to-vtt, then test the WEBVTT file in the actual video player with captions enabled.
A translator wants subtitles in a spreadsheet.
Use /convert/srt-to-csv and preserve cue IDs and timings so translated text can be reconciled later.
Caption text should be indexed without timecodes.
Use /convert/srt-to-txt, accepting that cue boundaries and timing are removed.
Styled karaoke subtitles are expected downstream.
Use /convert/srt-to-ass only as a starter file, then add styles and positioning manually in an ASS editor.
Automation needs machine-readable cues.
Use /convert/srt-to-json and validate that timestamps, text, and cue order match the source video.