Skip to content

SMI to SCC Subtitle Converter

Transform Synchronized Accessible Media Interchange subtitles into SCC format instantly and privately in your browser.

Drag & drop your SMI file here

or click to browse

Supports .smi, .sami, .html files up to 50 MB

Core Engine Architecture

Free Online SMI to SCC Converter

Our SMI to SCC converter reads Synchronized Accessible Media Interchange input and produces Scenarist Closed Captioning output entirely in your browser. Source SMI timing (whole milliseconds (Start=...)) is converted to SCC timing (SMPTE HH:MM:SS:FF at 29.97fps). SMI styling and markup are stripped, and unsupported characters are replaced in the basic ASCII caption stream. The conversion runs client-side, so your subtitle files are never uploaded to a server.

Payload & Syntax Inspector

SMI to SCC Code Syntax & Structure Inspection

Side-by-side code inspection illustrating header definitions, timestamp syntax, and cue payload formatting

Millisecond Sync
input.smi
SMI SOURCE
<SAMI>
<BODY>
<SYNC Start=1000><P Class=ENCC>Hello, world!</P>
<SYNC Start=4000><P Class=ENCC>&nbsp;</P>
<SYNC Start=4500><P Class=ENCC>This is a subtitle file.</P>
<SYNC Start=8000><P Class=ENCC>&nbsp;</P>
<SYNC Start=8500><P Class=ENCC>Converted locally!</P>
<SYNC Start=12000><P Class=ENCC>&nbsp;</P>
</BODY>
</SAMI>
output.scc
SCC RESULT
Scenarist_SCC V1.0
 
00:00:01:00 9420c8e5ececef2c20f7eff2ec64a180942f
00:00:04:00 942c
00:00:04:15 94205468e97320e973206120737562f4e9f4ece520e6e9ece5ae942f
00:00:08:00 942c
00:00:08:15 942043ef6e76e5f2f4e56420ecefe361ecec79a1942f
00:00:12:00 942c
Specification Sheet

SMI vs SCC Technical Specifications

Standard Compliant
Input Format

SMI

SMI

SMI (SAMI, Synchronized Accessible Media Interchange) is a Microsoft subtitle format built from HTML-like <SYNC> elements whose Start attribute is given in milliseconds. SMI supports multiple language tracks through CSS classes and was widely used for Windows Media Player captions and accessibility content.

Output Format

SCC

SCC

SCC (Scenarist Closed Captioning) is the industry-standard format for delivering CEA-608 (Line 21) closed captions to North American broadcast television and streaming services. SCC encodes caption text as hexadecimal byte pairs paired with SMPTE timecodes at 29.97 fps and begins with a Scenarist_SCC V1.0 header.

Format Differences

SMI and SCC use different internal structures; the converter normalizes the source cues into the target layout.
SMI uses millisecond Start attributes on <SYNC> elements; SCC uses SMPTE timecodes HH:MM:SS:FF at 29.97fps with hex byte pairs.
SMI may carry styling or markup; SCC has limited caption controls, and source styling is not mapped and is dropped.

Conversion Troubleshooting & Gotchas

Practical solutions for player compatibility, character encoding, and timing synchronization

4 Common Gotchas
GOTCHA #1

Subtitle timing drifts or appears out of sync on media players

Video files frequently differ in framerate (e.g., 23.976 fps vs 25 fps). If the timing drifts steadily, use our Subtitle Sync tool to adjust the global offset or framerate stretch.

GOTCHA #2

Characters appear as garbled symbols or question marks (Mojibake)

Legacy files saved in Windows-1252, Shift-JIS, or GBK may render incorrectly. Our exporter standardizes output to clean UTF-8. Use our Subtitle Encoding Converter if the source file is corrupted.

GOTCHA #3

Overlapping captions when multiple speakers talk simultaneously

Different formats handle overlapping dialogue differently. If your target player cannot render stacked cues cleanly, open the file in our Subtitle Editor to adjust individual cue timings.

GOTCHA #4

Video editing software (Premiere, DaVinci, Final Cut) rejects the file

Professional NLE software enforces strict syntax rules. Our converter eliminates malformed line breaks and non-standard tags, producing clean, standardized files.

Features

Encodes supported basic ASCII text into CEA-608 hexadecimal byte pairs.
Converts source timing to SMPTE timecodes (HH:MM:SS:FF at 29.97fps).
Inserts CEA-608 pop-on caption control codes for proper display.
Adds the required Scenarist_SCC V1.0 file header.

Why Convert?

SCC is commonly used for closed-caption delivery to North American broadcast workflows.
Streaming delivery specifications may request SCC or another caption format; check your platform's current requirements.
FCC rules govern closed captioning for applicable television programming; verify that generated output meets your delivery specification.
Broadcast automation and playout servers read SCC but not plain-text subtitle formats.
Scenarios

Common Use Cases

Broadcast Caption Delivery

Produce basic SCC files for broadcast-oriented workflows, then verify them against the recipient's CEA-608 specification.

Streaming Delivery

Generate SCC when a streaming platform explicitly accepts it, and confirm the current delivery specification.

FCC Context

Create SCC as part of a compliance workflow; professional delivery requires final specification checks.

Format Ecosystem

Related Formats

How It Works

  1. 1

    Upload your .smi file by dragging it in or browsing.

  2. 2

    The parser reads the Synchronized Accessible Media Interchange structure and extracts each cue's start, end, and text.

  3. 3

    Source SMI timing (whole milliseconds (Start=...)) is converted to SCC timing (SMPTE HH:MM:SS:FF at 29.97fps).

  4. 4

    SMI styling and markup are stripped, unsupported characters become ?, and cues are formatted to the SCC specification.

  5. 5

    The output .scc file is generated and ready to download.

Frequently Asked Questions

It reads a Synchronized Accessible Media Interchange file, parses each cue's timing and text, strips SMI markup, and writes a .scc file. Source SMI timing (whole milliseconds (Start=...)) is converted to SCC timing (SMPTE HH:MM:SS:FF at 29.97fps).

Absolutely. Every conversion runs client-side in your browser. No subtitle data, file contents, or metadata is ever transmitted to a server.

SMI styling and markup are dropped. Unsupported characters are replaced with ?, and timing is quantized to 29.97 fps SCC frames, so review delivery-critical output before use.

Yes, completely free with no sign-up, no watermarks, and files up to 50 MB each. All processing happens in your browser, so your files are never uploaded to a server.

Source SMI timing (whole milliseconds (Start=...)) is converted to SCC timing (SMPTE HH:MM:SS:FF at 29.97fps).

Yes. The converter is fully responsive and works in any modern mobile browser on iOS and Android.

Ready to convert your subtitles?

Drop your SMI file here and convert to SCC instantly.