Transloadit

What is Dynamic Metadata?

Dynamic metadata is metadata created or updated as content, context, analysis results, user activity, or delivery conditions change; examples include live captions, automated tags, and rights status. In HDR video the same term has a distinct standardized meaning: scene- or frame-level color-volume metadata such as the SMPTE ST 2094 family.

File + supplied context
Metadata processing
Structured media record
Metadata is read, normalized, and used to drive decisions about the media it describes. This diagram shows metadata broadly, not specifically Dynamic Metadata.

How Dynamic Metadata works

In asset management, dynamic metadata represents facts whose values or applicability evolve after initial cataloging. Updates may arrive from live production, analysis models, business rules, rights systems, or audience context, and can apply to an entire asset or a precise time range. Consumers need both the value and enough temporal, version, and provenance information to decide whether it is current, and it participates in live playback, search reindexing, personalization, compliance, and operational automation. HDR delivery uses the term differently: there, dynamic metadata carries per-scene or per-frame display-mapping guidance, in contrast to static metadata that describes a whole program.

Key facts

  1. Timed metadata needs a media timeline or timestamp domain; wall-clock time alone cannot reliably attach a caption, cue, score, or scene label after edits or discontinuities.
  2. Event messages in segmented video and timed ID3 metadata are delivery mechanisms, while the authoritative catalog may store a normalized record for search and later reprocessing.
  3. Out-of-order analysis jobs can overwrite newer values unless updates carry source, model or rule version, event time, and conflict policy; cache and index invalidation must follow accepted changes.

When Dynamic Metadata matters

Use dynamic metadata when consumers need current information rather than a fixed catalog record. Define update timing and authority carefully, because stale or conflicting values can drive incorrect search or access decisions.

Common use cases for metadata

These examples cover metadata broadly, not specifically Dynamic Metadata.

  • 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

This guidance covers metadata broadly, not just Dynamic Metadata.

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.

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.

Before production

  1. Distinguish supplied metadata from values detected or derived during processing.
  2. Normalize units, time zones, encodings, and controlled vocabularies at ingestion.
  3. Remove sensitive fields before exposing files or metadata to another audience.

Turn media knowledge into a working pipeline

Connect uploads, processing, AI, storage, and delivery through one declarative API — with the encoding stack, scaling, and format churn handled for you.

Try Transloadit for free