Verbatimly

SUB to SRT.

MicroDVD .sub files count frames, not seconds — so the frame rate decides whether the timings land right. Paste the file or drop it, set the rate, get SRT. Nothing uploaded.

Film is usually 23.976 or 24 · PAL is 25 · NTSC video is 29.97 or 30. If the file declares its own rate on line one, that wins.

MICRODVD · 25 FPS2 cues
{25}{100}Hello there.
{138}{206}Second line.
SRT2 cues
1
00:00:01,000 --> 00:00:04,000
Hello there.

2
00:00:05,520 --> 00:00:08,240
Second line.

Frame numbers are not times

Most subtitle formats say "this line appears at 00:01:23,500". MicroDVD says "this line appears at frame 2092". Those are only interchangeable if you know how many frames pass per second — which the file usually does not tell you.

{25}{100}Hello there.
{138}{206}Second line.

Two numbers in braces, then the text. At 25 frames per second, frame 25 is exactly one second in and frame 100 is four seconds in — so this becomes 00:00:01,000 --> 00:00:04,000. At 30 frames per second the same file means 0.83s to 3.33s. Same file, different subtitles.

Why the wrong rate looks like a drifting problem

The error is proportional, not constant. Pick 25 when the video is actually 23.976 and every timestamp is off by about 4% — a cue that should appear at 1:00 arrives at 1:02, and a cue at 10:00 arrives 24 seconds late. It looks like the subtitles "drift" out of sync over time, which sends people looking for a sync tool when the real problem was the frame rate at conversion.

Practical sign: if the subtitles are right at the start and increasingly late toward the end, the frame rate was too low. Too early and worsening means it was too high.

What rate to use

The {1}{1} trick

Many MicroDVD files declare their frame rate on the first line, disguised as a caption that lasts one frame:

{1}{1}23.976
{24}{96}Hello there.

Players read that line as a rate setting rather than a subtitle. This converter does the same: if the declaration is there it is used, the line is removed from the output, and the frame rate box is ignored. That is the safe case — the file is telling you the answer.

Line breaks and italics

MicroDVD packs multiple lines into one cue with a pipe character, so Line one|Line two becomes a two-line cue in the SRT. Style overrides written as brace commands at the start of the text, like {y:i} for italics, are dropped — SRT has no styling field, though it does tolerate basic HTML tags if you want to add them back by hand.

Why convert at all

MicroDVD died with standalone DivX players. Nothing modern writes it and most tools refuse to read it. SRT opens in every video editor and upload form; WebVTT is the one browsers play natively. Both come out of the same converter.

Questions

Why does MicroDVD need a frame rate?

It stores frame numbers instead of times. Turning frames into timestamps needs frames per second.

Which frame rate should I pick?

The video's own rate: 23.976/24 for film, 25 for PAL, 29.97/30 for NTSC video. If the file declares one on line one, that value wins.

How far off is a wrong rate?

25 versus 23.976 is about 4% — roughly 24 seconds of drift across ten minutes.

What is the {1}{1} line at the top?

A frame rate declaration. It is read, used, and dropped from the output.

Is my file uploaded?

No — everything runs in your browser. See the privacy policy.

Related tools

VTT to SRT · SBV to SRT · SMI to SRT · SRT to TXT