Free online TTML converter. Convert TTML to SRT, VTT, ASS, SSA, SUB and more online — no limits, no watermark.
.ttml caption file or click to add it. The same tool also opens .dfxp files, since DFXP is just an older name for TTML. Need the reverse direction? Switch the "From format" dropdown to load SRT, VTT, ASS, SSA, SBV, SUB, LRC, SMI, STL, TXT, or CSV instead.<track> captions on a web page.<track> captions that load natively in the browser.dfxp extension some legacy systems still expectTTML — Timed Text Markup Language, a W3C XML standard first published as a Recommendation in 2010 and updated to TTML2 in November 2018 — is the caption format the professional video world runs on. Netflix, the BBC, and most broadcast and OTT delivery pipelines require TTML or one of its profiles, because XML lets a caption file describe far more than words and timing: colors, fonts, named regions, precise positioning, multiple languages, and accessibility metadata all live inside the markup. That richness is exactly why a TTML file rarely drops cleanly into a consumer player or a simple video editor.
You may also see the same captions as a .dfxp file. DFXP (Distribution Format Exchange Profile) is the original name TTML was published under; the W3C kept the term alive only in formal profile names like DFXP Transformation and DFXP Presentation. For practical purposes a .dfxp and a .ttml file are the same XML format with a different extension.
The most common reason to convert away from TTML is destination mismatch — the place you're handing the subtitles to wants a simpler, more broadly playable file:
.srt) is the lightweight classic almost every editor, player, and platform reads. It carries no styling and travels everywhere without surprises, which makes TTML to SRT the single most-requested conversion here.<track> element loads directly in the browser. If the captions are headed for a web page rather than broadcast, VTT is the native target..smi), or EBU STL rather than an XML schema.| Format | Full name / origin | Structure | Styling & positioning | Best for |
|---|---|---|---|---|
| TTML | Timed Text Markup Language, W3C (2010; TTML2 2018) | XML | Rich XML styling, regions, layout, metadata | Broadcast and OTT caption delivery |
| DFXP | Distribution Format Exchange Profile — TTML's original name | XML (same as TTML) | Same as TTML | Legacy systems expecting the .dfxp extension |
| SRT | SubRip, early-2000s DVD-ripping software | Plain text | None | Universal hand-off, editors, YouTube |
| VTT | WebVTT, W3C HTML5 caption standard | Plain text + header | CSS cue settings, regions | HTML5 <track>, browser-native captions |
| ASS | Advanced SubStation Alpha | Styled text script | Full styling, fonts, precise placement | Aegisub, styled fansubs, anime |
| SSA | SubStation Alpha (ASS predecessor) | Styled text script | Styling, basic placement | Legacy styled-subtitle workflows |
| TXT | Plain text transcript | Plain text | None (timecodes removed) | Transcripts, search indexing, translation |
TTML and SRT are the most-requested pair because they sit at opposite ends of the complexity scale: the conversion parses TTML's XML clock, offset, and tick-based timing, normalizes it to SRT's HH:MM:SS,mmm timecodes, and flattens the styling to plain text. In our testing, a 350-cue broadcast TTML episode file converts to SRT in well under a second with every cue's timing preserved line-for-line; the only visible change is that a colored or positioned caption comes out as plain text.
A .ttml file is an XML document holding timed captions — Timed Text Markup Language, a W3C standard. Because it's XML, it opens in any text editor, but to see it rendered you need a caption-aware player or a broadcast/streaming tool; consumer players like VLC read it inconsistently. That's the usual reason to convert: turning the XML into an SRT or VTT file that an editor, YouTube, or a web <video> element reads without complaint. The captions and timing carry over exactly — only the XML styling is dropped.
For most purposes, none. DFXP (Distribution Format Exchange Profile) is simply the name TTML was first published under, and the W3C now keeps the term only inside formal profile labels. A .dfxp file is the same XML you'd find in a .ttml file, so a system that asks for one will almost always accept the other. If a tool insists on the .dfxp extension specifically, convert TTML to DFXP to re-label it without touching the content.
Yes — and that's expected. TTML can describe colors, fonts, named regions, and exact on-screen positions in its XML; SRT has no way to store any of that, so converting to SRT (or TXT) flattens those captions to plain text. The dialogue and the timecodes survive intact; the visual formatting does not. If keeping more of the look matters, target TTML to ASS instead, since ASS is built for styled, positioned subtitles and preserves far more than SRT can.
It depends on where the captions are going. Convert TTML to SRT when you're handing the file to a video editor, an offline player, or a platform like YouTube — SRT is the format least likely to be rejected anywhere. Convert TTML to VTT when the captions belong to an HTML5 <track> element on a web page, since WebVTT is the browser-native format and keeps cue positioning that SRT would drop. Both are plain-text targets that strip TTML's heavier XML styling.
Yes — convert TTML to TXT. That output strips the XML tags, the timecodes, and the cue structure, leaving just the spoken lines as continuous text. It's the fastest way to turn a broadcast caption file into show notes, a searchable transcript, source text for translation, or content to paste into a document. Keep the original TTML if you might need the timing back later — the transcript is one-directional.
Yes. The conversion runs entirely in your browser — your file is parsed and rewritten on your own device and never sent to or stored on our servers. It's never shared, made public, or reused, and there's no sign-up and no watermark on the output. TTML files are small plain XML, so even a long broadcast caption file converts almost instantly.