SubtitleMedic

Convert SMI to VTT

Turn SAMI (.smi) subtitles into WebVTT captions for web players and HTML5 video.

Processed in your browserNo sign-up.smi

How to convert SMI to VTT

  1. Open your .smi file

    Drop the subtitle file into the box above, or click to browse. To try it first, use the .smi sample under the box: a short film with Korean and English subtitles in one file.

  2. Pick a language

    If the file has more than one language, choose the one to keep, or keep them all stacked. A file with one language skips this step.

  3. Download the .vtt file

    The file keeps its name and is saved as UTF-8 with the WEBVTT header: movie.smi becomes movie.vtt.

Why browsers can't play SMI

SAMI was built into Windows Media Player and Internet Explorer. No current browser reads it, and the HTML5 video element only accepts WebVTT.

<SYNC Start=3120><P Class=ENCC>Is this seat taken?
<SYNC Start=5480><P Class=ENCC>&nbsp;

A SAMI file writes each change on screen as a sync point, with every language as a class of its own. WebVTT writes each line with its start and end time:

WEBVTT

00:00:03.120 --> 00:00:05.480
Is this seat taken?

The converter works out the end of every line from the sync points that follow it, and writes the file a browser expects.

How the converter reads a SAMI file

A line ends at the next sync point of its language. In a file with Korean and English, the Korean line can stay while the English one changes, as it would in KMPlayer.

A blank clears the screen. &nbsp; ends the line of its language; an empty sync point ends them all. A line that nothing clears goes after 10 seconds, and the last line after 4.

Markup is read loosely. Tags in any case, unclosed paragraphs and unquoted attributes are read the way players read them. <br> becomes a line break, <i>, <b> and <u> are kept, and characters such as & and < are written the way WebVTT needs them.

Lines that can't be read are listed. A sync point with an unreadable time is skipped and shown with its line number; the rest of the file still converts.

Using the .vtt on a web page

<video controls src="film.mp4">
  <track kind="subtitles" src="film.ko.vtt" srclang="ko" label="한국어" default />
  <track kind="subtitles" src="film.en.vtt" srclang="en" label="English" />
</video>

Serve the .vtt from the same site as the page, or with a CORS header, or the browser won't load it. Video.js, Plyr, JW Player and Vimeo take the same file.

Tips

Subtitles early or late? Shift Subtitle Timing moves every line by the same amount.

Garbled Korean? Pick the encoding next to the file name. Fix Subtitle Encoding explains EUC-KR and the other legacy encodings.

Need .srt for a TV or a video editor? Use Convert SMI to SRT. What is a VTT file? explains WebVTT in more detail.

Frequently asked questions

What is the difference between SMI and VTT?

Both are text formats, but for different players. SMI (SAMI) was made for Windows Media Player and is common for Korean and Japanese subtitles. VTT (WebVTT) is the caption format of the web, read by the HTML5 <track> element and by players such as Video.js, JW Player and Vimeo.

My .smi file has two languages. What goes into the .vtt?

The first language in the file, unless you pick another. When the file holds more than one language, a list appears above the Download button with each language, and an option to keep them all, stacked one line per language.

Can I make one .vtt per language?

Yes. Convert the file once for each language. The HTML5 <track> element takes a separate .vtt for each language, with its own srclang, so viewers can choose in the player.

How long does each line stay on screen?

SAMI only says when something starts. A line stays until the next sync point of its language, or until a blank (&nbsp;) clears it, for at most 10 seconds. The last line shows for 4 seconds when nothing clears it.

Why does the Korean text look garbled?

Older .smi files are saved in EUC-KR rather than UTF-8. The converter reads the language the file declares and decodes Korean files as Korean. If the text still looks wrong, pick another encoding next to the file name. The .vtt is always UTF-8, as WebVTT requires.

Is the formatting kept?

Italic, bold and underline are kept. Colours and fonts from <font> tags are removed; style them with CSS on your page instead, using the ::cue selector.

Are my files uploaded?

No. The file is read and converted by JavaScript in this browser tab and never leaves your device.