StreamLive Pro

WHIP from OBS to StreamLive Pro: beta status and setup

How to send WHIP from OBS to StreamLive Pro, why the WHIP tab is still beta and untested with encoders, and why RTMPS or SRT is the safer way to multistream today.

Updated November 5, 2026 · 4 min read

The Encoder card in StreamLive Pro has a WHIP tab marked beta, and OBS can send WHIP: in OBS you set the service to WHIP and paste the WHIP URL into Server. Before you do, know where this stands. We have not tested the WHIP tab with OBS or any other encoder, and Cloudflare Stream, which receives your stream, says its WHIP inputs do not support restreaming over RTMP or SRT, which is how a broadcast reaches YouTube, Facebook and the other networks. For a broadcast that has to reach your networks today, use RTMPS (Connect OBS to StreamLive Pro and multistream) or SRT (Stream with SRT from OBS, vMix or a hardware encoder).

What follows: what WHIP is, what the WHIP tab gives you, how OBS is set up for it, and what to expect.

What WHIP is

WHIP (WebRTC-HTTP Ingestion Protocol) sends video over WebRTC, the technology behind browser video calls. It aims for very low delay and works through most networks because it starts over HTTPS. In OBS it is a separate service type, next to the familiar Custom RTMP server. The protocols side by side are in RTMP vs RTMPS vs SRT: which one to use and when.

What Cloudflare says about WHIP inputs

StreamLive Pro receives encoder streams through Cloudflare Stream. Its WebRTC page lists these limits for WHIP inputs (Cloudflare Stream: WebRTC, checked 5 November 2026):

Cloudflare also lists the codecs it accepts over WHIP: H.264 Constrained Baseline, VP8 and VP9.

The StreamLive Pro phone app also sends WHIP, but through a bridge on our servers that turns it into RTMPS before it reaches the broadcast. The WHIP address on the Encoder card does not go through that bridge.

Before you start

• A paid plan. Encoder ingest, including the WHIP tab, is on the paid plans. In the 7-day trial every tab of the Encoder card shows that RTMP and OBS are on paid plans. See the pricing page.
• OBS 31.0 or later. Cloudflare's page gives its OBS settings for that version.
• A test broadcast. Try WHIP on a broadcast nobody watches, with one channel you can check.

Steps

1. Open the Encoder card. Click New stream and choose Stream from software like OBS (RTMP / SRT). The card is under the preview on the Live stream page.
2. Open the WHIP tab. It is marked beta. It shows a WHIP URL and no separate key: the secret is part of the URL. Copy it with the copy button and treat it like a password.
3. Set the service in OBS. In OBS open Settings, Stream. Set Service to WHIP and paste the URL into Server. Cloudflare says to leave Bearer Token empty, because the secret is already in the URL.
4. Set the output. In Settings, Output, Cloudflare's page recommends an Opus audio encoder, x264 or a hardware H.264 encoder for video, CBR or VBR, 3,000 to 7,000 kbps, profile main or baseline, and B-frames 0. In Settings, Video, set 30 fps.
5. Tick one test channel in the Channels list and keep the page open.
6. Start Streaming in OBS and check three things: whether StreamLive Pro detects the stream, whether the preview shows it, and whether the test channel receives it.
7. Stop and switch if anything is missing. Press Stop stream in StreamLive Pro and Stop Streaming in OBS. Change Service back to Custom, copy the RTMPS address and key, and use that for the real broadcast.

When WHIP is worth trying

At the moment, for testing only. The low delay WHIP is known for applies to the leg from OBS to the ingest; viewers on YouTube or Facebook watch through the network's own player, with its own delay (What is stream latency, and where does the delay come from?). Whatever WHIP saves on the first leg does not reach them, while the limits above can cost you the broadcast itself.

What can go wrong

If you were trying to send a broadcast out to a WHIP server rather than into StreamLive Pro, see Destination not supported": WHIP and HLS destinations.

Frequently asked questions

Does StreamLive Pro support WHIP from OBS?

The Encoder card has a WHIP tab in beta, and we have not tested it with OBS or another encoder. Cloudflare, which receives the stream, says WHIP inputs do not support restreaming over RTMP or SRT, so use RTMPS or SRT to reach your networks.

What goes in the Bearer Token field in OBS?

Nothing. Cloudflare says the secret is already part of the WHIP URL, so the Bearer Token field stays empty.

Is WHIP better than RTMPS for multistreaming?

Not today. RTMPS is tested, encrypted and reaches every network you tick. WHIP's lower delay on the first leg does not shorten the delay viewers see on the networks.

Can I add a WHIP destination instead?

No. WHIP and HLS destinations are refused, because broadcasts go out only over RTMP, RTMPS or SRT.

Why does the phone app use WHIP if it is beta?

The phone app's WHIP goes through a bridge on our servers that turns it into RTMPS. The WHIP address on the Encoder card does not use that bridge.

Keep reading