PuppyIP Resource Center
Developer Integration 6 min read Published 2026-11-14

RealtimeKit Browser Noise Cancellation: Microphone Control and Cleanup

RealtimeKit noise cancellation filters background noise in supported web browsers before audio is sent to a meeting. Integrate it after meeting initialization and manage each canceller with its meeting lifecycle.

Cloudflare RealtimeKit Browser noise cancellation Microphone management JavaScript

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The November 12, 2026 announcement introduced a web noise-cancellation package for React, Angular and JavaScript apps in supported browsers; RealtimeKit’s native iOS and Android SDKs are not supported.
  • Initialize the meeting first and create one canceller per meeting instance. Keep asynchronous setup separate from joining or rendering the meeting UI.
  • autoManage is on by default and follows microphone availability. When it is off, your app must start, stop and dispose the instance; enable() requires an active, unmuted microphone.
  • enabled can be false for several reasons, and getStatus() is only for active processing. Handle promise rejections separately from onError; dispose() does not stop a microphone track or close AudioContext.

Check browser support, then choose the setup order

On November 12, 2026, Cloudflare announced that RealtimeKit web apps can use @cloudflare/realtimekit-noise-cancellation to filter background noise on the participant’s device before audio is sent to the meeting. The web integration supports React, Angular and JavaScript apps in Chrome, Edge, Firefox and Safari, including mobile browsers. RealtimeKit’s native iOS and Android SDKs do not currently support this feature.

Install the package with your project’s package manager, initialize the RealtimeKit meeting, and then call RealtimeKitNoiseCancellation.init({ meeting }). Create one canceller for each meeting instance. Keep its asynchronous setup separate from join() and UI startup so processing does not hold up joining. If you use the UI Kit, attach the meeting to its meeting element first. The announcement and guide do not establish plans or fees, per-account eligibility, regional availability or device-by-device performance benchmarks; confirm those separately.

Automatic management follows the microphone without unmuting it

autoManage defaults to true. The canceller starts processing when the microphone is available and manages processing through mute, unmute and reconnection states. If the microphone is muted during initialization, processing starts only after the participant unmutes. The package never unmutes the microphone.

Read enabled to check whether processing is on, but false can mean processing has not started, was turned off or the instance was disposed. Call getStatus() only while processing is active and enabled is true. Do not treat false as a single failure diagnosis or request processing metadata before processing has started.

With automatic management off, own startup and cleanup

When you set autoManage: false, initialization creates the instance without starting processing or registering automatic cleanup when the participant leaves. Wait until the microphone is active and unmuted before calling enable(). disable() temporarily stops noise cancellation and restores the microphone’s previous processing settings; call enable() again when the microphone is ready and processing should resume.

Call dispose() when the participant leaves, the app switches meetings or the component unmounts. You can also pass an AbortController signal to init() and abort it during application or component teardown; aborting disposes the instance even when autoManage is false. Manage the microphone track and RealtimeKit AudioContext separately: dispose() does not stop the track or close that AudioContext.

Handle promise failures separately from runtime errors

init() and explicit calls to enable(), disable() and dispose() return Promises. Handle rejections from each call, for example with .catch(...) on the corresponding promise chain. The optional onError callback receives runtime and automatic lifecycle errors; it does not replace promise rejection handling. If initialization rejects, record and handle that rejection instead of assuming onError also covers the failed explicit call.

With autoManage: true, the canceller is disposed when the participant leaves, but a temporary disconnection does not dispose it. Switching to a different connected meeting disposes the old meeting’s instance; initialize a new canceller for the new meeting object. With autoManage: false, your app owns activation and cleanup and should define how its leave, reconnection and meeting-switch flows handle the instance. Keep a temporary disconnect distinct from leaving the meeting.

Validate on your target devices and read the dates correctly

The Noise Cancellation documentation page says it was last updated on November 10, 2026; the feature announcement is dated November 12. The documentation timestamp is a page update, not evidence of when individual accounts or regions received access.

Before integrating, check meeting initialization in your web app, then validate mute and unmute, reconnection, leaving, meeting switches and component teardown in the browsers and devices you target. Read getStatus() only when processing is active. This guide is based on Cloudflare’s announcement and documentation; no package was installed, meeting joined, microphone audio captured, account eligibility checked or device benchmark run for this article. Perform those steps in your own authorized test environment.

Sources

Frequently Asked Questions

Does on-device filtering mean audio is never sent to the meeting?

No such conclusion follows. The documentation places filtering on the participant’s device before audio is sent to the meeting. That describes processing location and order; it does not say audio is never transmitted or establish transmission, storage, privacy or retention rules. Continue to follow the applicable product information and your organization’s requirements.

Does mobile-browser support guarantee the same performance as desktop?

No. The browser list establishes web-app support scope, but the pages provide no device-level benchmark or uniform performance guarantee. RealtimeKit’s native iOS and Android SDKs are also not supported. Validate the browsers and devices you intend to use.