“Live” describes when the media is produced and made available, not just which protocol is used. A live stream may use HLS or DASH, but its playlist keeps advancing and its content may never settle into one complete file. An on-demand asset has a defined beginning, end and availability window.
FAST-VID is intended for supported public on-demand page URLs. It does not promise live-stream download or recording support, and a live stream does not become supported merely because it uses HLS or DASH.
The core difference
On-demand media is prepared and stored before playback. The viewer can request it at any time, seek within it and expect the same content on a later request, subject to availability and licensing.
Live media is produced and delivered as an ongoing event. The viewer joins at the current point, and the available content changes over time. A live stream may offer a DVR window, allowing a short rewind, but that window is not the same as a permanent recording.
Some platforms turn a finished live event into an on-demand replay. That replay is a separate asset with its own storage, manifest and rights. The existence of a replay does not mean the original live stream was downloadable.
Latency, buffering and startup
Live playback has to balance latency against reliability. A player may buffer several segments so that a brief network slowdown does not interrupt the event. Lower latency can mean less buffer and more sensitivity to jitter.
On-demand playback can buffer ahead more freely because the content is already complete. Seeking is also simpler: the player can request a known segment or byte range. A live player may have a limited seekable window and may not be able to jump to a future point.
Neither mode guarantees smooth playback. Encoding delays, segment duration, CDN performance, device decoding and the local network all affect the result.
Live manifests and rolling playlists
HLS uses playlists. A live media playlist is updated as new segments become available and may remove older segments as they leave the window. A DASH manifest can describe a live presentation with a time-shift buffer and updating segment availability.
The client periodically reloads the playlist or manifest, fetches new segments and discards old ones. If the client falls too far behind the live edge, it may skip ahead or restart. That is different from playing a fixed file from beginning to end.
Because the manifest changes, capturing “the URL” once may not capture the event. A recording process must follow updates, handle discontinuities and decide what to do when segments expire or the event ends.
Storage and the missing single file
A live broadcast may never exist as one complete file on the server. It can be generated as segments, delivered through a CDN and discarded after the live window. A replay may be created later from a separate recording pipeline.
Even when segments are retained, assembling them requires correct ordering, timestamps, initialization data and handling of gaps. A simple concatenation of segment files may produce an unplayable or out-of-sync result.
Downloading a live stream in real time also requires continuous capture. If the client stops, the missing interval is gone unless the service provides a replay or DVR window.
Rights and recording
Watching a live event is not the same as recording it, storing it or republishing it. A platform may allow live viewing under one set of terms and prohibit recording or redistribution. The event may include music, performances or third-party footage with separate rights.
A recording can also raise privacy, publicity and consent issues, especially for a private event or an identifiable audience. Technical ability to capture a stream does not create permission.
If you need a recording, check the platform’s terms and ask the rights holder. A public live page is not an automatic licence to keep or share the broadcast.
Common playback and network limitations
Live playback can fail when the client cannot keep up with the live edge, when a segment is delayed, when the clock drifts or when the service rotates keys or URLs. A player may show a spinner, skip forward or stop.
On-demand playback can fail for different reasons: an expired URL, an unsupported codec, a corrupted file or a server range problem. The symptoms can look similar, but the underlying causes differ.
If a live event is unwatchable, use the service’s official player and support channel. A third-party downloader is not a fix for a live delivery problem.
What FAST-VID supports
FAST-VID accepts supported public on-demand page URLs through yt-dlp extractors. It does not promise live-stream download or recording support, and it does not turn a live manifest into a complete file.
A live stream that uses HLS or DASH is not automatically supported. Live, restricted, private, age-gated and DRM-protected content is outside the intended scope.
For a supported on-demand source, FAST-VID may produce a completed media file. For a live event, use the platform’s official replay or recording options where available, subject to its terms.
A practical comparison
| Property | Live | On-demand |
|---|---|---|
| Content availability | Ongoing; changes at the live edge | Fixed asset, subject to availability |
| Manifest | Updated or rolling | Usually fixed for the asset |
| Seeking | Limited to the DVR window | Any available position |
| Recording | Needs continuous capture and rights | Depends on permissions and file format |
| Typical FAST-VID scope | Not promised | Supported public page URLs |
What to check before recording
Confirm whether the event is live, whether a replay will be published, and what the platform’s terms allow. Check whether the event includes third-party music, performances or footage that may need separate permission.
If you need a personal reference copy, use the platform’s official recording feature where available. A live page that happens to use HLS or DASH is not a general recording permission. A replay may also be region-locked, removed later or have a different duration from the live event. That difference matters when someone expects a replay to match the broadcast exactly.
Frequently asked questions
What is the difference between live and on-demand?
Live is an ongoing event delivered as it happens. On-demand is a fixed asset that can be started, paused, sought and replayed.
Is a live stream just an HLS or DASH file?
No. It may use those protocols, but its manifest changes over time and its segments may expire. It is not necessarily one complete file.
Does FAST-VID record live streams?
No. FAST-VID is intended for supported public on-demand page URLs and does not promise live-stream download or recording.
Does a live replay mean I can download the original?
Not necessarily. A replay is a separate asset with its own availability and rights. Check the platform’s terms and permissions.
Why does a live stream keep buffering?
Latency, segment availability, CDN performance, network jitter and device performance can all affect live playback.
Sources and references
- Apple Developer: HTTP Live Streaming
- IETF RFC 8216: HTTP Live Streaming
- MPEG: MPEG-DASH standards
- FAST-VID: HLS vs DASH
Try FAST-VID
Open the FAST-VID downloader for a supported public on-demand page. FAST-VID does not promise live-stream download, recording or protected-stream support.