How the Zoom Plugin SDK Changes OBS Integrations

Quick Answer

• Zoom’s new Plugin SDK allows developers to connect directly to the official Zoom Workplace app via IPC for deep native integrations.
• CoreVideo is a free, open-source OBS plugin that leverages the SDK to capture isolated Zoom participants as native 1080p sources without needing NDI or virtual cameras.
• Capturing multiple 1080p sources directly requires significant bandwidth, consuming roughly 4-6 Mbps per participant.
• Feeds offers a premium, tier-based OBS alternative that includes built-in Twitch-style chat overlays, popup messaging, and support for up to eight isolated video feeds.

How the Zoom Plugin SDK Changes OBS Integrations

Integrating video conferencing feeds into broadcast environments requires precise architectural planning. The Zoom Plugin SDK establishes a distinct approach to how developers bridge native applications running on macOS or Windows with live meeting environments. Rather than operating as a standalone endpoint, this SDK leverages Inter-Process Communication (IPC) to tether native external applications directly to the official Zoom Workplace app.

This structural design eliminates the need to bundle an entire client inside a third-party application, a requirement that traditionally defines the Zoom Meeting SDK. By offloading the core connection to the official Zoom Workplace client, external tools can operate with significantly less overhead. Through this IPC bridge, the Plugin SDK exposes a dense control layer consisting of over 170 callable methods. These methods grant developers granular programmatic control over a wide array of in-meeting features and settings functionality directly from their external application.

Despite this deep integration for remote control and meeting management, developers handling live broadcast feeds must weigh their media extraction requirements carefully. The Zoom Meeting SDK is the architecture that offers direct access to raw video and audio data natively. Broadcast workflows often rely on this raw media isolation to manipulate individual tracks—such as routing caller audio independently to separate stream audio without VoiceMeeter. The Plugin SDK dictates the local software environment’s behavior, while the Meeting SDK manages direct raw media extraction.

Zoom Integration Architectures

Requirement	Zoom Plugin SDK	Zoom Meeting SDK
Connection Method	Connects to Zoom Workplace on macOS or Windows via IPC	—
Bundles a Client	No	Yes
Callable Methods	Over 170 methods for in-meeting features and settings	—
Raw Media Access	—	Direct access to raw video and audio data on native platforms
Required Authorization	Marketplace Access Token (Scope: plugin_sdk:read:connection_meta)	ZAK or OBF tokens, or RTMS (required for outside accounts starting March 2, 2026)
Account Sign-In	App and Zoom Workplace must be signed in using the same Zoom account	—

Securing the IPC connection between a native application and Zoom Workplace involves rigid credential protocols. The developer must first acquire a Marketplace Access Token configured with a highly specific scope: plugin_sdk:read:connection_meta. Passing this token is only the first phase of the handshake. The integration relies on strict identity alignment; both the native application utilizing the Plugin SDK and the local Zoom Workplace application must be actively signed in using the exact same Zoom account. If the account credentials do not match perfectly across both applications, the plugin will fail to connect.

This identical-account mandate for the Plugin SDK provides crucial context when evaluating Zoom’s integration roadmap. Authentication standards for the Meeting SDK are tightening. Zoom has scheduled a firm cutoff: beginning March 2, 2026, any application leveraging the Zoom Meeting SDK to join meetings that exist outside of their own account will face hard restrictions. These out-of-network connections will strictly require authorization utilizing ZAK or OBF tokens, or mandate the use of RTMS.

By forcing the local Zoom Workplace app and the integrating tool to share identical credentials, the Plugin SDK bypasses out-of-network authorization complexities. The integration behaves as an authenticated extension of the user’s primary client rather than a discrete external bot, fundamentally dictating that the broadcast machine must be configured as a fully authenticated first-party participant to successfully execute the connection.

CoreVideo Features: Adding Native Zoom Sources in OBS

CoreVideo fundamentally changes how broadcasters handle remote guests by bringing Zoom participants directly into OBS Studio as native sources. Released entirely as free and open-source software under the MIT license, it eliminates the traditional friction and heavy resource overhead of remote live production. Producers no longer need to rely on local network protocols like NDI, juggle complex arrays of third-party virtual cameras, or resort to cropping messy desktop screen captures just to isolate a single guest’s webcam.

