Add your ITT file
Drop one or more .itt 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.
ITT to JSON
Converting a .itt 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.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop ITT files here
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.About converting iTunes Timed Text to JSON data
Converting a .itt file to .json extracts the document's content from its office package into a portable form. An .itt file is an iTunes Timed Text document: a constrained TTML profile that Apple defined for subtitle delivery to the iTunes Store and Apple TV. Its defining trait is timing — cues are addressed in SMPTE timecode (HH:MM:SS:FF) against a frame rate declared in the document header.
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.
Why convert ITT to JSON?
The practical trigger for this conversion is usually a mismatch: with .itt, frame timecodes are meaningless without the declared frame rate, so a mis-set header shifts every cue. 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.
ITT vs JSON at a glance
| Aspect | iTunes Timed Text (.itt) | 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 | timing is frame-accurate: begin and end are HH:MM:SS:FF timecodes resolved against ttp:frameRate, optionally scaled by ttp:frameRateMultiplier for drop-frame rates such as 23.976 | exactly six value types; no dates, no comments, no trailing commas — the strictness is deliberate |
| Strongest at | delivering subtitles to Apple's ingest specifications | rEST and HTTP API request and response payloads |
| Weak spot | frame timecodes are meaningless without the declared frame rate, so a mis-set header shifts every cue | no comments — a perpetual annoyance for configuration files |
Pick JSON as the output
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.
Convert on your device
Press Convert. The package is unzipped in memory and its XML content parsed locally; nothing is uploaded.
Verify and download
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.
ITT to JSON questions, answered
Will converting ITT to JSON lose quality?
There is no visual quality to lose — itt 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.
Is it private to convert ITT files here?
Yes — the .itt 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.
Where will the JSON file work?
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.
Will the JSON file be bigger or smaller than my ITT?
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.
What happens to the metadata in my ITT file?
In .itt, the frame-rate parameters are read because timing depends on them; styling attributes are dropped, since millisecond caption targets have nowhere to record them. 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.