Free, instant, and entirely in your browser — your subtitle file is never uploaded.
MicroDVD counts frames, not seconds — this has to match the video.
WebVTT is SRT rebuilt for the web: the same cue structure, a WEBVTT header line, a dot instead of a comma before the milliseconds, and optional positioning settings after the timestamp. It is the only subtitle format HTML5 video natively understands.
MicroDVD is the odd one out: it counts frames, not time. Each line is {start}{end} followed by the text, with a pipe between display lines. There is no timestamp anywhere in the file.
A caption file built for the web being sent to a device that predates it by a decade or more. Nothing about VTT's world applies on the other side: no styling, no positioning, no UTF-8 guarantees on some players, and no seconds — only frame numbers counted from the start of the video. Set the rate to the video's actual rate, not the rate you wish it were, and if the target is an old standalone player, expect to test on the device rather than trusting a preview.
You want MicroDVD because something old needs feeding: a DivX-era AVI, a hardware player, a set-top box that was never updated. It is not a format anyone chooses for new work, and going into it means committing to one frame rate for the life of the file — which is why the control above matters more here than anywhere else on the site.
Both sides carry the same thing — lines of text with a start and an end — so this is the cleanest conversion in the set. Nothing is approximated and nothing is thrown away; the timestamps are rewritten in the target's notation and the text goes across as it stands. What changes is compatibility: which players, platforms and browsers will accept the file you end up with. Because MicroDVD is the destination here, the frame rate is a decision you are making rather than one you are reading. Every timestamp is multiplied by it and rounded to a whole frame, so the file you get is locked to that rate: correct on a video that runs at it, and progressively wrong on one that does not. Set it to match the video before you convert, not after.
No. The conversion runs in your browser using JavaScript — your VTT file is read from disk, converted in memory and handed back as a download. Nothing is transmitted, so there is nothing for us to store or delete. You can disconnect from the internet after this page loads and the conversion still works.
A caption file built for the web being sent to a device that predates it by a decade or more. Nothing about VTT's world applies on the other side: no styling, no positioning, no UTF-8 guarantees on some players, and no seconds — only frame numbers counted from the start of the video. Set the rate to the video's actual rate, not the rate you wish it were, and if the target is an old standalone player, expect to test on the device rather than trusting a preview.
The page checks before it converts. Subtitle formats are identified by what is inside the file rather than by the extension — which matters, because .sub alone is used by three unrelated formats. If you hand this page something that is not VTT, it says so and points you at the all-format converter instead of producing a broken file.