What does VTT to SRT Converter do?
Tubelexity converts WebVTT into sequential SubRip SRT cues with comma millisecond separators. WEBVTT headers are removed, NOTE blocks are ignored, cue identifiers become SRT numbering, and unsupported cue settings, STYLE/REGION blocks or WebVTT-specific annotations produce visible warnings rather than false preservation claims.
How to use VTT to SRT Converter
- 1Upload a .vtt file or paste WebVTT text.
- 2Convert and review cue count, timing coverage and discarded-feature warnings.
- 3Check the numbered SRT output preview and multiline cue text.
- 4Copy the result or download a UTF-8 .srt file.
Supported inputs and outputs
Inputs
WebVTT (.vtt), Pasted WEBVTT text, Cue identifiers and settings, NOTE, STYLE and REGION blocks
Outputs
Sequential UTF-8 SubRip (.srt)
Practical uses
- Moving web captions into an editor
- Creating sequential SRT numbering
- Auditing WebVTT-only features
- Normalizing subtitle timestamps
Browser and media limitations
- SRT cannot represent WebVTT cue settings, regions or style blocks.
- Voice, class, language and ruby annotations are simplified with warnings.
- NOTE blocks are not exported.
- Overlaps are reported without changing timing.
- Conversion does not translate or transcribe text.
How local processing works
Subtitle parsing and serialization use lightweight TypeScript in this browser. No FFmpeg, account, network upload, translation, or AI service is involved.
Frequently asked questions
How do VTT timestamps change in SRT?
The period before milliseconds becomes a comma, such as 00:01:12.500 to 00:01:12,500.
Are cue identifiers preserved?
No. SRT uses sequential numbers, so WebVTT identifiers are replaced with a warning.
What happens to cue settings and regions?
They are not representable in SRT and are reported as discarded.
Are basic bold and italic tags retained?
Basic b, i and u tags remain; WebVTT-specific annotations are simplified.
Does conversion happen locally?
Yes. Subtitle text never leaves the browser tab.