FORMAT WORKSHOP · 16 OCTOBER 2026
LRC vs SRT: differences and conversion mistakes
By Jianming Duan · Prepared with AI assistance; examples checked against this converter.
A file can contain the right words and still produce the wrong subtitles. LRC and SRT describe different timing decisions: a lyric start is not a complete subtitle interval. Use the comparison below to decide what can transfer directly and what you need to review.
The structural difference
Line-level LRC associates text with a start tag. SRT groups text into numbered cues, each with a start and an end. SRT timecodes use hours, minutes, seconds and comma-separated milliseconds; LRC tags in this converter use minutes, seconds and optional decimal fractions. The Library of Congress description of SubRip documents the cue-block structure and notes the format’s limited standardization.
[00:09.40]Windows catch the evening light [00:13.00] [00:18.25]Footsteps fade along the lane
This original input contains two text lines and an empty timed line. With offset disabled, zero shift and a final-line duration of two seconds, LRC Workbench produces:
1 00:00:09,400 --> 00:00:13,000 Windows catch the evening light 2 00:00:18,250 --> 00:00:20,250 Footsteps fade along the lane
The blank tag ends the first cue without adding an empty subtitle block. The second cue’s end comes from your two-second setting. Neither end time was discovered by listening to audio.
Mistake: expecting an end time to exist in the source
If you remove the empty 13-second tag, the first cue remains visible until 18.250 seconds in this converter. That may be correct for continuous singing and wrong for a pause. Add a blank timed line where the lyric should disappear, or shorten the cue later in your subtitle editor. Do not globally shorten every line to fix one instrumental break.
Mistake: confusing fractions and milliseconds
The LRC fraction .40 means 400 milliseconds, so the first SRT start is 00:00:09,400. Copying it as ,040 moves the cue by 360 milliseconds. Keep the precision you have, and let the converter pad the fraction. Replacing punctuation by hand also misses SRT’s numbered blocks and end-time requirement.
Mistake: correcting timing twice
An offset tag and an editor track adjustment can both move the same cue. Here a positive LRC offset advances the lyric, while positive shift delays it. If a file already has its correction written into every timestamp, applying the old offset again changes otherwise correct timing. Keep an unmodified source, compare one recognizable word, then apply a correction in one place.
A constant error throughout the song suggests a uniform shift. A growing error or a sudden jump after an edit requires a different investigation. Neither file format knows which audio recording or video cut you intended.
Mistake: expecting word timing or styling to survive
Enhanced LRC may contain inline word timestamps. The tool rejects those rather than exporting a seemingly successful file with lost karaoke timing. Use a line-level export if ordinary subtitles are sufficient; retain the word-timed source if highlighting is essential. SRT text also does not guarantee the same font, color or position across players. Set and check presentation in your destination workflow.
Mistake: treating every timed line as a separate cue
When two lines share a start time, this converter groups their text into one multiline cue. This is useful for bilingual subtitles, but you should inspect the resulting line count and wrapping. Repeated identical text at that time is deduplicated. A repeated timestamp on a single source line schedules that line again at each listed time.
Mistake: blaming the timing format for broken characters
If letters appear as replacement symbols, stop and return to the source encoding. The converter rejects replacement characters because it cannot recover the original letters from them. Re-save a readable original as UTF-8 and convert that copy. Renaming the extension or downloading again does not repair already damaged text.
A short verification routine
- Compare a known start in the LRC with its SRT start after offset and shift.
- Check one silence: the preceding cue should end when you intend.
- Inspect the last cue’s end, which has no later lyric to guide it.
- Import into the destination editor and confirm bilingual text and timing.
- Retain the LRC because the SRT cannot reconstruct discarded metadata or word timing.
If the preview and SRT agree but playback differs, report the destination application and a minimal example through the contact page. That separates a parser problem from an import or presentation problem.
Put it into practice
Starting with plain or timestamped text? Use TXT to SRT to prepare a timing draft, then check it against your recording.