WHIP Ingest: How to Connect a Live Stream

Before you start

WHIP is a WebRTC-based protocol for publishing live media from a capture source to an ingest endpoint. The workflow is local by default: your camera, encoder, browser, or capture app connects directly to the WHIP endpoint using the endpoint URL and, when required, a token. The connection is peer-to-peer and does not rely on a separate desktop streaming application unless your device requires one.

Before starting, confirm two things. First, the capture source must be able to open a WHIP endpoint URL over HTTPS or WSS and support WebRTC publishing. Second, you need the exact ingest URL from your streaming service. Keep the URL private if it includes an authentication token. Do not share it in screenshots or chat messages.

Network conditions affect the result. A wired connection or a stable local network is more predictable than a congested wireless link. WebRTC-based ingest can be sensitive to packet loss, but the behavior depends on the encoder and the service configuration rather than on a universal setting.

Step-by-step instructions

The exact path depends on whether you are connecting from a browser-based tool, a hardware encoder, or an application. The core process is the same: open the publishing interface, enter the WHIP endpoint, and start the stream.

1) Copy the WHIP ingest URL from your streaming service. It may contain a token after the path. Copy the complete URL exactly.

2) On the capture source, open the WebRTC or WHIP publishing option. Some tools label this as browser-based streaming, WebRTC publish, or a WHIP endpoint field. If the option is not visible, check whether the current firmware or software version supports WHIP.

3) Choose the video and audio source. For a camera or capture card, select the device that should feed the stream. For a browser source, select the requested tab, window, or display if the tool supports that choice.

4) Paste or enter the WHIP endpoint URL. Do not add spaces or line breaks. If the URL was split across lines in a message, assemble it as one continuous string.

5) Review the stream settings before going live. Common options include resolution, frame rate, bitrate, and audio selection. Where the tool exposes these controls, start with the service's recommended values if available. Avoid raising bitrate or frame rate beyond what the connection can carry.

6) Start the stream. In many interfaces this button is labelled Connect, Publish, Start, or Go Live. After the connection is established, the interface typically changes to show a live indicator or a disconnect option.

7) Stop the stream when the session is done. Use the Stop or Disconnect control in the capture source rather than closing the browser or unplugging the camera abruptly, where possible. This gives the service a cleaner end-of-stream signal.

Check the output

Verify the stream from the receiving side, not only from the camera or encoder preview. Open the streaming service's preview page or player while the WHIP connection is active and confirm that the expected video and audio are present.

Check for obvious motion or audio problems. If the picture is clear but audio is missing, review the microphone or audio routing setting on the capture source. If the stream is choppy, test with a lower bitrate or frame rate and compare the result.

The service may show connection details such as negotiated resolution, frame rate, and bitrate. These numbers reflect the actual WebRTC negotiation and may differ from the source settings when network conditions or service limits require a lower value.

WHIP ingest is intended for real-time publishing rather than archival. The recording format and availability of a saved file depend on the streaming platform. If you need a local recording, use a separate capture method configured on the device or application.

Common problems and next steps

A failed connection is often caused by an incomplete URL, an expired or mistyped token, or a service endpoint that is not currently accepting WHIP connections. Re-copy the full endpoint from the service without retyping it manually. If the URL includes a token, confirm it has not expired and that it belongs to the current channel or stream key.

If the browser or application cannot find a WHIP option, check the software version and documentation. WHIP support varies by device and release. Some browsers and tools support WebRTC publishing only through a specific page or companion application provided by the streaming service.

Poor quality can have several causes. Reduce the bitrate first if the connection is unstable, then try a lower frame rate or resolution. Audio breakup may require a different audio source or a lower audio bitrate where that control is available. Keep changes reversible by testing one adjustment at a time.

If the capture source reports an HTTPS or certificate error, the device's clock or root certificates may be out of date. Update the device time and software, then try again. If the error persists, confirm that the endpoint is using a certificate the device can validate.

For service-specific limits, consult the streaming platform's documentation for the supported resolution, frame rate, bitrate, and session duration. WHIP handling can differ between providers, so a setting that works on one service is not a guarantee for another.