Definition

What Is an SCC File?

VideoText editorial team. Updated September 13, 2026.

Direct definition

SCC (Scenarist Closed Caption) is a file format that stores CEA-608 caption data as hexadecimal byte pairs with timecodes. It is common in North American broadcast and finishing workflows.

The sections below explain how SCC is used in transcription and subtitle work, what people often mix up, and which VideoText workflow applies when the next step is a file or review pass.

Key takeaways

  • SCC is caption data for 608/708 pipelines, not a casual subtitle edit format.
  • Converting SCC to SRT loses channel and positioning information unless the tool maps it.
  • Do not assume every “caption file” is SRT.

How SCC is used

Finishing tools encode pop-on or roll-up captions into 608 byte sequences. Players and broadcast encoders — not web <track> elements — are the usual consumers.

What the format carries

Scenarist Closed Captions is a broadcast format that encodes caption data as hexadecimal control and character codes, each block paired with an SMPTE timecode. It expresses the caption as instructions to a decoder rather than as readable text.

Those instructions include positioning, pop-on and roll-up behaviour, and styling, which is why SCC preserves presentation detail that a plain-text format such as SRT cannot represent.

Working with it in practice

It is tied to a frame rate and to the drop-frame convention of the material, so an SCC file delivered against the wrong rate drifts. A delivery specification will normally state both.

Converting SCC to a web format loses information: positioning and styling flatten, and the frame-accurate timecodes become decimal seconds. Converting the other way has to invent the detail SCC expects, so it rarely round-trips cleanly.

Frequently asked questions

Can I edit an SCC file in a text editor?
Technically it is text, but the content is hex codes rather than words, so editing by hand is impractical. Use a caption tool that understands the format.
Is SCC still used?
Yes, in broadcast delivery and archive workflows, where specifications continue to require it. Web platforms use WebVTT or SRT instead.
Why did my SCC captions drift after conversion?
Almost always a frame rate or drop-frame mismatch between the file and the material it was authored against.
Can I create an SCC file from an SRT?
Tools will do it, but the conversion has to invent what SCC expects — positioning, presentation style, and frame-accurate timecode at a stated rate. Check the result against the delivery specification rather than trusting the conversion.

Related terms

Sources

  1. FCC: Closed captioning of televised video programming (47 CFR § 79.1)

Related VideoText workflow