The LRC File Generator does not listen to your audio and does not auto-align each lyric line to a recording. It creates a deterministic simple LRC file by placing one [mm:ss.xx] centisecond timestamp in front of every line of text you supply, where the spacing between consecutive lines is a single fixed interval you choose. There is no microphone capture, no vocal detection, no speech-to-text transcription, no beat estimation, no phoneme alignment, and no upload to any service. Every calculation happens in your current browser tab from the text, start timestamp, and interval you provide. Because the tool produces a uniform draft rather than a recording-aware sync, the result is best understood as a starting point that you open beside the actual track and refine in a dedicated LRC editor or your music player. That contract is intentional and bounded — the page does exactly what is described above, and no more. Readers who want audio-aware alignment should treat this tool as the first half of a two-step workflow, with manual retiming supplying the second half.
What the Generator Actually Does and Doesn't
Several readers arrive at the tool expecting an AI-assisted sync similar to Whisper-based aligners, where the application listens to a track and stamps each lyric line at the moment vocals begin. The LRC File Generator works differently. It treats your text as a list of display events and assigns timestamps by simple arithmetic: line N receives the start timestamp plus N−1 intervals, with the interval converted to an exact integer number of centiseconds before any line is emitted. This avoids the binary floating-point drift that would otherwise accumulate across hundreds of additions.
The product does not analyze a song file, does not detect onsets, does not estimate tempo, does not pull lyrics from a catalog, does not confirm copyright, and does not grant any synchronization license. You supply the text, the first timestamp, and the interval; the tool emits [ti:], [ar:], and [al:] metadata only when you provide values, and emits nothing else. Editing any input clears the preview so the displayed text always matches the current settings. Users must have permission to reproduce and distribute the lyric text they enter — the tool simply formats what you already have.
The Fixed-Interval Approach Explained
The simple LRC subset that the tool implements marks every display line with a bracketed minutes, seconds, and centiseconds value followed immediately by the lyric text, for example [01:23.45]Example line. According to the QuickLRC LRC format reference, this de-facto form is what most players accept as a baseline, and the independent Subforge parser confirms the contribution of each field — minutes contribute 60,000 milliseconds, seconds contribute 1,000 milliseconds, and the two fractional digits represent centiseconds.
The interval is parsed as a decimal between 0.01 and 600.00 seconds, with at most two decimal places, and is converted to an integer count of centiseconds before any rows are produced. A 2.50-second interval therefore becomes exactly 250 centiseconds per line, and repeated addition does not drift. A worked example drawn from the tool's own arithmetic: a start of 00:12.34 plus a 2.50-second interval applied to three lines yields 00:12.34 for line 1, 00:14.84 for line 2 (12.34 + 2.50 = 14.84), and 00:17.34 for line 3 (14.84 + 2.50 = 17.34). If the final calculated timestamp would exceed 999:59.99, the tool fails generation rather than truncating — nothing is silently dropped.
How to Create an LRC File With This Method
Use the following sequence to produce a fixed-interval draft with the LRC File Generator, then move it into a player or editor for manual alignment.
- Open the LRC File Generator and paste 1–500 non-empty lyric lines into the text area, with one line per display event. Blank rows are removed automatically, and Windows, old Mac, and Unix line endings are normalized so the count of timed rows always equals the count of meaningful lines.
- Enter a first timestamp in MM:SS.xx form using 2–3 minute digits, two second digits from 00 through 59, a period, and two centisecond digits. Valid examples include 00:00.00, 09:59.99, 10:00.00, and 123:45.67. The first timestamp you choose is the moment the first line appears on screen.
- Type an interval between 0.01 and 600.00 seconds with at most two decimal places. A smaller interval produces a denser display, while a larger interval spreads lines further apart; pick a value close to the song's average line length as a starting guess.
- Optionally fill the title, artist, and album fields. Each is trimmed, limited to 120 characters, and cannot contain square brackets or control characters, so a single field cannot inject an extra tag or line. Empty fields are omitted entirely from the output.
- Read the preview carefully. It shows the exact bytes that will be downloaded, including every [mm:ss.xx] header, the metadata block when used, and a blank line separating metadata from the timed rows. Confirm that the first and last timestamps look sensible for your track before saving.
- Click Download to save the file locally as UTF-8 text without a byte-order mark. When a title is set, the filename is derived from it with unsafe punctuation replaced by hyphens; otherwise the file is named synced-lyrics.lrc.
- Open the downloaded file next to the actual recording in your music player or a dedicated LRC editor and adjust individual timestamps until each line lands where vocals begin. This manual retiming step is what closes the gap between a uniform draft and a track-aware sync.
Optional Tags, Limits, and the Exact Output Format
The metadata layer is deliberately narrow. Only three tags are ever emitted: [ti:value] from the title, [ar:value] from the artist, and [al:value] from the album. There are no hour fields, no colon-separated frames, no three-digit milliseconds, no enhanced word-level angle-bracket timestamps, no karaoke duet markers, and no player-specific extensions. Lyric text is preserved exactly as typed — spelling, punctuation, capitalization, language, and any embedded copyright notice pass through untouched, with up to five hundred non-empty lines, fifty thousand input characters in total, and at most five hundred characters on a single line.
The first timestamp must contain two or three minute digits, exactly two second digits from 00 through 59, a period, and exactly two centisecond digits. Disallowed control characters in either lyrics or metadata are rejected rather than inserted into a text file that a downstream player may parse inconsistently. The table below summarizes the valid first-timestamp shapes the tool accepts.
| Example | Minutes | Seconds | Centiseconds | Notes |
|---|---|---|---|---|
| 00:00.00 | 00 | 00 | 00 | Start at the very beginning of the track |
| 09:59.99 | 09 | 59 | 99 | Largest single-digit-minute value |
| 10:00.00 | 10 | 00 | 00 | Two-digit minute field |
| 123:45.67 | 123 | 45 | 67 | Three-digit minutes, supported through 999:59.99 |
Finalizing Timing After Download
A fixed interval is only a starting draft. Real vocals rarely begin at perfectly equal spacing, and a uniform interval will land early on long instrumental sections and late on dense runs of short lines. Treat the downloaded file as a template and refine it in the target player or a dedicated editor: nudge individual [mm:ss.xx] markers forward or backward until each line appears at the moment the corresponding lyric starts. Different players support different metadata tags, timestamp precision, encodings, long minute values, and enhanced-LRC extensions, so always test the file in the application you actually use. The page cannot guarantee that every player interprets the same simple subset identically. All arithmetic and content stay in the current browser tab — no lyric text is uploaded, stored in an account, or sent to an AI service — so the only edits that matter happen after download, on your own machine.
Fixed-Interval Draft vs AI Audio Alignment
The fixed-interval draft and an AI-based audio aligner solve different problems and belong at different points in a workflow. The table below compares them on the criteria that matter for this decision.
| Aspect | LRC File Generator (fixed interval) | AI audio aligner |
|---|---|---|
| Audio analysis | None — no listening, no detection | Listens to the track and detects vocal onsets |
| Lyric source | User-typed text in the browser | Either supplied text or automatic speech recognition |
| Timestamp math | Single decimal interval, integer centiseconds, no drift | Per-line estimate from detected onsets, model-dependent |
| Output format | Simple [mm:ss.xx] with optional ti/ar/al tags | Varies by tool — simple, enhanced, or word-level LRC |
| Network behavior | Local only, no upload | Usually uploads the audio for processing |
| Best use case | Drafting a uniform baseline quickly | Producing a track-aware sync when no manual editor is available |
| Manual retiming needed | Yes — refine against the recording | Often small, sometimes substantial |
In practice the two approaches complement each other: a fixed-interval draft is a fast way to populate every line with a plausible timestamp, and any remaining offsets can be corrected either by retiming manually or by feeding the rough file back into a player that supports per-line nudge. If your priority is privacy, offline work, or a known uniform structure, the fixed-interval path is the better starting point. If your priority is minimizing hand work and you can upload audio, an aligner is a reasonable second step on top of this draft.
If you're weighing options, Avoid Mistakes When You Generate an LRC File covers this in detail.
If you're weighing options, How to Check an LRC File Result After Creation covers this in detail.