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.
Converting a .itt file to .sbv 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 .itt file to .sbv 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 .sbv file is a SubViewer-style caption document used by YouTube's caption editor: each cue is a single line of start,end timings followed by the caption text on the next lines, separated by a blank line. It carries the same timed dialogue as SubRip but divides the two timestamps with a comma instead of an arrow. For this route the practical draw is accepted directly by YouTube's caption workflow and simpler than SubRip, with no index numbers to renumber after edits — balanced against almost no desktop or browser player plays .sbv directly, so conversion is usually required, which is worth knowing before you commit a large batch.
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 .sbv buys you accepted directly by YouTube's caption workflow, which is why it is the better fit for downloading and re-uploading captions through YouTube's caption editor. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | iTunes Timed Text (.itt) | YouTube SBV subtitles (.sbv) |
|---|---|---|
| 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 | each cue is a timing line H:MM:SS.mmm,H:MM:SS.mmm followed by one or more text lines and a blank separator |
| Strongest at | delivering subtitles to Apple's ingest specifications | downloading and re-uploading captions through YouTube's caption editor |
| Weak spot | frame timecodes are meaningless without the declared frame rate, so a mis-set header shifts every cue | almost no desktop or browser player plays .sbv directly, so conversion is usually required |
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.
Select .sbv in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if SBV 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 SBV file. Outputs keep the original filename with the .sbv extension.
There is no visual quality to lose — itt is text-oriented and sbv 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 .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.
YouTube's caption tools import and export .sbv directly, but most desktop and browser players expect SubRip or WebVTT, so .sbv is typically converted to .srt or .vtt for playback. Any text editor can open and edit it.
It depends on the content: each cue is a timing line H:MM:SS.mmm,H:MM:SS.mmm followed by one or more text lines and a blank separator. Convert one representative file first and compare before batch-processing a large set.
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.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .itt → .sbv → .itt is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.