An LRC file is a plain UTF-8 text file in which every lyric line is preceded by a timestamp written as [mm:ss.xx], with two digits for seconds and two digits for centiseconds. You can make one on Android by opening a browser-based generator in Chrome, entering one lyric line per row, choosing a starting timestamp and a fixed interval in seconds, and tapping Download to save the resulting .lrc file to your phone's Downloads folder. The whole workflow runs inside the mobile browser, so there is no Play Store install, no APK sideload, and no separate lyric editor app required. Once the file is on your device, any Android music player that recognises the simple LRC format pairs the file with a matching song by filename and shows each line at the timestamp the generator assigned.
Why a browser-based tool fits Android
Most older Android-specific lyric editors required you to install a small APK, grant storage and media permissions, and rebuild your lyric on a cramped touch keyboard. A browser-based generator removes every one of those steps. You open a URL in Chrome, Samsung Internet, Firefox, or any modern Android browser, paste the lines you have already written somewhere else, and let the page do the formatting. The output file lands in the standard Android Downloads folder, which means your file manager, your music player, and any chat app can all reach it without permission dialogs. Because the tool runs as a normal web page, the same workflow also works on a Chromebook, a tablet, and the Android desktop modes that some manufacturers ship.
Privacy follows from the same architecture. The generator formats text, validates timestamps, and emits a download. It does not require an account, it does not post your lyrics anywhere, and it does not call out to an AI service. If you are working with unreleased lyrics, drafts you are not ready to publish, or material you only want stored on your own device, that local behaviour matters more than any single formatting feature.
What the LRC File Generator produces (and what it skips)
The LRC File Generator writes the conservative simple LRC subset, not a full superset of every extension that has ever appeared in the wild. Each timed line is a single [mm:ss.xx] stamp directly followed by the lyric text you entered, with no extra characters between the closing bracket and the first letter of the line. Optional metadata is limited to three tags: [ti:title], [ar:artist], and [al:album]. Anything else, such as length, language, by, offset, or re-encoded karaoke tags, is intentionally left out so the file behaves the same way in the widest range of players.
The page does not emit hour fields, colon-separated frame counts, three-digit milliseconds, enhanced word-level timestamps wrapped in angle brackets, karaoke duet markers, or any player-specific extension. The download is a UTF-8 text file saved without a byte-order mark, which is what Android players expect when they read .lrc files from local storage. The filename is derived from the title you entered; unsafe punctuation becomes hyphens, and a blank title falls back to synced-lyrics.lrc. If you want a more advanced format, you would need a different tool, but for the common Android use case of showing lines at roughly the right moment, the simple subset is what the players actually parse.
Make an LRC file on Android, step by step
- Open the LRC File Generator in Chrome on your Android phone, then tap the lyric input area. Paste your lines from a notes app, or type them directly with the on-screen keyboard, keeping one lyric line per row.
- Leave any blank rows out: the generator strips empty lines before formatting, and a stray empty row will not produce a stray timestamp.
- Tap the first-timestamp field and enter a value in MM:SS.xx form. The minutes field accepts two or three digits, the seconds field must be 00 through 59, and the centisecond field must be exactly two digits. Examples that work: 00:00.00, 00:12.34, 09:59.99, 10:00.00.
- Tap the interval field and enter a number of seconds between 0.01 and 600.00, using at most two decimal places. 2.50, 3.75, and 4.00 are all valid. The page converts this decimal into an integer number of centiseconds before any line is produced, so repeated addition cannot drift.
- Optional: fill in the title, artist, and album fields. Each value is trimmed, capped at 120 characters, and cannot contain square brackets or control characters. Empty fields are simply omitted from the file.
- Tap Generate. The full file appears in the preview area on the same screen. Scroll to the top to confirm the optional [ti:], [ar:], and [al:] tags look right, then scroll to the bottom to confirm the last timestamp is what you expect.
- Tap Download. Chrome saves the file to the Downloads folder on your phone's internal storage, ready for your music player or file manager to pick up.
Valid timestamp and interval values
| Field | Required format | Valid example | Invalid example |
|---|---|---|---|
| First timestamp | [mm:ss.xx], 2 or 3 minute digits, 2 second digits 00–59, period, 2 centisecond digits | 00:12.34 | 0:12.3, 00:60.00, 00:12.345 |
| Maximum timestamp | Anything up to 999:59.99 inclusive | 123:45.67 | 1000:00.00 |
| Interval | 0.01 to 600.00 seconds, at most two decimal places | 2.50 | 0, 600.01, 2.500 |
| Lyric lines | 1 to 500 non-empty lines, up to 500 characters each | One verse per row | An empty row, a row of 501 characters |
| Total lyric text | Up to 50,000 input characters across all rows | A long song in one paste | An entire album pasted at once |
| Title / artist / album | Up to 120 characters, no [ ] or control characters | Song Name | Song [live], any tab or newline |
How the interval math works
The interval you type is converted to an integer count of centiseconds before the first row is written. For a starting timestamp of 00:12.34 and an interval of 2.50 seconds, the centisecond values are 1234, 1234 + 250 = 1484, and 1484 + 250 = 1734. Those integers are then written back as [mm:ss.xx] stamps, producing three lines beginning with [00:12.34], [00:14.84], and [00:17.34]. Because each step is an integer addition, a hundred lines cannot accumulate the small binary drift that a naive floating-point loop would introduce. If the final calculated timestamp would exceed 999:59.99, generation fails and nothing is silently truncated, so a too-long song either needs a smaller starting timestamp, a smaller interval, or fewer rows.
After the download lands on Android
Chrome on Android saves the file to the system Downloads folder, typically at /storage/emulated/0/Download/. Open your file manager, tap the .lrc file, and check that it previews as readable text. Most Android music players pick the lyrics up automatically when the .lrc file sits next to the audio file with the same base name, for example song.mp3 beside song.lrc. Some players, including several that handle Spotify local files, look inside a /Lyrics subfolder next to the track instead, and a few only read the lyric file when it is loaded manually through a side menu. QuickLRC's LRC file format reference describes the de-facto line that the generator follows, so behaviour matches what most modern Android parsers expect.
Different players support different metadata tags, timestamp precisions, encodings, long minute values, and enhanced-LRC extensions. A file that scrolls perfectly in one Android player can sit frozen in another if the player ignores [ti:], [ar:], or [al:] tags, treats the file as Latin-1 instead of UTF-8, or stops reading at the first invalid timestamp. Always open the same file in the player you actually use and watch the first ten lines at least before you assume it works.
Retiming the draft against the real recording
A fixed interval is only a starting draft. Real vocals rarely begin at perfectly equal spacing: a chorus may hold a note, a bridge may pause, and a spoken intro may push the first lines earlier than the average gap would suggest. The generator does not listen to audio, detect speech, transcribe lyrics, align phonemes, identify beats, or estimate performance timing, and the de-facto parser described in the Subforge LRC time implementation only converts timestamps to milliseconds; it does not generate them. After the download, open the .lrc beside the exact recording in a dedicated Android-side editor and nudge individual timestamps until each line lands where the singer actually starts.
If your reader benefit leans toward a deeper walkthrough of start time and interval settings, the guide on making an LRC file with a start time and interval covers the same tool from a more general angle.
Privacy and copyright on the phone
Every step above happens inside the current browser tab on your Android device. The page does not upload your lyric text to Lizely, store it in an account, or send it to an AI service for alignment. The generator does not supply copyrighted lyrics, search a catalogue, identify a song, confirm ownership, or grant a synchronisation licence, so the responsibility for permission to reproduce and distribute the lyric text you paste stays with you. In practice that means: paste only text you have the right to use, then keep the resulting .lrc file on your own device or share it with the same audience the lyrics were originally meant for.
Troubleshooting on Android
If your music player does not show the lyrics, confirm the filename matches the song exactly apart from the extension, that the file is saved as UTF-8 without a BOM (which is what the Download button emits), and that the file is not nested inside a folder the player does not scan. If the lines scroll but stay late, the interval is probably too large for the section you are watching; if the lines scroll too early, the interval is probably too small. If the file opens fine on a computer but not on the phone, the player is most likely reading the wrong encoding or ignoring one of the optional tags. None of those problems come from the generator; they come from the variety of Android players, and the safest fix is to retime the affected lines and test again in the actual player you use every day.