An LRC File Generator turns typed lyric lines into a simple, time-stamped .lrc file that music players load beside an MP3, with no audio upload, speech recognition, or catalog lookup required. Each lyric row becomes a single line in the file prefixed by a bracketed minutes, seconds, and centiseconds timestamp, such as [01:23.45], and optional title, artist, and album fields become standard [ti:], [ar:], and [al:] metadata tags. The generator computes every timestamp by adding a fixed interval to a starting time, so it does not listen to the MP3, analyze vocals, or align phonemes. Everything happens locally in the browser tab: lyrics are not uploaded, no AI service is called, and the downloaded file is plain UTF-8 text without a byte-order mark. Because the preview always reflects the exact text that will be saved, you can confirm the result before clicking download. After download, individual timestamps are retimed in a dedicated editor against the actual MP3 recording, because a regular interval is only a first draft and real vocals rarely fall on perfectly equal spacing.
Inside the LRC File Generator
The tool solves one narrow problem well: producing a deterministic simple LRC text file from user-provided lyric lines plus a starting timestamp and a regular interval. You type or paste up to 500 non-empty lines, choose where the first lyric begins in MM:SS.xx form, and set how many seconds should pass between successive lines. The page then multiplies the decimal interval by 100, converts it to an exact integer number of centiseconds, and adds that count to the start time for each line. Because arithmetic happens in integer centiseconds rather than binary floating-point seconds, repeated addition does not accumulate drift, so line 50 stays exactly the same distance from line 1 as the interval predicts.
The output is intentionally conservative. The file uses only the simple-LRC subset that QuickLRC documents as a de-facto form and that the Subforge LRC parser source confirms by converting minutes to 60,000 milliseconds, seconds to 1,000, and the two fractional digits to centiseconds. Hour fields, three-digit milliseconds, angle-bracket word-level timestamps, karaoke duet markers, and player-specific extensions are not emitted, so the file remains compatible with the broadest range of players without locking anyone into a particular application's dialect.
Inputs, Limits, and the Simple LRC Subset
Before you click generate, it helps to know exactly what the tool accepts and what it deliberately rejects. The table below summarizes every interaction limit that determines whether the LRC File Generator can complete the task from your inputs.
| Setting | Accepted range or rule |
|---|---|
| Lyric lines | 1–500 non-empty rows; one lyric event per row |
| Characters per line | Up to 500 |
| Total input characters | Up to 50,000 across all lines |
| First timestamp format | 2–3 minute digits, exactly 2 second digits (00–59), a period, and exactly 2 centisecond digits |
| Valid timestamp examples | 00:00.00, 09:59.99, 10:00.00, 123:45.67 |
| Maximum timestamp | 999:59.99; generation fails if the last calculated time would exceed this |
| Interval | 0.01–600.00 seconds, with up to 2 decimal places |
| Metadata value length | Up to 120 characters after trimming |
| Disallowed in metadata | Square brackets and control characters |
| Line endings | CRLF, CR, and LF are normalized before generation |
| Blank rows | Removed before generation |
| Output encoding | UTF-8 plain text, no byte-order mark |
The contract is intentionally small. Optional metadata is limited to three tags: title becomes [ti:value], artist becomes [ar:value], and album becomes [al:value]. Empty metadata fields are omitted entirely, and a blank line is placed between the metadata block and the timed lyrics for readability. Any disallowed control characters in the lyric text are rejected rather than inserted into a file that a player might parse inconsistently, and the generator does not alter spelling, punctuation, capitalization, language, or copyright notices inside ordinary lyric text.
Generate an LRC File from MP3 Lyrics
The workflow is the same whether your source MP3 lives in foobar2000, iTunes, AIMP, VLC, or a phone-based player: prepare the lyric text, set the timing in the LRC File Generator, generate, then download. For a deeper walkthrough of the MP3-specific context, see how to get an LRC file for an MP3 in a local workflow.
- Enter 1–500 non-empty lyric lines, using one line for each display event. Paste from a plain-text editor or type directly. Windows, old Mac, and Unix line endings are normalized automatically, and blank rows are removed before generation.
- Set the first MM:SS.xx timestamp where the first lyric should appear, an interval between 0.01 and 600.00 seconds, and optional title, artist, and album values if you want standard metadata tags.
- Click Generate. The complete simple LRC text appears in the preview. Inspect the first and last timestamps to confirm the file ends before the song's runtime and never crosses 999:59.99.
- Click Download. The same text shown in the preview saves as a UTF-8 .lrc file with no byte-order mark. The filename is derived from the title when available, with unsafe punctuation replaced by hyphens; a blank title uses synced-lyrics.lrc.
- Load the file next to your MP3 in your target player or open it in a dedicated LRC editor to retime individual lines against the actual recording.
Because the preview always matches the downloaded bytes, you can verify the exact text before saving. Editing any input clears the previous preview, so stale content never lingers on the page, and temporary download object URLs are revoked after direct use and when the component unmounts, so an older file cannot be re-presented as the result of newer text.
A Worked Centisecond Interval Example
Suppose your first lyric begins at 00:12.34 and you choose a 2.50-second interval between lines. The tool multiplies 2.50 by 100 to get an integer offset of 250 centiseconds, then adds that count to each prior timestamp. Three lyric rows therefore receive:
- Line 1: 00:12.34 (the start time)
- Line 2: 00:12.34 + 250 centiseconds = 00:14.84
- Line 3: 00:14.84 + 250 centiseconds = 00:17.34
Line 100 at the same interval would land at 00:12.34 plus 99 × 250 centiseconds, and the page refuses to generate if any calculated timestamp would exceed 999:59.99. The full arithmetic in centiseconds is the reason this approach stays accurate for long songs: the file is never quietly truncated, and timestamps do not drift because of accumulated floating-point error. For a complementary explanation of how the start time and interval combine to produce a complete simple LRC, see how to make an LRC file with a start time and interval.
Retiming Lyrics Against the Real MP3 Recording
A fixed centisecond interval is a useful draft but rarely a finished product. Real vocals change tempo between verses and choruses, hold long notes across bar lines, and arrive early or late on certain phrases. Because the LRC File Generator does not listen to audio, detect speech, transcribe lyrics, align phonemes, identify beats, or estimate performance timing, the timestamps it produces reflect only the math you provided. Open the downloaded file beside your MP3 in a dedicated LRC editor and nudge individual lines until each lyric lands where a singer actually delivers it. Treat the generator as a way to skip the tedious blank-file setup and to populate hundreds of timestamps at once; treat the editor as the place where accuracy is achieved.
Player Compatibility Notes
Different music players support different metadata tags, timestamp precision, encodings, long minute values, and enhanced-LRC extensions, and the page cannot guarantee every player interprets the same file identically. The table below summarizes the considerations that matter most when you load a freshly generated .lrc next to an MP3.
| Consideration | What to expect |
|---|---|
| Line timestamp format | [mm:ss.xx] is the simple-LRC subset and is widely supported |
| Hour fields | Not emitted; players that require [hh:mm:ss.xx] may need a separate converter |
| Metadata tags | Only [ti:], [ar:], and [al:] are written; players that expect other tags will ignore the absence |
| Encoding | UTF-8 without a byte-order mark keeps the file portable across operating systems |
| Long minute values | Files are valid up to 999:59.99; some players may clip unusually long songs |
| Enhanced extensions | Word-level, karaoke duet, and player-specific extensions are not produced |
Always test the file in the exact player and on the exact device where the MP3 will be played. The generator's contract ends at producing a valid simple-LRC text file; everything downstream depends on the player and workflow you choose later.
Privacy, Copyright, and Local Processing
All content and arithmetic stay in the current browser tab. No lyric text is uploaded to Lizely, stored in an account, or sent to an AI service, and no audio from the MP3 is read by the page at any point. The downloaded .lrc file is built from the same string that appears in the preview, so what you see is what you save. You remain responsible for securing permission to reproduce and distribute any lyric text you enter; the tool does not supply copyrighted lyrics, search a catalog, identify a song, confirm ownership, or grant a synchronization license. It is purely a formatter for text you already have and have the right to use, and the resulting file remains yours to publish, share, or load into whichever player sits beside your MP3.