The core integration happens completely within the standard OBS Studio interface. Once the plugin is installed, producers manage the entire meeting connection through a dedicated Zoom Control dock, which can be quickly enabled by navigating to the top menu and selecting Docks -> Zoom Control. While CoreVideo excels at pulling these isolated participant feeds directly into your local broadcasting environment, it keeps the two-way communication seamless by sending your tailored return feed back to the Zoom meeting room through the built-in OBS Virtual Camera.

The absolute strongest advantage of this plugin lies in its strict source separation. CoreVideo assigns each individual Zoom participant as an entirely separate OBS source, natively supporting video resolutions up to 1080p. Just as crucially, the plugin automatically isolates every individual participant’s microphone, placing their audio on its own dedicated track within the OBS audio mixer. This native separation gives you immediate, granular control over equalization and volume levels, mirroring the exact precision required when you Separate Stream Audio Without VoiceMeeter: The Easy Fix.

CoreVideo Dynamic Routing Options

Routing Target	System Behavior
Active speaker	—
Zoom spotlight slot 1…N	—
Fixed guest	Automatic failover

Managing these individual sources during a live, unscripted broadcast requires significant flexibility, and CoreVideo provides multiple dynamic routing options to handle unpredictable meeting environments. Broadcasters can configure a specific OBS source to simply track the active speaker, ensuring the person currently talking is always displayed on screen. Alternatively, you can bind an OBS source to a specific Zoom spotlight slot (ranging from 1 to N), allowing the meeting host to control the layout from within the Zoom client. For strict run-of-shows, you can lock an OBS source to a fixed guest. If that fixed guest drops their connection abruptly, CoreVideo automatically initiates a failover mechanism to protect your broadcast layout.

Beyond pulling individual webcams, the plugin seamlessly handles advanced meeting assets. If a participant starts a presentation, CoreVideo pulls that live screen share into OBS as a completely dedicated, independent source. Existing Zoom interpretation audio channels can also be pulled directly into OBS as dedicated sources, ensuring translated audio can be accurately mixed into the final broadcast.

For post-production workflows, CoreVideo acts as a powerful isolated recording tool. Every assigned participant feed is recorded locally to its own muxed MP4 file, complete with perfectly matching PCM audio. This provides video editors with pristine, separate tracks for every speaker, making it effortless to cut multicam timelines or Edit Talking Head Videos Without Constant Zoom-ins by utilizing the isolated 1080p source files.

CoreVideo System Requirements and Installation Guide

Before deploying CoreVideo to capture isolated feeds, you must audit your hardware, software, and network capabilities against the plugin’s strict limitations. The primary deployment environment is Microsoft Windows. Windows 10 or Windows 11 (x64) is the only supported, packaged, and CI-released target for CoreVideo. You must also be running a 64-bit version of OBS Studio 30 or newer.

For macOS users, CoreVideo remains in a public beta phase with strict hardware constraints. It supports Apple Silicon Macs (M1 or later) only. If you are operating on older Apple hardware, you are out of luck; Intel Macs are entirely unsupported by the beta bundle. Like the Windows version, macOS users must run OBS Studio 30 or newer.

The most common point of failure when configuring this plugin is network bandwidth. CoreVideo requires roughly 4-6 Mbps downstream bandwidth per 1080p participant. If you plan to host a panel with five external guests, you must allocate up to 30 Mbps of reliable downstream bandwidth solely for their incoming video feeds. This mathematical requirement directly clashes with default platform limits. Standard Zoom accounts are typically capped around 30 Mbps incoming bandwidth. Pushing multiple 1080p feeds through a standard account will saturate this limit, resulting in severe degradation of the incoming video quality. Upgrading your platform license to an Enhanced Media / HBM account resolves this bottleneck. An Enhanced Media / HBM account raises the incoming bandwidth allowance to roughly 100 Mbps, providing the necessary overhead to ingest a dozen 1080p guests simultaneously without triggering bandwidth caps.

When you execute the installation on Windows, the process requires establishing secure permissions. CoreVideo requests two read-only scopes during authorization: user:read:user and user:read:token. CoreVideo’s latest Windows release is v0.1.44. Before running the setup file, the CoreVideo installer checksum can be verified on Windows using the following PowerShell command to ensure file integrity:

Get-FileHash .\CoreVideo-Setup-v0.1.44.exe -Algorithm SHA256

Installing the macOS beta bundle requires manual file management and overriding system security protocols. First, the macOS beta plugin file named obs-zoom-plugin.plugin must be copied directly into your OBS plugins directory. You must place it at the following absolute path: ~/Library/Application Support/obs-studio/plugins/.

