Professional Broadcast & Editing Subtitle Converter

Convert .ITT to .SRT — instant, private, frame-accurate

Final Cut Pro and iTunes write caption tracks as iTunes Timed Text XML. Most editors cannot import them. Drop the .ITT file here and download a clean SubRip file in seconds.

Frame-accurate XML tags stripped Free, no signup

100% Local Browser Processing — Your files never leave your device.

Subtitle converter

Ready — drop a file to start

Drop a subtitle file here

or

.ITT · .SCC · .STL · .ASS · .SSA · .VTT · .SBV · .SRT

    — cues — source —
    100% Local Browser Processing — Your files never leave your device.

    Background

    What an .ITT file actually is

    An .ITT file is an XML document from the Timed Text Authoring Format (TTAF) — the caption format Apple shipped with iTunes, Final Cut Pro and early versions of QuickTime. Inside you will find a <head> block describing styles and regions, and a <body> block holding the actual cues.

    Each cue lives in a <div> (and usually a nested <p>) carrying begin and end attributes:

    <p begin="00:00:01.240" end="00:00:03.480">Hello there</p>

    Some broadcast exports use frame-based stamps such as 00:00:01:12 (12 frames), and nearly all of them wrap the visible text in <span> tags carrying font, colour and alignment overrides.

    Troubleshooting

    Why .ITT captions break in Premiere, Resolve and YouTube

    "Unsupported file format"

    Premiere Pro, Avid and Resolve only accept SubRip, WebVTT, EBU STL and a handful of interchange formats. XML-based Timed Text is not on that list, so the import simply fails.

    Text arrives with visible XML

    Naive "rename to .srt" workflows leave <span tts:fontSize="150%"> markup inside the cues, and drop the cue index numbers that SubRip requires.

    Everything lands at 00:00

    Apple sometimes writes timestamps as frames (HH:MM:SS:FF) and sometimes as milliseconds (HH:MM:SS.mmm). A converter that assumes one format will push the whole track to the wrong place on the timeline.

    Fonts and regions are lost

    The ITT head block describes safe-title regions and type styles that no other editor understands, so the captions can end up in the wrong part of the frame.

    Under the hood

    How SubRescue converts ITT to SRT

    1. 01

      Every <div> and <p> is collected

      SubRescue walks the document, pairing each cue with the nearest enclosing element that carries a begin timestamp, so cues that only inherit their timing from the parent block are still captured correctly.

    2. 02

      Timestamps are normalised to milliseconds

      Both 00:00:01.240 and frame-based 00:00:01:08 stamps are resolved, including dur attributes when an end is missing.

    3. 03

      Formatting markup is removed

      <span>, <p> and style attributes are stripped, <br/> becomes a real line break and XML entities such as &amp; are decoded back into the characters you typed.

    4. 04

      A clean SubRip file is written

      The output carries sequential cue indices and HH:MM:SS,mmm timings, ready for Premiere Pro, Resolve, Final Cut, Avid, YouTube or your broadcast delivery spec.

    DIY

    Converting .ITT to .SRT by hand

    You can rename .itt to .xml and open it in a text editor, but you still have to convert every begin/end attribute by hand, renumber the cues and strip the style tags. On a 40-minute documentary with 900 cues that is hours of work — and the usual mistake is silently losing an hour of timing.

    SubRescue does the same job in about four seconds, and you can still review the output in the preview pane before downloading it.

    Other conversions

    Related subtitle converters

    FAQ

    Frequently asked questions

    How do I convert an .ITT file to .SRT for Final Cut Pro?
    Drop the .ITT file into the converter above, keep the output set to SRT, and download the result. Final Cut Pro reads SubRip directly, so the converted file can be imported as a caption track, attached to a timeline and re-exported as burned-in text if you need it.
    Does the .ITT to .SRT converter keep my timing exactly?
    Yes. Every begin/end value is parsed and converted to milliseconds, including frame-based timestamps such as 00:00:01:12, which are resolved at 29.97 frames per second, and duration-only cues where only a dur attribute is present.
    What happens to the formatting tags inside my .ITT file?
    They are removed by default. The <span>, style attributes and XML wrappers are stripped so the cue contains only the words the viewer should see, with <br/> tags converted into genuine line breaks. You can toggle "strip formatting tags" off if you want to keep the original markup for your own pipeline.
    Can I convert an .ITT file with Arabic text?
    Yes. The Text Encoding Fixer detects whether the file is UTF-8 or Windows-1256, and repairs the common double-encoding corruption that turns Arabic and accented characters into mojibake.
    Is there a limit on how many .ITT files I can convert?
    The free tier converts one file of up to 500 KB. Lifetime Pro converts up to 100 files per batch with a single ZIP download, and raises the per-file limit to 50 MB.
    Can I convert .ITT to .VTT instead of .SRT?
    Yes — switch the output format selector to VTT and you will get a WebVTT file with the same timings, which is the right target for HTML5 video players, JW Player and most modern streaming workflows.