Documentation Index
Fetch the complete documentation index at: https://docs.daydream.live/llms.txt
Use this file to discover all available pages before exploring further.
What is Delivery and Outputs?
Delivery is the mechanism that transports your livestream from the server to the viewers watching the stream. The platform takes the ingested stream and sends it to viewers at scale using CDNs (Content Delivery Networks) with servers around the world and handles transcoding (creating multiple quality versions) along with optimizing routing to get video to viewers quickly.Why This Matters
After you create your AI-generated stream in Daydream, there’s one more important decision: how will you get it to your viewers? Think of it like choosing how to deliver a package. You could use overnight express shipping (fast but expensive) or standard shipping (slower but handles more volume). With streaming, you’re choosing between speed and scale.WHEP Output (Low Latency)
WHEP (WebRTC HTTP Egress Protocol) is designed for ultra-low latency streaming — typically under 1 second of delay. How it works: Uses WebRTC technology (the same technology used for video calls) creates direct peer-to-peer-style connections between your stream and viewers. Data travels quickly with minimal buffering.| Best For | Trade-offs |
|---|---|
| Live auctions or betting where every second counts | Smaller audience capacity (harder to scale to thousands of viewers) |
| Interactive streams (gaming, live Q&A, reactions) | Requires more server resources per viewer |
| Video conferencing or webinar-style broadcasts | Less compatible with traditional CDNs |
| Real-time collaboration where immediate feedback matters | May have more connection stability issues on poor networks |
HLS Output (CDN Distribution)
HLS (HTTP Live Streaming) is the industry standard for scalable, reliable delivery to large audiences. How it works: Breaks your stream into small video chunks (typically 2-10 seconds each) Distributes these chunks across CDN (Content Delivery Network) servers worldwide Viewers download and play chunks sequentially| Best For | Trade-offs |
|---|---|
| Large-scale events (concerts, conferences, sports) | Higher latency (typically 10-30 seconds delay) |
| On-demand playback and DVR features | Not suitable for real-time interaction |
| Mobile apps and broad device compatibility | The chunked nature means slight quality adjustments as network conditions change |
Choosing the right output
| WHEP | HLS |
|---|---|
| Latency under 2 seconds is critical | You need to reach a large audience (thousands or millions of viewers) |
| You have a smaller, engaged audience (dozens to hundreds) | A few seconds of delay won’t impact the experience |
| Interaction is a key part of the experience | You want maximum device/platform compatibility |
| You’re okay with higher infrastructure costs per viewer | Reliability and scale matter more than instant feedback |
API Examples
Create a Output with WHEP
WHEP output is provided when you create a stream with the Daydream API. Theoutput_playback_id provided in the response is used to pull the stream from Daydream.
How It Works
Create a Output with HLS
HLS output is provided when you create a stream with the Daydream API. Theoutput_playback_id provided in the response is used to pull the stream from Daydream for scalable CDN distribution.
How It Works
Create a Output with RTMP
Using Streaming Platforms to deliver your stream.You are only able to change the
output_playback_id when creating a NEW
stream. You cannot change it on an existing stream.