The broadcast industry has been talking about IP video for two decades. NDI — Network Device Interface — is the protocol that actually made it practical for everyone from tier-one broadcasters to a church AV volunteer running a single GigE cable to a camera. Developed by NewTek (now part of Vizrt Group) and first released in 2015, NDI lets any NDI-enabled device — cameras, switchers, graphics systems, capture cards, computers — discover each other automatically on a standard local area network and share broadcast-quality video with remarkably low latency and no proprietary hardware required.

If you've been handed a budget for an IP production upgrade, or you're simply trying to understand why every PTZ camera spec sheet now mentions NDI|HX3, this guide covers everything: the technology behind NDI, every version from 1.0 through 5.6, the difference between Full NDI and NDI|HX, network requirements, setup best practices, common pitfalls, and a curated look at the NDI cameras, converters, encoders, decoders, and switchers available at Coremicro today.

What Is NDI and How Does It Work?

NDI is an open, royalty-free software specification — not a physical cable standard like HDMI or SDI. It runs on top of standard TCP/IP networking and uses multicast DNS (mDNS / Bonjour) to let every NDI source on a network advertise itself automatically. When you plug an NDI-capable camera into the same switch as your vMix machine, TriCaster, or OBS instance, the camera shows up as a source automatically — no IP address entry, no manual routing.

Under the hood, NDI uses a proprietary lossy codec optimized for very high quality at moderate bit rates. On a gigabit LAN, a single 1080p60 stream typically consumes around 100–150 Mbit/s (Full NDI), meaning a single GigE uplink comfortably handles seven simultaneous 1080p60 sources. 4K60 streams run at around 250–400 Mbit/s, so a 10GbE network becomes advisable for multi-camera 4K environments. This efficiency is why the protocol requires approximately 90% less bandwidth than uncompressed SMPTE 2110 at equivalent 4K resolution.

NDI is more than a transport protocol. It is a full production infrastructure that includes:

• Auto-discovery via mDNS — sources appear in any NDI-aware application automatically within the same subnet.
• Tally signaling — cameras receive program/preview tally from the switcher over the same network connection, eliminating separate tally cable runs.
• PTZ control — standard PTZ pan, tilt, zoom, focus, and preset recall commands are transmitted back to cameras over the NDI connection.
• Bidirectional metadata — arbitrary XML metadata can accompany every frame, enabling use cases like timecode distribution, scripted lighting control, and live entertainment cue triggers.
• Multi-unicast and multicast — sources can serve an unlimited number of destinations; multicast mode reduces bandwidth when many receivers consume the same stream.
• Audio — up to 16 channels of floating-point audio (and beyond in newer SDKs) are embedded in each stream alongside video.

NDI Discovery Modes: LAN, Access, and Discovery Server

By default, NDI uses mDNS and operates within a single subnet. For larger or more complex facilities, two additional discovery modes extend NDI's reach:

• NDI Access — manually enter the IP address of a machine on another subnet. That machine's sources become visible across the network boundary. Useful for smaller multi-subnet facilities or remote offices.
• NDI Discovery Server — a dedicated server (or cloud instance) coordinates all NDI source registration and discovery across subnets without relying on mDNS. This is the recommended approach for large facilities, universities, and multi-campus deployments. NDI 4.0 formalized this capability; NDI 5 added redundant Discovery Server support for failover resilience.

NDI Version History: From 1.0 to 5.6 (2015–2026)

NDI has evolved significantly since launch. Understanding the version history helps explain why some devices support features others don't, and what your NDI Tools installation actually unlocks.

Full NDI vs. NDI|HX vs. NDI|HX2 vs. NDI|HX3 — What's the Difference?

This is the question that generates the most confusion among buyers. The short answer: there are now four distinct flavors of NDI, each with different codec, latency, bandwidth, and quality tradeoffs. The right choice depends entirely on your network and workflow.

