Guides

    VTT to SRT Converter in the browser is not a generate

    /free-tools/vtt-to-srt-converter never spends a credit. Do not pay a model to do an in-browser file job.

    Versely Team4 min read

    /free-tools/vtt-to-srt-converter never spends a credit. Do not pay a model to do an in-browser file job.

    VTT to SRT Converter turns WebVTT into SubRip in your browser. Nothing is uploaded. Nothing is sent to a model. There is no account gate and no generation meter. That is the product constraint for the whole free-tools shelf: Canvas, the File API, or arithmetic on the visitor's machine. A "converter" that quietly called a caption model, an OCR pass, or a chat completion would be a generate wearing a utility label.

    Versely has no free tier for generation. Every model call costs credits. Browser utilities sidestep that because they cost nothing to run. Use this tool when the job is "this .vtt needs to be a .srt." Do not prompt a video model to "redraw these captions as SubRip."

    The engine is your machine

    The file you choose is read into memory locally, converted there, and offered back as a download. Network off, it still works. That is also why it is actually free: no hardware of ours is in the loop. What it costs is the other book — credit formulas for per-second video, per-character voice, per-megapixel stills, caption burns, editor exports. VTT to SRT is not in that book. If a job is in that book, it is not this tool.

    Do not paste a caption file into an AI video generator and ask for a "subtitle restyle." You will spend a clip rate to invent a visualisation of a track. You will not get a sequential SubRip file. You will get a generate. The converter already emits numbered cues with comma timestamps. That is the artefact.

    What SubRip cannot carry

    WebVTT carries things SubRip has no way to express — positioning, alignment, styling blocks. Those are removed rather than pasted into the text, which is what a naive conversion does and why subtitles sometimes appear with stray markup burned into them.

    Cue settings such as position, line, size and alignment, plus any STYLE or REGION blocks and inline classes, do not survive. SubRip has no representation for any of it. The timing and the text survive intact, which is everything most workflows need, but a caption that relied on manual positioning will fall back to the player's default placement. If you need placement, stay in WebVTT until the player that will draw the captions.

    The converter also strips WebVTT inline markup (<v Speaker>, <c.classname>, <i>) so literal tags do not print on screen. It renumbers from 1 across the cues it actually emits, so a source that started at cue 2 — a NOTE block or a stray header counted as a cue — still lands as a sequential file.

    WebVTT separates seconds from milliseconds with a dot. SubRip uses a comma. That swap is the whole format. A file with the wrong separator parses as zero valid cues.

    Credits start after the file job

    Caption burns, Hailuo takes, editor exports: those quote a credit figure before they charge. This converter does not quote a figure because there is no charge. Mixing the two is how teams burn a model on a file job — "just generate new captions instead of converting." If you already have a VTT, convert it. If you need speech transcribed into a new track, that is add captions to a video, and it bills. Honesty about which object you are in is the whole decision.

    The sibling on the same shelf, also in-browser, is SRT to VTT when the player wants WebVTT. Timing drift after a trim is subtitle timing shifter, still not a generate.

    FAQ

    Does VTT to SRT use credits or a free-generation quota?

    Neither. It never spends a credit. The work never leaves your browser. Generation on Versely is a different surface and always bills.

    Are my caption files uploaded to Versely?

    No. The tool uses the File API on your machine. Nothing is sent to a server.

    Why did positioning disappear?

    Because SubRip cannot represent it. Cue settings, STYLE, REGION, and inline classes are dropped on purpose. Timing and text remain. Stay in VTT if placement is the deliverable.

    Can I prompt a video model to restyle the captions instead?

    You can waste the credits. You will not get this tool's sequential SubRip. Convert the file here. Burn or restyle captions on a video when the job is a video.