Transloadit

What is Slice-Based Encoding?

Slice-based encoding divides a video frame into regions that can be decoded with limited dependence on other slices in that frame. This structure can support parallel processing and contain some transmission errors.

How Slice-Based Encoding works

Within codecs that support slices, each frame is partitioned into coded units with boundaries that limit which neighboring data may be referenced during entropy decoding and prediction. Multiple slices can be assigned to threads or packets, and a decoder may recover unaffected areas when one slice is lost. Slices are not the same as independently seekable frames, because they still belong to a picture and may depend on other pictures. Encoders choose their number or size as part of a latency, resilience, parallelism, and compression tradeoff.

Key facts

  1. In H.264/AVC, a slice contains an integer number of macroblocks and begins with its own header; arbitrary rectangular screen regions are not guaranteed by basic slice ordering.
  2. Starting additional slices resets or limits some coding contexts and cross-boundary prediction, which usually costs compression efficiency at a comparable visual quality.
  3. Putting slices into separate transport packets can limit the visible impact of packet loss, but recovery still depends on codec structure, reference use, and decoder concealment.

When Slice-Based Encoding matters

Configure slices when latency, multicore decoding, packetization, or error resilience outweighs maximum compression efficiency. Additional slice boundaries reduce prediction opportunities and can increase bitrate at equal quality.

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