SMI to TTML
Or paste subtitle text
What this conversion changes
1 thing is dropped or needs a decision
- 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 SMI 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: format-specific content has 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 SMI file, converted to TTML
Input
<SAMI>
<HEAD>
<STYLE TYPE="text/css">
<!--
P { text-align: center; font-family: Arial; }
.ENCC { Name: English; lang: en-US; }
-->
</STYLE>
</HEAD>
<BODY>
<SYNC Start=1000>
<P Class=ENCC>Hello there.
<SYNC Start=3000>
<P Class=ENCC>
<SYNC Start=3500>
<P Class=ENCC>How are you?<br>Fine, thanks.
<SYNC Start=6000>
<P Class=ENCC>
</BODY>
</SAMI>
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:03.000">Hello there.</p>
<p begin="00:00:03.500" end="00:00:06.000">How are you?<br/>Fine, thanks.</p> </body>
</tt>
Dropped in this output: format-specific content. Everything else matches line for line.
The same conversion on an awkward input
Input
<SAMI>
<HEAD>
<TITLE>Episode 1</TITLE>
<STYLE TYPE="text/css">
<!--
.ENCC { Name: English; }
-->
</STYLE>
</HEAD>
<BODY>
<sync start="00:00:02,500">
<P Class=ENCC>Line one<br>Line two
<sync start=9000>
<P Class=ENCC>Tom & Jerry
<SYNC Start=12000>
<P Class=ENCC>
</BODY>
</SAMI>
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:02.500" end="00:00:09.000">Line one<br/>Line two</p>
<p begin="00:00:09.000" end="00:00:12.000">Tom & Jerry</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 SAMI's `<STYLE>` block, `<TITLE>` and `Class=` attributes in TTML?
They are dropped. SAMI says what its subtitles look like outside the text of the cue: a `<STYLE>` block of CSS for the paragraphs, a `<TITLE>`, and the channel marker each paragraph carries — `Class=ENCC`, which points at one of those rules. TTML stores cues rather than a document, so there is nowhere for any of that to go. Emphasis written inside a cue's own text is unaffected — that belongs to the line — and the cues come through with their text and timings whole.
What does the output look like when SMI 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 SMI cue becomes one TTML cue, in the same order, with the same text.
Are the SMI timings exact in the TTML file?
Yes, to the millisecond — which is as fine as either format goes. SMI writes a moment as `Start=4126` 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 SMI 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 SMI lines still belong to one subtitle in the TTML output, and a player shows them together.
Do SMI 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 SMI 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 SMI?
Yes, and it has its own list: converting TTML to SMI drops styling 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 SMI file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the SMI 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.