Full NDI is the gold standard for wired studio environments. It uses an intraframe codec — every frame is independently compressed, with no inter-frame prediction — which means frame-accurate switching, lossless (perceptually) quality, and sub-frame latency. The tradeoff is bandwidth: each 1080p60 Full NDI stream uses roughly 100–150 Mbit/s, which is why it requires a solid wired GigE infrastructure.

NDI|HX variants use long-GOP inter-frame codecs (H.264 or H.265), which dramatically reduce bandwidth at the cost of latency and switching precision. HX3 with H.265 is the current sweet spot for camera-to-switcher workflows over both wired and wireless links — modern PoE-capable PTZ cameras like the AIDA Imaging UHD-NDI3 line, Datavideo PTC-325 series, and PTZOptics Move 4K all support HX3. The latency of 1–2 frames is acceptable for most live production scenarios but still makes Full NDI preferable for live IMAG (image magnification) applications where latency is visible to audience members looking from the stage to the screen.

Network Requirements for NDI — Infrastructure That Actually Works

NDI does not require exotic infrastructure, but it does require good infrastructure. A consumer-grade Wi-Fi router is not an NDI switch. Cheap unmanaged switches with inadequate buffers will produce dropped frames. Here is what a reliable NDI environment looks like:

Wired GigE (Full NDI Standard Environment)

• Standard Cat5e or Cat6 cabling to every NDI source and destination
• Managed GigE switch with IGMP snooping enabled (critical for multicast performance) and large packet buffers — typically 1 MB or more per port
• One GigE uplink per camera/source works for up to 7 simultaneous 1080p60 Full NDI streams on a single trunk
• For 4K environments, use a 10GbE core switch with GigE access ports; each 4K60 Full NDI stream needs approximately 250–400 Mbit/s
• Avoid consumer switches — look at purpose-built AV-over-IP switches like the Netgear AV Line M4250 NDI Managed Switch which are optimized for NDI traffic patterns

Wireless NDI (NDI|HX Environments)

• Use NDI|HX2 or NDI|HX3 exclusively on wireless — Full NDI will saturate a Wi-Fi channel
• Wi-Fi 6 (802.11ax) access points with dedicated SSIDs for production video traffic
• Separate production traffic onto its own VLAN/SSID away from guest or office traffic
• Band-steer all NDI devices to 5 GHz minimum; 6 GHz (Wi-Fi 6E) is preferred for 4K HX3 sources

Jumbo Frames

Enabling jumbo frames (MTU 9000) on your switch and all NDI devices can improve throughput efficiency — particularly for Full NDI on 10GbE core networks. This must be configured consistently across all devices in the path; mismatched MTU settings cause more problems than jumbo frames solve.

How to Set Up an NDI Workflow: Step-by-Step

NDI Use Cases: Who Uses NDI and How

Best NDI PTZ Cameras Available at Coremicro (2026)

The most visible category of NDI products is PTZ cameras. The range today spans from compact PoE POV cameras under $500 to 4K 30x zoom broadcast cameras exceeding $12,000. Below is a selection of current models across key price and performance tiers available through Coremicro.

Entry-Level NDI PTZ Cameras

Mid-Range NDI PTZ Cameras (1080p–4K)

Professional/Broadcast NDI PTZ Cameras

NDI Converters and Encoders: Bringing Existing Gear Into an NDI Workflow

You don't need to replace every camera to adopt NDI. NDI converters take SDI or HDMI signals from existing cameras, signal processors, or presentation computers and deliver them to your network as NDI streams. Similarly, NDI decoders convert NDI streams back to SDI or HDMI for monitors, traditional program outputs, or legacy infrastructure.

Entry-Level NDI Encoders and Decoders

Professional Bi-Directional NDI Converters

Broadcast-Grade NDI Converters

NDI Encoding Cards for Rack Systems

NDI-Native Switchers and Production Systems

NDI's biggest productivity advantage in a switcher is the elimination of video routing matrix infrastructure. An NDI-native switcher accepts NDI sources directly from the network — up to dozens simultaneously on modern systems — without dedicated SDI or HDMI input cards for each source.

NDI Players, Multiview, and Monitoring Tools

