Camera mode lets you go live straight from the browser on your phone or computer, without installing an encoder.

You can switch between the front and the back camera of a phone during the broadcast, and it keeps running on the same connection.

The microphone stays on while you change cameras.

Switching the camera does not open a second connection, so the broadcast is not restarted.

The camera you chose last time is remembered and opens first on your next broadcast.

If that camera is no longer connected, the default camera opens instead of the start failing.

If the connection drops, the browser keeps trying to publish again with the same camera picture, without stopping the capture.

If a reconnection attempt fails, the browser waits a little longer before the next one, and the broadcast keeps its on-air state in the meantime.

When you come back to the browser after switching apps on your phone, the connection is checked right away.

Pressing Stop ends the broadcast itself, not only the camera, so viewers are not left waiting on a dead stream.

The quality panel shows the frame rate, the resolution and the bitrate your browser is actually sending.

When nothing is being sent, the panel shows empty readings instead of made-up numbers.

Camera mode suits quick updates, interviews and events where carrying a laptop with an encoder is not practical.

Before you go live from a phone, connect to a stable network and plug in the charger if you can.

WHIP lets an encoder publish to a broadcast over WebRTC, the real-time technology browsers use for video calls.

A WebRTC broadcast gives you one WHIP address that already carries its stream key, so there is a single line to paste into your encoder.

Every broadcast has its own WHIP address, and two broadcasts never share one.

An address without a key is never handed out, because it would publish nowhere.

The key is encoded safely inside the address, so a key with unusual characters cannot break it.

If your encoder reconnects while the old session of the same key is still held, the stale session is cleared so the new one can publish.

Only the session of your own key is ever cleared, never a session that belongs to another broadcast.

WHIP is a good fit when your encoder already supports WebRTC publishing.

Keep the WHIP address private, because it contains the key that publishes to your broadcast.