Add your TTML file
Drop one or more .ttml files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .ttml file to .json extracts the document's content from its office package into a portable form. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .ttml file to .json extracts the document's content from its office package into a portable form. A .ttml file is a Timed Text Markup Language document: an XML vocabulary in which each <p> element carries begin and end (or dur) attributes plus the caption text. It is the W3C standard that broadcast and streaming systems use as their interchange format for captions and subtitles.
A .json file holds JavaScript Object Notation: nested objects, arrays, strings, numbers, booleans, and null written in a strict text syntax. It is the default data language of the web — most APIs speak nothing else. For this route the practical draw is parsers ship in the standard library of essentially every language and readable by humans and machines alike — balanced against no comments — a perpetual annoyance for configuration files, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .ttml, far more verbose than SubRip or WebVTT for the same cues. Switching to .json buys you parsers ship in the standard library of essentially every language, which is why it is the better fit for rEST and HTTP API request and response payloads. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Timed Text Markup Language (.ttml) | JSON data (.json) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | the root <tt> element declares the TTML namespace and optional ttp: parameters such as frameRate, tickRate, and timeBase | exactly six value types; no dates, no comments, no trailing commas — the strictness is deliberate |
| Strongest at | delivering captions to broadcast and streaming platforms that mandate a TTML profile | rEST and HTTP API request and response payloads |
| Weak spot | far more verbose than SubRip or WebVTT for the same cues | no comments — a perpetual annoyance for configuration files |
Drop one or more .ttml files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .json in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if JSON is selectable, the route is real and validated.
Press Convert. The package is unzipped in memory and its XML content parsed locally; nothing is uploaded.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid JSON file. Outputs keep the original filename with the .json extension.
There is no visual quality to lose — ttml is text-oriented and json is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Yes — the .ttml file is processed inside your browser tab and never uploaded. The package is unzipped in memory and its XML content parsed locally; nothing is uploaded. Close the tab and the file is gone from memory.
Browsers parse it natively through JSON.parse, every mainstream language bundles support, and most editors validate and highlight it out of the box. Viewing a raw .json file is possible in any text editor or browser tab.
It depends on the content: exactly six value types; no dates, no comments, no trailing commas — the strictness is deliberate. Convert one representative file first and compare before batch-processing a large set.
In .ttml, styling, layout, and region definitions are read past rather than applied: timing and text convert, presentation does not, and no external resource is ever fetched. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.