suggestedPresentationDelay is missing or too small
Players start too close to the live edge and have no room to absorb a slow segment.
What it means
The manifest declares no @suggestedPresentationDelay, or one shorter than about two segment durations.
Why it matters
This value is how far behind the live edge a player should sit. Too small and every hiccup in segment production or delivery becomes a rebuffer, because the player is asking for content the moment it exists. Absent entirely and each player picks its own, so latency and stability differ per device.
How to fix it
- Add suggestedPresentationDelay to <MPD>, at least two to three segment durations.
- With four-second segments, PT12S is a reasonable starting point for standard latency.
- Lower it only alongside shorter segments and a CDN you have measured under load.
Check your own stream
The free DASH validator runs this check on every analysis and links each finding straight back here.
Open the DASH validator →Frequently asked questions
- What does "suggestedPresentationDelay is missing or too small" mean?
- The manifest declares no @suggestedPresentationDelay, or one shorter than about two segment durations.
- Why does it matter?
- This value is how far behind the live edge a player should sit. Too small and every hiccup in segment production or delivery becomes a rebuffer, because the player is asking for content the moment it exists. Absent entirely and each player picks its own, so latency and stability differ per device.
- How do I fix it?
- 1. Add suggestedPresentationDelay to <MPD>, at least two to three segment durations. 2. With four-second segments, PT12S is a reasonable starting point for standard latency. 3. Lower it only alongside shorter segments and a CDN you have measured under load.
- How can I detect this automatically?
- Paste your MPEG-DASH streaming URL into StreamTest's free DASH validator. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.
Related DASH checks
- DASH manifest has no UTCTiming elementA live MPD without UTCTiming forces players to trust the device clock, so any skew on the viewer’s machine becomes stalls or missing segments.
- DASH availabilityStartTime is in the futureThe manifest claims the presentation starts later than the current time, so no segment is available yet and playback cannot begin.
- The DASH manifest is not well-formed XMLThe document could not be parsed as XML, so nothing else could be checked.
- The document has no MPD root elementThe XML parsed, but its root is not <MPD>, so it is not a DASH manifest.
- MPD declares no profileWithout @profiles a player cannot tell which DASH feature set the manifest expects.
- MPD declares no minBufferTimePlayers use this required attribute to size the initial buffer before starting playback.