Turn a plain TXT subtitle file into an LRC subtitle file quickly and securely—right in your browser.
[mm:ss.xx] tag — minutes, seconds, and hundredths of a second — followed by an optional metadata block of [ti:], [ar:], [al:], and [by:] ID tags at the top.[01:23.45] or SRT-style 00:01:23,450 --> ... markers, those are parsed and preserved. Either way the output opens cleanly in a synced-lyrics editor for retiming..lrc file individually or grab the whole batch as a ZIP.LRC was introduced in 1998 by Taiwan-based developer Kuo Shiang-shiang (Djohan) for the Lyrics Displayer program and an accompanying Winamp plug-in — making it one of the earliest karaoke-style synced-lyrics formats. It is a small sidecar text file that sits next to a music file (song.mp3 + song.lrc, same base name, same folder) and tells compatible players when to highlight each line. Almost every modern offline music player supports it, but only LRC's tagged form — a bare TXT of lyrics will not sync. Common reasons to convert a plain text lyric sheet into LRC:
[mm:ss.xx] tags only LRC provides..txt lyric files (from Genius pastes, liner-note scans, or old LyricWiki dumps), converting them to LRC and embedding them via Mp3tag or MusicBee preserves the lyrics with the audio and survives library moves.| Property | TXT | LRC |
|---|---|---|
| File extension | .txt |
.lrc |
| Standardized | No — generic plain text | De facto, no formal spec body; widely consistent |
| Timing data | None | [mm:ss.xx] per line; hundredths of a second |
| ID metadata | None | [ti:], [ar:], [al:], [au:], [by:], [length:], [offset:], [re:], [ve:] |
| Repeated lines (chorus) | Repeat the text | Stack timestamps on one line: [00:42.10][01:58.20]chorus |
| Word-level karaoke timing | No | Enhanced LRC ("A2"): <mm:ss.xx> per word inside a line |
| Typical encoding | UTF-8 or ANSI | UTF-8 (BOM-less recommended); UTF-16 is poorly supported |
| Best for | Source lyric sheets, transcripts, printable lyrics | Synced display in music players, karaoke apps, lyric plugins |
| Tag | Purpose | Example |
|---|---|---|
[mm:ss.xx] |
Line timing — minutes, seconds, hundredths | [01:23.45]Never gonna give you up |
[ti:] |
Track title | [ti:Bohemian Rhapsody] |
[ar:] |
Artist | [ar:Queen] |
[al:] |
Album | [al:A Night at the Opera] |
[au:] |
Lyricist / song author | [au:Freddie Mercury] |
[by:] |
LRC file creator | [by:[email protected]] |
[length:] |
Track duration mm:ss |
[length:05:55] |
[offset:] |
Global ms shift, +/- | [offset:+500] shifts everything 0.5 s later |
[re:] / [ve:] |
Editor / version | [re:xconvert] / [ve:1.0] |
<mm:ss.xx>word |
Enhanced LRC word timing | [00:15.20]<00:15.20>Hello <00:15.65>world |
Not automatically. LRC requires [mm:ss.xx] tags, but a plain text lyric sheet has no timing. The converter generates a structurally valid LRC file with sequential placeholder timestamps so it opens cleanly in a synced-lyrics editor (Foobar2000's ESLyric editor, MiniLyrics, LRC Editor by Soft Creator, or the web tool QuickLRC). You'll need to play the song against the file and nudge each line into place. If your TXT already contains [01:23.45]-style bracket timestamps or SRT-style HH:MM:SS,mmm markers, those are parsed and preserved as-is.
No. Both Spotify and Apple Music use proprietary lyric pipelines (Musixmatch for Spotify, an internal Apple system for Music) and neither accepts user-supplied .lrc sidecars. LRC is for offline players and self-hosted libraries — Foobar2000, MusicBee, AIMP, Poweramp, Jellyfin, Plexamp, Kodi, VLC with the third-party lyrics plug-in. If you want synced lyrics on Spotify, you need to submit them through Musixmatch, not through an .lrc file.
Standard LRC times to the hundredth of a second ([mm:ss.xx]) at the line level, which is sufficient for read-along lyrics but not strict karaoke. Enhanced LRC (sometimes called "A2 extended") adds word-level timing using angle brackets inside a line: [00:15.20]<00:15.20>Hello <00:15.65>world <00:16.10>!. Foobar2000 with ESLyric, AIMP, and several Android players render the word highlights; older or simpler players ignore the angle-bracket tags and just show the line.
Yes — the LRC must share the same base filename as the audio file and live in the same folder. For example, Bohemian Rhapsody.mp3 is paired with Bohemian Rhapsody.lrc. Most players (MusicBee, Foobar2000 + ESLyric, AIMP, Poweramp, Jellyfin) look there first, then optionally inside the audio file's tag. If filenames don't match exactly — including extension case on Linux — the lyrics won't load.
UTF-8 without a byte-order mark is the safest default in 2026. Every modern player (Foobar2000, MusicBee, AIMP, Kodi, Jellyfin, Poweramp) reads UTF-8 cleanly, including non-Latin scripts (Japanese, Korean, Chinese, Cyrillic, Arabic). UTF-8 with BOM works in most desktop players but some older Android lyric plug-ins choke on it. UTF-16 is widely unsupported — avoid it. If your TXT source is ANSI/Windows-1252 with Latin characters, the converter will normalize to UTF-8 automatically.
[ti:], [ar:], and [al:] metadata tags automatically?The structural LRC envelope is generated automatically, including a placeholder ID block. For accuracy you'll want to fill in [ti:Song Title], [ar:Artist Name], and [al:Album] after conversion — either by opening the .lrc in any text editor or by letting your music player auto-match against its tag database. Tools like Mp3tag can read the LRC and copy these fields from the paired audio file's ID3 tags in one click.
Plain TXT can't know which lines are choruses — it's just sequential text. The converter outputs one [mm:ss.xx] tag per non-empty source line, so a chorus that appears three times in the TXT becomes three timed lines in the LRC. LRC does support the more compact "stacked timestamp" form [00:42.10][01:58.20][03:14.30]Never gonna give you up, but generating that requires recognizing repetition. After conversion you can manually consolidate repeats in any text editor, which also shrinks the file.
Yes. Upload as many .txt files as you want — they convert in parallel inside your browser and download individually or as a single ZIP. There's no quantity cap and no per-file size limit beyond your device's available memory, since the conversion is fully client-side. Nothing is uploaded to a server, which matters if your lyric sheets are unreleased or under copyright restriction.
LRC is the right pick for music players and lyric apps — it's the only format Foobar2000, MusicBee, Poweramp, AIMP, Jellyfin, and Plexamp will treat as synced lyrics. SRT and WebVTT are subtitle formats designed for video players (VLC, YouTube, Plex video, HTML5 <track>) and most music players ignore them. If you're producing lyrics for a music video on YouTube, use SRT or WebVTT. If you're producing lyrics for an audio file in your library, use LRC.