Browser and Device Requirements for LiveClass
LiveClass runs directly in your web browser, so you don't need to install any additional software. However, certain browsers and devices are required to use features such as live audio, video, screen sharing, and background blur.
This guide explains which browsers and devices LiveClass supports, the requirements for different activities, and how to resolve common compatibility issues.
Supported Browsers
You can join LiveClass sessions using the following browsers:
| Browser | Desktop | Mobile |
|---|---|---|
| Google Chrome | Supported | Supported (Android) |
| Microsoft Edge (Chromium) | Supported | Supported (Android) |
| Mozilla Firefox | Supported | Supported (Android) |
| Safari | Supported (macOS) | Supported (iOS) |
| Brave, Opera, and other Chromium browsers | Supported | Supported (Android) |
Unsupported Browsers
Some browsers cannot provide the functionality required to run LiveClass sessions.
Internet Explorer: Not supported because it does not support WebRTC, which is required for live audio and video.
Legacy Microsoft Edge: The older, pre-Chromium version is not supported. Install the current Chromium-based Edge browser.
In-app browsers: Built-in browsers in applications such as Facebook, Instagram, LinkedIn, X, WeChat, Snapchat, and TikTok may block or interfere with camera and microphone access.
Open LiveClass in a Supported Browser
If you open a session link from a social media or messaging application, it may launch in that application's built-in browser.
To avoid compatibility issues, open the link directly in a supported browser.
On iPhone or iPad:
Open the session link.
Select the menu in the in-app browser.
Choose Open in Safari.
On Android:
Open the session link.
Select the menu in the in-app browser.
Choose Open in Chrome or another supported browser.
You can also copy the session link and paste it directly into your preferred browser.
Browser Requirements by Activity
Different LiveClass features require different levels of browser support.
| Activity | Browser Requirements |
|---|---|
| Watching and listening | Any supported browser |
| Speaking using a microphone | Supported browser with microphone permission |
| Using the camera | Supported browser with camera permission |
| Screen sharing | Desktop browser |
| Selecting an audio output device | Chrome, Edge, or Firefox on desktop |
| Background blur | Recent Chrome or Edge on desktop |
| Live captions | Chrome or Edge; partial support in Safari; not supported in Firefox |
Screen Sharing Requirements
Screen sharing has additional browser and device restrictions.
| Browser / Device | Screen Sharing | System Audio |
|---|---|---|
| Chrome / Edge / Opera (Desktop) | Full support: tab, window, or entire screen | Supported |
| Firefox (Desktop) | Supported for video | Limited or unavailable |
| Safari (macOS 13 or later) | Screen or window sharing; limited tab capture | Not supported |
| Android browsers | Limited or unavailable, depending on OS version | Not supported |
| iPhone / iPad | Not available | Not supported |
Important:
Screen sharing is not available on iPhone or iPad because of iOS platform restrictions.
If you need to present your screen, use a desktop or laptop.
To share a video with its sound, use Google Chrome or Microsoft Edge on a desktop. These browsers provide the most reliable system audio capture.
Recording and Browser Compatibility
LiveClass recordings are processed on its servers rather than directly in your browser.
This means:
Your browser choice does not affect recording quality.
Temporary connection issues on your device do not degrade the server-side recording file.
Closing your laptop does not stop an active server-side recording.
You can record a session using any supported browser, including Safari on iOS.
The same server-side processing applies to streams sent to external destinations.
Device Requirements
Your device requirements depend on how you plan to participate in a session.
For watching and listening
You can use any reasonably modern computer, tablet, or smartphone with a supported browser.
For using the camera and microphone
Make sure your device has:
A working camera and microphone.
Camera and microphone permissions enabled for your browser.
For participating in larger sessions
Your device processes every visible video tile displayed in the room. Older laptops or devices may struggle when many participant videos are visible at once.
To reduce the load, switch to Speaker layout, which displays one large video tile along with a smaller filmstrip of participants.
For more information, see [How Many Video Feeds Can Be on Screen].
Network Requirements
LiveClass automatically adjusts audio and video quality based on your available network connection. Therefore, there is no fixed minimum internet speed for joining a session.
For a better experience, follow these recommendations:
Prefer a wired connection: A wired internet connection is generally more stable than Wi-Fi, while Wi-Fi is generally more reliable than mobile data.
Check your upload speed: Upload speed is particularly important when sharing your camera or screen because it determines how well other participants receive your video.
Turn off your camera if your connection is poor: Disabling your camera is one of the most effective ways to reduce network usage.
LiveClass automatically adjusts quality when network conditions change. Video quality may decrease before audio quality so participants can continue hearing one another even when the connection becomes unstable.
Important Requirements for Joining a Session
Keep the following requirements in mind before joining a LiveClass session.
1. Open LiveClass Directly
LiveClass session join pages, live rooms, and launch pages must be opened directly in a browser tab or window. They cannot run inside an iframe.
Embedding these pages can interfere with camera access, screen sharing, and audio playback.
If you have embedded LiveClass into another webpage, make sure sessions open in a separate browser tab or window.
2. Use a Secure HTTPS Connection
LiveClass requires a secure HTTPS connection.
Browsers generally restrict camera and microphone access on insecure connections. LiveClass session links use HTTPS to ensure secure access to these features.
Frequently Asked Questions
1. Which browser should I recommend to session attendees?
We recommend Google Chrome or Microsoft Edge on desktop. Both offer broad feature support, reliable screen sharing, and better compatibility with LiveClass features.
2. Can attendees join a session using a mobile phone?
Yes. Attendees can join using:
Safari on iPhone and iPad.
Chrome or Firefox on Android.
They can watch, listen, speak, and use their cameras. However, screen sharing is not available on iPhone or iPad.
3. A participant's camera is not working. What should they check?
Ask the participant to check the following:
Browser: Make sure they aren't using an in-app browser. Open the session in Chrome, Safari, Firefox, or Edge, as appropriate for their device.
Camera permission: Check whether the browser has permission to access the camera.
Other applications: Close other applications that may be using the camera.
Device selection: Open the room's device settings and make sure the correct camera is selected.
4. Why can't I select a specific audio output device?
Selecting a specific audio output device requires browser support that Safari does not provide. This includes all browsers on iOS.
If you're using Safari or another browser on an iPhone or iPad, audio follows your device's system output settings instead.
5. Do attendees need a LiveClass account to join a session?
No. Attendees don't need an account to join a session. They can open the session link and enter their display name to participate.
6. Will an older browser still work with LiveClass?
Not necessarily. Older browsers may not support all the features required by LiveClass.
LiveClass checks browser compatibility before allowing you to join. If your browser cannot support the required features, you'll see a warning.
If you receive this warning, switch to a current version of a supported browser instead of trying to join with the unsupported one.
