Choose your SRT file
Select or drop one text subtitle. UTF-8 and BOM-marked Unicode files are detected automatically; legacy encodings require your explicit selection.
Subtitle Tools
SRT to VTT Converter
Convert a SubRip .srt subtitle into a valid UTF-8 WebVTT file locally in your browser, with cue previews and clear notices for safe repairs or unsupported formatting.
Convert an SRT subtitle
Choose one SRT file, review its cues and any safe repairs, then create a UTF-8 WebVTT file.
Reading the subtitle locally
Checking its text encoding and cue structure…
Encoding needed
Choose the file’s original text encoding
The file is not valid UTF-8, so BrowserPine will not guess. Choose an encoding and check the cue preview before converting.
This SRT file needs attention
SRT ready
- File size
- Encoding
- Line endings
- Cues
- Timeline duration
- Warnings / repairs
Review these non-blocking findings
Repairs are identified explicitly. Timing notices are reported without changing the source cue times.
First cue preview
Up to three cues are shown as plain text. Subtitle markup is never executed.
Conversion complete
Your WebVTT file is ready
The output is UTF-8 without a BOM. SRT cue numbers are intentionally omitted because WebVTT does not require them.
- Download file
- Output size
- Cues
- Warnings / repairs
Local processing
Your subtitle text stays on your device
The SRT file is decoded, checked, parsed, and converted inside your browser. BrowserPine does not upload, log, or persist its cue text, and the converter needs no account or server API.
Read how BrowserPine handles filesThree simple steps
How to convert SRT to VTT
Review cues and findings
Check the detected encoding, cue count, timeline duration, first cues, and any repairs or timing notices before converting.
Download WebVTT
Create a valid WEBVTT document and download the UTF-8 .vtt file without uploading the source subtitle.
What changes from SRT to WebVTT?
SRT and WebVTT both store timed text cues, but WebVTT begins with a WEBVTT header and uses a dot before milliseconds. For example, 00:01:02,345 becomes 00:01:02.345.
Numeric SRT cue numbers are omitted consistently because WebVTT does not require them. Cue order, start and end times, multiline text, Unicode, Arabic, RTL text, and emoji remain in the converted document.
Where is WebVTT used?
WebVTT is designed for timed tracks on the web and is commonly used with HTML5 video for captions, subtitles, chapters, and related timed text.
This converter creates a focused caption file. It does not upload a video, burn subtitles into media, or create a video player project.
Formatting compatibility
Common bold, italic, and underline tags are retained. Legacy font tags are removed because they do not map cleanly to this focused WebVTT output, but their visible text is preserved and the affected cue count is reported.
Other angle-bracket content is escaped as text rather than executed. Conversion is therefore not described as perfectly lossless when the SRT depends on unsupported legacy styling.
Encoding and safe repairs
Output is UTF-8 without a byte-order mark. UTF-8, UTF-16LE BOM, and UTF-16BE BOM input can be detected automatically. If strict UTF-8 decoding fails, the converter asks you to choose a supported legacy encoding instead of guessing.
Missing or irregular cue numbers, dot milliseconds, mixed line endings, and a missing final newline can be normalized safely. Invalid timing, binary data, inseparable cue blocks, and excessive input are rejected rather than partially converted.
Common questions
SRT to VTT FAQ
Are my SRT subtitles uploaded?
No. The file contents are decoded, parsed, and converted locally in your browser. BrowserPine does not send or store the subtitle text.
What is the difference between SRT and VTT timestamps?
SRT normally separates milliseconds with a comma, while WebVTT uses a dot and requires a WEBVTT header. The converter changes that syntax without shifting cue times.
Does SRT to VTT preserve subtitle formatting?
Bold, italic, and underline tags are retained. Legacy font tags are removed while preserving visible text, and the converter reports how many cues were affected.
Can this converter read non-UTF-8 subtitles?
BOM-marked UTF-16 files are detected automatically. If a file is not valid UTF-8 and has no recognized BOM, you can explicitly select one of the legacy encodings supported by your browser.
Will overlapping subtitle cues be changed?
No. Overlaps and unusual timing are reported for review, but valid cue start and end times are not altered during format conversion.
Why are SRT cue numbers missing from the VTT file?
SRT numbers are structural ordering markers. WebVTT does not require numeric cue identifiers, so this converter omits them consistently while preserving cue order.
Keep working
Related subtitle tools
Available
VTT to SRT
Convert WebVTT captions to SRT with clear feature-loss warnings.
View tool
Available
ASS / SSA to SRT
Convert ASS or SSA dialogue timing and visible text to simpler SRT subtitles.
View tool
Available
Subtitle Editor
Review and edit SRT cue text, timing, order, and file sections.
View tool