SSA 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)
- 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 SSA 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 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 SSA file, converted to LRC
Input
[Script Info]
Title: Example SSA
ScriptType: v4.00
Collisions: Normal
[V4 Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, TertiaryColour, BackColour, Bold, Italic, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, AlphaLevel, Encoding
Style: Default,Arial,20,&H00FFFFFF,&H000000FF,&H00000000,&H00000000,0,0,1,2,2,2,10,10,10,0,1
[Events]
Format: Marked, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: Marked=0,0:00:01.00,0:00:04.00,Default,,0,0,0,,Hello there.
Dialogue: Marked=0,0:00:05.00,0:00:08.00,Default,,0,0,0,,{\i1}Italic{\i0} line.
Dialogue: Marked=0,0:00:09.00,0:00:12.00,Default,,0,0,0,,Two\Nlines
Output
[ti:Example SSA]
[00:01.00]Hello there.
[00:05.00]Italic line.
[00:09.00]Two
[00:09.00]lines
Dropped in this output: timing, styling, positioning, karaoke and format-specific content. Everything else matches line for line.
The same conversion on an awkward input
Input
[Script Info]
Title: Dirty SSA
ScriptType: v4.00
[V4 Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, TertiaryColour, BackColour, Bold, Italic, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, AlphaLevel, Encoding
Style: Default,Arial,20,&H00FFFFFF,&H000000FF,&H00000000,&H00000000,0,0,1,2,2,2,10,10,10,0,1
[Events]
Format: Marked, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Comment: Marked=0,0:00:00.00,0:00:01.00,Default,,0,0,0,,not a subtitle
Dialogue: Marked=0,0:00:01.00,0:00:04.00,Default,,0,0,0,,{\b1}Bold{\b0} and {\u1}underlined{\u0}.
Dialogue: Marked=0,0:00:05.00,0:00:08.00,Default,,0,0,0,,A soft\nbreak and a {\p1}mystery{\p0} code.Output
[ti:Dirty SSA]
[00:01.00]Bold and underlined.
[00:05.00]A soft
[00:05.00]break and a {\p1}mystery{\p0} code.
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 SSA 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 SSA start is untouched.
What happens to bold, italic and colour from SSA to LRC?
LRC stores no styling of any kind, so all of it goes: an override tag such as `{\i1}` written into the event text, or a colour that came from the `[V4 Styles]` table — 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 SSA to LRC?
LRC cannot say where a subtitle is drawn, so the `\pos`, `\an` and `\move` codes are dropped on the way out of SSA, 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 SSA to LRC?
The timing goes; the words stay. Karaoke lives in the `\k`, `\kf` and `\ko` codes an SSA event 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.
What happens to SSA's `[Script Info]` block when the file becomes LRC?
Every `Dialogue:` line in the SSA script becomes a lyric line, and the title comes across as an `[ti:]` tag. Everything else goes: the style table, the remaining `[Script Info]` keys, any `Comment:` lines and whatever is embedded in `[Fonts]` or `[Graphics]`. LRC has no concept of a script, only of lines and when they start.
What does the output look like when SSA becomes LRC?
Like LRC: no cue numbers: every line carries its own bracketed timestamp. Every SSA cue becomes one LRC cue, in the same order, with the same text.
How does a two-line SSA 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 SSA lines still belong to one subtitle in the LRC output, and a player shows them together.
Do SSA 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 SSA 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 SSA?
Yes, and it has its own list: converting LRC to SSA drops timing. That list is different from the one above because the two formats keep different things.
Does the LRC output keep the SSA file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the SSA 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.