What is Low-Latency DASH?

Low-Latency DASH is an MPEG-DASH delivery approach that transfers a media segment progressively through successive fragment units while limiting buffering across the pipeline. It reduces live delay while retaining DASH-based playback.

How Low-Latency DASH works

The low-delay approach begins transferring a media segment while its later samples are still being produced. Successive ISO BMFF fragment units, typically moof and mdat box pairs, make more samples available inside that growing segment while the manifest signals early availability to the client. The player estimates throughput from partial transfers and controls a small live-edge target, sometimes using slight playback-rate adjustments to correct drift. Origin, CDN, HTTP transport, encoder, packager, and player must all preserve progressive delivery for the design to work.

Key facts

  1. A low-latency segment can be transferred progressively through successive moof and mdat box pairs, so playback can begin before the complete segment reaches storage. Specifications and implementations do not use “chunk” and “fragment” terminology consistently, so the box structure is the clearer boundary.
  2. In the DASH manifest, availabilityTimeComplete=false signals early access to an incomplete segment, while availabilityTimeOffset describes its advanced availability.
  3. If an origin or intermediary buffers the full response, compliant chunks and manifest signaling still produce ordinary segment latency; transport behavior is end-to-end.

When Low-Latency DASH matters

It supports broadcasts and interactive streams that need near-real-time delivery through DASH-compatible clients. Smaller buffers reduce latency but leave less protection against network jitter and throughput drops.

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