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 DFXP
Converting a .itt file to .dfxp 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 DFXP timed text
Converting a .itt file to .dfxp 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 .dfxp file is a TTML document written to the Distribution Format Exchange Profile — the profile the W3C defined for handing finished captions to a distributor. The extension signals the profile; the contents are ordinary TTML, which is why the same parser reads both. For this route the practical draw is accepted by name across a wide set of streaming ingest specifications and fully TTML, so any TTML tool can read and validate it — balanced against the distinct extension implies a distinct format and regularly confuses tooling, which is worth knowing before you commit a large batch.
Why convert ITT to DFXP?
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 .dfxp buys you accepted by name across a wide set of streaming ingest specifications, which is why it is the better fit for delivering captions to a platform whose spec names DFXP by extension. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
ITT vs DFXP at a glance
| Aspect | iTunes Timed Text (.itt) | DFXP timed text (.dfxp) |
|---|---|---|
| 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 | the document is TTML: a <tt> root, a <body>/<div> structure, and <p> cues with begin and end attributes |
| Strongest at | delivering subtitles to Apple's ingest specifications | delivering captions to a platform whose spec names DFXP by extension |
| Weak spot | frame timecodes are meaningless without the declared frame rate, so a mis-set header shifts every cue | the distinct extension implies a distinct format and regularly confuses tooling |
| Metadata | the frame-rate parameters are read because timing depends on them; styling attributes are dropped, since millisecond caption targets have nowhere to record them | profile and parameter attributes are read for timing purposes only; styling and layout are not carried into caption targets that cannot express them |
Pick DFXP as the output
Select .dfxp in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if DFXP 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 DFXP file. Outputs keep the original filename with the .dfxp extension.
ITT to DFXP questions, answered
Will converting ITT to DFXP lose quality?
There is no visual quality to lose — itt is text-oriented and dfxp 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 DFXP file work?
Streaming ingest pipelines, caption editors such as Subtitle Edit and CaptionMaker, and any TTML-aware library open .dfxp. Browsers and consumer players do not. Novus Convert reads it through the same hardened TTML parser used for .ttml — no document types, no external entities, no network access — and writes any of the twelve timed-text targets.
Will the DFXP file be bigger or smaller than my ITT?
It depends on the content: the document is TTML: a <tt> root, a <body>/<div> structure, and <p> cues with begin and end attributes. 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.
Can I convert DFXP back to ITT?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .itt → .dfxp → .itt is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.