A camera feed drops just as a presenter starts speaking. The camera is powered on, the NDI source is visible, and the network looks connected - but the live switcher cannot hold a clean feed. This is why the question “does NDI require ethernet” matters before a multi-camera workflow is installed, not after a production has started.

The short answer is no: NDI does not strictly require a physical Ethernet cable. NDI is a video-over-IP technology, so it needs an IP network. That network can be wired Ethernet or Wi-Fi. In professional livestreaming, conferencing, worship, education, and event production, however, wired Ethernet is usually the correct choice because it provides the throughput, stability, and predictable latency that live video requires.

Does NDI Require Ethernet, or Just a Network?

NDI sends video, audio, control data, and metadata across a network. A compatible camera, computer, encoder, switcher, or decoder joins the same network and makes its NDI stream available to other devices. The network is the requirement. Ethernet is the preferred transport for most production systems.

This distinction is useful because Ethernet can mean two different things. It can mean a standard wired network connection through an RJ45 port and Cat5e, Cat6, or better cable. It can also be used casually to describe local networking in general. NDI works over standard IP networking, but its performance depends heavily on how that network is built.

A camera with built-in NDI can send its feed through a wired LAN connection to a production computer running NDI software, an NDI-capable hardware switcher, or a decoder connected to a display. The same cable may also carry power when the camera and network switch support Power over Ethernet, or PoE. That can reduce installation complexity by providing camera power, video transport, audio, and PTZ control through one cable.

Why Wired Ethernet Is the Professional Standard

Live production is less forgiving than casual video viewing. A short network interruption can cause a frozen frame, audio interruption, delayed camera control, or a source that disappears from the switcher. Wired Ethernet avoids many of the variables that make Wi-Fi difficult to trust under pressure.

A Gigabit Ethernet connection is the baseline for most NDI installations. It gives multiple devices enough capacity to carry video streams while leaving room for control traffic, computers, network storage, internet access, and monitoring. For larger 4K systems, several high-bitrate sources, or facilities with multiple production spaces, 2.5GbE or 10GbE uplinks may be appropriate.

Wired connections also provide consistent latency. NDI is designed for low-latency production, but the total delay still reflects the camera, codec, network, receiving device, and display path. A congested or unstable wireless connection adds variation to that chain. In a live panel discussion, that variation can make camera cuts feel late and can complicate audio synchronization.

Physical connections are also easier to diagnose. A link light, switch port status, cable test, and network settings provide clear starting points when a source is unavailable. Wi-Fi adds radio interference, signal range, access-point capacity, roaming behavior, and competing devices to the troubleshooting process.

Can NDI Work Over Wi-Fi?

Yes. An NDI source can operate over Wi-Fi if the sending and receiving devices are on a network that allows them to communicate. This can be useful for testing, temporary setups, mobile production carts, or a single low-demand camera feed where running cable is not possible.

The practical question is not whether Wi-Fi can carry NDI. It is whether the wireless network can carry the required video traffic continuously, at the needed quality and latency, without affecting the rest of the production. A strong Wi-Fi signal alone does not answer that question.

High-quality NDI video can use substantial bandwidth, particularly at higher resolutions and frame rates. A 4K source requires far more network capacity than a basic webcam feed. Wireless performance is shared among connected devices and changes with distance, walls, radio congestion, and activity from phones, laptops, and guest networks.

If Wi-Fi is unavoidable, use a dedicated modern access point, keep the camera or computer close to it, limit competing traffic, and test under real production conditions. Do not judge reliability from a short preview. Run the expected camera count, frame rate, graphics, audio, and recording load for an extended period before using the setup for a client presentation or live event.

NDI High Bandwidth vs. NDI|HX

The type of NDI implementation affects network planning. Full-bandwidth NDI, sometimes called NDI High Bandwidth, prioritizes image quality and low latency while using more network capacity. It is well suited to fixed production networks with wired Gigabit Ethernet and multiple camera sources.

NDI|HX uses more compressed video, commonly based on H.264 or H.265. It requires less bandwidth and can be a practical choice for compact installations, remote contributions, or networks where capacity is limited. The trade-off is that compression and encoding can add latency and may place different demands on receiving hardware or software.

Neither version removes the need for a well-planned network. NDI|HX may make a wireless or lower-capacity environment more workable, but it does not make a weak Wi-Fi connection production-ready. Check the exact camera, switcher, decoder, and software specifications before building the workflow. Compatibility with NDI, NDI|HX, resolution, frame rate, and control functions can vary by model.

Build the Network Around the Camera Count

For a simple two-camera setup, a Gigabit router or switch with wired connections may be all that is needed. Connect each NDI camera and the production computer or NDI switcher to the same Gigabit switch. Use quality Cat5e or Cat6 cable, assign sensible device names, and confirm that every source appears before the event begins.

As the system grows, separate production traffic from general office or venue traffic where possible. A dedicated switch or VLAN helps prevent file transfers, guest Wi-Fi usage, and unrelated computers from competing with camera streams. Fixed IP addresses or DHCP reservations can make camera management easier, especially when the same devices are used repeatedly.

For larger installations, select managed network switches with adequate backplane capacity and uplink speed. Multicast may be useful when one NDI source must be received by many destinations, but it needs correct switch configuration. Features such as IGMP snooping help control multicast traffic rather than flooding it across every port. This is a network design decision, not a setting to enable without understanding the workflow.

PoE planning also matters. A PoE switch can simplify an AI PTZ camera installation, but every powered camera draws from the switch’s total PoE budget. Verify the power requirement per device and the total available wattage, especially when adding cameras, converters, or wireless access points.

A Practical NDI Ethernet Setup

A dependable compact workflow often uses this path: NDI cameras connect by Ethernet to a Gigabit PoE switch; the switch connects to an NDI-capable production computer or live video switcher; and the switcher sends the program output to streaming, recording, displays, or conferencing platforms. PTZ control, tally, and camera discovery can remain on that same production network when supported.

Keep the production computer wired as well. A wired camera feeding a Wi-Fi laptop still introduces a wireless weak point at the receiving end. For 4K production, use a computer with sufficient CPU, GPU, storage performance, and network adapter capacity to decode, switch, record, and stream the number of sources you expect to use.

Before going live, test more than picture quality. Confirm that AI tracking, pan-tilt-zoom control, audio embedding, frame rate, source discovery, and switching behavior all work as intended. Watch network utilization during the test. If the network is already near capacity in rehearsal, it has no room for real-world changes during the event.

When Ethernet Is Not Available

There are valid cases where a cable cannot reach the camera position. A temporary stage, rented venue, historic building, or moving production setup may make Wi-Fi the only immediate option. In those cases, consider whether an HDMI or SDI connection to a nearby encoder, a dedicated wireless video system, or a local recorder is more appropriate than asking a shared wireless network to carry every critical feed.

For less critical uses, such as a secondary angle or an internal confidence monitor, Wi-Fi NDI may be acceptable after thorough testing. For the primary presenter camera, program output path, or a camera that must respond reliably to PTZ commands, wired Ethernet remains the safer investment.

The useful rule is simple: NDI needs an IP network, but professional NDI workflows should be designed around wired Ethernet whenever possible. A properly specified network lets AI cameras, PTZ control, video switching, and audio systems operate as one production environment instead of a collection of devices competing for bandwidth. When selecting NDI-ready cameras and switchers, Kong Kei customers should treat the network connection as part of the equipment specification, not an accessory to decide on later.