SSA to TTML
Or paste subtitle text
What this conversion changes
2 things are dropped or need a decision
- 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 TTML. Drop a file in — or paste the text — and you get the TTML 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: karaoke and format-specific content have nowhere to go in TTML. 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 TTML
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
<?xml version="1.0" encoding="UTF-8"?>
<tt xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#styling">
<body>
<p begin="00:00:01.000" end="00:00:04.000">Hello there.</p>
<p begin="00:00:05.000" end="00:00:08.000"><span tts:fontStyle="italic">Italic</span> line.</p>
<p begin="00:00:09.000" end="00:00:12.000">Two<br/>lines</p> </body>
</tt>
Dropped in this output: 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
<?xml version="1.0" encoding="UTF-8"?>
<tt xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#styling">
<body>
<p begin="00:00:01.000" end="00:00:04.000"><span tts:fontWeight="bold">Bold</span> and <span tts:textDecoration="underline">underlined</span>.</p>
<p begin="00:00:05.000" end="00:00:08.000">A soft<br/>break and a {\p1}mystery{\p0} code.</p> </body>
</tt>
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 karaoke timing from SSA to TTML?
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 TTML has no way to record a moment inside a line — so the marks come off and the syllables arrive as ordinary TTML text.
What happens to SSA's `[Script Info]` block and the rest of the script in TTML?
Only the `Dialogue:` lines become subtitles. The `[Script Info]` block (title included — TTML has nowhere to put one), the style table, any `Comment:` lines and whatever is embedded in `[Fonts]` or `[Graphics]` are all dropped. For an SSA file whose styling was written by hand, this is the loss that shows most.
What does the output look like when SSA becomes TTML?
Like TTML: no cue numbers: every subtitle is a `<p>` element with `begin` and `end` attributes, nested in a `<body>` (and usually a `<div>`), with an XML declaration above the whole document. Every SSA cue becomes one TTML cue, in the same order, with the same text.
Are the SSA timings exact in the TTML file?
Yes, to the millisecond — which is as fine as either format goes. SSA writes a moment as `0:00:04.13` and TTML writes the same moment as `00:00:04.126`; nothing is rounded or shifted between the two, and a cue that was on screen for 2.9 seconds still is.
How does a two-line SSA cue come out in TTML?
As two lines with a `<br/>` between them, which is how TTML writes a hard line break. The pairing survives — the two SSA lines still belong to one subtitle in the TTML output, and a player shows them together.
Do SSA cues keep their order in the TTML 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 TTML 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 TTML back to SSA?
Yes, and it has its own list: converting TTML to SSA drops precision and format-specific content. That list is different from the one above because the two formats keep different things.
Does the TTML 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 TTML.