Upload LRC files and pick an output format — SRT is selected by default. Batch supported, free up to 400 MB per file.
For the most common job, use the dedicated LRC to SRT converter.
.lrc files are accepted here — a plain-text file of [mm:ss.xx] time tags and lyric lines. You can also paste the LRC text straight into the input box.<track> and the open webLRC is a synchronized-lyrics format, not a video-subtitle format. It was first introduced in 1998 by Taiwan-based Kuo (Djohan) Shiang-shiang's Lyrics Displayer, which shipped with a plug-in for Winamp, and it has been the standard "synced lyrics" sidecar for music players ever since. An LRC file is plain text: each line carries a [mm:ss.xx] start tag followed by the lyric, plus optional ID tags like [ti:] (title), [ar:] (artist), [al:] (album), and [offset:] for a global timing nudge. Players such as foobar2000, MusicBee, and many car and phone apps read it to scroll lyrics in time with the song.
The catch is that LRC speaks only to music players. Video editors and caption pipelines — Premiere Pro, Final Cut, YouTube's caption uploader, HTML5 <video> — don't read LRC time tags at all. So the most common reason to convert is to make timed lyrics ride along as captions somewhere LRC can't go:
<track> element loads natively, so LRC to VTT is the move for a lyrics overlay on a web player.One thing to know going in: LRC stores a start time per line and nothing else — there is no explicit end time. When converting to SRT or VTT, each cue's end is inferred from the start of the next line (the last line gets a short default duration). That is normal and expected, not a bug in the conversion.
| Property | Value |
|---|---|
| Full name | LRC — synchronized lyrics (a plain-text "sidecar" file) |
| Introduced | 1998, by Kuo (Djohan) Shiang-shiang's Lyrics Displayer, with a Winamp plug-in |
| File type | Plain text; UTF-8 recommended for non-Latin lyrics |
| Line timing tag | [mm:ss.xx] — minutes, seconds, hundredths of a second |
| End times | None — a line shows until the next line's timestamp |
| Word-level timing | Enhanced LRC ("A2") only: <mm:ss.xx> angle-bracket tag per word |
| ID / metadata tags | [ti:] [ar:] [al:] [by:] [offset:] [length:] |
| Offset unit | Milliseconds, prefixed + or - for a global shift |
| Styling / positioning | None |
| Opens in | foobar2000 (ESLyric), MusicBee, AIMP, Poweramp, Jellyfin, Plexamp; any text editor |
| Format | Timing model | Carries styling | Native use | Best for |
|---|---|---|---|---|
| LRC | Line start only ([mm:ss.xx]); A2 adds word-level <mm:ss.xx> |
No | Music players (foobar2000, MusicBee, car/phone apps) | Synced lyrics beside an audio file |
| SRT | Start + end per cue | No | Players, YouTube, every video editor | Universal subtitle/caption exchange |
| VTT | Start + end per cue | Limited (cue settings) | HTML5 <track>, web players |
Web captions and lyric overlays |
| ASS / SSA | Start + end per cue | Yes (font, color, position) | Aegisub, MPV, karaoke tools | Styled and karaoke-timed captions |
| TXT | None | No | Any text editor | A plain lyric sheet, no timing |
| CSV | Whatever you keep in a column | No | Spreadsheets, scripts | Data/automation pipelines |
An LRC file is a plain-text lyrics file that pairs each line of a song with a [mm:ss.xx] timestamp so a media player can scroll the words in time with the audio. It is a sidecar — usually named to match the track, like song.lrc next to song.mp3. Music players including foobar2000, MusicBee, AIMP, and many mobile and car apps read it directly; because it is just text, you can also open and edit it in any text editor like Notepad or TextEdit.
No — the line timing is preserved. The converter reads each [mm:ss.xx] start tag and writes it as a proper subtitle cue. The one thing LRC doesn't store is an end time per line, so the converter sets each cue to end when the next line begins, which is how synced lyrics already behave on screen. In our testing, a 40-line Simple LRC file converted to SRT produced 40 sequential cues with start times matching the originals to the hundredth of a second and end times chained to the following line.
Simple LRC (the original format) tags timing at the line level: one [mm:ss.xx] stamp per lyric line. Enhanced LRC — the "A2" extension — adds word-level timing inside the line using angle-bracket tags like <00:15.20>, so a karaoke player can highlight each word as it is sung. Both are valid .lrc files. When you convert Enhanced LRC to a subtitle format like SRT, the word-level tags are flattened to line-level cues, because SRT has no concept of per-word timing.
For most editors and platforms, choose SRT — it is the most universally accepted subtitle format and uploads cleanly to YouTube, Premiere Pro, Final Cut, and DaVinci Resolve. If the lyrics are for a web page played through an HTML5 video element, pick VTT instead, since <track> only loads WebVTT natively. Choose ASS or SSA when you intend to style the lines (font, color, on-screen position) or build karaoke timing in a tool like Aegisub.
Save the LRC as UTF-8 and any script — accented Latin, Cyrillic, Japanese, Korean, or Chinese — converts with the characters intact. If output comes back garbled, the source .lrc was almost certainly saved in a legacy single-byte encoding (Shift-JIS or Windows-1251, say); re-open it in a text editor, re-save as UTF-8, and convert again. The timestamps themselves are plain ASCII and are never affected by the encoding.
LRC ID tags such as [ti:], [ar:], and [al:] describe the whole file, not individual cues, and most subtitle formats have no equivalent header for them — SRT and VTT, for instance, carry no song-level metadata. So those tags are dropped during conversion to a subtitle format; only the timed lyric lines become cues. If you need to keep the metadata, convert to a format like CSV or TXT where you can retain the header text, or keep the original .lrc alongside the new file.
Yes — converting the other direction works the same way. Each subtitle cue's start time becomes a [mm:ss.xx] line tag and the end times are dropped, since LRC has none, so a karaoke subtitle or a music-video caption becomes a lyrics sidecar you can drop next to the audio. For the most common swap, the dedicated SRT to LRC converter walks through it; VTT, ASS, and other subtitle sources have matching pages.
Each [mm:ss.xx] tag in LRC holds a single line of text, so if your source has multiple lines sharing one timestamp they are joined into one. This matches how music players render lyrics — one highlighted line at a time. Going the other way, an LRC line stays on a single subtitle cue; if you later need it split across two on-screen lines, add the break in a text editor after conversion.
Yes. The conversion runs entirely in your browser. There is no sign-up and no watermark. Because LRC files are tiny plain text, the conversion is effectively instant and you can convert as many as you need.