Add your ASS file
Drop one or more .ass 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 .ass file to .dfxp 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 .ass file to .dfxp extracts the document's content from its office package into a portable form. An .ass file is an Advanced SubStation Alpha subtitle script: an INI-like document whose [Events] section holds Dialogue lines with start and end times, a named style, and text that may carry inline override tags. It is the format fansub and anime communities standardised on because it can position, colour, and animate captions rather than only time them.
A .dfxp file is a TTML document written to the Distribution Format Exchange Profile — the profile the W3C defined for handing finished captions to a distributor. The extension signals the profile; the contents are ordinary TTML, which is why the same parser reads both. For this route the practical draw is accepted by name across a wide set of streaming ingest specifications and fully TTML, so any TTML tool can read and validate it — balanced against the distinct extension implies a distinct format and regularly confuses tooling, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .ass, styling and positioning are lost the moment the file is converted to SubRip, WebVTT, or a lyric format. Switching to .dfxp buys you accepted by name across a wide set of streaming ingest specifications, which is why it is the better fit for delivering captions to a platform whose spec names DFXP by extension. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Advanced SubStation Alpha subtitles (.ass) | DFXP timed text (.dfxp) |
|---|---|---|
| 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 | the script is divided into [Script Info], [V4+ Styles], and [Events] sections, each with its own Format line naming the fields that follow | the document is TTML: a <tt> root, a <body>/<div> structure, and <p> cues with begin and end attributes |
| Strongest at | styled and positioned captions muxed into Matroska releases | delivering captions to a platform whose spec names DFXP by extension |
| Weak spot | styling and positioning are lost the moment the file is converted to SubRip, WebVTT, or a lyric format | the distinct extension implies a distinct format and regularly confuses tooling |
| Metadata | script metadata and the style table describe presentation rather than the cues themselves; conversion keeps timing and text and reports styling as lost, because no caption target can carry it | profile and parameter attributes are read for timing purposes only; styling and layout are not carried into caption targets that cannot express them |
Drop one or more .ass 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 .dfxp in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if DFXP 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 DFXP file. Outputs keep the original filename with the .dfxp extension.
There is no visual quality to lose — ass is text-oriented and dfxp 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 .ass 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.
Streaming ingest pipelines, caption editors such as Subtitle Edit and CaptionMaker, and any TTML-aware library open .dfxp. Browsers and consumer players do not. Novus Convert reads it through the same hardened TTML parser used for .ttml — no document types, no external entities, no network access — and writes any of the twelve timed-text targets.
It depends on the content: the document is TTML: a <tt> root, a <body>/<div> structure, and <p> cues with begin and end attributes. Convert one representative file first and compare before batch-processing a large set.
In .ass, script metadata and the style table describe presentation rather than the cues themselves; conversion keeps timing and text and reports styling as lost, because no caption target can carry it. 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 .ass → .dfxp → .ass is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.