Turn TTML subtitles into JSON. It is converted in your browser, so the file never leaves your device.
Drop TTML files here
or choose from your computer paste with Ctrl V
from Photos or Files
Ready · other file types work too0 bytes uploaded, ever
Drop TTML (DFXP) 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 TTML to JSON converter is part of this page and runs inside your browser. Your subtitles 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.
TTML is verbose XML that many consumer players cannot read. JSON is what APIs and most programming languages read natively. TTML is at home in subtitles delivered to broadcasters and streaming services; 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. Times in clock, offset, frame and tick form are all understood, and a region's position is kept as the cue's position. 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.
TTML is the W3C's XML subtitle format. Streaming services and broadcasters deliver captions in TTML profiles such as IMSC. It can describe regions, styles and timing precisely, but it is verbose, and many consumer players do not read it. DFXP is an earlier profile of it.
Opens in Broadcast and streaming systems, Apple and Netflix workflows, and some video players
TTML 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| TTMLTTML subtitles | JSONJSON data | |
|---|---|---|
| Stands for | Timed Text Markup Language | JavaScript Object Notation |
| Type | Subtitles | Structured data (text) |
| Compression | None (XML text) | None |
| Introduced | 2010, by the W3C | 2001, by Douglas Crockford |
| Opens in | Broadcast and streaming systems, Apple and Netflix workflows, and some video players | Any text editor, every programming language, browser developer tools |
| Best for | Subtitles delivered to broadcasters and streaming services | APIs and data exchanged between programs |
| File extension | .ttml, .dfxp | .json |
No. The TTML 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 TTML 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.