← All guides

Guide · NDI® OUT · Web Pro

Send LumaDeck Web to OBS, vMix or Resolume with NDI

16 August 2026 · 6 min read

This is not a disguised browser window and it is not screen capture. LumaDeck Output Bridge turns the Web Pro visual master into a native NDI video source on your local network.

Leer en español →

Download the local bridge

The bridge includes its own execution runtime, so it does not depend on a separate Node.js installation. It deliberately does not hide or repackage NDI Tools: the official NDI Runtime remains a separate prerequisite.

• Windows 10/11 · x64 installer
• Linux · x64 installer
• macOS · Apple Silicon package
• macOS · Intel package

Linux: after downloading, run chmod +x LumaDeck-Output-Bridge-0.1.0-linux-x64.run and then ./LumaDeck-Output-Bridge-0.1.0-linux-x64.run.

Unsigned preview: these first packages are not code-signed. Windows SmartScreen or macOS Gatekeeper may therefore show a security warning. Signing will be added later; it does not change how the source works.

The complete signal path

1. Install the official NDI runtime for the computer: Tools/Runtime on Windows/macOS, or libndi from the SDK on Linux.
2. Install and open LumaDeck Output Bridge. It binds only to 127.0.0.1:5960, not to a public or LAN control address.
3. Open LumaDeck in desktop Chrome and sign in with an active Web Pro account.
4. In the Master, press NDI OUT. Choose the source name, resolution and frame rate, then start the output.
5. In OBS, vMix, Resolume or another compatible receiver, add an NDI input and select the source name you chose.

OBS normally needs an NDI-compatible input plugin; other applications may expose NDI differently. LumaDeck publishes one standard source rather than maintaining a separate proprietary connector for every receiver. If the receiving software supports the same NDI generation and discovers the source on the network, it can use that source. Test the exact receiver version and network before a show.

Resolution, frame rate and sound

The current Web control publishes video only at 960 × 540, 1280 × 720 or 1920 × 1080, with 25 or 30 fps options. Full HD at 30 fps still moves and converts substantially more pixel data than 720p. Start at 720p/30 on unfamiliar hardware, verify the full chain, then raise the resolution.

Audio is not embedded in this first NDI OUT release. Route the booth or program audio directly into the receiving application and synchronize it there.

Compatibility and setup notes

The bridge route has completed end-to-end reception with OBS on Linux KDE and Windows 10. Linux has received the LumaDeck source at 1280 × 720/30 and 1920 × 1080/30; Stop→Start and opening OBS after NDI OUT was already live both recovered the source.

Windows needs the official NDI Runtime and OBS needs an NDI input plugin: without either piece, there is no source to publish or receiver entry to select. Other receivers expose NDI through their own version and configuration, so use the same setup checklist before a show. The macOS packages remain unsigned previews.

What stays local

The browser hands frames to the bridge through the IPv4 loopback interface. LumaDeck does not upload those frames to its servers. The bridge then publishes the NDI video source on your local network, where your chosen receiver can discover it. Authorization is checked against Web Pro, but the video path itself remains local.

If the source does not appear

• Confirm that the bridge is open and its local health service is running.
• Confirm that the official NDI Runtime is installed; reinstall or restart the bridge after adding it.
• Use the same local network profile and allow the sender and receiver through the operating system firewall.
• Confirm that the receiver really has NDI input support enabled.
• Try 720p/30 first and use a short, unique source name.