Stream Bridge Stream Bridge

Stream DeckLink / SDI to a web browser

Stream Bridge takes a feed from any Blackmagic Desktop Video source, SDI, HDMI, capture card, whatever DeckLink hardware you're running, and turns it into a low-latency browser stream. Producers, directors and clients just open a link and watch - no capture card or receiver needed at their end.

Join Beta
Signal Flow

4 Simple Steps

  1. Connect your source

    Plug in any DeckLink input: cameras, vision mixers, routers or replay outputs.

  2. Pair the app

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

  3. Share a link

    Send a viewer link, password optional. No port forwarding or network admin needed.

  4. They watch live

    Open it in Chrome, Firefox, Edge or Safari. Direct where possible, via our cloud when not.

How it works

Setup is the same as any Stream Bridge source. Install the desktop app, create a device on the dashboard, then enter the connection key. Once connected, any DeckLink inputs on that machine become available to set up as a stream, alongside NDI, OMT and other source types.

A stream can handle as many viewers as your connection allows, and each one gets a link you can configure separately - branding, password protection, extra audio, whatever that viewer needs.

Share the link and viewers connect straight in through their browser. If a direct connection isn't possible, we route it through our cloud network automatically, so it still works from offices, venues or mobile networks with tighter firewalls.

The stream is monitored continuously in the background, adjusting buffering and delay to keep playback stable. Latency can be as low as 50ms on a strong connection, though we advertise around 500ms to allow for realistic 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

Technical detail on the source, audio path, encoding load, picture quality, internet route, and viewer controls.

Supported Sources

Any Blackmagic Desktop Video input the paired device can see.

Explore details

Stream Bridge captures video from anything running through compatible Blackmagic hardware and Blackmagic Desktop Video - that's not limited to SDI. Capture cards, HDMI inputs and DeckLink SDI are all supported, covering cameras, vision mixers, routers and replay outputs.

Keep the source running before you start the stream. New devices can take around 30 seconds to finish discovery, especially on a network with a lot of sources.

Audio

Up to 16 embedded audio channels come through with the picture.

Explore details

Stream Bridge can capture up to 16 audio channels embedded in the source, the same as it does for NDI. These are delivered to the browser as individually controllable tracks, so viewers can select programme audio, clean feeds, commentary or other production channels.

If the audience needs more than the source mix, add separate audio feeds to the link and let them set their own levels. Return communication is a separate setting per link.

Performance

NVENC where available, CPU as the fallback.

Explore details

NVENC on a supported NVIDIA GPU keeps latency and CPU use low - that's the recommended route. CPU encoding is the fallback when there's no compatible GPU, or it's already committed elsewhere.

Each device defaults to four GPU encodes and two CPU encodes. Those are safety limits, not performance targets - watch the live CPU/GPU meters before raising them.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

The DeckLink input needs to be free and not already held by another application. Every viewer is a separate connection, and your configured bitrate applies to each one - two viewers at 5Mbps needs roughly 10Mbps upload.

Pick your bitrate based on the content and the whole route, not just the source resolution. Start conservative, watch the connection stats, and adjust live if quality or stability isn't there.

Networking

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

Explore details

There's no need for a shared VPN between the sending site and the viewer. Stream Bridge introduces the two ends and prefers a direct, peer-to-peer connection across their existing internet.

When a direct route isn't available, a time-limited relay kicks in automatically. You don't need to reconfigure anything, though the extra hop can add some distance and use more bandwidth.

Security & Customisation

Separate, controllable links per audience.

Explore details

Access and appearance are set at the link level, so a polished client player and a technical operator view can share the same source without sharing controls or branding.

Use separate, revocable links for different audiences, and remove links or bridge routes once a production is done with them.

Stream DeckLink / SDI to a web browser

Frequently Asked Questions

What production teams need to know before configuring this source, route, and destination.

Setup & sources

Anything running through compatible Blackmagic hardware and Blackmagic Desktop Video - capture cards, HDMI and SDI are all supported, not just SDI. Make sure DeckLink discovery is switched on, the runtime is installed, and the input isn't locked by another app, then create a stream and pick your viewer or Bridge Sharing destination.

No. They open the link in Chrome, Firefox, Edge or Safari - Chrome's the most reliable for WebRTC - and nothing needs installing at their end.

On a strong direct connection with NVENC it can feel close to local. CPU encoding, Wi-Fi, congestion, long distances and relay routing can all add delay, so it's worth testing your actual route beforehand.

Delivery & performance

A 5Mbps stream watched by two people and bridged to one device works out at roughly 15Mbps of upload before overhead. Stable capacity matters more than a one-off speed test result.

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

The route is negotiated automatically, and TURN provides a fallback for tricky NAT or firewall setups. Bridge state is kept, so a brief outage at either end doesn't mean rebuilding the route from scratch.

Related workflows

Send DeckLink / SDI as remote NDI Convert DeckLink / SDI to WebRTC Stream desktop capture to a web browser Stream NDI straight to a web browser