SyncMySubsConvert SRT to SCC
Turn an SRT file into a Scenarist .scc closed-caption file (CEA-608) for broadcast delivery. It encodes standard pop-on captions as byte-pair hex with odd parity and 29.97 drop-frame timecode. Drop your SRT below; it converts in your browser, nothing is uploaded.
New to these formats? Broadcast caption formats explained →
Output is standard CEA-608 pop-on captioning: white text anchored to the bottom rows, byte-pair hex with odd parity, and 29.97 drop-frame timecode starting at 00:00:00;00. Colours, italics, precise positioning and roll-up/paint-on styles are not encoded — this is the interoperable core of the format, not the full spec.
SRT to broadcast closed captions
SCC (Scenarist Closed Caption) is the file broadcasters and post houses use to carry CEA-608 (line-21) closed captions. Unlike SRT, it isn't plain text you can eyeball: each caption is a stream of two-byte hex codes — control codes and characters — each byte carrying an odd-parity bit, timed to a 29.97 drop-frame clock. This tool builds that stream for you from an ordinary SRT.
It writes pop-on captions, the standard style for scripted and pre-recorded programming: each caption is loaded into off-screen memory (RCL), positioned with a preamble address code, then flipped on screen (EOC) at the cue's in-point and erased (EDM) at the out-point. The loading is back-timed so the caption appears exactly when your SRT says it should.
Because SCC timecode is an absolute program clock, captions land wherever your SRT times place them (this tool starts at 00:00:00;00); if your delivery expects a 01:00:00;00 start, shift the SRT first with the Shift tool. To read an existing SCC back, use SCC to SRT.
FAQ
Which caption style does it produce?
Pop-on captions, the standard for pre-recorded and scripted content. Roll-up (used for live/news) is intentionally not generated, since it's a different timing model; the page states this so there are no surprises in a broadcast workflow.
Does it preserve colours, italics or caption position?
No. It writes white text on the bottom rows — the interoperable core of CEA-608. Colours, italics, and precise positioning aren't encoded. If your workflow needs them, treat this as a starting point and finish in your captioning software.
What about the timecode base?
Timecodes are 29.97 drop-frame and start at 00:00:00;00. Many broadcast deliverables expect a 01:00:00;00 program start — if so, shift your SRT by one hour before converting.
Are non-English characters handled?
Common accented Latin characters (à, é, ñ, ü, ç and so on) are encoded using CEA-608's Special and Extended character sets. Anything outside those sets is replaced with "?" and flagged after conversion.
Is my file uploaded anywhere?
No. The SCC is built in JavaScript in your browser. Your file never leaves your device and no server is involved.