Convertisseur SRT en VTT

Subtitles travel as small text files, and the format matters. Video players and editors expect SRT, web players built on the HTML video element need WebVTT, and YouTube's own caption exports come as SBV. A file in the wrong format either fails to load or shows its timing codes on screen.

This converter reads SRT, VTT and SBV, detects which one you have, and writes any of the three. It can move every subtitle earlier or later by a number of milliseconds, fix overlapping lines, and lists timing problems it finds, each with its line or subtitle number. Everything happens as you type, in your browser, without the video converter download the other video tools need.

SRT, WebVTT and SBV compared

All three formats are plain text with a start time, an end time and the words to show. SRT, from the SubRip program, numbers each subtitle and writes times with a comma before the milliseconds, as in 00:01:02,500. WebVTT, the W3C format for web video, starts with a WEBVTT line, uses a full stop before the milliseconds, allows an hour part to be omitted and adds optional cue settings for position and alignment. SBV, used by YouTube, puts both times on one line separated by a comma and has no numbering or styling.

When converting, the timing and text carry over exactly. WebVTT cue identifiers and settings are kept when writing VTT; comment, style and region blocks are dropped. SRT output keeps the italic, bold, underline and font tags that SRT players understand and removes other markup, and SBV output is plain text. WebVTT character references such as & are turned back into characters for SRT and SBV.

Typical subtitle jobs

Encodings, validation and the overlap fix

Opened files are decoded carefully, because subtitle files come in many text encodings. UTF-8, with or without a byte order mark, and UTF-16 with a byte order mark are recognised directly. Older files that are not valid UTF-8 are read as Windows-1256 when that turns their special characters into Arabic letters, otherwise as Windows-1252, the Western European code page; a note names the encoding used. The result is always UTF-8, which every modern player reads, so this also repairs files that show garbled accented or Arabic letters. The reader is forgiving: missing numbers, missing blank lines and Windows or Mac line endings are accepted.

Below the result, a panel shows the detected format, the number of subtitles, when the last one ends and how many problems were found: timing lines that cannot be read (that subtitle is left out), text outside any subtitle, subtitles that end before they start, overlap the previous one, are out of order or have no text. Turning on Fix overlaps sorts the subtitles by start time, ends each one where the next begins and merges subtitles that start at the same moment into one with stacked lines. A shift that moves a subtitle entirely before 0:00 removes it, and the panel says how many were removed.

Comment utiliser cet outil

1. 1Paste subtitles into the Subtitles box, press Open file to load an .srt, .vtt, .sbv or .txt file, or press Try a sample.
2. 2Choose SRT, VTT or SBV under Convert to.
3. 3Optionally type a Shift (ms) and switch on Fix overlaps, then read the Validation panel.
4. 4Press Copy, or Download to save the result under the original name with the new extension.

Limitations

• Only SRT, WebVTT and SBV are supported. ASS, SSA, TTML and image-based subtitles such as PGS or VobSub are not.
• Shift moves all subtitles by the same amount. It cannot fix a drift that grows during the video, as happens with a different frame rate.
• Positioning and styling are lost when converting from VTT to SRT or SBV, since those formats cannot store them.
• Subtitles are not added to a video here. To show them permanently in the picture, use Burn Subtitles.