Dacast Upgrades WebRTC Ingest with WHIP: Faster, More Reliable Browser-Based Streaming
By Dacast Editorial Team | Reviewed by Jon Whitehead, COO at Dacast | Updated April 2026
Going live from a browser should be the easy part. No encoder to install, no settings to dig through, just open Dacast, hit Go Live, and you’re streaming. That simplicity hasn’t changed. But the infrastructure making it possible just got a serious upgrade.
Dacast has migrated its WebRTC ingest to WHIP, a modern standard that puts browser-based streaming on the same technical footing as RTMP and SRT. In plain terms: the engine under the hood is now faster, more reliable, and built to last. If you’ve ever had a Go Live session behave unexpectedly, or if you’re a developer looking to build on top of Dacast’s ingest, this one’s for you.
TL;DR
Dacast upgraded the engine behind its Go Live feature. Browser-based streaming now runs on the same modern pipeline as RTMP and SRT; more reliable, more consistent, and open to developers via a standard called WHIP. The experience looks identical. What’s underneath is meaningfully better. One thing it doesn’t do yet: sub-500ms ultra-low latency delivery. That’s a separate project, and this upgrade is a step toward it.
Table of Contents
- What’s New
- What Changed
- Why This Matters
- How to Use the Go Live Feature – Including with OBS
- A Bit of Technical Context
- How WebRTC/WHIP Fits into the Streaming Protocol Landscape
- What’s Next
- Frequently Asked Questions
- Try It Today
What’s New
Dacast has migrated its browser-based “Go Live” feature to WHIP, the WebRTC-HTTP Ingestion Protocol, as part of a broader investment in a unified, modern ingest pipeline. This update affects every Dacast user who streams directly from a browser, and opens new doors for developers building custom WebRTC ingest workflows.
Here is a summary of what changed:
- The Go Live feature now runs on the same modern ingest pipeline (ingest v2 / SRS-based) as RTMP and SRT
- The WHIP endpoint is now visible in the Encoder Setup UI alongside RTMP and SRT
- The WHIP URL is returned by the API in encoder settings responses
- Stream key rotation now works consistently across RTMP, SRT, and WebRTC/WHIP
- WebRTC channels are now correctly reflected in API list and lookup responses
- Dacast has contributed WHEP support to FFmpeg upstream (PR #21603), extending ecosystem compatibility
What Changed
WebRTC Ingest Now Uses WHIP
WHIP (WebRTC-HTTP Ingestion Protocol) is a standardized protocol developed by the IETF, designed specifically for WebRTC-based ingest. It defines how a WebRTC stream is pushed from a client (a browser, an encoder, or a custom app) to a media server over HTTP. Think of it as doing for WebRTC what RTMP did for encoder-to-server communication: creating a reliable, predictable, and widely interoperable standard.
Before this upgrade, every platform implementing WebRTC ingest, including Dacast, had to build proprietary signaling and handshake logic from scratch. That led to fragmented systems that were hard to integrate with external tools. WHIP standardizes that handshake.
By adopting WHIP, Dacast aligns with where the broader industry is heading and makes WebRTC ingest more predictable, interoperable, and easier to build on.
A Unified Ingest Pipeline
Previously, the Go Live feature relied on a legacy AMS-based infrastructure. It worked, but it was isolated : WebRTC channels weren’t integrated with the new ingest pipeline (ingest v2 / SRS-based) that powers RTMP and SRT on Dacast. That meant WebRTC users weren’t benefiting from pipeline-level improvements, and the architecture was inconsistent.
That’s now changed. WebRTC ingest runs on the same modern infrastructure as RTMP and SRT. Stream key rotation works consistently across all three protocols. This reduces edge cases, simplifies stream management, and makes the overall system more robust and easier to maintain.
WHIP Endpoint Now Accessible in the UI and API
The WHIP endpoint is now visible in the encoder setup section of your Dacast account and available through the API. This makes it possible for developers to build custom WebRTC ingest workflows, not just use the built-in Go Live tool.
This is an important capability unlock: any tool or encoder that supports WHIP can now connect directly to Dacast’s ingest infrastructure without custom integration work.
WHEP Contributed to FFmpeg
As part of this project, Dacast’s engineering team developed WHEP (WebRTC-HTTP Egress Protocol) support and contributed it upstream to FFmpeg, the widely-used open-source media framework (PR #21603). WHEP is the playback counterpart to WHIP: it standardizes how clients connect to and decode WebRTC streams. This contribution extends the broader ecosystem’s compatibility with WebRTC ingest workflows and reflects Dacast’s investment in open-source streaming infrastructure.
Why This Matters
This update is primarily about reliability and architectural integrity. Here’s what it means in practice:
- Go Live from your browser with improved consistency : fewer edge cases, more predictable behavior
- Consistent stream key management across RTMP, SRT, and WebRTC : no more protocol-specific quirks
- Developer access to the WHIP endpoint for building custom ingest solutions
- A stronger technical foundation for future WebRTC features and improvements
One important note: this update does not introduce ultra-low latency (sub-500ms) delivery. WebRTC ingest is now more reliable and standardized, but Dacast’s current delivery layer still uses HLS. Ultra-low latency playback is a separate capability, one that this infrastructure makes easier to build toward.
How to Use the Go Live Feature – Including with OBS
The Go Live feature is designed for browser-based streaming, no encoder required. But if you prefer to use OBS or another WHIP-compatible encoder, you now have a direct path to do that on Dacast.
Option 1: Go Live Directly from Your Browser
This is the simplest option and requires no additional software:
- Log into your Dacast dashboard
- Create a new live channel
- Click “Go Live” to activate your webcam and microphone
- Click “Start Streaming” and you’re live
The feature works in any modern browser (Chrome, Firefox, Edge, Safari) on desktop or laptop. No encoder setup, no RTMP keys to configure.
Option 2: Stream to Dacast via WHIP with OBS
OBS Studio version 31 and later includes native WHIP support. If you’re on an older version, update OBS before proceeding.
To stream to Dacast using WHIP from OBS:
- In your Dacast dashboard, go to your channel’s Encoder Setup
- Select the WHIP tab : you’ll see your WHIP endpoint URL and stream key
- In OBS, go to Settings > Stream
- Set Service to “WHIP”
- Paste your Dacast WHIP endpoint URL into the Server field
- Paste your stream key into the Bearer Token field
- Click OK, then click Start Streaming in OBS
Why use WHIP with OBS instead of RTMP?
RTMP remains the most common and widely-tested ingest protocol, and for most broadcasters it’s still the best choice. WHIP via OBS is useful when you want WebRTC-based ingest from a desktop encoder, for example as a building block for lower-latency workflows in the future. For standard broadcast, RTMP ingest is recommended.
Option 3: Build a Custom WHIP Integration
The WHIP endpoint is now accessible via the Dacast API, which means developers can build custom WebRTC ingest solutions (mobile apps, web apps, kiosk-based streaming setups, or automated workflows) that connect directly to Dacast without using the built-in Go Live tool.
Contact Dacast support or refer to the API documentation for endpoint details and authentication.
A Bit of Technical Context
For those curious about what changed under the hood:
- The Go Live feature previously used a legacy ingest system. It now runs on the same modern ingest infrastructure that powers RTMP and SRT streaming on Dacast.
- WHIP is an IETF-standard protocol that defines how WebRTC streams are ingested over HTTP. Using a standard means better interoperability with external tools and encoders that support WHIP.
- Dacast has also contributed WHEP support to FFmpeg, the widely-used open-source media framework, as part of this broader investment in the WebRTC ecosystem.
How WebRTC/WHIP Fits into the Streaming Protocol Landscape
Not all streaming protocols serve the same purpose. Here’s a quick reference:
| Protocol | Latency | Primary Use | Scalability | Security |
|---|---|---|---|---|
| WebRTC / WHIP | Real-time (low) | Browser-based ingest & interactive streaming | Small–medium groups; SFUs extend reach | DTLS + SRTP (mandatory) |
| RTMP | 1–3 seconds | Encoder ingest, live broadcast | Large audiences via CDN | RTMPS (TLS) |
| SRT | Sub-second to a few seconds | Contribution workflows, remote production | Moderate (point-to-point) | AES encryption |
| HLS | 6–30+ seconds | Large-scale delivery to passive audiences | Very high (CDN-native) | HTTPS, DRM, AES-128 |
Key takeaway: WebRTC via WHIP is best for browser-based ingest and interactive scenarios. For large-scale delivery to mass audiences, RTMP ingest feeding into HLS delivery remains the standard and Dacast supports all three protocols on the same unified pipeline.
What’s Next
This infrastructure upgrade is part of a longer-term investment in WebRTC at Dacast. By building on a standardized, modern foundation, the platform is now better positioned to support:
- More robust browser-based streaming workflows
- Expanded developer access to WebRTC ingest via WHIP
- Future improvements to real-time streaming capabilities
Specific features and timelines will be announced as they’re ready. For now, the focus is on giving existing workflows a more solid and reliable foundation.
Frequently Asked Questions
What is WHIP?
WHIP (WebRTC-HTTP Ingestion Protocol) is a standardized protocol for sending WebRTC streams to a media server over HTTP. It was developed to give WebRTC ingest a reliable, interoperable standard, the same way RTMP standardized encoder-to-server communication for live streaming.
Does this change how I use the Go Live feature?
No. If you use the browser-based Go Live tool in your Dacast dashboard, the experience is unchanged. The upgrade is infrastructure-level : the same interface, now running on a more reliable foundation.
Does WebRTC/WHIP on Dacast support ultra-low latency playback?
Not currently. WebRTC ingest is now more reliable and standardized, but video delivery on Dacast still uses HLS. Ultra-low latency end-to-end delivery is a separate capability. This update is a step toward that direction, but it’s not available yet.
Can developers use the WHIP endpoint directly?
Yes. The WHIP endpoint is now visible in the encoder setup section of your Dacast account and accessible through the API, making it available for custom WebRTC ingest integrations.
Which Dacast plans include the Go Live feature?
The browser-based Go Live feature is available to all active Dacast subscribers. Check your dashboard or contact Dacast support for plan-specific details.
Try It Today
The Go Live feature is available to all active Dacast subscribers. Log into your dashboard, create a new channel, and stream directly from your browser, no encoder or third-party software required.
New to Dacast? You can start a free 14-day trial and test the Go Live feature with no commitment and no credit card required.
Start your free trial at dacast.com
For regular tips on live streaming and exclusive offers, feel free to join our LinkedIn
In the meantime, check out our Knowledge Base, which offers a wide range of resources.
