Add your VTT file
Drop one or more .vtt 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 .vtt file to .itt 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 .vtt file to .itt extracts the document's content from its office package into a portable form. A .vtt file is a WebVTT caption document: a WEBVTT header followed by timed cues for HTML5 video and audio. It is the web-native caption format browsers expect for the track element.
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. For this route the practical draw is frame-accurate timing that lines up exactly with an edit timeline and a narrow, validatable profile with far fewer interoperability surprises than full TTML — balanced against frame timecodes are meaningless without the declared frame rate, so a mis-set header shifts every cue, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .vtt, some legacy desktop players prefer .srt and mishandle WebVTT settings. Switching to .itt buys you frame-accurate timing that lines up exactly with an edit timeline, which is why it is the better fit for delivering subtitles to Apple's ingest specifications. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | WebVTT subtitles (.vtt) | iTunes Timed Text (.itt) |
|---|---|---|
| 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 | files begin with WEBVTT and optional metadata headers before the first blank line | 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 |
| Strongest at | captioning HTML5 video with the track element | delivering subtitles to Apple's ingest specifications |
| Weak spot | some legacy desktop players prefer .srt and mishandle WebVTT settings | frame timecodes are meaningless without the declared frame rate, so a mis-set header shifts every cue |
Drop one or more .vtt 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 .itt in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if ITT 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 ITT file. Outputs keep the original filename with the .itt extension.
There is no visual quality to lose — vtt is text-oriented and itt 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 .vtt 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.
Final Cut Pro, Compressor, and Apple's delivery pipelines read and write .itt, and Subtitle Edit imports it. Browsers and consumer players do not. Novus Convert resolves the SMPTE timecodes against the document's own ttp:frameRate and ttp:frameRateMultiplier — falling back to 30 fps only when neither is declared — and exports to any of the twelve timed-text targets.
It depends on the content: 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. Convert one representative file first and compare before batch-processing a large set.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .vtt → .itt → .vtt is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.