Reference
Which format rides which path
The format follows from where SyncWords sits in your chain. Find your path, read your options. Cells with a caveat link to the page that explains it.
Formats × paths
| SRT / MPEG-TS | CMAF ingest | HLS at origin | RTMP(S) | Widget | |
|---|---|---|---|---|---|
| Embedded EIA-608 | Yes, plus passthrough of existing 608 | No | No. An MPEG-TS capability, not an HLS one | Yes, rendered natively by social platforms | No |
| Teletext (DVB-TXT) | Yes | No | No | No | No |
| DVB-SUB (bitmap, any script) | Yes | No | No | No | No |
| DVB-TTML | Yes, where the chain decodes it | No | No | No | No |
| TTML | No | Yes; the packager converts it, so only its supported subset survives | No | No | No |
| WebVTT | No | Via the packager's conversion of our TTML | Yes, nearly the full spec | No | No |
| Burned-in open captions | No | No | Yes | No | No |
| Dubbed audio tracks | Yes, as additional audio PIDs | No | Yes | Yes, one stream per language | Yes, over LL-HLS in the widget |
| On-screen caption page | No | No | No | In parallel with the stream | Yes: URL, QR code or embed |
Go deeper
The pages behind the cells
Each path page owns its protocol detail; each format page owns the carriage and presentation detail. Outputs beyond the stream itself, like driving an existing caption encoder over IP or posting captions into Zoom, Teams and Adobe Connect, are covered on the pages below.
Not sure which cell is yours?
Describe your chain and our engineers will tell you which position fits, which formats it carries, and what a proof of concept looks like.