Convert SRT to WebVTT and WebVTT to SRT
Convert between SubRip (`.srt`) and WebVTT (`.vtt`) without uploading the subtitle file. The browser validates cue timestamps, preserves cue text and line breaks, writes the target format's timestamp separator, and regenerates SRT numbering. It does not translate dialog, fix overlaps, or promise to preserve every player-specific styling extension, so preview the result in the target media player before publishing.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeWhat it does
- Convert SRT to WebVTT
- Convert WebVTT to SRT
- Validate cue timestamps and missing text
- Preserve cue text and line breaks
- Run entirely in the browser
How to use Subtitle Converter
- 1
Choose a subtitle file
Drop an SRT or WebVTT file into the converter. The browser reads the text locally and identifies the source format from the extension and header.
- 2
Choose the target format
Select SRT or WebVTT. The tool defaults to the opposite of the detected input format so the normal conversion takes one click.
- 3
Convert and preview
Convert the cues, then inspect the output preview. Cue text and timing remain visible so a malformed file fails instead of silently losing subtitles.
- 4
Download and test
Download the target file and test the first, middle, and last cues in the media player or platform where it will be used.
How it works
SRT and WebVTT both store a sequence of timed text cues, but they differ in syntax. SRT normally has a numeric cue identifier and uses commas before milliseconds, such as 00:01:02,500. WebVTT starts with a WEBVTT header and uses periods, such as 00:01:02.500. This tool parses the cue boundaries, validates that every cue has text and a positive duration, then writes the target format from the parsed cue data.
The conversion is intentionally text-only and local. It does not need a video upload, a media decoder, or a language model. That keeps the tool quick and private, but it also means there is no audio-based timing correction. If the source captions are late, early, overlapping, or split into unreadable lines, those editorial problems remain visible in the output rather than being guessed away.
Format limits
SRT has a small, widely supported grammar. WebVTT can add cue settings, regions, styling blocks, and notes. The converter keeps the dialog and line breaks that are portable between the formats, while format-specific metadata is not guaranteed to survive an SRT round trip. If positioning, colors, karaoke timing, or custom CSS matters, keep the original WebVTT and test the converted copy separately.
Troubleshoot a subtitle conversion
Verify the result
If a player rejects the output, open the file as plain text and check its header,
timestamp separator, and blank lines between cues. WebVTT requires the WEBVTT header,
while SRT expects numbered blocks with a comma before milliseconds. A cue with an end
time before its start time, an empty text block, or an unusual timestamp format should
be corrected in the source rather than hidden by a conversion. Also check the file
encoding when accented characters appear incorrectly. Keep a copy of the original and
test the converted captions on the same player or hosting platform where viewers will
see them. Format conversion changes syntax; it does not validate editorial timing.
Open the downloaded file in the target platform. Check a cue near the start, one over a scene change, a multiline cue, and the final cue. Confirm that punctuation, accented characters, line breaks, and timing behave as expected. A successful parse means the syntax is understandable; it does not guarantee that the captions are well timed or that every player renders them identically.
Examples
Prepare captions for a web video
WebVTT is commonly accepted by HTML video tracks and web publishing tools.
Convert a browser caption file for editing
SRT has no standard header, so the converter writes clean sequential numbering while retaining line breaks.
Frequently asked questions
Does conversion translate or improve the subtitles?
No. The converter changes the container syntax, timestamp separator, and SRT numbering. It does not translate dialog, correct spelling, repair overlaps, align audio, or judge whether a line is readable on screen. Editing remains your responsibility.
What happens to WebVTT styling and metadata?
Cue text and line breaks are preserved, but WebVTT NOTE, STYLE, REGION, cue settings, and player-specific metadata are not reproduced in SRT. Review styling-dependent captions in the destination player, and keep the original VTT when those details matter.
Does it upload my subtitle file?
No. The file is read and converted in this browser tab. The output is assembled in memory and downloaded from the page, so no subtitle text is sent to a conversion server or third-party processing service.
Why did my file fail validation?
The tool requires recognizable cue timing, a positive end time after each start time, and at least one text line per cue. Fix malformed timestamps or empty cues in the source editor, then try again.
Can it preserve overlapping cues?
Yes, the converter does not silently move or merge overlapping cues. Some players support overlaps and others handle them differently, so test the converted file in the player that will display it before final delivery.
Further reading
- How to Check Whether a Conversion Actually Kept Your FileEvery conversion tool reports success. None of them report what they threw away, because from the tool's point of view nothing went wrong — it did the conversion it was asked for, and the things the destination format cannot hold were discarded before compression even started. Here is how to find out what you actually got.
- What Actually Happens When You Convert a FileNothing is "turned into" anything. The original is taken apart into raw numbers, and a second program writes an entirely new file from those numbers in a different language. Almost everything people find surprising about converters follows from that one fact.
- YouTube Title Length: Where Titles Actually Get CutThe character limit is 100 and almost nobody hits it. The number that decides whether your title works is the point where each surface truncates, and those range from about 40 characters on a mobile home feed up to around 70 on desktop search. Which means the real skill is word order, not brevity.