Bring SRT or VTT.
Paste the text or open a local .srt / .vtt file. The format is detected from the header and timing lines, not the extension.
Turn SRT into WebVTT or WebVTT into SRT without uploading a thing. Timing, line breaks and cue order stay where you put them.
Paste the text or open a local .srt / .vtt file. The format is detected from the header and timing lines, not the extension.
Every cue must have a timing line and an end after its start. Malformed lines are reported with a line number instead of silently dropped.
Copy the result or download it as .srt / .vtt. Position settings and styling that only one format understands are called out, not invented.
Both formats keep hour, minute, second and millisecond precision. SRT uses a comma before milliseconds; VTT uses a dot.
Cue text is preserved as written, including tags such as <b> or VTT <c> spans. Wrapping is
never reflowed.
Backwards timings, impossible minutes and missing arrows stop the conversion with a message. A broken file is not quietly rewritten.
Yes. SRT becomes WebVTT and WebVTT becomes SRT. The source format is detected automatically, and you choose the output format in the result pane.
Settings such as align, line or position are specific to WebVTT and cannot be represented in SRT. They are dropped, and the result pane warns you that this happened. The text and timing are still converted.
The converter needs a timing line containing “-->” with an end time after the start. A missing arrow, a 61st minute or a backwards range cannot be converted honestly, so the tool points at the line instead of guessing.
Files up to 2 MB and 500 cues are accepted. That covers a feature-length subtitle file comfortably while keeping parsing responsive in a browser tab.
No. Parsing and serialisation happen in this page. There is no media upload endpoint or account, and closing the tab discards the text.