What is Timed Text Markup Language?
Timed Text Markup Language (TTML) is an XML-based W3C format for captions and subtitles. It represents text timing, layout, styling, and placement in regions associated with media.
How Timed Text Markup Language works
TTML models a timed-text document as namespaced XML whose body contains timed elements linked to style and layout declarations. Timing can be inherited through the document tree, while regions describe where text is composed on the output canvas. The broad language is narrowed by profiles so senders and receivers share an implementable feature set. It commonly serves as an interchange or distribution representation between caption authoring, broadcast, packaging, and player systems.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
A format may describe a container, a bitstream, or both, and the filename extension can be misleading. Evaluate decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
Key facts
- 1TTML timing may be expressed with begin, end, or duration attributes, and nested elements can inherit timing context; careless parent timing can suppress otherwise valid child cues.
- 2Profiles such as IMSC constrain TTML features for interoperable subtitle and caption delivery, so a document valid against the base language can still violate a target profile.
- 3Native HTML media tracks generally consume WebVTT rather than arbitrary TTML XML; web delivery therefore often converts the document or renders it through player-specific code.
When Timed Text Markup Language matters
Choose TTML when a broadcast, player, or streaming workflow requires it and supports the needed profile. Browser playback often favors WebVTT, so direct TTML delivery may require conversion or player-specific support.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats at scale
Guidance that holds across every file formats term in this glossary, not just Timed Text Markup Language.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Answer these before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.
How Transloadit helps with Timed Text Markup Language
When Timed Text Markup Language is relevant to your workflow, you can hand the surrounding file formats work to Transloadit instead of maintaining the processing stack yourself. Transloadit detects file and MIME information, filters inputs, and converts images, audio, video, and documents into formats suited to browsers, applications, archives, and downstream services.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.