'%20data-app-shape='true'/%3e%3cg%20data-format-symbol='srt'%3e%3crect%20x='15'%20y='24'%20width='29'%20height='46'%20rx='5'%20fill='%23fff'/%3e%3cpath%20d='M24%2038h11m-11%208h11m-11%208h8'%20stroke='%23344665'%20stroke-width='3'%20stroke-linecap='round'/%3e%3c/g%3e%3cg%20data-format-symbol='vtt'%3e%3crect%20x='52'%20y='24'%20width='29'%20height='46'%20rx='5'%20fill='%23fff'/%3e%3cpath%20d='M61%2038h11m-11%208h11m-11%208h8'%20stroke='%23344665'%20stroke-width='3'%20stroke-linecap='round'/%3e%3c/g%3e%3cpath%20d='m42%2045%209%200m-4-5%205%205-5%205'%20fill='none'%20stroke='%23f4c34f'%20stroke-width='4'%20stroke-linecap='round'%20stroke-linejoin='round'/%3e%3c/g%3e%3c/svg%3e)
Convert SRT to VTT
Convert strict UTF-8 SRT cues to WebVTT while preserving times, text, identifiers, and line breaks.
- SECURE
- NO UPLOADS
- NO SIGNUP
- BROWSER BASED
- FREE
- FOREVER.
Support us with a link or a share
Convert SRT to VTT without rewriting the captions
SRT and WebVTT both describe timed text cues, but their timestamp punctuation and document framing differ. SRT commonly starts each cue with a sequence number and writes milliseconds after a comma. WebVTT begins with a WEBVTT signature and uses a period. This converter changes those structural details while keeping every parsed cue boundary and payload line.
Choose a local .srt file or paste SRT text. The parser requires strict UTF-8, a recognizable SRT signature, valid time tokens, an end after each start, and at least one payload line. A filename that says SRT while its content says VTT is reported as a mismatch rather than routed through a forgiving guess.
Every output cue is reopened and compared
Times are parsed as integer milliseconds. The output writer changes comma punctuation to WebVTT periods and emits an explicit hours field, then the completed VTT document is parsed again. Cue count, start time, end time, and joined payload lines must match the source. A mismatch produces no download.
SRT cue numbers are retained as WebVTT cue identifiers. Subtitle text, line breaks, and inline text markup are copied as payload rather than interpreted as HTML. Conversion does not translate captions, move them on the timeline, repair malformed markup, or burn them into video. Use the subtitle shifter when the actual job is timing correction.
A complete local file comes back
The preview is bounded for page performance, but the download contains the complete verified result. UTF-8 BOM state and the source's consistent CRLF choice are preserved; mixed or lone-CR input is normalized to LF so the result has one explicit newline style. The filename keeps the source stem and changes only the extension to .vtt.
Caption files often contain unreleased dialogue, names, or client material. Parsing, conversion, verification, preview, and Blob download creation all run in this tab. Nothing is written to a server, URL, or storage. To perform the reverse representable conversion, use VTT to SRT.
Questions
Does conversion change subtitle timing?
No. Every start and end time is parsed as integer milliseconds, written with WebVTT punctuation, reparsed, and compared with the SRT source.
Are formatting tags preserved?
Payload lines are preserved as text, including common inline markup. The converter does not translate or sanitize caption content.
Can I paste subtitles?
Yes. A local SRT file and pasted SRT text use the same parser and output verification.
Are subtitle files uploaded?
No. Parsing, conversion, verification, preview, and download generation happen in this browser tab.