Convert a TTML/DFXP subtitle file to the simple SRT format that practically every player understands, locally in your browser. No upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
Continue with this file
No re-upload neededThese tools accept .SRT - your file is handed over directly.
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
TTML/DFXP files typically come from professional delivery chains for streaming platforms and broadcasters - they are usually unsuitable for everyday use in a desktop player or editing software, since those almost exclusively read SRT or VTT. This tool extracts the timings and text from a TTML file and writes them out as SRT.
The tool specifically looks for <p begin="..." end="..."> elements in the document, reads their timing (the common hours:minutes:seconds.milliseconds format as well as bare-seconds values like "12.5s") and their text content, converts any <br/> breaks inside into real line breaks, and strips other XML markup. Frame- or tick-based timecodes, a rarer TTML detail, are honestly not supported.
The whole process happens locally in your browser without a full XML parser - a targeted detection tuned to this one element pattern is enough for typical subtitle content. If the tool finds no matching elements, it stops with a clear message.
| Input formats | TTML, DFXP |
|---|---|
| Output format | SRT |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Only unprefixed <p begin end> elements with clock-time or bare-seconds timing are read; frame- or tick-based timecodes and a namespace prefix like <tt:p> are honestly not supported. Regions, styling and layout information from TTML are lost, since SRT has no place for them.
No, the conversion runs entirely locally in your browser.
The tool specifically reads the common <p begin end> pattern with clock-time or seconds timing; frame-based timecodes or a namespace prefix like <tt:p> are deliberately not covered.
No, SRT has no concept of styling, regions or layout - only times and plain text are carried over.
Yes, there is the sibling tool "Convert SRT to TTML" for that.