Stream Bridge Stream Bridge

Convert NDI to WebRTC

Stream Bridge converts full-bandwidth NDI and NDI HX into WebRTC, so the source can reach a browser viewer or another paired device over the internet without exposing your local NDI network or building a separate gateway.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick an NDI source

    Any NDI or NDI HX source on your network: cameras, vMix, OBS, PTZ or graphics.

  2. Pair the app

    Install Stream Bridge, add a device on the dashboard and enter its connection key.

  3. Convert to WebRTC

    Choose GPU or CPU encoding, set the bitrate and carry up to 16 audio channels.

  4. Receive it anywhere

    In a browser or on another paired device. Direct where possible, cloud when not.

How it works

The setup is the same as any other Stream Bridge source. Install the desktop app, create a device on the dashboard, and enter the connection key. Once connected, any NDI or NDI HX sources on your network become available to convert into a WebRTC stream.

You choose GPU or CPU encoding, set the live bitrate, and share up to 16 source audio channels. From there you can create as many different viewer experiences as you need from the one stream.

We always try a direct connection first, so the local NDI network never has to be extended out to the internet. If that's not possible, we bridge it through our cloud network automatically.

Once live, the connection is monitored continuously - keyframe recovery, jitter handling and automatic reconnection all run in the background to keep delivery smooth. Latency can be as low as 50ms, though we advertise around 500ms to allow for buffering.

Get Started Quickly

To get started straight away, join our beta, download the application, and get streaming. We also have a host of documentation available that goes through all of the features of Stream Bridge, troubleshooting issues, and our support team are ready to help if needed.

Join Beta View Documentation

Devices

Studio A

Online
Sources 5 sources
Last Seen 18 January 2026 | 10:21 AM
CPU 21%
GPU 20%
Under the hood

Technical Breakdown

What operators need to know about inputs, audio channels, device performance, bandwidth, routing, and control.

Supported Sources

Full-bandwidth NDI and NDI HX sources on the paired device.

Explore details

Stream Bridge picks up full-bandwidth NDI and NDI HX sources the paired device can see - cameras, vMix, OBS, PTZ cameras, graphics systems and anything else on NDI.

Discovery is controlled per device, so you can turn off input families you don't use, or restrict results to local sources on a busy network.

Audio

Up to 16 channels, individually controllable.

Explore details

Stream Bridge can capture up to 16 audio channels from a single NDI source and deliver them to the browser as individually controllable tracks - programme audio, clean feeds, commentary, whatever the source carries.

Different audiences don't need the same audio. Configure extra tracks and communication tools at the viewer-link level to suit each role.

Performance

NVENC where available, CPU as the fallback.

Explore details

A supported NVIDIA GPU encodes through NVENC with barely any CPU impact, which is usually the best fit alongside live production software. CPU encoding is the fallback when there's no compatible GPU, or it's already committed.

Live telemetry shows encoder headroom. If load's getting close to the top or frames start dropping, cut back on concurrent work or move the encode to better hardware.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

The WebRTC route includes ICE negotiation, keyframe recovery, jitter handling and relay fallback. Every viewer is a separate connection, and your bitrate applies to each - two viewers at 5Mbps needs roughly 10Mbps upload.

A static presentation and a fast sports camera put very different demands on the encoder, so tune bitrate live while watching device and viewer behaviour.

Networking

Direct connection first, cloud relay if that's blocked.

Explore details

There's no manual IP exchange or router forwarding required. Each session negotiates its own route automatically.

Corporate and venue networks sometimes block a direct connection. When that happens, Stream Bridge falls back to relay, and you can drop the bitrate if the longer route has less headroom.

Security & Customisation

Custom links, passwords and branding per audience.

Explore details

Custom URLs, passwords, colours, logos and controls let you match the viewer experience to its audience. Up to 25 viewer links can be created per stream.

Security isn't just about the connection - keep your dashboard account protected, keep pairing keys private, password anything sensitive, and remove access you no longer need.

Convert NDI to WebRTC

Frequently Asked Questions

Common questions from source discovery through to the receiving viewer or production device.

Setup & sources

On the paired desktop device. Make sure NDI discovery is switched on in Device Settings and the source is actively transmitting, then create a stream from the dashboard and pick a viewer or Bridge Sharing destination.

They open the link in Chrome, Firefox, Edge or Safari - Chrome's the most reliable for WebRTC - and don't need anything installed.

Usually measured in hundreds of milliseconds rather than seconds, but no internet path is fixed. Use wired connections and leave headroom where timing matters.

Delivery & performance

Pick something both the sender and the weakest receiver can sustain. Many 1080p30 feeds start around 3-5Mbps, with higher-motion or 60fps content often needing more.

Up to 16 channels, delivered as individually controllable tracks. You can expose additional audio sources separately, and return communication is set per viewer link.

No, a direct route is preferred but not required. Relay kicks in automatically when the endpoints can't reach each other, and the app works to recover any interrupted connection.

Related workflows

Stream NDI straight to a web browser NDI to remote NDI over the internet Convert DeckLink / SDI to WebRTC Convert OMT to WebRTC