Skip to main content
Echoryte

Local subtitles tool

Convert WebVTT to SRT locally

Turn a WebVTT caption file into a clean SubRip file locally, while rejecting invalid headers, timing, empty cues, and overlaps.

Go to local workbench
Execution
This browser
Output
Validated .srt subtitle file
Content review
2026-07-20

Browser workbench · no upload

Work on this device

File content stays inside this browser tab.

Output

.srt · UTF-8

The parser validates the complete document before a download is enabled.

Nothing leaves this tab.

This browser tool reads a WEBVTT document, ignores specification-defined NOTE blocks, validates each timed cue, and writes a sequential SRT document. It is intended for straightforward timed text, not for flattening every WebVTT styling or positioning feature.

Workflow

A short, inspectable path

  1. 01Select a WebVTT file that starts with the WEBVTT header.
  2. 02Run the local validator and correct the cited cue or source line if conversion stops.
  3. 03Download the new SRT and compare a few cue boundaries against the original media.

How the formats map

A valid WebVTT file begins with WEBVTT. The parser then reads timed blocks, converts dot-based timestamps to SRT comma timecodes, assigns contiguous one-based cue numbers, and escapes cue text. Invalid input produces a cue or line hint instead of a partial download.

Know what SRT cannot carry

SRT is widely exchanged but has no single styling model comparable to WebVTT. If the source uses regions, vertical writing, alignment settings, or styled spans, keep the original as the archival copy and manually inspect the simplified SRT output.

Local-data boundary

The WebVTT bytes remain in browser memory. Tool routes load no third-party analytics and emit no tool outcome event; the file name, cue text, timing, format choice, and byte count remain local.

Limits worth keeping visible

  • WebVTT regions, CSS styling, voice spans, and cue positioning have no complete SRT equivalent and are not preserved by this basic converter.
  • The parser accepts timed cues and NOTE blocks; documents that depend on advanced WebVTT metadata should stay in WebVTT.

Reviewed references