LRC to SBV
Or paste subtitle text
Options
Used when the source has no end times (plain text, LRC). The timeline in the output is generated here rather than converted, so this number is what you get.
What this conversion changes
1 thing is dropped or needs a decision
- Timing
cue end times — the source does not record them, so the output's will be generated rather than converted
This list comes from the capability matrix for these two formats, not from the particular file you loaded. A specific file may lose more if it uses features the format allows but the matrix does not model.
This page converts LRC to SBV. Drop a file in — or paste the text — and you get the SBV version back. The conversion runs entirely in your browser, so nothing is uploaded and no account is needed.
These two formats do not store the same things, and the difference is not cosmetic: timing has nowhere to go in SBV. The list above comes from what the two formats can each express rather than from your file, so it is the same answer before you load anything.
One file is fine, and so is a whole season: the queue works through them in order and the results come down together as a single ZIP.
Examples
A typical LRC file, converted to SBV
Input
[ti:Sample Song]
[ar:Some Artist]
[length:00:41.00]
[offset:+250]
[00:12.00]First line of the song.
[00:15.30]Second line.
[00:15.30]Second line, translated.
[00:18.00]
[00:21.50]Final line.Output
0:00:12.000,0:00:15.300
First line of the song.
0:00:15.300,0:00:18.000
Second line.
Second line, translated.
0:00:18.000,0:00:21.500
0:00:21.500,0:00:23.500
Final line.
Dropped in this output: timing. Everything else matches line for line.
The same conversion on an awkward input
Input
[ar:Some Artist]
[0:05.5]Leading zero omitted, one decimal.
[00:07]Second with no centiseconds.
[00:03.00]Out of order.
[00:07.00][00:09.00]Repeated chorus line.
[00:12.00]Output
0:00:03.000,0:00:05.500
Out of order.
0:00:05.500,0:00:07.000
Leading zero omitted, one decimal.
0:00:07.000,0:00:09.000
Second with no centiseconds.
Repeated chorus line.
0:00:09.000,0:00:12.000
Repeated chorus line.
0:00:12.000,0:00:14.000
This is the kind of damage real files have — mixed line endings, stray whitespace, fields left empty. Compare it with the tidy example above to see what the parser forgives.
Frequently asked questions
How does an LRC line get an end time in SBV?
From the next line's start. An LRC line runs until the following one begins — that is the rule a lyrics player follows — so the SBV ends are real rather than invented. The exception is the last line, which has nothing after it and is given the duration set on this page.
What does the output look like when LRC becomes SBV?
Like SBV: no cue numbers and no header — a line with the two times on it, and then the text. Every LRC cue becomes one SBV cue, in the same order, with the same text.
How does a two-line LRC cue come out in SBV?
As two lines, one under the other. The pairing survives — the two LRC lines still belong to one subtitle in the SBV output, and a player shows them together.
Do LRC cues keep their order in the SBV output?
Yes, and they are sorted by start time on the way — earliest first, which is how every format here expects them and how players read them. If your LRC file listed its cues out of sequence, the SBV output puts them back in order; that is a change to the file's structure rather than its content, and it is deliberate.
Can I convert the SBV back to LRC?
Yes, and it has its own list: converting SBV to LRC drops timing and precision. That list is different from the one above because the two formats keep different things.
Does the SBV output keep the LRC file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the LRC file used. A file that arrives in UTF-16, or in a Windows single-byte encoding, is decoded on the way in (the result panel says so when that happens); what comes out is always the same UTF-8 SBV.