NDI output lets OBS send its programme picture and sound across your network to another NDI-compatible application or device. For a current OBS setup, start with DistroAV, the third-party plugin identified by NDI for OBS workflows, then check its release requirements before installing it.
The important distinction is direction: NDI Output sends from OBS; NDI Source brings a feed into OBS. If a menu is missing, an older OBS-NDI guide or an incompatible plugin build may be the reason, rather than a setting you have overlooked.
What NDI output in OBS does
NDI is a way to carry audio and video over an IP network. When DistroAV's NDI Output is enabled, it sends OBS's main programme view for another NDI receiver to discover and use. That can be useful when a second computer handles recording, projection, switching, or another part of a production while OBS builds the composed programme.
Think of OBS as the point where your scenes, sources, overlays, and audio are assembled. The NDI output is a network hand-off of that finished programme. A receiving application still needs to be configured to find and receive it, and both ends need a working network path. Installing a plugin does not by itself prove that the receiving device can see the output.
For a small devotional channel, for example, OBS might combine a bhajan video, a title graphic, and a microphone before sending the result to a second computer in the same production space. NDI can avoid treating that feed as a conventional capture-card connection, but it does not remove the need to test picture, sound, and discovery at the receiving end.
NDI output is not the same thing as sending your OBS programme to YouTube. If your aim is to publish a live broadcast, OBS still needs to stream to YouTube using the channel's live setup. NDI is a local network workflow between compatible devices or applications, not a replacement for YouTube's ingest connection.
DistroAV: the current OBS NDI plugin
NDI's current OBS documentation says it does not provide an official OBS plugin and points users to DistroAV, formerly known as OBS-NDI. That distinction matters: DistroAV is a third-party OBS plugin, not a built-in feature maintained as part of OBS Studio. Its OBS Project resource listing describes the plugin's audio and video input and output role.
DistroAV exposes three different workflows. NDI Output sends the main OBS programme view. NDI Source adds an incoming NDI feed as a source in an OBS scene. NDI Filter sends a selected parent source or scene to NDI, rather than the complete programme output. The filter's audio support is limited to particular source types, so check its current resource notes if you need audio as well as video.
If you are following a guide that says to install OBS-NDI, check when it was written and which release it describes. The project was renamed, and DistroAV's update notes say that moving to its 6.x line requires removing the older OBS-NDI plugin first. The same notes say settings are transferred automatically in that move, but still use the current project instructions for your own version rather than assuming an old installation procedure remains valid.
Check OBS, DistroAV, and NDI compatibility
Before downloading anything, note your OBS Studio version, operating system, and whether your installation is 64-bit. Then compare those details with the requirements on the current DistroAV listing and release notes. Compatibility can change between plugin releases, so an old recommendation may no longer cover a newer OBS version or a required NDI component.
As listed on the DistroAV resource page and in its 6.2.0 release notes in September 2026, the minimum OBS Studio version is 31.1.1; the release notes also specify NDI SDK 6.3.0 or newer. NDI's OBS page describes the requirement as NDI Runtime 6.3 or newer. These are version-specific requirements, not a promise that every later or differently packaged combination will work. Check the current pages again immediately before installation.
| Check | What to verify | Why it matters |
|---|---|---|
| OBS Studio | Your installed version meets the minimum on the current DistroAV listing and release notes | A plugin built for a newer OBS release may not load in an older one |
| Operating system and architecture | The plugin offers a build for your operating system and architecture; the listing covers 64-bit Windows, macOS, and Linux | A compatible operating system name alone does not guarantee that a particular architecture or install type is covered |
| NDI component | Follow the matching release's SDK or Runtime requirement | The plugin may be present but unable to operate if a required NDI component is missing |
| Existing OBS-NDI install | Identify and remove the old plugin when moving to DistroAV 6.x, following the project instructions | Two plugin versions can conflict instead of providing a usable output |
OBS's plugin guidance also warns that plugins can be limited by operating system or architecture, or may not yet be updated for the OBS version you have installed. That is why “I installed the plugin” is not a sufficient compatibility check. If you run a portable or custom OBS installation, look for the current plugin instructions on selecting the appropriate target directory rather than copying files by guesswork.
Install the plugin and restart OBS
Use the installation route documented for the DistroAV release and your operating system. The route has varied by release: DistroAV's 6.2.0 notes describe a one-click installer to address missing requirements on Windows and macOS, while earlier 6.1.1 notes list platform-specific routes such as Winget for Windows, Homebrew for macOS, and Flathub for Linux. Treat those as documentation for those particular releases, not as permanent commands for every current version.
If you already have OBS-NDI, follow NDI's direction to remove the older plugin before installing DistroAV. This is especially relevant when moving to DistroAV 6.x. Do not install a second copy over the first and hope OBS chooses the right one; plugin conflicts can make the expected controls disappear or behave unpredictably. Consult the matching release notes for removal and settings migration details.
Once installation finishes, close and reopen OBS. A restart allows OBS to load the plugin; without it, newly installed controls may not appear in the current session. Then use the current DistroAV instructions and the labels shown in your installed version to locate the NDI output controls. Menu placement and dialogue wording can differ across versions and platforms, so avoid relying on an old screenshot as an exact map.
If you use a custom data directory or portable installation, the installer may need a different target from the default OBS location. OBS notes that plugin availability can depend on platform and architecture, and DistroAV's own guidance should take precedence over generic file-copy instructions. If you are uncertain where OBS loads plugins from, resolve that before manually moving files.
Enable and configure NDI output
First make sure OBS has a programme worth sending: select the intended scene, confirm the sources are visible, and check the audio meters. Then enable the DistroAV control for NDI Output, using the current in-app labels and release-matched instructions. This is the control that sends the main programme view. Do not add an NDI Source if your goal is to send OBS out to another device; that function receives a feed into OBS.
Next, configure the receiving application or device to discover and select the OBS output. The receiving end may display a list of NDI sources or offer another selection mechanism, depending on the software. Confirm that it has selected the intended OBS programme, then check that moving video and audio arrive together. A still image, silent feed, or absent source points to different parts of the chain, so test them separately rather than repeatedly changing unrelated OBS settings.
NDI carries media over the network, so the sender and receiver need network connectivity that permits discovery and traffic. Existing network equipment may be sufficient; the reviewed documentation does not make a new cable or particular network product a plugin prerequisite. A wired Ethernet connection can be a sensible option where stability matters, but treat it as a choice for your network setup, not as a DistroAV installation requirement.
For an always-on YouTube channel, keep the jobs separate in your plan. OBS and DistroAV can provide an NDI feed to another production device, while YouTube delivery remains a separate broadcast step. If your real need is simply to keep a prerecorded video looping to YouTube overnight, a guide to looping a video on YouTube Live addresses that workflow more directly than adding NDI.
Output versus input: choose the right workflow
The choice depends on where the picture starts and where it needs to go. Use the table below to identify the DistroAV feature by direction and scope before changing scenes or adding sources.
| DistroAV feature | Direction | What it sends or receives | Example use |
|---|---|---|---|
| NDI Output | Out of OBS | OBS's main programme view | Send the composed show to another NDI receiver |
| NDI Source | Into OBS | A selected external NDI feed, added as a scene source | Bring a remote camera or another system's feed into an OBS scene |
| NDI Filter | Out from a selected source or scene | The parent source or scene to NDI, rather than the full programme | Make one particular source or scene available to another receiver |
Suppose you have a laptop sending a camera feed to an OBS computer. On the OBS computer, add an NDI Source to receive that camera and place it in a scene. If you then want to send the complete composed programme onward, enable NDI Output. They solve opposite legs of a workflow; one is not a substitute for the other.
A filter is useful when you want to expose only a chosen source or scene instead of the entire programme. Check the current DistroAV resource notes for its audio limitations before building around it: the listing describes audio support only for video capture sources, media sources, and VLC sources. If you need the whole mix, the main programme output is the more direct fit.
For production that ends at YouTube, NDI may add complexity without solving the actual need. If the computer must stay on all night to run OBS, you are solving a different problem from moving media between devices. An overview of OBS and prerecorded-video streaming approaches can help clarify whether you need an OBS production workflow or a service that runs a file without your computer.
Troubleshoot missing NDI options
If you cannot find NDI controls after restarting OBS, work through the chain in order. First confirm that DistroAV, rather than an older OBS-NDI build or only the NDI runtime, is actually installed. Then compare OBS and NDI component versions against the current DistroAV release notes. A plugin that no longer meets the newer minimums may fail to load, and its controls will not appear simply because an NDI receiver is installed.
Next check whether the package matches the operating system and architecture, and whether OBS is using a custom or portable plugin directory. OBS's plugin guidance explains that a plugin can be unavailable for a particular platform or architecture, or lag behind an installed OBS version. Use the current DistroAV installer or its own documentation to correct the target location; hand-copying files can make it harder to see which build OBS is loading.
If you upgraded from OBS-NDI to DistroAV 6.x, remove the old plugin as directed before reinstalling the current one. Then restart OBS again and check the current labels. Older tutorials may refer to menu paths or controls that have moved, and a missing menu in such a tutorial does not necessarily mean the current plugin is broken. The DistroAV release history records changing OBS and NDI minimums, so match instructions to the version you actually use.
If the output control exists but the receiver cannot see it, treat that as a discovery or network issue rather than a missing OBS plugin. Check both ends are on a network that allows the required NDI traffic, and review local firewall permissions and the current DistroAV troubleshooting guidance. DistroAV's 6.1.1 notes mention Windows firewall rules, but do not assume that an installer setting resolves every network policy or discovery problem.
For an overnight broadcast, keep the failure under observation rather than assuming a visible menu proves the entire route works. Test from OBS to the intended receiver, watch for both image and sound, and then check that the receiver remains able to see the source after a restart. A wider live-streaming technology overview helps place NDI in the larger chain of capture, production, network transport, and platform delivery.
If the production file itself needs to be online continuously, an OBS NDI output is not a substitute for a machine or workflow that stays available. StreamNeo removes the specific burden of keeping your own computer running for a prerecorded YouTube broadcast: upload the file, provide the YouTube stream key, and the stream runs with your computer off. It is YouTube-only, so it does not replace NDI when the job is to pass a live OBS programme to another device.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is NDI an official OBS plugin?
No. NDI's documentation says it does not provide an official OBS plugin and identifies DistroAV, formerly OBS-NDI, for NDI workflows in OBS. OBS itself also treats plugins as separate additions, so check the plugin project's current requirements and instructions.
Why is NDI missing from my OBS menus?
The plugin may not be installed or loaded, its OBS or NDI requirements may not be met, or the build may not match your operating system, architecture, or custom OBS location. Restart OBS after installation, check the current DistroAV release notes, and remove a conflicting older OBS-NDI install when moving to DistroAV 6.x.
Should I add NDI Source to send OBS to another computer?
No. NDI Source receives a feed into OBS. To send OBS's complete programme view outward, use DistroAV's NDI Output; use NDI Filter when the intended output is a selected source or scene.
Do I need a new Ethernet cable for NDI?
Not necessarily. NDI carries media over an IP network, and the reviewed plugin documentation does not require buying a cable or specify a particular network product. Your existing network may work; a wired connection is an optional setup choice if it suits the reliability needs of your production.