Beyond cameras and switchers, the NDI ecosystem includes a growing category of software and hardware tools for monitoring, multiview display walls, and NDI playback.

NDI and SRT: Complementary Protocols for Different Scenarios

A common point of confusion in modern live production is where NDI ends and SRT begins. They solve different problems and are increasingly used together in the same production chain.

NDI is a LAN protocol. It is optimized for low-latency, high-quality video transport within a facility over a managed Ethernet network. Its codec is intraframe (full NDI) or short-GOP (HX variants), it uses TCP or reliable UDP, and it is not designed for internet transport — latency spikes and packet loss on public internet connections are fundamentally incompatible with NDI's timing assumptions.

SRT (Secure Reliable Transport) is a WAN protocol. It uses adaptive bitrate, ARQ (automatic repeat request) for reliability, and AES encryption for security — all designed for the unpredictable conditions of internet video delivery. SRT handles the long-haul contribution path; NDI handles the local production environment.

The practical workflow that has become standard in modern live production is: cameras → NDI (local LAN) → NDI-native production switcher → SRT encoder → internet → SRT receiver → streaming platform or remote production hub. Several devices in Coremicro's catalog, like the AIDA HD3G-NDI-200 and Kiloview E1-S-NDI, output both NDI and SRT simultaneously, enabling hybrid local/remote workflows from a single camera without additional devices.

For a deep dive into SRT, read our Complete Guide to SRT Protocol.

Common NDI Mistakes and How to Avoid Them

• Using consumer switches: Unmanaged or consumer-grade switches frequently drop NDI frames under load due to small packet buffers. Always use a managed switch with large buffers and IGMP snooping enabled.
• Confusing NDI|HX3 with Full NDI capabilities: NDI|HX3 is significantly improved over HX1, but it is still an inter-frame codec. It is not appropriate for frame-accurate switching or live IMAG where latency matters to the audience.
• Ignoring cross-subnet discovery: mDNS does not cross VLANs or subnets by default. If your cameras and production computer are on different network segments, configure NDI Access or deploy an NDI Discovery Server.
• Overloading a single GigE uplink: Seven 1080p60 Full NDI streams fit comfortably on GigE. Eight or more — especially at 4K — require 10GbE uplinks or a dedicated NDI network segment.
• Not updating firmware: NDI version support is often unlocked or improved through firmware updates. Many cameras that shipped with NDI|HX1 have received HX3 support via firmware. Always check manufacturer firmware release notes.
• Mixing NDI Bridge versions below 5.6: All NDI Bridge nodes in a WAN setup must run NDI 5.6 or later to use TLS 1.3 encryption. A single older node in the chain forces the entire session to negotiate down.
• Buying NDI|HX without a license: Some products require a separate NDI license activation (sold by OBSBOT and others). Confirm whether NDI is included or must be activated before purchasing.

Frequently Asked Questions About NDI

Conclusion: NDI in 2026 Is the Foundation of Modern Live Production

NDI has moved from an interesting protocol to the underpinning infrastructure of live video production at every scale. A house of worship with a single PoE PTZ camera and a laptop running vMix and a broadcaster running 44 NDI sources into a TriCaster Vizion are both running the same protocol — the difference is only in the scale of the network and the hardware connected to it.

The current state of the art is NDI|HX3 for cameras and edge devices, Full NDI for wired studio workflows and production software, and NDI Bridge with TLS 1.3 for any cross-WAN contribution that needs to stay in the NDI ecosystem before hitting an SRT encoder for the final internet hop. If you're building a new facility or upgrading an existing one, designing around NDI from day one eliminates a significant proportion of the physical infrastructure cost and operational complexity of traditional SDI routing.

Coremicro carries a complete range of NDI cameras, converters, encoders, decoders, managed network switches, and production switchers — all the components you need to build or expand an NDI production environment, backed by expert pre-sales support from our team in Fremont, CA.

Explore our full range of NDI products, read our related guides on vMix capture cards and the SRT protocol, and reach out to Coremicro if you need help designing a system for your specific venue and workflow.