⌘ K
srt → webvtt · comma → dot · WEBVTT header · live

Convert SRT to WebVTT

Add the WEBVTT magic header, replace the comma decimal separator with a dot and drop SRT cue numbers. The output drops straight into <track kind="subtitles"> elements.

SRT → WebVTT
Input
146 B
11 lines
Output
148 B
10 lines
Status
ready
live
Ratio
1.01×
out/in
input · srt
output · webvtt
WEBVTT

00:00:01.000 --> 00:00:04.000
Hello, world.

00:00:05.500 --> 00:00:07.500
Second cue here.

00:00:08.000 --> 00:00:11.500
And a third line.
Quick Start

How the conversion works

SRT uses cue numbers and comma decimals (00:00:01,000); WebVTT uses no cue numbers and dot decimals (00:00:01.000), plus the WEBVTT header. The body text is identical, so we just rewrite the metadata.

  1. 01

    Paste SRT

    Standard SRT format — blank lines between cues, optional cue numbers.

    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 · sourcesrt · live
    00:00:01,000 --> 00:00:04,000
    loaded · parsedtarget · ready
  2. 02

    Strip cue numbers

    SRT prefixes each block with a number — WebVTT doesn't need it.

    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
    n · optionsdrop · live
    1 → (removed)
    options applied · liveround-trip
  3. 03

    Comma → dot

    Milliseconds use a dot decimal separator in WebVTT.

    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 .vtt — ready for HTML5 video subtitle tracks.

    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 toolsVTT to SRTCSV to JSONXML to JSONYAML to JSONJSON to XMLCSV to YAML
Use Cases

When to convert SRT to WebVTT

HTML5 video, modern players, accessibility.

HTML5 video

Browsers require WebVTT (.vtt) for the <track> element. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the &quot;'true' becomes &quot;true&quot;&quot; bug class.

round-trip safe

Streaming platforms

Most cloud players accept WebVTT natively. 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

Accessibility audit

Move legacy SRT captions to modern WebVTT for screen readers. 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.

a11y

Static sites

Drop a .vtt into your CDN and reference it from <track>. 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

Migration

Switch a video site from a Flash-era SRT pipeline to HTML5. 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

Localisation

Translate SRT files and ship them as WebVTT alongside the video. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks &quot;works on my machine&quot; doesn't apply here.

i18n
FAQ

Frequently asked questions

WebVTT supports optional identifiers but SRT cue numbers are stripped — they often duplicate the sequence.
Plain text and basic HTML tags (b, i, u) carry across. WebVTT styles via CSS pseudo-elements aren't generated.
Vertical, line, position and align settings aren't inferred — add them manually if needed.
Yes — newlines inside a cue are preserved.
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!