Because the plugin is downloaded directly from an external source, the macOS system will quarantine the file and prevent OBS Studio 30 from loading it. The macOS beta bundle requires running a specific Terminal command to clear the quarantine flag from the plugin. Open your Terminal application and execute the following command exactly as written:

xattr -dr com.apple.quarantine ~/Library/Application\ Support/obs-studio/plugins/obs-zoom-plugin.plugin

Clearing this flag is not optional. If you bypass this terminal command, OBS Studio will silently ignore the plugin file upon initialization, completely breaking your video feed workflow.

Advanced CoreVideo Configuration and Developer APIs

CoreVideo operates far beyond a standard graphical interface, exposing local servers designed for programmatic control. This allows tight integration with existing broadcast automation, custom hardware controllers, and specialized streaming environments. Accessing these endpoints requires pointing your client application directly to the local loopback address.

The software runs two distinct local API servers to handle different types of programmatic interaction. The first is a TCP control API JSON server listening on 127.0.0.1:19870. This endpoint accepts standard JSON payloads over a reliable TCP connection, making it the primary target for custom web-based dashboards, automation tools, or scripts tracking stream state. Sending state changes here ensures absolute data delivery, which is critical when scripting sequential scene transitions or managing complex broadcast logic. If you are building a custom studio interface to edit talking head videos without constant zoom-ins during post-production, you can use this JSON API to automate dynamic, multi-camera live cuts directly from a physical control surface. Developers often utilize these automation capabilities to scale production workflows. When analyzing metrics on how to find outlier YouTube videos for channel growth, creators frequently discover that dynamic visual formats perform best. The JSON API allows solo creators to replicate complex broadcast timing automatically without hiring a dedicated technical director.

The second endpoint is a UDP OSC (Open Sound Control) control API server located at 127.0.0.1:19871. Because it relies on UDP, this server prioritizes speed and low latency over guaranteed packet delivery. OSC is the industry standard for tying visual changes to live audio data, MIDI triggers, or lighting cues. Once you configure your operating system to separate stream audio without VoiceMeeter, you can pipe that isolated audio data through an OSC generator to trigger CoreVideo actions based on precise volume thresholds. A sudden audio spike in a remote guest’s microphone can instantly switch the active video layout via this UDP port with virtually zero delay.

If you intend to fork or modify the software from source, CoreVideo requires a strict toolchain and dependency tree to compile correctly. You must have CMake 3.16+ installed to handle the build generation across different operating systems. The application’s user interface relies entirely on Qt 6.x, meaning older Qt 5 development environments will fail during the initial configuration phase.

At the core broadcast engine level, the application strictly depends on libobs combined with the obs-frontend-api. This dual requirement ensures that any video manipulation within CoreVideo directly interfaces with the underlying OBS Studio rendering pipeline rather than attempting to process elements independently. Heavy media handling, decoding, and encoding operations are passed directly through FFmpeg. Finally, for ingesting secure remote feeds, you must link the build against the Zoom Meeting SDK. The codebase explicitly supports Zoom Meeting SDK versions 5.17.x or the newer 7.x branch. Failing to match these exact SDK versions breaks the application’s ability to extract raw audio and video buffers from active Zoom calls, resulting in compilation errors or immediate crashes upon connecting to a meeting.

Exploring Feeds: A Premium OBS Plugin Alternative for Zoom

Integrating Zoom calls into a professional broadcast often feels like a balancing act between awkward screen captures and cropped windows. The Feeds OBS plugin bypasses these clunky workarounds by providing a direct bridge between the two platforms. Available through the Zoom App Marketplace, this integration allows broadcasters to pull individual elements from a meeting straight into their OBS scenes. For developers or creators looking to inspect the underlying code, the project maintains a public presence on GitHub at https://github.com/LetsDoVideo/feeds, providing a direct line to the repository for issue tracking and updates.

The core functionality of Feeds revolves around how it handles video and screen captures inside your broadcasting software. Instead of relying on a standard window capture that grabs the entire Zoom interface—complete with participant galleries, chat boxes, and control bars—Feeds creates dedicated source types within the software. When you need to add a live video element to your scene, you simply select a “Zoom Participant” source. This gives you the freedom to scale, apply filters, and position that individual’s camera feed anywhere on your canvas.

