⌘ K
webvtt → srt · dot → comma · cue numbering · live

Convert WebVTT to SRT

Strip the WEBVTT header, switch the millisecond separator from a dot to a comma and add sequential cue numbers. Output is plain SRT ready for any player that hasn't moved to WebVTT yet.

WebVTT → SRT
Input
144 B
10 lines
Output
142 B
11 lines
Status
ready
live
Ratio
0.99×
out/in
input · webvtt
output · srt
1
00:00:01,000 --> 00:00:04,000
Hello, world.

2
00:00:05,500 --> 00:00:07,500
Second cue here.

3
00:00:08,000 --> 00:00:11,500
Closing line.
Quick Start

How the conversion works

WebVTT uses dot decimals (00:00:01.000) and an optional cue ID line; SRT uses comma decimals and a numeric cue ID before every block. We drop the WEBVTT header, rewrite the timestamps and emit a sequence number per cue.

  1. 01

    Paste WebVTT

    Begins with the WEBVTT header; cues are separated by blank lines.

    Parsing is strict-but-tolerant — comments and trailing commas are accepted on input where the source format historically permits them; output stays canonical.

    inputstricttolerantliveparse
    in · sourcevtt · live
    WEBVTT

00:00:01.000 --> ...
    loaded · parsedtarget · ready
  2. 02

    Strip header

    Everything from the WEBVTT line is removed.

    Conversion preserves type information where the target supports it (numbers stay numeric, booleans stay boolean) so the destination parser never has to re-coerce.

    cleantype-preservinglosslesslivememoised
    head · optionsdrop · live
    WEBVTT → (removed)
    options applied · liveround-trip
  3. 03

    Dot → comma

    Each timestamp's millisecond separator flips from . to ,.

    Re-encoding is idempotent: running output back through the same converter produces the same bytes, which keeps round-trips git-friendly.

    timestampsidempotentround-tripdiff-cleandeterministic
    . · converted, · ready
    00:00:01,000
    converted · livediff-clean
  4. 04

    Copy or download

    Save as .srt — ready for VLC, MPC-HC or legacy upload pipelines.

    Copy writes via navigator.clipboard.writeText; downloads use the target’s native MIME so editors apply the right syntax highlighting on open.

    exportclipboardtarget MIMEblobclient-side
    ✓ · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Converting between formats, safely

Pick the strictest source format

Lossy formats hide bugs. Choose JSON or YAML as your source-of-truth, convert downstream as needed.

Round-trip in CI

If your converter is idempotent, your CI can verify A → B → A equals the original. Catches subtle data loss.

Numbers vs strings differ

YAML/TOML have a number type; CSV doesn’t. Quote IDs in CSV to keep leading-zero values intact.

Watch character encoding

Source format may be Latin-1 / Windows-1252; target should be UTF-8. Convert encoding before structure.

Preserve comments where you can

YAML and TOML support comments. Don’t silently drop them — they often encode intent.

Schema-aware beats blind

Use a schema to guide conversion. Field types, required-ness, and defaults survive better with structure.

Related toolsSRT to VTTCSV to JSONXML to JSONYAML to JSONJSON to XMLCSV to YAML
Use Cases

When to convert WebVTT to SRT

Legacy players, DVD authoring, archive.

Desktop players

VLC and most desktop players prefer SRT. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the "'true' becomes "true"" bug class.

round-trip safe

DVD / Blu-ray

Authoring tools accept SRT input directly. Run output back through the inverse converter to verify idempotent round-trips in CI. A → B → A should produce byte-identical input — if it doesn't, you've found data loss.

type-preserving

Backup

Archive a WebVTT source alongside its SRT twin. Comments and metadata survive where the target format supports them (YAML, TOML, HCL). The tool doesn't silently drop intent-encoded annotations, which keeps your config self-documenting.

schema-aware

Re-encoding

Some encoders take SRT but not WebVTT. Pair with a schema (JSON Schema, OpenAPI, Zod, Pydantic) to catch shape drift on either side. Catch breaking changes at conversion time rather than at runtime in production.

lossless

Sharing

Hand subtitles to teammates who only have VLC installed. Output respects target-format conventions: quoting in CSV, indent in YAML, brackets in JSON. Existing parsers don't need patches, and the result drops into legacy pipelines unchanged.

diff-clean

Open source players

Most embedded subtitle libraries default to SRT. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks "works on my machine" doesn't apply here.

spec-grade
FAQ

Frequently asked questions

WebVTT identifier lines are skipped — SRT cue numbers are generated sequentially.
Plain text and basic HTML tags carry over. WebVTT-specific styling (cue settings, CSS) doesn't translate to SRT.
Yes — newlines inside a cue stay intact.
Paste the text only; if you have a file with a BOM, strip it first.
No. The conversion runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!