Google Meet Lagging or Freezing: How to Fix It

Step 1: Use Chrome

Google Meet is engineered for Chrome. Safari and Firefox have noticeably worse Meet performance — Google's WebRTC implementation is optimised for its own browser. If you are on Safari or Firefox and experiencing lag, switching to Chrome alone often resolves it. Ensure Chrome is up to date: three-dot menu > Help > About Google Chrome.

Step 2: Close unused browser tabs

Each open browser tab consumes RAM and CPU cycles even when not in focus. Google Meet needs 2-4 GB of free RAM for stable HD video. With 20+ tabs open, Chrome can exhaust available memory and begin swapping to disk, causing Meet video to freeze and stutter. Close all tabs not needed during the call.

Step 3: Disable browser extensions

Ad blockers, privacy extensions, and network proxies interfere with Meet's WebRTC video streams. WebRTC is the real-time communication protocol Meet uses — extensions that intercept or modify network requests can delay or drop media packets. Disable all extensions before the call: Chrome menu > More tools > Extensions. Re-enable after the call to identify the culprit.

Step 4: Switch to wired Ethernet

Like all WebRTC video apps, Google Meet is sensitive to upload packet loss. A wired Ethernet connection eliminates Wi-Fi jitter and packet loss. If a wired connection is not available, connect to 5 GHz Wi-Fi and position the device within clear line of sight to the router to minimise interference.

Step 5: Lower resolution in Meet

In Google Meet: bottom-right three-dot menu > Settings > Video > Send resolution > Standard definition (480p). This drops the upload requirement from 3.2 Mbps to around 500 kbps and removes lag on constrained connections. You can also reduce Receive resolution to lower the processing load on your device.

Step 6: Check upload speed

Google Meet needs 3.2 Mbps upload for HD video. Run a speed test to verify your actual upload. If upload is below this threshold, Meet will auto-degrade quality but may do so unevenly, causing intermittent freezes. Closing other upload-consuming apps — cloud sync, email, streaming — frees bandwidth for Meet.

Step 7: Close other audio apps during the call

Having Spotify, system audio alerts, or other conferencing apps open simultaneously can conflict with Meet's exclusive access to the audio device. This causes echo, dropouts, and processing delay. Close all other audio applications before joining a Meet call, and ensure Meet is set to the correct microphone and speaker in Settings > Audio.

Frequently Asked Questions

Why is Google Meet so laggy?

Google Meet runs entirely in the browser, which means it competes with all other browser activity for CPU, RAM, and network resources. The most common causes of Meet lag are too many open tabs consuming memory, browser extensions interfering with WebRTC, insufficient upload bandwidth, or an underpowered device where the browser-based video encoding saturates the CPU. Switching to Chrome, closing tabs, and disabling extensions resolves the majority of Meet lag issues.

Does Google Meet work on Firefox?

Google Meet technically works on Firefox but with degraded performance. Google optimises Meet's WebRTC implementation for Chrome — hardware acceleration, codec selection, and bitrate adaptation are all better tuned for Chrome. Firefox users typically see lower video quality, more frequent quality drops, and higher CPU usage for the same call. For important meetings, Chrome is the recommended browser.

How much upload speed does Google Meet need?

Google Meet requires approximately 3.2 Mbps upload for HD video (720p), 1 Mbps for standard definition, and 1 Mbps for one-on-one calls. Group calls with more participants can require up to 3.2 Mbps upload as Meet sends individual streams to each participant. Audio-only Meet calls need around 32 kbps upload.