When the meeting shifts to a slide deck or software demonstration, you can independently add a “Zoom Screenshare” source. This strict separation of visual elements is vital for creating polished, multi-layered layouts. Much like how a broadcaster might separate stream audio without VoiceMeeter to ensure granular control over what the audience hears, isolating the screenshare from the participant video gives you total control over what they see. You can craft dynamic side-by-side scenes or picture-in-picture layouts that feel natural, helping you avoid the need to aggressively edit talking head videos without constant zoom-ins just to keep the visual presentation engaging. By treating the participant camera and the screenshare as distinct, selectable sources, your production maintains a clean, professional aesthetic.

Beyond video routing, Feeds directly addresses a major limitation of standard Zoom broadcasts: real-time audience interaction. Traditional webinars often silo the conversation away from the main viewing experience, making it difficult for presenters to acknowledge viewer input dynamically. Feeds remedies this by introducing a Twitch-style overlay specifically designed for the Zoom Webinar Chat. This brings the energy and visibility of modern live streaming platforms into the structured environment of a webinar, transforming a rigid presentation into a highly interactive broadcast.

The integration is not limited to a passive, scrolling wall of text. It includes actionable elements that elevate the production value on the fly. When an audience member asks a highly relevant question or leaves a comment that adds value to the current topic, the producer can click on any Zoom message to pop it up directly on screen. This targeted overlay mechanic visually rewards audience participation, keeps the viewers engaged, and provides a clear focal point for the presenter to address on the live broadcast.

Feeds Pricing Plans and Subscription Tiers

Choosing the right software tier dictates the technical ceiling of your production. The Feeds ecosystem scales from solo podcast setups to multi-guest network broadcasts, offering a structured upgrade path as your production demands grow. Creators evaluating these options must weigh their maximum concurrent guest count against their required post-production flexibility. You can maintain month-to-month financial agility or commit to annual billing, which saves up to 21% across all the paid subscription tiers, freeing up budget for hardware upgrades or marketing.

The Feeds Free plan offers immediate utility without a financial commitment. This baseline tier provisions one 720p isolated video feed alongside an Active Participant (Speaker) feed. It serves as a highly functional starting point for straightforward, single-guest remote interviews. By isolating the active speaker, you gain clean, distinct control over the most critical visual element of the conversation before routing the signal into your primary broadcasting software.

Stepping up to the Feeds Basic plan costs $9.99 per user per month and fundamentally shifts your baseline production quality. The resolution cap lifts to full 1080p, and your capacity increases to accommodate up to three isolated feeds. This tier introduces native screenshare functionality and Local ISO Source Recording. Capturing distinct local recordings for each participant entirely transforms your post-production workflow. Instead of hacking apart a flattened master file where guests are permanently baked into a single layout, you retain individual, high-quality video files. This granular separation makes it far easier to edit talking head videos without constant zoom-ins, as you can seamlessly cut between clean, isolated guest angles. Furthermore, the Basic plan includes a Zoom Chat Dock natively within OBS, allowing producers to monitor guest communication without breaking their primary workspace focus.

For creators pushing heavier engagement and larger discussion panels, the Feeds Streamer plan runs $24.99 per user per month. It expands your technical capacity to five 1080p isolated feeds. Beyond raw feed count, this tier prioritizes on-screen engagement tools, adding a Zoom Chat Overlay and Message Popup functionality directly into your visual mix. These interactive tools allow you to highlight guest input dynamically. The Streamer plan also bundles 6 Creative Templates, reducing the friction of building multi-box layouts from scratch. Handling this many inputs requires strict organization. Just as many creators look to separate stream audio without VoiceMeeter for better mixing control, the Streamer plan ensures your numerous video sources remain perfectly untangled.

At the absolute top of the stack, the Feeds Broadcaster plan costs $79.99 per user per month. This tier caters directly to complex, large-scale live events by unlocking up to eight 1080p isolated feeds simultaneously. Operating an eight-person remote panel introduces significant technical variables, which is why this premium tier provides exclusive access to a Dedicated Broadcaster Discord Channel. Relying on this dedicated channel ensures that operators executing high-stakes, multi-point broadcasts have a direct line to resolve bottlenecks before going live.

References

• Zoom Developer Blog: New SDKs Expand Possibilities for Direct Integration with Zoom Workplace
• OBS Plugin for Live Zoom Video - CoreVideo Documentation
• GitHub - iamfatness/CoreVideo Repository
• Zoom Community: New App for Zoom Webinars (for OBS users) - Looking for Feedback