StreamTest

LL-HLS PART-HOLD-BACK is below three part durations

The declared PART-HOLD-BACK is smaller than three times PART-TARGET, so players chase a live edge they cannot reach.

What it means

In low-latency HLS, PART-HOLD-BACK tells the player how far behind the live edge to start. The specification requires it to be at least three times PART-TARGET.

Why it matters

Set too low, the player starts closer to the edge than the server can reliably serve. Every jitter in part production becomes a stall, so the stream rebuffers continuously on exactly the connections low latency was supposed to help.

How to fix it

  1. Set PART-HOLD-BACK to at least 3 x PART-TARGET in your EXT-X-SERVER-CONTROL tag.
  2. If you are targeting the lowest possible latency, reduce PART-TARGET rather than PART-HOLD-BACK.

Check your own stream

The free HLS analyzer runs this check on every analysis and links each finding straight back here.

Open the HLS analyzer

Frequently asked questions

What does "LL-HLS PART-HOLD-BACK is below three part durations" mean?
In low-latency HLS, PART-HOLD-BACK tells the player how far behind the live edge to start. The specification requires it to be at least three times PART-TARGET.
Why does it matter?
Set too low, the player starts closer to the edge than the server can reliably serve. Every jitter in part production becomes a stall, so the stream rebuffers continuously on exactly the connections low latency was supposed to help.
How do I fix it?
1. Set PART-HOLD-BACK to at least 3 x PART-TARGET in your EXT-X-SERVER-CONTROL tag. 2. If you are targeting the lowest possible latency, reduce PART-TARGET rather than PART-HOLD-BACK.
How can I detect this automatically?
Paste your HLS streaming URL into StreamTest's free HLS analyzer. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.

Related HLS checks