An LRC file is a plain text document that pairs each line of song lyrics with a display timestamp in [mm:ss.xx] form, and a beginner-friendly LRC file generator turns raw lyric text into that file by stamping one bracketed timestamp in front of every line at a fixed centisecond interval. The format is a de-facto standard rather than a documented specification, but its core is simple: each line begins with a bracketed minutes, seconds, and centiseconds value that controls when the lyric appears in a synced-lyrics player. After you paste your lyrics and pick a starting timestamp such as 00:12.34 alongside a 2.50-second interval, the generator adds that same interval to the start time for every successive line, producing a complete file inside the current browser tab. The math is integer-based so repeated addition does not drift, optional title, artist, and album tags are emitted only when you fill them in, and bracketed values or control characters in metadata fields are rejected before they can sneak into the output. Because every validation step, the preview, and the download happen client-side, your lyric text never leaves the page, and the saved file is the exact UTF-8 text shown in the preview without a byte-order mark.
What an LRC File Actually Is
Beginners often hear "LRC" and picture something exotic, but the format is built on three modest pieces: an optional metadata header, one timestamp per lyric line, and the lyric text itself. A timed line in the simple LRC subset looks like [01:23.45]Example lyric line, where the bracketed value is minutes (two or three digits), a two-digit second value from 00 to 59, a period, and exactly two centisecond digits. That fractional pair represents hundredths of a second, which gives most modern synced-lyrics players enough resolution to feel responsive during playback. According to the QuickLRC format documentation, this simple form is the widest-used subset across mainstream music apps, even though extensions exist for word-level karaoke and duet markers.
The minutes field stretches unusually far. The generator accepts timestamps through 999:59.99 so very long DJ mixes and podcasts remain representable, even though most pop songs sit comfortably below the 99-minute mark. Hours are not emitted, because the format relies on long minute values rather than a dedicated hour segment. Optional header tags such as [ti:] for title, [ar:] for artist, and [al:] for album are written only when you supply them, and they sit above a blank separator line before the timed rows begin.
Two details are worth knowing up front. First, blank rows inside your pasted lyrics are treated as separators and stripped, so each line you submit becomes exactly one timed row. Second, square brackets inside metadata values, and disallowed control characters inside your lyric text, are refused rather than embedded, because a stray bracket inside an [ar:Example [Live] Version] field could otherwise be parsed as an extra LRC tag by another player.
Inputs the Generator Accepts
The form is deliberately narrow so beginners can fill it in without a learning curve. The table below summarizes every input, what it controls, and the limits the generator enforces.
| Field | What it controls | Accepted range and shape |
|---|---|---|
| Lyric lines box | One display line per row, used as the lyric text of every timestamped line | 1–500 non-empty rows; 50,000 input characters total; 500 characters per row |
| Start timestamp | The display time of the first lyric line | [mm:ss.xx] with 2–3 minute digits, 00–59 seconds, period, two centisecond digits, e.g. 00:00.00, 09:59.99, 123:45.67 |
| Interval | Seconds between successive lines, added by line index | 0.01–600.00 seconds, at most two decimal places; converted to integer centiseconds internally |
| Title, Artist, Album | Optional [ti:], [ar:], [al:] header tags | Up to 120 characters each, no square brackets, no control characters; blank values are omitted |
| Output ceiling | Largest timestamp the file can contain | 999:59.99; generation fails rather than truncating if the last line exceeds this |
Notice that the start timestamp is your anchor, not a per-line offset. If you choose 00:30.00 and a 3.00-second interval, the third line lands at 00:36.00, the seventh at 00:48.00, and so on. If the calculated final timestamp would pass 999:59.99, the generator fails outright rather than silently truncating the last few lines, which prevents you from downloading a file that quietly ends mid-song.
Build Your First LRC File Step by Step
This walkthrough assumes you have a text file with lyrics or a rough draft in a notes app and want to produce a working file on your first try.
- Open the LRC File Generator in any modern desktop or mobile browser; nothing installs, no account is required, and no audio file needs to be uploaded.
- Paste your lyric text into the lyrics box. Use one row per display line and remove blank separators if you want tight alignment with sung phrases.
- Enter a start timestamp in MM:SS.xx form, for example 00:10.00 if your song's first sung line enters ten seconds into the track.
- Set an interval between 0.01 and 600.00 seconds. Pick something close to the average spacing of your song, knowing you will refine individual lines later.
- Fill in the Title, Artist, or Album fields only if you want [ti:], [ar:], or [al:] tags in the header; leave them blank to skip them entirely.
- Click Generate and read the preview pane, paying attention to the first and last timestamp and to any metadata block at the top.
- Click Download to save a UTF-8 .lrc file. The filename comes from your Title (with unsafe punctuation replaced by hyphens) or defaults to synced-lyrics.lrc if you left the Title blank.
- Open the saved file in a text editor to confirm the preview matches the file exactly, then load both the audio and the .lrc into your music player.
Editing any field clears the previous preview so the file you download can never be a stale snapshot of older inputs. The Download button uses a fresh object URL that the browser revokes after use and again when the page unmounts, so an earlier file cannot linger as the apparent result of newer lyrics.
A Worked Example from Start to Last Line
To make the arithmetic visible, here is one concrete run with a start of 00:12.34, a 2.50-second interval, and three lines long. The interval is converted to 250 integer centiseconds before any row is produced, then added by line index without floating-point drift:
- Line 1: 00:12.34 plus 0 × 250 cs = 00:12.34
- Line 2: 00:12.34 plus 1 × 250 cs = 00:14.84
- Line 3: 00:14.84 plus 250 cs = 00:17.34
This single example matches the arithmetic described in the implementation notes: each successive line receives the original start time plus the integer-centisecond interval multiplied by its zero-based index, so even hundreds of additions stay exact. If you entered an interval of 2.33 seconds (233 centiseconds) starting at 09:58.99, line 30 would land at 11:06.56, still well within the supported 999:59.99 ceiling.
Reading the Preview Before You Click Download
The preview pane is not decorative: it shows the exact text that Download will save, character for character. Beginners should verify three things before clicking the button. First, confirm that the first timestamp matches the moment your vocalist actually begins; a 00:00.00 anchor with no vocal until 00:08 will look fine in the preview but feel late on playback. Second, scan the last timestamp to make sure it does not run past your song's real ending; if it does, drop your interval or trim the lyric count. Third, inspect any [ti:], [ar:], or [al:] lines on top to make sure titles, artist names, or album names are spelled correctly and were not truncated to the 120-character maximum.
If a [ti:] or [ar:] tag is missing entirely, that means you left the corresponding field blank rather than the generator refusing to write it; empty metadata fields are simply omitted, and no placeholder line appears in their place. If the preview has no metadata block at all, all three optional fields were empty.
After Download: Retime Against the Real Recording
A fixed-interval file is a starting draft rather than a finished product. Real vocals rarely space themselves at perfectly equal intervals, and an autogenerated file will only feel "in sync" at the exact instants where the constant interval happens to coincide with a sung phrase. To tighten the result, open the .lrc file beside your audio in a dedicated lyrics editor that supports clicking on a waveform to snap a timestamp, then walk through line by line. The independent Subforge LRC time implementation confirms the centisecond arithmetic the generator uses, but it does not promise identical parsing behavior across every player app.
Different players read the same file differently. Some reject long minute values above 99, others ignore certain enhanced-LRC extensions, and character encoding can vary. Always test the file in your target player, and if a section reads late or early, edit that specific [mm:ss.xx] value in a text editor until the alignment is correct. The optional header tags are also read differently: a player that ignores [al:] is not broken, it simply does not display album metadata.
What the Generator Does Not Do (and Why That Matters)
This tool is intentionally narrow. It does not listen to audio, transcribe lyrics, identify a song, align phonemes, detect beats, or estimate performance timing. It does not search a lyrics catalog, supply copyrighted text, or grant a synchronization license, and it does not upload your lyrics anywhere; every calculation and the download itself happen inside the current tab, and the only network activity is loading the page.
For a beginner, this narrow contract is a benefit: you always know what the generator will and will not give you. You provide the words, you choose the start and interval, you read the preview, you download the file, and you refine the timing by hand against the actual recording. The reliable contract covers only the simple LRC subset plus optional ti/ar/al metadata, so any compatibility beyond that remains the responsibility of the player and the workflow you choose later.
If you are new to synced lyrics altogether, the simplest way to start is to pick a short song whose lyrics you already know by heart, use a 3.00-second interval, inspect the preview's first and last timestamp, and load the result into your music player to see whether the timestamps land near the right words. From there, retime a few problem lines, save the corrected file in your player, and you have your first working .lrc without ever leaving the browser.
For a deeper look, see Free LRC File Generator, No Sign-Up Required.
For a deeper look, see Volume Changer for Beginners: First-Time User Guide.