JSON 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)
- Karaoke
karaoke timing (per-syllable highlighting)
- 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 JSON 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, karaoke 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 JSON file, converted to LRC
Input
{
"version": 1,
"title": "Fixture: typical",
"fps": 25,
"styles": {
"Default": {
"name": "Default",
"fontFamily": "Arial",
"fontSize": 20,
"primaryColor": "#FFFFFF",
"bold": false,
"italic": false
}
},
"generator": "subtitlematrix fixtures",
"cues": [
{
"id": "1",
"start": 0,
"end": 2000,
"lines": [
"Hello world.",
"Second line."
],
"style": "Default",
"position": {
"x": 100,
"y": 200,
"align": "center"
}
},
{
"id": "2",
"start": 2500,
"end": 4000,
"lines": [
"Plain line.",
{
"text": "Styled line.",
"tags": [
{
"kind": "italic",
"start": 0,
"end": 6
}
]
}
]
},
{
"id": "3",
"start": 4500,
"end": 6000,
"lines": [
"Roger: I am here."
],
"speaker": "Roger"
}
]
}
Output
[ti:Fixture: typical]
[00:00.00]Hello world.
[00:00.00]Second line.
[00:02.50]Plain line.
[00:02.50]Styled line.
[00:04.50]Roger: I am here.
Dropped in this output: timing, styling, positioning, karaoke and precision. Everything else matches line for line.
The same conversion on an awkward input
Input
[
{ "start": 0, "end": 1000, "lines": ["First."] },
{ "start": 1000, "end": 2000, "text": "Second." },
"not an object",
{ "start": 2000, "end": 3000, "lines": ["Third."], "class": "top" }
]
Output
[00:00.00]First.
[00:01.00]Second.
[00:02.00]Third.
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 JSON 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 JSON start is untouched.
What happens to bold, italic and colour from JSON to LRC?
LRC stores no styling of any kind, so all of it goes: the `tags` a cue's line carries, or an entry of the document's own `styles` object — 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 JSON to LRC?
LRC cannot say where a subtitle is drawn, so the position stored with each cue is dropped on the way out of JSON, and every cue goes back to the default position the player chooses — the bottom of the frame, centred, for most of them.
What happens to karaoke timing from JSON to LRC?
The timing goes; the words stay. Karaoke lives in the karaoke spans a JSON cue carries, which mark when each syllable lights up, and LRC has no way to record a moment inside a line — so the marks come off and the syllables arrive as ordinary LRC text.
Why have the timestamps moved from JSON to LRC?
LRC stores time as `[00:04.12]` where JSON stores it as `4126` — 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 does the output look like when JSON becomes LRC?
Like LRC: no cue numbers: every line carries its own bracketed timestamp. Every JSON cue becomes one LRC cue, in the same order, with the same text.
How does a two-line JSON 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 JSON lines still belong to one subtitle in the LRC output, and a player shows them together.
Do JSON 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 JSON 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 JSON?
Yes, and it has its own list: converting LRC to JSON drops timing. That list is different from the one above because the two formats keep different things.
Does the LRC output keep the JSON file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the JSON 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.