How to Set Up NDI
From your first NDI source to a full multi-camera IP production — network requirements, encoders, decoders, software setup, managed switch configuration and troubleshooting.
In this guide
What Is NDI?
NDI (Network Device Interface) is a royalty-free standard developed by NewTek for sending professional video over a standard Ethernet network. Instead of running separate HDMI or SDI cables from each camera to a production system, NDI cameras and encoders send their video over the same network infrastructure already in place — Cat 6 cable, Gigabit switches, the same network your computers and phones use.
In a traditional production, every camera needs its own physical cable run to a central router or production switcher. With NDI, a camera connected to a network port anywhere in a building is immediately visible on every other NDI-capable device on that network — instantly, automatically, without any patching.
Full NDI, NDI|HX and NDI|HX2
There are three NDI variants. Choosing the right one depends on your network capacity and latency requirements.
Full NDI
Visually lossless SpeedHQ compression. One-frame latency. For local LAN production where bandwidth is not a constraint.
NDI|HX2
H.264 or H.265 compression. 2–3 frame latency. High quality at much lower bandwidth. For bandwidth-constrained networks.
NDI|HX
H.264 compression. 3–5 frame latency. Lowest bandwidth NDI. For Wi-Fi sources or networks with many simultaneous streams.
Bandwidth planning — how many NDI streams can your network carry?
| NDI Type | Bandwidth per 1080p60 stream | Streams on 1 Gbps switch | Typical use |
|---|---|---|---|
| Full NDI | ~125 Mbps | 7–8 streams | Studio, fixed installations |
| NDI|HX2 | 20–40 Mbps | 25–45 streams | Multi-camera productions, venues |
| NDI|HX | 8–15 Mbps | 65–120 streams | Wi-Fi sources, large scale |
| Full NDI (4K60) | ~250–400 Mbps | 2–3 streams | 4K production (10 GbE recommended) |
⚠️ 4K NDI note: Full NDI at 4K requires 250–400 Mbps per stream — this saturates a Gigabit connection with just 2–3 sources. For 4K NDI productions with multiple cameras, a 10 Gigabit Ethernet infrastructure is strongly recommended, or use NDI|HX2 at 4K which runs at approximately 50–80 Mbps per stream.
Network Requirements
Switch requirements
- Minimum: Gigabit unmanaged switch — for small setups of 1–6 NDI sources. Any Gigabit switch works for basic NDI on a flat network.
- Recommended: Managed Gigabit switch with IGMP snooping — for 7+ NDI sources. Full NDI is multicast by default; without IGMP snooping, multicast floods all switch ports and saturates bandwidth even on unused ports.
- Enterprise: 10 GbE for 4K NDI — 10 Gigabit switches and NICs for 4K Full NDI multi-camera production.
Recommended switches for NDI
- Netgear GS308E / GS316E — affordable managed Gigabit switches with IGMP snooping. Good for small to medium NDI setups.
- TP-Link TL-SG108E / TL-SG116E — easy-to-configure managed switches suitable for NDI with IGMP snooping.
- Cisco SG350 series — enterprise-grade managed switches for larger broadcast NDI installations.
- Netgear M4250 AV Line — purpose-built AV-over-IP switches preconfigured for NDI, SDVoE and AV production networks.
Cabling
- Cat 5e minimum — supports Gigabit at up to 100m runs.
- Cat 6 recommended — better crosstalk rejection, more reliable at full Gigabit speeds, essential for 10 GbE.
- Cat 6A for 10 GbE — required for 10 Gigabit over distances above 55m.
IP addressing and subnets
NDI uses mDNS (multicast DNS) for automatic source discovery — all NDI devices must be on the same IP subnet. A single flat network (e.g. 192.168.1.x with a /24 subnet mask) is the simplest configuration and works for most productions.
⚠️ VLANs and managed switches: If your network uses VLANs, NDI sources and receivers on different VLANs cannot see each other by default. mDNS does not cross VLAN boundaries without an mDNS repeater or proxy. For NDI across VLANs, configure your managed switch to forward mDNS between the relevant VLANs, or use a dedicated NDI VLAN for all production devices.
Firewalls and Windows Defender
NDI uses TCP port 5960 (discovery) and dynamic UDP ports for video. Windows Defender Firewall may block NDI on first use — when prompted, allow access on both private and public networks for NDI applications. If sources are not visible, temporarily disable the firewall to test, then add NDI as a firewall exception.
Step-by-Step NDI Setup
-
1
Verify your network switch is Gigabit
Check the switch specification — it must state Gigabit (1000 Mbps / 1 Gbps). 100 Mbps (Fast Ethernet) switches cannot carry even a single Full NDI 1080p60 stream. Most switches purchased in the last 5 years are Gigabit, but older office and venue infrastructure may still have 100 Mbps switches. Replace any 100 Mbps switches with Gigabit before proceeding.
-
2
Connect all NDI devices to the same network
Connect all cameras, encoders, production computers and monitoring devices to the same Gigabit switch via Ethernet. Assign static IP addresses for hardware devices (encoders, decoders) so they are always reachable. Production computers can use DHCP. All devices must be on the same subnet (e.g. all on 192.168.1.x).
-
3
Download and install NDI Tools
Download the free NDI Tools package from ndi.video. Install on all Windows and Mac production computers. NDI Tools includes NDI Studio Monitor (view any NDI source), NDI Test Patterns (generate test NDI sources), NDI Scan Converter (output your PC screen as NDI) and NDI Bridge (send NDI over internet). Install and open NDI Studio Monitor — if NDI sources appear here, your network is working.
-
4
Create your first NDI source
Options — choose the most appropriate for your setup: (a) Hardware encoder — plug a Magewell Pro Convert HDMI Plus into your switch and a camera into its HDMI input; the camera immediately appears as an NDI source on the network; (b) PC screen — NDI Scan Converter (included in NDI Tools) outputs your PC screen as an NDI source instantly; (c) vMix or OBS — enable NDI output from vMix or install the OBS-NDI plugin to make software outputs visible as NDI sources.
-
5
Verify the source in NDI Studio Monitor
Open NDI Studio Monitor on any computer on the same network. Click the source name in the list — the video should appear within 1–2 seconds. If the source does not appear, see the troubleshooting section. NDI Studio Monitor is the fastest way to confirm an NDI source is working before adding it to production software.
-
6
Add the source to OBS, vMix or your production software
OBS: install the obs-ndi plugin → Sources → + → NDI Source → select from dropdown. vMix: Add Input → NDI / Desktop Capture → select source. Wirecast: Shot Layer → + → NDI Source. Sources appear by name — typically "Device Name (Source Name)", e.g. "MAGEWELL-001 (CAM 1)".
-
7
Add hardware decoders for physical monitor outputs
For NDI video to appear on a physical display (confidence monitor, director screen, HDMI output to a projector), use a Magewell Pro Convert NDI to HDMI decoder. Connect it to your switch and a display — configure the NDI source in its web interface and the selected NDI stream appears on the HDMI output. No PC needed for monitor feeds.
-
8
Enable IGMP snooping if using 7+ sources
On a managed switch, enable IGMP snooping to prevent Full NDI multicast traffic from flooding all switch ports. Without it, a 7-source Full NDI network can saturate all ports regardless of which sources are being viewed. This is the single most important managed switch configuration for larger NDI setups. IGMP snooping is in the switch's management interface under Multicast or IGMP settings.
How to Create NDI Sources
An NDI source is any device or software that sends video over the network in NDI format. Here are the main ways to create NDI sources from cameras and other equipment.
Hardware NDI encoders (cameras without NDI output)
Most cameras output HDMI or SDI, not NDI. A hardware encoder converts that signal to NDI on the network. Connect the camera HDMI or SDI output to the encoder input, and the encoder sends NDI to the switch. The camera immediately appears on the network without any configuration on the receiving devices.
NDI-native cameras
Some PTZ cameras include built-in NDI output — BirdDog cameras are the leading example, outputting Full NDI natively via their Ethernet port with no additional encoder needed. Connect a BirdDog camera to a PoE switch port and it appears immediately as an NDI source. PTZOptics cameras also support NDI. These are the cleanest NDI source as no additional hardware is required per camera.
Software NDI output
- vMix — enable NDI output in Settings → NDI/Output → External Output. The programme mix, preview and individual inputs can all be output as separate NDI streams.
- OBS Studio — install obs-ndi plugin → Tools → NDI Output Settings → enable Main Output. OBS programme output becomes an NDI source on the network.
- NDI Scan Converter — included in NDI Tools, converts your PC display to an NDI source. Useful for presentation computers, score graphics and replay system outputs.
- Microsoft Teams / Zoom — NDI output is available in Teams (enable in settings) and Zoom (Pro accounts) — useful for feeding remote participants as NDI sources into production software.
NDI encoders from other brands
Kiloview NDI encoders, Epiphan Pearl encoders and Magewell Ultra Encode devices all output NDI alongside SRT and RTMP simultaneously — a single device can feed both the NDI production network and an internet stream at the same time.
Receiving NDI in Production Software
OBS Studio (free)
Requires the free obs-ndi plugin. After installation, NDI sources appear as a source type in the Add Source menu. OBS can simultaneously receive multiple NDI sources as separate scene sources. OBS can also output its programme mix as NDI for other applications to receive.
vMix (paid)
Native NDI support — no plugin required. Add Input → NDI / Desktop Capture. vMix is the most NDI-capable software production system, supporting hundreds of simultaneous NDI inputs on high-specification PCs. Full PTZ camera control via NDI is available in vMix for BirdDog and compatible PTZ cameras.
Wirecast
Native NDI support. Shot Layer → + → NDI Source. Wirecast is widely used in houses of worship and corporate events as an alternative to vMix.
Hardware NDI decoders
For physical signal outputs (HDMI to a monitor, SDI to broadcast infrastructure), hardware decoders receive NDI from the network and output a physical signal. No PC required. Magewell Pro Convert decoders are the professional standard for this workflow.
Who Uses NDI and Why
Houses of Worship
NDI eliminates long camera cable runs across large sanctuaries. PTZ cameras at any network port feed vMix or Wirecast instantly for live streaming and IMAG.
Broadcast Facilities
IP production replacing SDI infrastructure. NDI cameras and encoders on a network core replace SDI routing switchers for flexible, software-defined signal routing.
Universities & Education
Lecture capture, distance learning and campus productions. NDI sources from multiple rooms feed a central production system over the campus network.
Corporate AV
Boardroom cameras, conference room AV and corporate broadcast studios connected via NDI to central production systems for company-wide streaming.
Sports Production
Multi-camera sports coverage with NDI cameras around a venue feeding a production system over the venue network. Faster to deploy than SDI infrastructure.
Live Events & Concerts
Temporary NDI networks deployed at events — plug cameras into venue network ports and they appear immediately in the production system anywhere on site.
Medical & Healthcare
Surgical cameras and imaging equipment distributed over hospital networks as NDI sources for clinical communication, telemedicine and medical education.
Defence & Government
Secure facility video distribution over controlled networks. NDI over classified networks replaces physical routing infrastructure for command and control facilities.
Theatre & Performing Arts
Stage cameras, IMAG displays and monitoring distributed over venue networks. NDI replaces complex SDI cable runs between stage, FOH and technical areas.
Recommended NDI Products
HDMI to NDI encoders (camera → network)
Pro Convert HDMI Plus
Compact HDMI to Full NDI encoder. Plug in any HDMI camera — appears on the network in seconds. Fanless, PoE powered. From £383 ex-VAT.
Pro Convert HDMI 4K Plus
4K HDMI 2.0 to Full NDI. For 4K cameras in NDI productions. Fanless, PoE powered. From £665 ex-VAT.
Pro Convert HDMI TX
Ultra-compact HDMI to NDI. Mounts directly at camera outputs. PoE powered via a single Ethernet cable. From £323 ex-VAT.
SDI to NDI encoders (broadcast cameras)
Pro Convert SDI Plus
3G-SDI to Full NDI. Integrate broadcast SDI cameras into NDI networks. Fanless, PoE powered. From £412 ex-VAT.
Pro Convert 12G SDI 4K Plus
12G-SDI 4K to Full NDI. For Sony VENICE, Arri Alexa and top broadcast cameras. PoE powered. From £693 ex-VAT.
NDI Encoders
Kiloview HDMI and SDI to NDI encoders with additional SRT and RTMP outputs. Full range including rack-mount models for fixed installations.
NDI-native cameras (no encoder needed)
Full NDI PTZ Cameras
PTZ cameras with Full NDI output built-in. Connect to a PoE switch port — appears on the network immediately. Pan, tilt, zoom control via NDI. Full range available.
Pearl Encoders
Professional rack-mount encoders with NDI output. Multiple HDMI and SDI inputs, recording, streaming and NDI in one device for broadcast facilities.
NDI decoders (network → HDMI/SDI outputs)
Pro Convert NDI to HDMI
Receive any NDI source and output to HDMI display. Auto-discovers sources. PoE powered — one cable to each display. From £370 ex-VAT.
Pro Convert NDI to AIO
NDI to simultaneous HDMI, SDI and analogue outputs. One device feeds multiple output formats from a single NDI source. From £338 ex-VAT.
Pro Convert NDI to HDMI 4K
Receive 4K NDI sources and output to HDMI 2.0 4K displays. For 4K monitoring infrastructure. PoE powered. From £709 ex-VAT.
Multi-camera NDI production systems
Director Mini
All-in-one production: 4 HDMI inputs + IP/NDI sources. Live switching, graphics, streaming. Standalone — no PC required. From £799 ex-VAT.
HDMI & USB Converters
Inogeni capture and conversion devices for integrating physical signals into NDI and USB workflows. Broadcast-grade quality.
Troubleshooting NDI Issues
❌ NDI source not appearing in OBS, vMix or NDI Studio Monitor
Step 1 — Check they are on the same subnet. The source and receiver must have IP addresses in the same range (e.g. both on 192.168.1.x). Open a command prompt and run ipconfig on both devices and compare. Step 2 — Check the firewall. Temporarily disable Windows Defender Firewall on the receiving PC and retry. If the source appears, add NDI as a firewall exception. Step 3 — Check for a VPN. Any active VPN on the receiving PC reroutes network traffic and blocks mDNS discovery. Disable the VPN when using NDI on a local network.
📉 NDI stream choppy, dropping frames or freezing
Almost certainly a network bandwidth issue. Check your switch is genuinely Gigabit — connect a PC to the same switch and run a speed test between two computers (using iperf3) to confirm actual throughput. Check for packet loss using ping -t [encoder IP] — any lost packets indicate a network problem. Check cables are Cat 5e or better with clean terminations. For 7+ Full NDI sources, enable IGMP snooping on a managed switch to prevent multicast flooding.
⏱ NDI video is delayed — latency is too high
Full NDI latency is approximately one frame (16ms at 60fps). If you are experiencing 3–5 frame delay, you are likely receiving NDI|HX rather than Full NDI — check the encoder output settings and switch to Full NDI if bandwidth permits. Additional latency can come from the receiving software buffer — in OBS, reduce the NDI source buffer setting in the NDI plugin options. vMix has a dedicated low-latency NDI mode in the input settings.
🌐 NDI works on one VLAN but not across VLANs
mDNS does not cross VLAN boundaries by default. Solutions: (1) put all NDI devices on a single dedicated VLAN; (2) configure your managed switch or router to forward mDNS traffic between production VLANs — this is called mDNS proxying or Bonjour forwarding; (3) use NDI Access Manager (in NDI Tools) to manually specify source IP addresses when automatic discovery fails. For complex enterprise networks, consult your network team about multicast routing between subnets.
🖥️ NDI source appears but image is black or shows wrong colours
The NDI source is being received but the image data is incorrect. Check: (1) the hardware encoder has a valid signal on its input — if the source camera is off or on standby, many encoders output a black NDI stream rather than no stream; (2) colour space mismatch — in OBS NDI source properties, check the colour space and range settings match the source; (3) the encoder is outputting at a resolution your production software does not support — check encoder and production software are set to the same resolution.
📡 NDI stops working when more sources are added
Network saturation from Full NDI multicast flooding. This is the most common issue when scaling beyond 7–8 sources. Enable IGMP snooping on your switch to contain multicast traffic. If you do not have a managed switch, upgrade to one — this is non-negotiable for productions with more than 6 Full NDI sources. Consider switching some sources to NDI|HX2 to reduce per-stream bandwidth.
Need help with your NDI setup?
From first-time NDI network design to troubleshooting complex multi-VLAN installations, our technical team can advise on the right hardware and configuration for your specific environment.
Contact Technical SupportFrequently Asked Questions
How much bandwidth does NDI use?
Full NDI uses approximately 125 Mbps per 1080p60 stream. NDI|HX2 uses 20–40 Mbps. NDI|HX uses 8–15 Mbps. On a Gigabit network you can run 7–8 simultaneous Full NDI streams, or 25–45 NDI|HX2 streams. For 4K Full NDI, expect 250–400 Mbps per stream — a 10 Gigabit network is recommended for multiple 4K sources.
Does NDI work over Wi-Fi?
NDI|HX and NDI|HX2 can work over strong 5 GHz Wi-Fi 6. Full NDI at 125 Mbps per stream is generally too demanding for reliable Wi-Fi operation. For professional production always use wired Gigabit Ethernet for NDI sources. Wi-Fi is acceptable for monitoring and control applications using NDI|HX.
Why can I not see my NDI source in OBS?
Most common causes: different network subnets (devices must be on the same subnet); Windows Firewall blocking NDI traffic; an active VPN on the PC rerouting traffic; the obs-ndi plugin is not installed or is an incompatible version; the NDI source application is not running or NDI output is not enabled. Test in NDI Studio Monitor first — if the source appears there, the network is working and the issue is specific to OBS or the plugin.
What is the difference between Full NDI, NDI|HX and NDI|HX2?
Full NDI: visually lossless SpeedHQ compression, ~125 Mbps at 1080p60, one-frame latency. NDI|HX2: H.264/H.265, 20–40 Mbps, 2–3 frame latency, high quality. NDI|HX: H.264, 8–15 Mbps, 3–5 frame latency, lowest bandwidth. For local network production with sufficient bandwidth, use Full NDI. Use NDI|HX2 for bandwidth-constrained networks or large numbers of simultaneous sources.
Can NDI work between different buildings or over the internet?
NDI is designed for LAN use. For multi-site NDI: use a site-to-site VPN to connect two LANs (NDI then works as normal between sites); use NDI Bridge (free in NDI Tools) for point-to-point internet NDI tunnels; or convert NDI to SRT at each site using Magewell Pro Convert encoders and decode SRT back to NDI at the destination.
Do I need a managed switch for NDI?
For small setups (up to 6 Full NDI sources): an unmanaged Gigabit switch works fine. For 7+ sources: a managed switch with IGMP snooping is essential. Without IGMP snooping, Full NDI multicast floods all switch ports regardless of whether a source is being viewed, which saturates available bandwidth. NDI|HX2 sources are less affected as they use unicast delivery.
Is NDI free?
NDI runtime and NDI Tools are free from ndi.video. The OBS NDI plugin is free. vMix includes NDI natively. Magewell Pro Convert hardware includes NDI licences. BirdDog cameras include NDI licences. Some third-party devices may require a paid NDI licence — check the product specifications.
Can NDI and SDI coexist in the same production?
Yes — this is one of the most common real-world scenarios. Use NDI encoders (Magewell Pro Convert, Kiloview) to bring SDI cameras onto the NDI network, and NDI decoders (Magewell Pro Convert NDI to SDI) to send NDI signals out to SDI monitoring and recording infrastructure. A hybrid NDI/SDI facility can transition incrementally without replacing all SDI equipment at once.