What is an SCC file (and why it looks like hex)

An .scc file is a Scenarist Closed Caption file — the standard delivery format for CEA-608 closed captions in US broadcast, cable, and iTunes-era workflows. Open one in a text editor and you'll see a Scenarist_SCC V1.0 header followed by timecodes and rows of four-digit hex codes. Those hex pairs are the captions: each one is a CEA-608 command or two characters of text, encoded exactly as it would be transmitted on line 21 of an NTSC broadcast signal, one pair per video frame. That's why you can't read an SCC without a decoder — and why broadcasters keep asking for it: it's not a subtitle file that gets converted downstream, it's the finished caption transmission itself. If you just need the text, convert the SCC to SRT; if a delivery spec is asking you for SCC and your NLE only exports SRT, convert SRT to SCC.

What's actually inside an SCC file

A minimal SCC looks like this:

Scenarist_SCC V1.0

00:00:24;22	9420 9420 94ae 94ae 94f2 94f2 43f2 e973 f7e5 ecec

00:00:25;12	942f 942f

Each line is a timecode plus a run of hex words transmitted on consecutive frames. In the example, 9420 is RCL (Resume Caption Loading — "start composing a pop-on caption"), 94ae is ENM (erase the off-screen buffer), 94f2 is a Preamble Address Code that positions the cursor on row 15, and the pairs after it are text characters — 43f2 decodes to "Cr". The second line's 942f is EOC (End Of Caption), the command that actually flips the composed caption onto screen at 00:00:25;12. Commands are doubled (9420 9420) because broadcast transmission was lossy — decoders ignore the identical repeat.

Three practical consequences fall out of this design:

• Timing is frame-based, at 29.97 fps. The semicolon in 00:00:24;22 marks drop-frame timecode (a colon means non-drop). SCC is an NTSC format through and through.
• Text is not ASCII. CEA-608 has its own character set — {, _, and * don't exist in the standard set, while é, ñ, ♪, and ½ do, at nonstandard byte values. Accented capitals live in "extended" sets with fallback rules.
• Bandwidth is two bytes per frame. A full four-row caption takes roughly 2.5 seconds of video to transmit, which is why professional captioning leaves lead-in time before dense dialogue.

SCC vs SRT: what each format is for

SRT is an interchange format: human-readable text with millisecond timing, understood by nearly everything, and the natural export from Premiere, Resolve, or a transcription service. SCC is a delivery format: it encodes screen position, caption style (pop-on for scripted content, roll-up for news and live), the 608 character set, and frame-accurate transmission scheduling. A US broadcaster or distributor asking for "closed caption files" almost always means SCC (or its HD sibling MCC), not SRT — the spec sheet needs captions their playout systems can pass through unmodified.

The two formats don't map perfectly onto each other. Going SCC→SRT, screen positioning is dropped (SRT has none) and only the text, line structure, and timing survive. Going SRT→SRT — sorry, SRT→SCC — your cues get fitted to 608's constraints: lines wrap at 32 characters, captions cap at 4 rows, characters outside the 608 set get transliterated, and captions that can't be transmitted in the time available get scheduled as early as physically possible.

How to open or convert an SCC file

To read or edit an SCC, you need a 608-aware tool: Subtitle Edit (free, desktop) opens SCC directly, and professional packages like MacCaption/CaptionMaker are built around it. For a quick look at the raw structure, any text editor works — you'll see the hex, not the text.

To convert SCC to SRT — for translation, YouTube, editing, or just reading the dialogue — drop the file on CutConvert's SCC to SRT converter. It runs a real CEA-608 decoder: pop-on, roll-up, and paint-on captions, the full character set, drop-frame and non-drop timecode. The decoder is verified against a reference decode of a full broadcast feature — 664 of 664 captions matched exactly.

To convert SRT to SCC for a broadcast or distribution deliverable, use the SRT to SCC converter. It encodes channel-1 pop-on captions with drop-frame timecode — the standard delivery style — handles the 608 character mapping, and schedules caption loads around the format's per-frame bandwidth so display times land on the right frame.

FAQ

What program opens an .scc file? Caption-aware tools: Subtitle Edit (free, Windows/desktop), MacCaption/CaptionMaker, and broadcast QC software. A plain text editor shows the file's hex codes but not the caption text. To read the captions without installing anything, convert the SCC to SRT online.

Why is my SCC file full of hex numbers? Because SCC stores the literal CEA-608 byte stream that would be broadcast on line 21 of an NTSC signal — commands and character codes, two bytes per frame — rather than readable text. Decoding those bytes is exactly what a converter does.

Is SCC the same as SRT? No. SRT is readable text with millisecond timing for general interchange; SCC is a broadcast delivery format encoding CEA-608 captions with screen position, caption style, and frame-accurate 29.97 fps timing. Distributor spec sheets that require "closed captions" usually mean SCC.

Does SCC support accents and special characters? Partially. CEA-608 natively includes á, é, ñ, ç, ½, ♪ and a set of extended accented characters, but not the full Unicode range — smart quotes, em dashes, and many capitals with diacritics have to be transliterated when converting into SCC.

What frame rate is an SCC file? 29.97 fps NTSC, with drop-frame timecode (semicolon separator, like 00:01:00;02) or non-drop (colons). If your project is 23.976 or 25 fps, captions are conformed to 29.97 for SCC delivery.

Can I convert an SCC file back to SRT for free? Yes — short files (about 5 minutes of captions) convert free on CutConvert. Full-length episodes and features need a one-time $7 pack or a paid plan, still a fraction of desktop captioning software.