Skype for Content Creators once let you bring separate Skype call feeds into compatible production software through NDI. Skype was retired on 5 May 2025, so this is a record of a former workflow, not instructions you can rely on using with a current Skype service.
If you are looking for a way to get remote guests into OBS or another broadcast application today, do not assume Teams Free has replaced that NDI feature. Microsoft documents a move for Skype contacts and chats, but the reviewed sources do not confirm equivalent NDI output in Teams Free.
The legacy Skype NDI workflow
The old arrangement connected a remote conversation to a production application. Skype handled the call; NDI made video and audio feeds available on the network to compatible software or hardware; the production application composed those feeds into a programme for recording or streaming. That separation let a host arrange guests, titles, transitions and other sources in the production application rather than broadcasting the call window as a single desktop capture.
This was useful for a podcast that also ran live on YouTube. A host could build a scene with a guest’s video, the host’s camera, graphics and other material, then send the finished programme to the streaming platform. If you are planning a long-running stream from prepared footage rather than a live conversation, the constraints are different; the guide to making a YouTube live stream from recorded videos on a low budget covers that separate kind of workflow.
The useful distinction is between the call and the broadcast. Skype NDI did not itself produce a finished show or send it to YouTube. It exposed feeds that another application could use. You still needed to build the programme, manage sound, check the outgoing stream and handle the connection to YouTube in your chosen production setup.
What Skype retirement means
Microsoft says Skype was retired as of 5 May 2025. That changes the status of every step below: they describe how the feature was documented and used before retirement, not a supported route for starting a new Skype call now. Microsoft’s retirement notice explains the change and points users towards Teams Free for continuing with contacts and chats.
A migration of contacts and chats is not proof that every Skype feature moved with them. The creator-facing NDI capability was a particular production integration. The Microsoft material reviewed for this article does not establish that Teams Free exposes equivalent per-participant NDI feeds, so describing Teams as a direct replacement would go beyond the evidence. Check current official Microsoft documentation before building a production plan around any Teams feature.
This matters if you find old guides, downloads or forum posts while troubleshooting. A tutorial can accurately describe a past Skype interface while being useless as a current setup instruction. Similarly, software components that once worked together may no longer be compatible with present operating system, production software or call-client versions. The historical steps below are context, not a recommendation to install an old client or plugin.
How Skype for Content Creators used NDI
Skype’s creator guidance described an NDI control in the call settings. In the documented interface, the operator enabled “Allow NDI® usage” under Settings, Calling, then Advanced. Once enabled, a Skype call could make its feeds available to NDI-compatible production equipment or software. These labels belong to the former Skype interface and should not be expected in Teams Free.
The feature also made the broadcast possibility visible to participants. Skype’s creator page described a notice in the call indicating that it might be broadcast or recorded via NDI. That is a meaningful production detail: a guest should know when their image or voice is being used in a programme. For any current remote recording or live show, explain the recording and broadcast arrangement to guests and follow the applicable platform and legal requirements; a visible notice in an old product does not settle those responsibilities for you.
Historical tutorials then showed the operator starting a group video call and selecting the resulting sources in production software. Streamlabs’ legacy walkthrough, published in 2021, describes distinct feeds such as “Skype - Local”, a guest-name feed, and “Skype - Active Speaker”. Treat those names as examples from that documented workflow, not guaranteed labels in any current application.
A host could use the local feed for their own camera rather than opening the camera separately in the production application. This could simplify scene composition, but it also meant that the call client was part of the programme path. A device or application issue in that path could affect the camera feed. For a production you intend to run today, verify every participant feed and the finished mix using the actual current applications before committing to a format.
What NDI sent to production software
NDI’s role was to carry source feeds from the call into another application. It did not decide the show layout. In production software, the operator could add a feed as a source, position it in a scene, combine it with other media and direct the programme towards recording or streaming. Separate feeds gave the operator more flexibility than capturing one call window, because a guest or active speaker could be arranged independently where the software exposed those sources.
That flexibility came with practical checks. You needed to know which feed contained the local host, which corresponded to each guest, and whether the active-speaker feed behaved as expected for your conversation. You also needed to check that the selected source carried the picture and sound you intended, and that the production application was not also capturing a duplicate microphone or camera. A clean scene can still produce echo or doubled audio if the same sound enters the mix by two routes.
NDI should not be confused with a complete remote-podcast recording system. The documented workflow describes feeds for a live production application; it does not, by itself, establish separate high-quality local recordings for every guest, a particular audio mix-minus configuration, or a guaranteed recording backup. If those are requirements, look for evidence that a current tool supports them directly, and test the complete route rather than assuming that support for video feeds covers the rest.
The same care applies to OBS. NDI’s documentation describes the OBS plugin as unofficial and links to its setup material. The plugin is not an official OBS component simply because it appeared in historical instructions. NDI’s OBS plugin documentation is the place to check the current status and compatibility of that route before considering it. Do not assume that old installation steps, runtimes or versions remain suitable.
The historical setup at a glance
The following table summarises the former workflow, separating what historical sources described from what a reader should conclude now.
| Historical step | What it did | What not to assume now |
|---|---|---|
| Enable NDI in Skype | The documented Skype setting allowed the call’s feeds to be made available to NDI-compatible production tools. | That the retired Skype service remains available, or that the same setting exists in Teams Free. |
| Start a group video call | The host brought remote guests into the call; the streaming computer was the relevant machine for enabling and using its NDI output. | That each guest needed to configure NDI, or that present-day call software exposes the same feeds. |
| Add feeds in a production application | The operator selected local, guest or active-speaker sources for scenes in compatible software. | That source names, behaviour or compatibility carry over to current software versions. |
| Send the composed show to the platform | The production application handled the final programme output. | That NDI itself managed YouTube streaming, monitoring or a continuous broadcast. |
Microsoft’s creator guidance and the 2021 Streamlabs tutorial are the basis for this historical account. A Microsoft Community Hub article also described a desktop Skype, OBS Studio and obs-ndi arrangement, and said remote guests did not need to enable NDI themselves. That article is a dated tutorial, not current compatibility guidance. The boundary matters: the old procedure is useful for understanding why a Skype podcast guide mentioned NDI, but it cannot tell you which modern application pairing will work.
If your aim is a continuous YouTube channel rather than a live guest show, a call-and-scene workflow may also be the wrong tool. A pre-recorded stream has different failure points, such as the media loop, encoder and outgoing connection. The practical checks in how to keep a YouTube live stream running after disconnecting from Linode are relevant to that distinct operating problem, not a way to restore Skype NDI.
Why Teams Free is not a confirmed replacement
Microsoft’s retirement information explains that Skype users can move contacts and chats to Teams Free. That is useful for continuing conversations, but it does not answer a production question: can Teams Free publish separate call feeds in a way that a chosen NDI receiver or broadcast application can select? The reviewed source material does not confirm that it can.
Keep the answer narrow. It is not evidence that Teams can never support any production workflow, nor evidence that every Teams edition has the same features. It means the specific parity claim — Teams Free provides Skype for Content Creators’ NDI output — is unverified in the sources used here. Before changing your show around it, check Microsoft’s current documentation for the exact edition, account type and output feature you intend to use. Then confirm that the receiving production software supports that route too.
A useful test is more specific than asking whether a platform “works with OBS”. Find out whether each remote guest can be selected independently, what happens when the active speaker changes, whether audio is available and controllable as expected, and whether the result can be sent into the production application you use. If documentation does not answer those questions, ask the vendor or test a non-public session before announcing a live show.
Choosing a current production workflow
There is no verified present-day equivalent identified by the research for this article, so it would be misleading to name one as a Skype NDI replacement. Instead, decide what the show actually needs and evaluate candidate tools against those needs. A simple interview may only require a dependable call and one composed programme feed. A panel with guest-specific layouts may need distinct sources. A show that must preserve each guest’s recording for later editing needs a separate recording capability, not merely a live video feed.
| Requirement to verify | Question to ask before adopting a tool |
|---|---|
| Separate guest feeds | Can the production application select each guest independently, or does it receive one combined call view? |
| Audio routing | Can you control the host and guest audio without creating echo, and can the intended mix-minus arrangement be made? |
| Recording | Are recordings available, and are they individual tracks or only a single mixed programme? |
| Compatibility | Does the current version work with your operating system, call platform and broadcast software? Is the integration documented by the relevant vendor? |
| Operating cost and terms | What does the vendor currently charge, and what limits, trial terms or account requirements apply? Verify these on the vendor’s own current page rather than relying on an old tutorial. |
Run a rehearsal using the same host computer, guest devices, network conditions and production scene you plan to use. Check the scene transitions, sound levels, guest entry and exit, and the outgoing preview. If the show depends on a particular participant being visible or on clean audio, test that case rather than only a two-person call with everyone in the same room. Keep a fallback plan, such as postponing the live segment or switching to a prepared scene, that does not depend on the unverified feature.
For a YouTube channel that is meant to stay live when nobody is hosting a conversation, distinguish the broadcast operation from guest production. StreamNeo is relevant only to the specific pain of keeping a prepared video broadcast running without leaving your computer on; it does not restore Skype or provide an NDI guest-call workflow. If you are deciding between a live interview and a continuous loop, first compare the operating needs described in ways to loop videos on YouTube Live continuously, then choose a workflow that has been verified for the format you will publish.
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
How do I get a Skype call into OBS?
Historically, Skype for Content Creators could expose call feeds over NDI, and compatible production software could add those feeds as sources. Skype was retired on 5 May 2025, so this is not a current Skype setup procedure. NDI’s OBS plugin is unofficial; check the documentation and current compatibility before planning any present-day NDI workflow.
How did you enable NDI in Skype?
The former Skype creator guidance placed “Allow NDI® usage” under Settings, Calling, Advanced. The host then started the call and selected available feeds in compatible production software. Those are historical interface steps, not instructions for Teams Free or another current client.
Could you show each guest as a separate source?
Historical Streamlabs instructions describe guest-name feeds as well as local and active-speaker feeds. That let an operator choose sources separately in the production application, subject to the old software’s behaviour. It does not establish that a current platform exposes equivalent feeds.
Does Teams Free have Skype NDI?
The reviewed Microsoft retirement material confirms a route for moving Skype contacts and chats to Teams Free, but does not confirm that Teams Free reproduces Skype’s NDI output. Treat parity as unverified and check current official documentation for the exact Teams edition and production feature before relying on it.