TXT to LRC
Or paste subtitle text
Options
Used when the source has no end times (plain text, LRC). The timeline in the output is generated here rather than converted, so this number is what you get.
What this conversion changes
2 things are dropped or need a decision
- Timing
the timeline itself — the source records no timings, so the output's is generated rather than converted
- Precision
timing precision — the output's clock is coarser, so every timestamp is rounded to the nearest 10 ms
This list comes from the capability matrix for these two formats, not from the particular file you loaded. A specific file may lose more if it uses features the format allows but the matrix does not model.
This page converts TXT to LRC. Drop a file in — or paste the text — and you get the LRC version back. The conversion runs entirely in your browser, so nothing is uploaded and no account is needed.
These two formats do not store the same things, and the difference is not cosmetic: timing and precision have nowhere to go in LRC. The list above comes from what the two formats can each express rather than from your file, so it is the same answer before you load anything.
One file is fine, and so is a whole season: the queue works through them in order and the results come down together as a single ZIP.
Examples
A typical TXT file, converted to LRC
Input
The quick brown fox jumps over the lazy dog.
Second paragraph, first line.
Second paragraph, second line.
Output
[00:00.00]The quick brown fox jumps over the lazy dog.
[00:02.00]Second paragraph, first line.
[00:04.00]Second paragraph, second line.
Dropped in this output: timing and precision. Everything else matches line for line.
The same conversion on an awkward input
Input
Hello world.
Second block.
Output
[00:00.00]Hello world.
[00:02.00]Second block.
This is the kind of damage real files have — mixed line endings, stray whitespace, fields left empty. Compare it with the tidy example above to see what the parser forgives.
Frequently asked questions
Are the timecodes invented when a TXT file becomes LRC?
Yes, and it is worth saying plainly: a TXT file has no timings at all, so the timeline in the LRC output is laid out here rather than converted. The first line starts at zero and each line after it starts where the previous one ended, so the spacing is even and the order is yours. The duration field on this page decides how wide each slot is.
Why have the timestamps moved from TXT to LRC?
TXT has no timecodes to move — the timeline in this conversion is laid out here — and LRC stores time as `[00:04.12]`, a hundredth of a second. So the generated slots are rounded to the nearest 10 ms as they are written. Nothing is reordered, and no line moves by more than 5 ms from where this page put it.
What does the output look like when TXT becomes LRC?
Like LRC: no cue numbers: every line carries its own bracketed timestamp. Every TXT cue becomes one LRC cue, in the same order, with the same text.
Do TXT cues keep their order in the LRC output?
Yes, and they are sorted by start time on the way — earliest first, which is how every format here expects them and how players read them. If your TXT file listed its cues out of sequence, the LRC output puts them back in order; that is a change to the file's structure rather than its content, and it is deliberate.
Can I convert the LRC back to TXT?
Yes, and it has its own list: converting LRC to TXT drops timing and line breaks. That list is different from the one above because the two formats keep different things.
Does the LRC output keep the TXT file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the TXT file used. A file that arrives in UTF-16, or in a Windows single-byte encoding, is decoded on the way in (the result panel says so when that happens); what comes out is always the same UTF-8 LRC.