Transloadit

What is Cloud Transcoding?

Cloud transcoding converts media among codecs, containers, resolutions, or bitrates on remotely managed compute infrastructure. Jobs can produce multiple renditions from one source without dedicated local encoding servers.

How Cloud Transcoding works

Transcoding begins by decoding an existing media stream, then encoding it again with new technical parameters; a container-only rewrite is instead a remux. In a cloud pipeline, object storage, job queues, elastic workers, and callbacks separate upload from processing. The stage commonly feeds adaptive-packaging, thumbnail, and archival branches. Re-encoding is lossy for most delivery codecs, so source quality and generation count constrain every derivative.

Key facts

  1. Changing only an MP4 file’s container or track layout can be done by remuxing; decoding and recompressing the picture adds processing time and may introduce generation loss.
  2. Cloud job APIs should make retries idempotent, because a timeout can hide a successful encode and an unconditional resubmission may create duplicate outputs or charges.
  3. Throughput scales across independent files or renditions, but a single long group of pictures may have limited parallelism unless the encoder supports chunked processing.

When Cloud Transcoding matters

Submit cloud transcoding jobs after upload when playback targets require several formats or quality levels. Queue delays, transfer costs, provider limits, and nondeterministic processing time can affect delivery.

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