Convert VTT to SRT locally in your browser. Before a file becomes Ready, the worker parses the complete subtitle, counts cues, detects text encoding, and identifies richer formatting or WebVTT metadata.
Why convert VTT to SRT?
VTT and SRT store the same basic idea—timed text—but use different timestamp syntax and container rules. Converting creates a compatibility copy for software or publishing workflows that expect the destination format.
Full-file preflight before the queue says Ready
The Subtitle engine does more than check the filename. It sends the complete subtitle to its local Web Worker, parses every cue, validates each start/end pair, detects the text encoding, counts cues, records the timeline end, and flags richer formatting or WebVTT metadata. The queue metadata then shows useful facts such as cue count, timeline length, encoding, and whether presentation metadata was detected.
A file with a valid first cue but broken timing near the end is rejected during admission instead of failing only after you press Convert. Ambiguous SRT blocks containing multiple timestamp lines are also rejected rather than silently turning later timing into subtitle text.
What is preserved?
| Subtitle detail | Converter behavior |
|---|---|
| Cue order | Kept in source order; the converter does not sort or merge cues. |
| Start / end timing | Converted to millisecond timing where the destination supports it, with an optional exact global millisecond offset. |
| Line breaks | Dialogue line breaks are retained in timed subtitle outputs unless the chosen transcript mode changes spacing. |
| Readable text | Kept. Plain-text mode can intentionally remove inline formatting markup. |
| Original file | Never modified. |
Advanced controls without turning this into a subtitle editor
What changes during conversion?
WebVTT can carry cue identifiers, cue settings, regions, NOTE blocks, STYLE blocks, and timestamp-map metadata that simpler formats do not understand. Those features are detected during preflight so the source is not treated as plain timed text by accident.
How the browser-first Subtitle workflow works
- Add a subtitle. The engine checks the extension, then fully parses the file in its worker before admission.
- Review the queue facts. Cue count, timeline end, encoding, and richer-format flags appear with the source metadata.
- Choose output and controls. Set an exact timing offset, formatting cleanup, transcript options, line endings, or BOM as needed.
- Convert locally. The worker applies deterministic cue transforms and serializes SRT.
- Download a new file. The browser saves the converted copy; the original stays unchanged.
Before you replace the source subtitle
- Spot-check early, middle, and late cue timing in the destination player.
- Keep ASS/SSA sources if styling, karaoke, placement, or effects matter.
- Check speaker markup and inline emphasis when moving between subtitle ecosystems.
- Use negative timing shift carefully; the converter refuses to move cues before 00:00.
- Keep the original until the destination tool renders the converted file as expected.