TTML to LRC
Or paste subtitle text
What this conversion changes
5 things are dropped or need a decision
- Timing
cue end times (the output format only records when a cue starts)
- Styling
all styling (bold, italic, colour, outline, shadow)
- Positioning
on-screen positioning (every cue returns to the default position)
- Precision
timing precision — the output's clock is coarser, so every timestamp is rounded to the nearest 10 ms
- Format-specific content
content the source format keeps outside its cues (non-cue blocks, header text, per-cue settings, commented-out events) — the target format has no place for it
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 TTML 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, styling, positioning, precision and format-specific content 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 TTML file, converted to LRC
Input
<?xml version="1.0" encoding="UTF-8"?>
<tt xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#styling" xml:lang="en">
<head>
<styling>
<style xml:id="s1" tts:color="#FFFF00" tts:fontWeight="bold"/>
</styling>
<layout>
<region xml:id="bottom" tts:origin="10% 80%" tts:extent="80% 20%"/>
</layout>
</head>
<body>
<div>
<p begin="00:00:01.000" end="00:00:03.500" region="bottom" style="s1">Hello <span tts:fontStyle="italic">there</span>.</p>
<p begin="00:00:03.500" end="00:00:06.000" region="bottom">How are you?<br/>Fine, thanks.</p>
</div>
</body>
</tt>
Output
[00:01.00]Hello there.
[00:03.50]How are you?
[00:03.50]Fine, thanks.
Dropped in this output: timing, styling, positioning, precision and format-specific content. Everything else matches line for line.
The same conversion on an awkward input
Input
<?xml version="1.0" encoding="UTF-8"?>
<tt xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#styling"
xmlns:ttp="http://www.w3.org/ns/ttml#parameter"
ttp:frameRate="25" xml:lang="en">
<body>
<div>
<p begin="1.5s" dur="2s">Loaded from an offset and a duration.</p>
<p begin="4s" end="00:00:06.50">A coarser clock spelling.</p>
<p begin="00:00:07:00" end="00:00:08:12">Frames, at 25fps.</p>
<p begin="9s"><span tts:color="#FF0000">Half-open</span> and Tom & Jerry.</p>
</div>
</body>
</tt>
Output
[00:01.50]Loaded from an offset and a duration.
[00:04.00]A coarser clock spelling.
[00:07.00]Frames, at 25fps.
[00:09.00]Half-open and Tom & Jerry.
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
What happens to the end time of each TTML cue?
LRC records when a line begins and nothing else — a lyrics player keeps a line up until the next one starts, so an end time would be redundant. Every end is dropped and every TTML start is untouched.
What happens to bold, italic and colour from TTML to LRC?
LRC stores no styling of any kind, so all of it goes: a `<span tts:color="…">` inside a paragraph, or a named style from the `<styling>` table it points at — none of it has anywhere to land, and every line is written as plain text. The words themselves are untouched.
What happens to the on-screen position from TTML to LRC?
LRC cannot say where a subtitle is drawn, so the `region` and `style` references a `<p>` carries are dropped on the way out of TTML, and every cue goes back to the default position the player chooses — the bottom of the frame, centred, for most of them.
Why have the timestamps moved from TTML to LRC?
LRC stores time as `[00:04.12]` where TTML stores it as `00:00:04.126` — a hundredth of a second against a thousandth — so every timecode is rounded to the nearest 10 ms: 00:00:04,126 comes out as 4.13 seconds. Nothing is stretched or reordered and no cue moves by more than 5 ms, but if you are lining these subtitles up against another file, that is the one place this conversion stops being exact.
What happens to the TTML prolog, its `<styling>` and `<layout>` tables in LRC?
Dropped. A TTML file keeps its look and its layout in the head rather than in the words: the XML declaration and its namespace bindings, the `<styling>` table of named styles (`tts:color`, `tts:fontWeight`), the `<layout>` table of named regions (`tts:origin`, `tts:extent`), any `<metadata>`, and the `style` / `region` attributes a `<p>` uses to point at them. LRC stores cues, not a document, so nothing in that head has a place to land. Styling written *inside* a paragraph is a different matter — a `<span tts:fontStyle="italic">` is emphasis on the words, and it is written out in LRC's own markup wherever LRC has any.
What does the output look like when TTML becomes LRC?
Like LRC: no cue numbers: every line carries its own bracketed timestamp. Every TTML cue becomes one LRC cue, in the same order, with the same text.
How does a two-line TTML cue come out in LRC?
As two timestamped lines carrying the same time, which is how LRC says 'these two belong together'. The pairing survives — the two TTML lines still belong to one subtitle in the LRC output, and a player shows them together.
Do TTML 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 TTML 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 TTML?
Yes, and it has its own list: converting LRC to TTML drops timing. That list is different from the one above because the two formats keep different things.
Does the LRC output keep the TTML file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the TTML 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.