Getting an LRC file means producing a plain-text document in which each lyric line is preceded by a timestamp in [mm:ss.xx] format so that music players can highlight words in time with the audio. When a song has no pre-made LRC circulating online, the most reliable path is to build one yourself in a deterministic local tool, because manual transcription against the actual recording is the only way to guarantee the lyrics match what is actually sung. A simple LRC file is small enough to open in any text editor, easy to retime in a dedicated lyrics editor, and supported by the majority of desktop and mobile players that handle synchronized lyrics at all. The LRC File Generator produces exactly this file type: you enter one lyric line per row, set a first timestamp and a regular interval, optionally fill in title, artist, and album tags, and then download a UTF-8 .lrc file that mirrors the preview byte for byte. No lyric text leaves your browser, and the same tool documents its own centisecond arithmetic so you can verify the first and last timestamps before opening the file in your player.
Why Pre-Made LRC Files Are Often Missing
Searching for an LRC file online is a familiar experience: half the song titles return broken forum links, dead pastebins, or lyric sheets that no longer match the recording you own. Community-maintained databases rarely cover independent releases, regional artists, or remixes, and many large-label tracks are pulled down over time due to copyright claims. Even when a file does exist, the encoding, line-break style, and tag set may not match what your music player expects. For tracks that fall through those gaps, generating a file locally from the lyrics you already have in front of you is faster and more reliable than a third or fourth search attempt. The tool at /audio/lrc-generator/ follows this approach: it formats the text you provide using a documented centisecond timestamp subset, so the output behaves predictably across a wide range of players.
Anatomy of a Simple LRC File
A simple LRC file is a UTF-8 plain-text document. Optional metadata appears at the top as bracketed tags, and the lyrics follow with a bracketed timestamp on every display line. The generator described in this article emits only three metadata tags and the time-tagged lyric lines, which keeps the format conservative and broadly compatible across desktop and mobile players.
| Element | Format | Purpose |
|---|---|---|
| [ti:value] | Square-bracket tag | Optional song title metadata |
| [ar:value] | Square-bracket tag | Optional artist metadata |
| [al:value] | Square-bracket tag | Optional album metadata |
| [mm:ss.xx]Lyric line | Centisecond timestamp + text | One per display event |
The two-digit value after the period represents centiseconds, not milliseconds. According to the Subforge LRC time implementation, minutes contribute sixty thousand milliseconds, seconds contribute one thousand, and the two fractional digits represent centiseconds. This matches the de-facto format documented at quicklrc.com's LRC file format reference, where examples such as [01:23.45]Example line are given as the canonical simple LRC form. Other variants — hour fields, colon-separated frames, three-digit milliseconds, word-level angle-bracket timestamps, karaoke duet markers, and player-specific extensions — are intentionally not produced, because they are interpreted inconsistently across players.
Generate a Local LRC File Step by Step
- Open the LRC File Generator in a current browser tab. Everything that follows happens in this tab and no lyric text is uploaded.
- Enter one lyric line per row in the lyrics box. The generator accepts between 1 and 500 non-empty lines, up to 50,000 input characters total and at most 500 characters per line, and removes blank rows before it generates.
- Set the first timestamp in MM:SS.xx form. Valid examples include 00:00.00, 09:59.99, 10:00.00, and 123:45.67; the value must contain two or three minute digits, exactly two second digits from 00 through 59, a period, and exactly two centisecond digits.
- Enter the interval between successive lines in seconds, using 0.01 through 600.00 with no more than two decimal places. The value is converted to an integer number of centiseconds internally to prevent binary floating-point drift on long songs.
- Optionally fill in the title, artist, and album fields. Each value is trimmed, limited to 120 characters, and cannot contain square brackets or control characters; empty fields are omitted entirely.
- Click Generate. The preview box shows the exact text that will be saved, including the first and last timestamps, so you can confirm the arithmetic before downloading.
- Click Download to save a UTF-8 .lrc file whose name is derived from the title when available; a blank title falls back to synced-lyrics.lrc.
- Open the downloaded file in a dedicated lyrics editor alongside the exact recording and shift individual timestamps as needed.
Reading the Preview Before You Download
The preview is the contract. Whatever you see in the preview box is exactly what will be written to disk, including line breaks, spacing, and the order of metadata. Two specific checks are worth doing here. First, confirm the first timestamp on the first lyric line matches where vocals actually begin, because vocal intros, instrumental openings, and ad-libs before the first sung line are common sources of early misalignment. Second, glance at the last timestamp on the last lyric line and confirm it falls inside 999:59.99; if the final calculated timestamp would exceed that ceiling, the generator stops without writing a truncated file, which is the correct behaviour because a silently clipped timestamp can confuse a player.
For a working numeric example, suppose the first timestamp is 00:12.34 and the interval is 2.50 seconds. The first three lines receive:
- Line 1: 00:12.34 (start)
- Line 2: 00:14.84 (12.34 + 2.50 = 14.84)
- Line 3: 00:17.34 (14.84 + 2.50 = 17.34)
This is the arithmetic style the generator uses internally: convert the decimal interval to integer centiseconds, add it once per line, and never let binary floating-point error accumulate across hundreds of rows.
Refining Individual Lines in Your Music Player
A fixed interval is only a starting draft. Real vocals rarely begin at perfectly equal spacing: held notes, drum fills, and instrumental bridges can stretch the gap between two lines, while fast passages can compress it. The generator does not listen to audio, detect speech, transcribe lyrics, align phonemes, identify beats, or estimate performance timing, so the file you download is a structured scaffold rather than a finished product. After download, open the LRC beside the exact recording in a dedicated editor and shift individual timestamps against the recording until the highlighted words match the singer's delivery.
Different music players also support different metadata tags, timestamp precision, encodings, long minute values, and enhanced-LRC extensions. Always test the file in the target player before relying on it, because the same file can render differently across apps. If you also need an SRT companion file for use with video editors or karaoke rigs, the Create a Lyrics SRT File for Music with Exact Timestamps guide covers the companion workflow in detail.
Picking Metadata That Survives Across Players
Not every player reads every tag. Many desktop players ignore [ti:] and [al:] and rely on the audio file's embedded ID3 or Vorbis tags instead; some mobile players read [ti:] and [ar:] but skip [al:]. The narrow metadata set produced by the generator — only ti, ar, and al — is therefore a deliberate choice, since a tag the player does not understand is at worst ignored and at best rendered alongside the artist name on screen. Title, artist, and album are the three fields most likely to display consistently, which is why they are the only optional metadata this tool exposes. Disallowed control characters inside any metadata value are rejected rather than inserted, preventing one field from injecting an extra LRC tag or stray line into the file.
Privacy and Local Processing
All content and arithmetic stay in the current browser tab. No lyric text is uploaded, stored in an account, or sent to an AI service; the file you download is produced entirely on your device. Windows, old Mac, and Unix line endings are normalized before generation, and the temporary object URL used for the download is revoked after direct use and when the component unmounts, so an older file cannot remain presented as the result of newer text. These safeguards matter because lyric text is often sensitive in the sense that it may be under copyright: you remain responsible for having permission to reproduce and distribute the lyrics you enter, since this utility does not supply copyrighted lyrics, search a catalog, identify a song, confirm ownership, or grant a synchronization license. It simply formats user-provided text according to a small, documented contract.