What are Captions?
Captions are time-aligned text tracks that represent spoken dialogue and may identify speakers or relevant sounds. They can be embedded in media or delivered as a separate selectable resource.
How Captions work
A caption file or stream is organized into cues containing timing, text, and sometimes positioning or style instructions. Unlike a transcript, it participates in the playback timeline; unlike dialogue-only subtitles, accessible captioning can convey speakers, music, and meaningful non-speech audio. Authoring occurs after transcription or translation, followed by timing review, format conversion, packaging, and player validation across the intended languages and devices.
A metadata reader parses known structures and can derive additional properties from the encoded content. The workflow then validates and normalizes fields before using them for search, routing, naming, filtering, or access decisions.
Metadata can be embedded in a file, stored beside it, or derived during analysis. Track its source and normalization rules, and decide which fields are authoritative, searchable, privacy-sensitive, or safe to copy into derivatives.
Key facts
- 1WebVTT is widely used for web text tracks, while TTML-family documents are common in professional exchange and streaming; conversion can lose styling or placement not shared by both models.
- 2Overlapping cues, line wrapping, and safe-area placement must be tested against real video because syntactically valid captions can still obscure important graphics or one another.
- 3Burned-in captions become image pixels and work without track support, but viewers cannot disable them, search them as text, or independently select another caption language.
When Captions matter
Add captions to support accessibility, silent viewing, localization, indexing, and search. Incorrect timing or character encoding can make an otherwise valid track difficult or impossible to follow.
- Filtering files by dimensions, duration, codec, MIME type, language, or detected content.
- Building catalogs with searchable descriptions, rights, locations, and relationships.
- Driving output paths, transformation parameters, moderation, and retention rules.
Working with metadata at scale
Guidance that holds across every metadata term in this glossary, not just Captions.
What you gain
- Structured metadata makes media searchable, filterable, and automatable.
- Technical properties let workflows choose valid transformations before processing.
- Provenance and rights fields support governance throughout an asset’s lifecycle.
What it costs
- Copying all metadata preserves context but can leak private or obsolete information.
- Derived labels scale classification but carry confidence limits and model bias.
- Rigid schemas improve consistency while making novel or vendor-specific fields harder to retain.
Answer these before production
- 1Distinguish supplied metadata from values detected or derived during processing.
- 2Normalize units, time zones, encodings, and controlled vocabularies at ingestion.
- 3Remove sensitive fields before exposing files or metadata to another audience.
How Transloadit helps with Captions
When Captions are relevant to your workflow, you can hand the surrounding metadata work to Transloadit instead of maintaining the processing stack yourself. Transloadit reads technical metadata as files enter a workflow and exposes it to later Steps and Assembly Variables. It can also write selected metadata into supported output files.
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.