SoftwareSeptember 24, 20266 min read

How can you record Zoom meetings without a bot?

We'll go over 3 ways to record Zoom meetings without a bot: Zoom's native RTMS and Cloud Recording APIs, OS-level capture with ScreenCaptureKit and WASAPI, or a desktop recording SDK. Here's how they compare.

TL;DR: The simplest way to record Zoom meetings without a bot is with a desktop recording SDK. It can capture real-time and post-meeting data locally without relying on Zoom permissions or customer configurations, while also supporting platforms like Google Meet and Microsoft Teams through the same integration.

Building an AI sales intelligence product or another meeting intelligence app, and want to capture Zoom meeting data without adding a bot? You have three main options: use Zoom RTMS to receive media directly from Zoom, build local capture using operating system APIs or capture the meeting locally through a desktop recording application.

Method 1: Using Zoom native APIs for recording meetings without a bot

Best for: Products focused exclusively on Zoom whose teams are prepared to build and maintain two separate recording integrations from scratch, and obtain the required permissions and approvals.

Zoom's Realtime Media Streams (RTMS) lets your application receive live audio, video, screen sharing, and transcript data from Zoom meetings and webinars. Streams can start automatically when a user joins or hosts a meeting, provided auto-start is configured and the relevant host and administrator settings permit it, which is where the challenge often lies.

For post-meeting workflows, Zoom's Cloud Recording APIs let your application retrieve processed recordings and any associated transcript files. These files' availability also depend on cloud recording and transcription being enabled and completed.

To use RTMS, you need to create a Zoom app, configure the required scopes and event subscriptions, and maintain an active Zoom Developer Pack subscription with sufficient credits. Before users outside your Zoom account can install the app, it must also pass Zoom's App Review process. This is why using Realtime Media Streams and Zoom Developer Pack may be the less practical option if you want your users to just start recording.

Limitations of Zoom native APIs for recording meetings without a bot

The biggest limitation with RTMS is that your recording pipeline depends on Zoom being configured correctly. Your app needs to be installed and authorized with the right permissions, and the customer's Zoom account needs to allow real-time meeting content to be shared with apps. So even if your integration is working perfectly, a missing customer-side setting can still prevent your app from capturing meetings.

Cloud Recording APIs, which give you post-meeting artifacts, have a different limitation. If the meeting wasn't recorded to the cloud, there won't be a recording for your app to retrieve. So your customer needs to remember to always have the right set up.

Using both approaches means dealing with both sets of concerns. There are also additional scaling constraints. RTMS requires Zoom Developer Pack credits, and Zoom limits the number of concurrent streams based on your subscription. As usage grows, you need to keep an eye on both your credit usage and available stream capacity. Zoom currently documents a default limit of 2,000 concurrent streams for the Developer Pack, with higher limits available by request.

And all of this only solves meeting recording on Zoom. If your product also needs to support Microsoft Teams or Google Meet, you still have to build and maintain separate integrations for each platform.

That's why teams building for production often look beyond native meeting APIs, especially for a growing, multi-platform user base.

Method 2: Using ScreenCaptureKit and WASAPI for recording meetings without a bot

Best for: Capturing only audio on one specific operating system

ScreenCaptureKit on macOS and WASAPI on Windows are 2 native APIs that can capture Zoom audio directly from the user's computer without a bot. Capture does not require Zoom's RTMS or Cloud Recording APIs, and your app can process the audio in real time or save it for post-meeting use.

However, though these APIs provide capture functionality, you still need to build meeting detection, recording controls, storage, audio synchronization, transcription, speaker attribution, and recovery from recording failures. You also need to handle microphone input alongside Zoom's playback audio to capture both sides of the conversation.

A desktop recording SDK can reduce this work by packaging capture functionality for your app. If you build a desktop recording app with a recording SDK, you can get both live audio and post-meeting recordings without building the capture stack from scratch.

Method 3: Using a desktop recording SDK for recording meetings without a bot

Best for: Capturing meetings on all platforms and operating systems

A desktop recording SDK works across macOS, Windows, and meeting platforms like Zoom, Google Meet, and Microsoft Teams, and captures meetings through an app on the user's device. It can automatically detect meetings and record them locally without adding a meeting bot into the call.

A desktop recording SDK can capture both audio and video while the meeting is in progress, provide real-time meeting data during the call, and generate post-meeting recordings and transcripts once the meeting ends. This gives your application a consistent recording and transcription layer across supported platforms without relying on a separate native media integration for each provider.

That is particularly useful for AI applications where meeting data is the context layer for everything that follows. Instead of maintaining different media pipelines and transcript formats for each provider, your application can work with a consistent capture layer as users and meeting volume grow.

Install a desktop recording SDK. Then initialize it when your Electron application starts:

const RecallAiSdk = require("@recallai/desktop-sdk");

RecallAiSdk.init({
  apiUrl: "https://us-west-2.recall.ai"
});

From there, your application can respond to meeting-detection events and start recording automatically based on your product's workflow.

The result is still a bot-free Zoom recording experience, but the recording layer is no longer limited to Zoom. As customers expand to other meeting platforms, your application can keep using the same underlying capture and transcription infrastructure rather than rebuilding it provider by provider.

Zoom native APIs vs a desktop recording SDK

RequirementZoom RTMSZoom Cloud Recording APIDesktop Recording SDK
Real-time meeting dataLive audio, video, screen share, and transcripts directly from Zoom.Not supported.Live audio, video, screen share, and transcripts locally from the user's device.
Post-meeting dataNot supported.Audio and video recordings, and transcripts, when recording and transcription are enabled.Audio and video recordings, transcripts, and meeting metadata.
Platform coverageZoom meetings.Zoom meetings.Zoom, Microsoft Teams, Google Meet and in-person meetings using one SDK.
Scaling to other platformsRequires a new integration to be built.Requires a new integration to be built.No new integration needed.
Approval processRequires Zoom App Review.Requires Zoom API authorization and depends on the customer's cloud recording configuration.Does not require Zoom approval or authorization.

As you can see in the side-by-side comparison, a desktop recording SDK lets you access both real-time and post-meeting data through the same integration, support users across multiple meeting platforms, and avoid depending on how each customer's Zoom environment is configured.