Stream Bridge Stream Bridge

OBS remote NDI over the internet

Stream Bridge brings NDI from another location into OBS as a local source - the internet transport happens outside the scene, so OBS just sees a named NDI or OMT input through its normal plug-in.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick the remote source

    Cameras, gameplay, graphics or a programme feed on the remote NDI network.

  2. Pair both ends

    Install Stream Bridge at each site and pair each device with its connection key.

  3. Bridge the stream

    Pick the source and bridge it to the receiving device. No ports, VPN or network admin.

  4. Add it to OBS

    It appears on the OBS machine as a local NDI source for any scene.

How it works

The WAN connection stays separate from how OBS builds a show. The remote feed is received and republished locally, so OBS uses its normal NDI or OMT source plug-in instead of internet settings buried inside every scene.

Output names are set per bridge, so remote cameras, gameplay, graphics and programme feeds stay easy to identify. The same source can also go to browser viewers or additional devices at the same time.

The paired devices connect directly wherever possible, with cloud relay available automatically when NAT or firewall policy blocks that route. No shared VPN or inbound ports needed.

If the source or a device drops out temporarily, Stream Bridge keeps the bridge configuration and works to reconnect it, so OBS can keep the local source in its scene while the transport recovers.

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

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

Explore details

Stream Bridge works with full-bandwidth NDI and NDI HX sources the paired device can see - cameras, vMix, OBS, PTZ cameras, graphics systems and other NDI sources.

Only sources visible to the desktop device can be selected. Allow discovery time after connecting, and use local-sources-only filtering on a busy production LAN.

Audio

Up to 16 channels, individually controllable.

Explore details

Stream Bridge can capture up to 16 audio channels from a single NDI source, delivered as individually controllable programme tracks.

Where the audience needs more than the source mix, add separate audio feeds to the link and let them control their own levels. Return communication is an independent per-link choice.

Performance

NVENC where available, CPU as the fallback.

Explore details

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

Each device starts with limits of four GPU and two CPU encodes. Treat these as safety limits rather than performance targets, and watch the live CPU/GPU meters before raising them.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

OBS needs the matching NDI or OMT plug-in on its end; the remote contributor only needs the Stream Bridge sending device. Every browser viewer and receiving-device bridge is its own connection - plan sender upload for the bitrate multiplied by the number of simultaneous routes.

You can change bitrate live without rebuilding the stream. Most 1080p30 pictures sit comfortably around 3-5Mbps; fast motion or 60fps usually wants 5-10Mbps and a stronger connection.

Networking

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

Explore details

ICE negotiation finds a usable route without asking either end to open an inbound port. Where the networks allow it, video goes straight between the production device and its viewer or receiver.

Restrictive NAT and firewall policy can force the connection through TURN instead. That reaches more networks, though the extra hop may add delay, so stick to stable wired bandwidth where you can.

Security & Customisation

Separate, controllable links per audience.

Explore details

Create a different link for each role rather than exposing one universal player - each can have its own URL, password, appearance, audio choices and communication controls while using the same stream.

Anyone with a viewer link can access its feed, so distribute it deliberately and add a password where appropriate. Device connection keys should stay private to whoever manages that machine.

OBS remote NDI over the internet

Frequently Asked Questions

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

Workflow setup

A paired desktop device with NDI discovery switched on and the source actively transmitting on a reachable network. Create a stream, then pick a viewer or Bridge Sharing destination pointed at the OBS machine.

As a named NDI or OMT source on the receiving device, and where compatible Blackmagic hardware and Card Output are enabled, it can also be assigned to selected SDI ports.

We target under 500ms real-time delivery. What you actually get depends on encoder choice, distance, route quality, buffering, and whether it's going direct or through TURN.

Monitoring & delivery

Each destination is a separate send - multiply your bitrate by the expected simultaneous viewers and bridge routes, then leave headroom for overhead and normal fluctuation.

Yes, up to 16 channels, delivered as individually controllable tracks. Additional audio sources can be exposed separately, and return communication is set per viewer link.

No inbound port forwarding is needed. The session tries direct first and falls back to TURN if network policy blocks that; bridges reconnect once the source and receiver are both available.

Related workflows

Remote NDI monitoring for clients and directors Custom branded viewer links for clients Enterprise remote production infrastructure Group talkback for remote production teams