Turn MCC captions into JSON. It is converted in your browser, so the file never leaves your device.
Drop MCC files here
or choose from your computer paste with Ctrl V
from Photos or Files
Ready · several at once0 bytes uploaded, ever
Drop MCC (MacCaption) 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 MCC 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.
MCC is a hex dump that most players, and people, cannot read. JSON is what APIs and most programming languages read natively. MCC is at home in closed captions for broadcast and streaming delivery that carry CEA-708 as well as CEA-608; 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. The CEA-608 caption data inside each packet is read, as for SCC. Captions that exist only as CEA-708 service data are not read. 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.
MCC is MacCaption's caption file: one line per video frame, each a caption distribution packet in hexadecimal that can hold both CEA-608 and CEA-708 data. It exists so that captions can follow the video's own frame rate, 24 to 60 fps, and so that one file serves analogue and digital caption decoders.
Opens in MacCaption, CaptionMaker, Premiere Pro, Final Cut Pro and DaVinci Resolve
MCC 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| MCCMCC closed captions | JSONJSON data | |
|---|---|---|
| Stands for | MacCaption Closed Captions | JavaScript Object Notation |
| Type | Subtitles | Structured data (text) |
| Compression | None (hex text) | None |
| Introduced | The 2000s, by Computer Prompting and Captioning Company (CPC) | 2001, by Douglas Crockford |
| Opens in | MacCaption, CaptionMaker, Premiere Pro, Final Cut Pro and DaVinci Resolve | Any text editor, every programming language, browser developer tools |
| Best for | Closed captions for broadcast and streaming delivery that carry CEA-708 as well as CEA-608 | APIs and data exchanged between programs |
| File extension | .mcc | .json |
No. The MCC 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 MCC 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.