Supported Browsers & Devices

As a browser-based platform, we're able to support any operating system that's capable of running one of our supported browsers.

Whether it's macOS, Linux, or Windows, we've got you covered as long as you can run an up-to-date and supported browser!

Due to a bug in Safari for macOS, we've temporarily disabled our Picture in Picture feature for versions 17.x

Desktop Browsers

All of the below browsers have full support for WebRTC. For the best experience, we recommend Chrome or Chromium-based browsers such as Edge, Vivaldi, Opera, Brave or Arc.

With consistently updating browsers and web API's, we're committed to supporting the two latest versions of each of the support browsers listed below.

Older versions of the below browsers will generally work as they support the basics of WebRTC. However, users may have a degraded experience due to newer browser level APIs and bug fixes.

If your users are experiencing problems, instruct them to update their browser as a first step. We recommend testing on older devices when possible, if you expect your user base to use predominately out of date software.

BrowserSupportedNotes

Chrome

βœ…

Firefox

βœ…

Edge

βœ…

Edge Legacy is unsupported

βœ…

Safari is a supported browser. However, Apple is slower to release updates and added WebRTC support later than other vendors. If Safari users are reporting problems, instruct them to try another browser.

Other Chromium browsers: Opera, Brave, Arc, Vivaldi

βœ…

In some cases Brave's stricter security settings can cause connection issues. Cross-site cookies must be enabled in Brave's "Shield" feature

Internet Explorer

❌

Unsupported

Mobile Browsers

Screen sharing is currently unavailable on Mobile devices due to browser API limitations

iOS

BrowserSupportedVersionNotes

Safari

βœ…

13.1+

Chrome

βœ…

Firefox

βœ…

Edge

βœ…

Android

BrowserSupportedNotes

Chrome

βœ…

Firefox

βœ…

Edge

βœ…

Samsung Internet

βœ…

Has a slower release cycle than other major browser vendors. If issues are experienced, try using Chrome to see if things improve

Last updated