How to convert DFXP to SRT
- Paste the XML, or open one or more .dfxp, .ttml or .xml files.
- Keep Convert to on SRT (SubRip) and Input format on TTML / DFXP (preselected here).
- Shift the timing if needed.
- Copy or download the .srt file, or the ZIP for a batch.
Worked example
<p begin="00:00:01.000" end="00:00:03.200">Hello,<br/>world.</p> becomes SRT cue 1, 00:00:01,000 --> 00:00:03,200, on two lines. <p begin="4s" dur="1.5s"> with a span styled italic through a style id becomes cue 2, 00:00:04,000 --> 00:00:05,500, in <i> tags.
Formats and limits
| Input | DFXP, TTML, XML |
|---|---|
| Output | SRT |
| Engine | Shared subtitle parser and serializers; encoding detection (UTF-8/UTF-16 byte-order marks, UTF-8, Windows-1252 fallback) |
Limitations
- Regions, positions, colors and fonts are ignored.
- Elements written with a namespace prefix, such as <tt:p>, are not read.
- Styles set on div, body or a region are not applied; only styles on p and span count.
- Up to 20 MB per file.
Questions
Which time formats are read?
Clock times such as 00:00:01.000, clock times with frames using the file's frameRate, and offsets such as 4s, 1500ms or 10000000t with the file's tickRate. A cue with begin and dur instead of end works too.
What does basic support leave out?
Regions, positions, colors, fonts and animation. Italic, bold and underline are kept when they are set on the p or span element, directly or through a style id.
Why does it say no timed <p> elements were found?
Either the cues have no readable begin time, or the file writes its elements with a prefix such as <tt:p>, which this reader does not handle. Remove the tt: prefixes in a text editor and try again.
Is my caption file uploaded?
No. The subtitle file is read and converted in your browser.
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
This page opens the Subtitle format converter ready for this task. See the privacy policy for how toolsdocks handles data.