LRC File Generator runs in any laptop browser to turn pasted lyric lines into a simple .lrc file with centisecond timestamps, optional tags, an exact preview, and a local UTF-8 download. The page itself parses the text, performs the timing math, renders the preview, and writes the file from your current browser tab without an installer, a desktop executable, an account, or any lyric upload. Every step stays local to the laptop, which means the same workflow works on a borrowed machine, a fresh profile, or a corporate device where installing utilities is restricted.
Laptop users have long relied on installed Windows programs to make LRC files — small desktop utilities that import a TXT file, let you tap a key to mark each line against a playing song, and export a standard .lrc file. Those programs still work, but they require a download, an installer, sometimes elevated permissions, and a restart of the workflow every time you change machines. A browser tab sidesteps all of that: open the page, paste your lyrics, choose two timing numbers, and download the finished file next to your MP3. The trade-off is that the page cannot listen to your audio or detect when vocals actually appear — it hands you a fixed-interval draft that you retime against the exact recording afterwards.
What the laptop workflow actually produces
The generator outputs a conservative subset of the de-facto LRC format that most modern players recognize. Every timed line uses a bracketed minutes-seconds-centiseconds value immediately followed by the lyric text, in the form [mm:ss.xx]Lyric line. Examples such as [00:00.00], [09:59.99], [10:00.00], and [123:45.67] all pass the parser. Optional metadata is written as [ti:title], [ar:artist], and [al:album] at the top of the file, separated from the timed lyrics by a blank line for readability. The QuickLRC documentation of this simple de-facto form is consistent with what the page emits.
What the tool does not emit matters just as much for laptop users who plan to test the file in a specific player. There are no hour fields, no colon-separated frames, no three-digit milliseconds, no enhanced word-level angle-bracket timestamps like <00:12.34>, no karaoke duet markers, and no player-specific extensions. UTF-8 is used without a byte-order mark, so the file opens cleanly in Windows Notepad, macOS TextEdit, and Linux editors without showing a hidden character at the start.
| Element | Emitted by the generator | Not emitted |
|---|---|---|
| Line timestamp format | [mm:ss.xx] bracketed centisecond value | Hour fields, frames, three-digit milliseconds |
| Metadata tags | ti (title), ar (artist), al (album) | by, length, offset, tool, re, ve, custom tag keys |
| Word timing | One timestamp per display line | Angle-bracket <mm:ss.xx> word markers |
| Encoding | UTF-8 without BOM | UTF-16, GB18030, ANSI codepages |
| Karaoke features | None | Duet singers, syllable highlight duration |
This narrow contract keeps the output predictable across the players that matter on a laptop — AIMP, foobar2000 with the lyrics panel, MusicBee, VLC, and most mobile players that you later sideload the file to. A single-file contract also keeps the math simple enough to verify by eye in any plain text editor on the laptop.
How to create an LRC file on your laptop
The full laptop workflow is short enough to repeat for every song. Treat the result as a draft and then refine each line against the real recording.
- Open the generator in your laptop browser. No installer, no extension, no account. The page loads the editor and download controls in the current tab. Visit the LRC File Generator directly to start.
- Paste 1 to 500 non-empty lyric lines, one per row. A row is one display event — a complete phrase that should appear together on screen. Blank rows are removed automatically. Windows, old Mac, and Unix line endings inside the pasted text are normalized before generation, so copying from Notepad, TextEdit, or VS Code all produce the same result.
- Set the first timestamp in MM:SS.xx form. Two or three minute digits, exactly two second digits from 00 through 59, a period, and exactly two centisecond digits. 00:12.34 works; 1:2.3 does not. The form supports timestamps through 999:59.99.
- Set the interval between successive lines. Accepts 0.01 through 600 seconds with up to two decimal places. The page rounds this to integer centiseconds internally before adding, so the math does not drift across hundreds of rows.
- Fill optional metadata if you want. Title, artist, and album become ti, ar, and al tags. Empty fields are omitted. Each value is trimmed, capped at 120 characters, and cannot contain square brackets or control characters — a value that contained a bracket could otherwise inject an extra LRC tag.
- Generate and read the preview. The preview shows the complete, untruncated file that download will write. Editing any input clears the previous preview, so the text you see is always the text that matches the current inputs.
- Inspect the first and last timestamps in the preview. If the final calculated timestamp would exceed 999:59.99, generation fails and nothing is silently truncated — the file is not produced.
- Download the .lrc file. The download uses UTF-8 without a BOM and saves with the .lrc extension. The filename is derived from the title when available; unsafe filename punctuation becomes hyphens, and a blank title uses synced-lyrics.lrc.
- Place the file beside the audio and retime individual lines. Save the .lrc with the same base name as the MP3 in the same folder, open both in your music player, and adjust individual timestamps against the exact recording in a dedicated editor. The fixed interval is only a starting draft.
How the centisecond math produces consistent output
Most timing bugs in hand-written LRC files come from floating-point drift. If the interval is 2.50 seconds and the start is 00:12.34, a naive float loop adds 2.5 to a running counter each row. By the hundredth line the counter is off by a few microseconds; by the thousandth it is off by a fraction of a second, and centisecond rounding starts to skip values. The LRC File Generator avoids this by converting the decimal interval to an integer number of centiseconds once, then adding that integer by line index. The centiseconds-to-timestamp conversion follows the rules documented in the Subforge LRC time implementation: minutes contribute sixty thousand milliseconds, seconds contribute one thousand, and two fractional digits represent centiseconds.
Worked example using the values from the contract: start 00:12.34, interval 2.50 seconds. The interval becomes 250 centiseconds. Line 1 receives 00:12.34. Line 2 receives the start plus 250 centiseconds, which is 00:14.84. Line 3 receives the start plus 500 centiseconds, which is 00:17.34. Each step is exact because centiseconds are integers and the addition uses integer arithmetic, not binary float. The preview shows these three lines verbatim, and download writes the same string with no hidden rewriting. For deeper coverage of how the centisecond pipeline handles boundary cases — intervals with three decimal places, intervals near the 600-second ceiling, or minute values past the two-digit boundary — the dedicated walkthrough on how the math produces LRC files walks through each conversion step.
Limits and what the page deliberately leaves out
Several input limits shape what fits inside the laptop workflow, and the page enforces them by rejecting bad input rather than silently truncating:
- Lines: 1 to 500 non-empty rows. Above 500, generation is rejected.
- Total characters: up to 50,000 across all lyric text, with at most 500 characters on one line.
- Start timestamp: two or three minute digits, seconds 00 through 59, a period, exactly two centisecond digits. Files are supported up to 999:59.99; beyond that, generation fails.
- Interval: 0.01 to 600.00 seconds, no more than two decimal places.
- Metadata values: trimmed, capped at 120 characters, no square brackets or control characters.
- Spelling and language: the generator preserves the text exactly as entered. It does not translate, correct capitalization, add punctuation, strip characters, or insert copyright notices inside ordinary lyric text.
- Audio: the page does not decode audio, detect vocals, transcribe lyrics, identify the song, identify beats, or estimate performance timing. It only formats the text you give it.
- Uploads: nothing leaves the browser tab. Lyric text, metadata, and the downloaded file all stay on the laptop; temporary download object URLs are revoked after direct use and when the component unmounts.
Users are responsible for having the right to reproduce and distribute the lyric text they paste into the form. The tool does not supply lyrics, search a catalog, confirm ownership, or grant a synchronization license — it formats text that you already have.
Verifying the file on your laptop and pairing it with audio
Before you commit, do a quick sanity check on the file your laptop just saved. Open it in a plain text editor — Notepad on Windows, TextEdit in plain-text mode on macOS, or gedit on Linux — and confirm that every timed line starts with a bracketed timestamp, that the metadata block (if any) sits above a blank line, and that the last line carries the timestamp you expected. If the file shows  at the very beginning, the player saved a BOM; this generator does not emit one, so a visible BOM means the file was opened and re-saved by another tool. Re-download if needed.
Pair the .lrc file with your audio using the same base filename: song.mp3 lives next to song.lrc in the same folder. Open both in your target player and scroll the lyrics while the song plays. Real vocals rarely begin at perfectly equal spacing, so adjust individual timestamps in a dedicated editor rather than trying to make the fixed-interval draft match the song exactly. Different players support different metadata tags, timestamp precision, encodings, long minute values, and enhanced-LRC extensions, so always test the file in the actual player you intend to use. The generator's contract is intentionally small: validate the de-facto centisecond timestamp subset, convert a bounded decimal interval to exact centiseconds, preserve bounded lyric text, emit only the optional ti, ar, and al tags, show the complete untruncated file, and download the exact preview. Compatibility beyond that subset remains the responsibility of the player and the workflow you choose afterwards.
If you're weighing options, Volume Changer on Laptop: Adjust Audio Files Locally covers this in detail.