Free, instant, and entirely in your browser — your subtitle file is never uploaded.
MicroDVD counts frames, not seconds — this has to match the video.
SRT is the plainest subtitle format there is: a number, a start and end time, the lines of text, a blank line, repeat. It came out of a 1990s DVD-ripping program called SubRip and has outlived every format designed to replace it, precisely because there is almost nothing in it to go wrong.
SBV is YouTube's own caption format, and about as simple as SRT with one line less: no sequence number, and the two timestamps separated by a comma rather than an arrow.
Worth pausing before you do this one: YouTube reads SRT perfectly well, so if you are uploading captions by hand you almost certainly do not need SBV at all. Where it earns its place is when something else in the chain insists on it — a caption-management tool, an agency's delivery spec, a script someone wrote years ago against YouTube's own export. The conversion itself is trivial and lossless, because the two formats hold exactly the same thing in different punctuation. The shape of the change is easy to check by eye: SRT numbers every cue and separates the two times with an arrow, while SBV drops the numbering entirely and joins them with a comma, on a single-digit hour. If a tool rejected your SRT and you are here as a guess, open the file first — a stray byte-order mark or the wrong text encoding is refused far more often than the format is.
You want SBV because you are uploading to YouTube and want the format its own editor writes. It is worth knowing this is rarely necessary — YouTube accepts SRT quite happily — so choose SBV when a workflow or a tool specifically asks for it, not as a default.
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.
No. The conversion runs in your browser using JavaScript — your SRT 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.
Worth pausing before you do this one: YouTube reads SRT perfectly well, so if you are uploading captions by hand you almost certainly do not need SBV at all. Where it earns its place is when something else in the chain insists on it — a caption-management tool, an agency's delivery spec, a script someone wrote years ago against YouTube's own export. The conversion itself is trivial and lossless, because the two formats hold exactly the same thing in different punctuation. The shape of the change is easy to check by eye: SRT numbers every cue and separates the two times with an arrow, while SBV drops the numbering entirely and joins them with a comma, on a single-digit hour. If a tool rejected your SRT and you are here as a guess, open the file first — a stray byte-order mark or the wrong text encoding is refused far more often than the format is.
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 SRT, it says so and points you at the all-format converter instead of producing a broken file.