Stream Bridge Stream Bridge

Convert OMT to WebRTC

Stream Bridge converts an OMT source into WebRTC, so it can reach a browser viewer or another paired device over the internet, while OMT discovery and the original media stay on your local network.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick an OMT source

    Any OMT source on your network: OBS, cameras, graphics or production feeds.

  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

OMT works the same way as any other Stream Bridge source. Install the desktop app, create a device on the dashboard, and enter the connection key. Once connected, any OMT sources the device can see are ready to convert into a stream.

One encoded stream can support client monitors, director feeds and device-to-device routes at the same time. Viewer links carry their own access, branding and audio, and Bridge Sharing can also place the same source into another production as NDI or OMT.

We negotiate the internet connection for every destination separately, preferring a direct route and falling back to cloud relay automatically when a site sits behind a restrictive network.

Once live, the app keeps tracking source state, device load and connection health, managing buffering and recovery continuously so the feed stays usable for real-time viewing.

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

A closer look at source handling, production audio, encoding performance, delivery quality, networking, and access control.

Supported Sources

OMT sources on the paired device.

Explore details

Stream Bridge works with OMT audio and video sources the paired device can see - OBS OMT outputs and most other OMT-compatible systems on your local network.

The source needs to stay active and reachable by the paired device. Discovery can take around 30 seconds, and local-sources-only filtering helps on a busy network.

Audio

Up to 16 channels come through with the source.

Explore details

Stream Bridge can capture up to 16 audio channels from an OMT source and deliver them as individually controllable tracks in the browser.

Viewer links can include additional audio sources with independent level controls, and Audio Return or Group Audio can be switched on separately when the remote person needs to speak back.

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.

Default limits are four simultaneous GPU encodes and two CPU encodes per device. Use the CPU/GPU meters to raise those cautiously and catch overload before it turns into dropped frames.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

OMT source discovery stays local - Stream Bridge only handles the internet-facing WebRTC connection. Every viewer is a separate connection, and your bitrate applies per viewer, so two people at 5Mbps needs about 10Mbps upload.

Bitrate changes apply live. A reasonable starting point is 3-5Mbps for most 1080p30 feeds, and 5-10Mbps for high-motion or 60fps content, depending on the weakest connection in the chain.

Networking

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

Explore details

No VPN or inbound port forwarding is needed. Stream Bridge uses ICE to find a workable path between the sending device and each viewer or receiver, preferring a direct connection.

If strict NAT or firewall rules get in the way, the session falls back to our TURN network automatically. That improves reachability, though the extra hop can add latency, so wired connections and sensible bitrate headroom still matter.

Security & Customisation

Separate links, passwords and named outputs per audience.

Explore details

Viewer links can use readable custom URLs, optional passwords and player customisation, letting a client, director, operator and internal team each get different controls from the same stream.

Treat device connection keys and viewer links as credentials. Keep connection keys private, password sensitive feeds, and remove links or bridges once an audience no longer needs access.

Convert OMT to WebRTC

Frequently Asked Questions

Practical answers about setup, delivery, quality, audio, bandwidth, and reliability for this Stream Bridge workflow.

Setup & sources

Through a paired desktop device. Make sure OMT discovery is switched on in Device Settings and the source is available to the app, then create a stream and pick a viewer or Bridge Sharing destination.

Just a browser - Chrome, Firefox, Edge or Safari. Chrome's the most reliable for WebRTC, and nothing needs installing at their end.

Many connections land under 500ms end to end. Fibre-to-fibre direct routes with NVENC can be faster; distance, Wi-Fi, congestion, CPU encoding or TURN relay can all add delay.

Delivery & performance

Allow at least your configured bitrate for every simultaneous viewer or bridge route, plus headroom. Three independent 5Mbps connections need roughly 15Mbps of stable upload before overhead.

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

Stream Bridge falls back to its TURN relay network automatically. If a source or receiving device goes offline, configured bridges wait and reconnect once it's back.

Related workflows

Stream OMT to a web browser Convert OMT to remote NDI Convert DeckLink / SDI to WebRTC Convert NDI to WebRTC