GlossaryWHEP

WHEP

WHEP (WebRTC-HTTP Egress Protocol) is a standard way for a player to receive a live stream from a server using WebRTC, set up with a single HTTP request. It is the playback partner of WHIP, which handles sending video in. WHEP gives viewers delay of under a second while letting any compatible player work with any compatible server, instead of relying on custom code for each vendor.

Why it matters

Real-time playback has long required custom player code tied to one vendor's servers. WHEP standardizes that handshake, so a business can switch providers or players without rewriting playback. That lowers lock-in for products like betting and live auctions, where viewers need delay under one second.

How it works

  1. The player sends one HTTP POST request with an SDP offer describing what it can receive.
  2. The server replies with an SDP answer and a session URL for that viewer.
  3. The connection is set up with standard WebRTC networking and media starts flowing to the player.
  4. When the viewer leaves, the player sends an HTTP DELETE request to end the session.

What is the difference between WHIP and WHEP?

WHIP sends a live stream into a server, and WHEP pulls a live stream out to a viewer. Both use the same simple pattern: one HTTP request to set up a WebRTC session and one to end it. Together they let encoders, servers and players from different vendors work together for real-time streaming.

Is WHEP a finished standard?

Not yet. WHEP is still an IETF Internet-Draft working through review, while its sibling WHIP was published as an RFC in 2025. Several servers and players already implement WHEP, so it is usable today, but details can still change. Teams adopting it should test against the specific server and player versions they plan to ship.

Where it's used

Betting services, live auctions and interactive watch party apps use WHEP to give viewers real-time playback in a standard way, while large passive audiences usually stay on HLS.

By the numbers

Making Video Dead Easy For Developers

We've put together valuable insights in the form of blogs and guides. Check'em out.

What a microdrama platform costs to run: about 30 cents a viewer, and falling

What a microdrama platform costs to run: about 30 cents a viewer, and falling

Explore the true cost of building a microdrama platform. Understand streaming, encoding, storage, infrastructure costs, and how unit economics improve as your audience grows.

Your content is a channel. Castr limits how much of it you can broadcast.

Your content is a channel. Castr limits how much of it you can broadcast.

Compare FastPix and Castr for cloud playout. See differences in channel limits, scheduling, API access, EPG support, analytics, automation, and pricing for 24/7 streaming.

AI content moderation using NSFW and Profanity filter

AI content moderation using NSFW and Profanity filter

Discover how AI is changing content moderation with advanced NSFW and profanity filters. This blog highlights how AI boosts efficiency, accuracy, and cost-effectiveness, making online spaces safer and more respectful. Learn about the technology behind these filters and their impact on user experience.