Stream Bridge Stream Bridge

Remote sources for vMix over the internet

Stream Bridge brings remote cameras, contributors and programme feeds into vMix as familiar local sources - the internet transport happens outside your scene, so what shows up is just a named NDI or OMT input.

Signal Flow

4 Simple Steps

  1. Pick the remote source

    An NDI, OMT or DeckLink SDI source on a machine at the remote location.

  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 vMix

    It appears on the vMix machine as an NDI or OMT input, ready to switch.

How it works

vMix keeps working with the local source types you already know. Install the desktop app at each site, pair a device, and send the source over to your vMix machine as NDI or OMT.

Remote cameras, outside broadcasts, guest feeds, graphics and return programmes can all follow the same route. Per-bridge output names keep every feed identifiable when several locations are contributing at once.

The sending and receiving devices connect through a direct-first connection with cloud relay available for restrictive networks. Neither site needs to extend its local media discovery or open any ports.

Bridge state and automatic recovery bring the input back after a short source or network interruption, so your scene and input structure stay stable while Stream Bridge manages the changing WAN path behind it.

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.

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

NDI, OMT, desktop or DeckLink sources on a paired device.

Explore details

Stream Bridge works with an NDI, OMT, desktop or DeckLink/SDI source available to a paired device - programme outputs, multiviews, camera feeds, clean feeds and graphics returns are typical picks.

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

Programme audio travels with the source; add extra tracks as needed.

Explore details

Programme audio can travel with the source, and up to 16 channels are available where the source supports it. Additional tracks and return communication can be configured separately.

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

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

Live telemetry makes encoder headroom visible. 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

Give each bridge a clear output name so it's easy to tell remote feeds apart during setup and recovery. Every browser viewer and receiving-device bridge is its own connection - plan sender upload for the bitrate multiplied by the number of simultaneous routes.

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 when 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 don't reuse access beyond the event it was made for.

Remote sources for vMix over the internet

Frequently Asked Questions

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

Workflow setup

Through a paired desktop device with an NDI, OMT, desktop or DeckLink source available to it. Create a stream and pick a viewer or Bridge Sharing destination pointed at your vMix machine.

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

Latency's usually in the hundreds of milliseconds rather than seconds, but no internet path is fixed - use wired connections and leave headroom where timing matters.

Monitoring & delivery

Set 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.

Yes, programme audio can travel with the source, with up to 16 channels available where the source supports it. Additional audio and return communication are set per viewer link.

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

Related workflows