Browser support

Meeting SDK usage policy

The Meeting SDK is reserved for human use cases and does not support bots or AI notetakers. To build an AI notetaker application or access realtime media, use Zoom RTMS (Real-time media streams).

The Zoom Meeting SDK for web supports browsers on this page within two (2) versions of their current version. The following table shows the features supported by browser. See the numbered feature support footnotes and Mobile and tablet browser support for details.

FeatureChromeFirefoxSafariEdgeiOS/iPadOSAndroid
720p Video (receive)
720p Video (send) (1)
Audio (receive)
Audio (send)
Background Noise Suppression (2)
Be remote controlled (3)
Breakout Rooms
Call In (PSTN)
Call Out (PSTN)
Closed Captioning
Cloud Recording
Encryption (4)
End-to-End Encryption (E2EE) (5)
Gallery view (6)
In-Meeting Chat
In-Meeting Chat - send file
Live Transcription
Live Translation
Remote Control(3)(3)(3)(3)
RTMP Live Streaming
Screen Share (receive)
Screen Share (send)(7)
Share tab audio (8)
Share system audio (8)
Stay awake (component view) (9)
Video (receive)
Video (send)
Virtual background
Waiting Room
Webinar Q&A
WebRTC video (10)
Whiteboard (edit)
Whiteboard (view)

Browser and feature support

As browser vendors release new versions, the minimum supported browser version will increase up to two (2) versions behind the new version. For example:

  • If the current version of Chrome is 139, the SDK will support versions 137, 138, and 139.
  • When the current version increases to 140, the SDK will support versions 138, 139, and 140.

The Meeting SDK for web supports the same features as the Zoom web client. See Zoom Meetings and Webinars comparison by platform for web client features.

Footnotes

  1. 720p send requires SharedArrayBuffer. Supported for mobile landscape mode in iOS >= 16.4 and Android chrome >= 112.
  2. Background Noise Suppression requires SharedArrayBuffer.
  3. The remote control feature allows you to take control of another participant's screen in a meeting when they've given you permission. Users on any platform can remote control. Users on the web platform cannot be remote-controlled as browsers do not supported it.
  4. The Zoom Meeting SDK uses TLS 1.2 and 256-bit AES-GCM Encryption. See the Zoom Encryption whitepaper for details.
  5. End-to-end encryption (E2EE) is not supported on any browser.
  6. Up to a maximum of 25 videos in gallery view. Safari requires version 17.0 or later, macOS Sonoma, and SDK v2.18.0 or later.
  7. Screen share (send) supported by component view. Supported by client view using Safari 17 and above with macOS 14 Sonoma and above.
  8. Share tab audio and share system audio require SharedArrayBuffer for WebAssembly (WASM) audio, but not for WebRTC audio. When sharing with a Chrome or Edge browser, users can share a tab, window, or entire screen. If they share a tab, they can also share the tab audio. If they share a window or the entire screen, they can share the system audio. The option is displayed on the screen as "Also share tab audio" or "Also share system audio" with a toggle to turn it on or off. Non-Chromium browsers can only share the window or entire screen and microphone audio, but no computer audio as these browsers do not support audio capture in getDisplayMedia.
  9. Added "stay awake" support on component view to prevent devices from going to sleep during meetings on the following browsers:
    • Chrome (version 116 and later)
    • Edge (version 90 and later)
    • Safari (version 16.4 and later)
    • This feature may require newer browser versions than listed. For more details, see WakeLock API compatibility.
  10. WebRTC video supported on:
    • Chrome on Windows, macOS, Android (with some model-specific exceptions), iOS, and ChromeOS
    • Edge on Windows
    • Safari on macOS
    • Mobile Safari and other WebKit-based browsers on iOS
    • Support for additional browsers and OS platforms is being gradually expanded.

Mobile and tablet browser support

  • iOS and iPadOS - All browsers on iOS and iPadOS use the same underlying WebKit engine (including Safari and Chrome). Because of this, supported features are based on the OS version, rather than individual browser versions.

  • Android

    • Most Android browsers are based on Chromium Blink and generally follow its versioning.
    • Samsung Internet is also Chromium-based but uses its own versioning scheme, which maps to specific Chromium versions.
    • For simplicity, supported features are listed by Android OS version, as the SDK offers the same capabilities across all supported Android browsers.
    • Android Firefox is not supported because it uses GeckoView, a different rendering engine, and different versioning.
  • Microsoft Tablets - Microsoft tablets run Windows, so browser support matches the same browsers on Windows desktops.

  • Chromebooks - Chromebooks run ChromeOS and support the same features as desktop browsers.

In general, mobile and tablet browser support follows OS versions currently supported by Apple and Android, including Samsung devices.

The Meeting SDK for web component view is designed specifically for desktop browser widget use cases and is not supported on mobile or tablet browsers. For mobile and tablet use cases, use client view.

Component view support

Component view is designed specifically for desktop browser use cases, and is not supported on mobile or tablet browsers. For mobile and tablet use cases, use client view.

Content Security Policy header

If you're using Content Security Policy (CSP) on your browsers and want to use any Zoom SDK for web, you must configure your web server to return the Content-Security-Policy header. For example, using the Nginx add_header directive.

add_header 'Content-Security-Policy' "default-src 'self';base-uri 'self';worker-src blob:;style-src 'self' 'unsafe-inline';script-src 'self' 'unsafe-inline' 'unsafe-eval' https://zoom.us *.zoom.us dmogdx0jrul3u.cloudfront.net blob:;connect-src 'self' https://zoom.us https://*.zoom.us wss://*.zoom.us;img-src 'self' https:;media-src 'self' https:;font-src 'self' https:;"

Warning

When script-src-elem is present in your CSP configuration, be sure its value matches the script-src directive.

For more on CSP, see the Mozilla, web.dev, or W3C documentation.

You'll need to add this if you see something like this error in the browser console.

CompileError: WebAssembly.instantiate(): Refused to compile or instantiate WebAssembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'strict-dynamic' 'nonce-LxlpktY6Sou9E-ZC46OlZA' blob: https: 'unsafe-inline'"
at 3afbd0c1-54af-4f01-9d3f-8ffb8dcb31cf:1:22144

Note: If your browser supports it, you can use wasm-unsafe-eval instead of unsafe-eval. However, not all browsers support this. See the mdn web docs for CSP: script-src: Unsafe WebAssembly execution for details.