SubtitleKitHow it works
Open a UTF-8 SRT or WebVTT file, or paste its contents. Choose the output format and process the source. The converter validates each cue, orders cues by start time and numbers SRT entries again. Output contains visible plain text rather than original formatting. Voice labels in WebVTT are retained as text. Positioning, regions, styles, cue identifiers and metadata blocks are not preserved. Keep the original if these features matter to your project.
Example
SRT uses commas before milliseconds, while WebVTT uses periods and a WEBVTT header. A cue from 00:00:01,000 to 00:00:03,000 retains its time range when converted. Multiline text and Unicode characters remain readable. Invalid timestamps or end times that precede start times stop processing. Overlaps are reported but not automatically removed. Test the downloaded file in your target player before publishing.
Assumptions and limitations
Plain text output: styling, regions, positions and cue IDs are not preserved. Inputs stay in memory. Download your result before leaving this page.
Frequently asked questions
Are subtitles or videos uploaded?
No. Parsing, processing and local video playback happen in your browser. Only the theme preference is stored; source text is lost when you leave the page.
Will formatting and positioning survive?
Output uses plain visible cue text. Styling, regions, cue IDs, positions and metadata are not retained. Keep your original files.
Which files are supported?
UTF-8 SRT and WebVTT, up to 5 MB and 50,000 cues per input. Convert legacy encodings first. Video preview depends on your browser’s codecs.