Turn SCC captions into JSON. It is converted in your browser, so the file never leaves your device.
Drop SCC files here
or choose from your computer paste with Ctrl V
from Photos or Files
Ready · several at once0 bytes uploaded, ever
Drop SCC (CEA-608, EIA-608, line 21) files onto the box above, or click it to choose them. ToAny reads the file's contents to detect the type, so a wrong extension does not matter.
Press Convert. There is nothing else to set. The work happens in this tab.
Save the JSON, or download everything as one ZIP if you converted several files.
The SCC to JSON converter is part of this page and runs inside your browser. Your captions are never sent to ToAny or to anyone else.
Nothing has to travel to a server and back, so the conversion starts the moment you press Convert, even on a slow connection.
No sign-up, no email address and no watermark. Add several files and download them together as a ZIP.
SCC is a hex dump that people cannot read or edit by hand, and web players do not read it. JSON is what APIs and most programming languages read natively. SCC is at home in closed captions for US and Canadian broadcast, DVD and some streaming deliveries; JSON is the usual choice for APIs and data exchanged between programs.
The text is read as UTF-8 or UTF-16, whichever the file is. An older file in another code page is read using the charset it declares, or as Windows-1252 if it declares none, so accented letters in an unlabelled legacy file can come out wrong. A file that is not text, such as the picture-based subtitles of a DVD, is refused instead of being converted to nonsense. CEA-608 pop-on, roll-up and paint-on captions on the first caption channel (or the second, if the first is empty) are read; colours are dropped, and a roll-up row becomes one cue that ends when it scrolls off. Times follow the 29.97 fps frame clock, drop-frame or not. The result is a JSON list with one object per cue: its number, start and end as clock times and in milliseconds, and its text.
SCC stores the CEA-608 caption data of line 21 video as lines of hexadecimal byte pairs, each line starting at a timecode, one pair per video frame. It is limited to 32 characters on up to four rows, a Latin character set and a frame-based clock (usually 29.97 fps drop-frame), but it is what American broadcasters and many video editors expect.
Opens in Broadcast and DVD authoring tools, Premiere Pro, Final Cut Pro, DaVinci Resolve and VLC
SCC converterJSON represents data as nested objects and lists in plain text. It is the default language of web APIs. Unlike a spreadsheet it can be nested to any depth, which is also why turning it into rows and columns takes a decision about how to flatten it.
Opens in Any text editor, every programming language, browser developer tools
JSON converter| SCCSCC closed captions | JSONJSON data | |
|---|---|---|
| Stands for | Scenarist Closed Captions | JavaScript Object Notation |
| Type | Subtitles | Structured data (text) |
| Compression | None (hex text) | None |
| Introduced | The 1990s, by Sonic Solutions (Scenarist) | 2001, by Douglas Crockford |
| Opens in | Broadcast and DVD authoring tools, Premiere Pro, Final Cut Pro, DaVinci Resolve and VLC | Any text editor, every programming language, browser developer tools |
| Best for | Closed captions for US and Canadian broadcast, DVD and some streaming deliveries | APIs and data exchanged between programs |
| File extension | .scc | .json |
No. The SCC to JSON conversion runs inside your browser, on your own phone or computer. The file is not sent to ToAny or to anyone else.
The content is carried over as faithfully as JSON allows; features that JSON does not have are left out.
Yes. Add as many as you like, convert them together and download each result or all of them as one ZIP.
The steps are the same everywhere because ToAny runs in the web browser: open this page in a current version of Chrome, Edge, Safari or Firefox, add the SCC file, press Convert and save the JSON. There is nothing to install.
Yes, but a subtitle file is small. Files up to 50 MB are accepted, far more than any real subtitle file. Beyond that the limit is your device's memory, since nothing is uploaded; a computer copes with large files better than a phone.