Before WHIP, every WebRTC ingest service had its own signalling protocol — WebSocket schemas, REST quirks, vendor SDKs. An OBS plugin written for one service could not work with another without code changes. WHIP standardises the simplest possible signalling: the encoder POSTs an SDP offer to a known URL, the server replies with an SDP answer and a session URL, and media flows over the resulting WebRTC PeerConnection. PATCH and DELETE on the session URL manage ICE candidates and teardown.

RFC 9725 was published in March 2025 after several years as a draft (draft-ietf-wish-whip). By 2026 WHIP is supported by OBS (built-in since 30.x in 2023), Cloudflare Stream, Mux, Dolby.io, AWS MediaLive, Twitch, and most managed live platforms. It does for WebRTC ingest what RTMP did for Flash ingest — a single common surface area that every encoder vendor can target. The killer combination is OBS pushing H.264/Opus over WHIP to a managed service that converts to LL-HLS for distribution.

WHIP gives sub-second contribution latency where RTMP gives 2–5 seconds, with no port headaches (all signalling on HTTPS/443, media on standard WebRTC UDP). The cost is that WHIP requires WebRTC-capable encoders and ingest servers, both of which are heavier to operate than RTMP. The trend through 2026 is WHIP for new low-latency workflows, RTMP for everything that already works and has no latency requirement.

Book cover: Video Streaming, Volume 2 of the Fora Soft Video Engineering Handbook

The book · Volume 2 of 7

Video Streaming: A Complete Guide to Video Delivery: From Network Protocols and Transport to Ingest, HLS, and MPEG-DASH

WHIP turns WebRTC ingest into a single HTTP request, so OBS and hardware encoders can publish to any compliant server without a vendor SDK. This volume covers WHIP in detail as part of contribution, with WebRTC ingest, RTMP and SRT alternatives, NAT behaviour and the ingest share of the latency budget. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

Adding WHIP ingest so encoders and OBS can publish with sub-second latency?

Tell us about your ingest servers and sources and we will deliver a WHIP rollout plan with endpoint design, auth, codec settings and an RTMP fallback. 250+ video products shipped since 2005.

Book a 30-min call →WhatsApp →Email us →