← Back to App-Specific Camera Conflicts

App-Specific Video & Camera Conflicts

How to Fix Google Meet Low Frame Rate and Laggy Video Stream

Google Meet's video quality depends on the interaction between your available bandwidth, your device's raw processing power, and Meet's own configurable send and receive resolution settings — a limitation in any one of these three areas can independently produce low frame rate or laggy video. Lowering the send resolution manually, or closing other demanding applications, often restores a noticeably smoother stream.

Your live camera preview appears here

Live Camera Test

Quick Check: Confirm Smoother Performance

Not started — click below to test.

🔒 100% private — runs locally in your browser, nothing is uploaded.

Factors Influencing Google Meet Video Performance

Meet, like most modern video-calling platforms, actively adapts its video quality in real time based on current conditions rather than streaming at one fixed setting regardless of circumstances — this adaptive behavior is generally a feature, not a bug, since it prioritizes keeping the call connected smoothly over maximizing resolution at any cost.

Meet specifically exposes both a "Send resolution" and "Receive resolution" setting, letting you directly control how much your device sends out versus how much incoming video from others it has to process and display — genuinely useful controls when your device or connection is the limiting factor rather than something on the other end of the call.

Beyond Meet's own settings, background applications competing for the same CPU and network resources are a common, often-overlooked contributor — video encoding is genuinely demanding work, and a device already under load from other tasks has less headroom left for smooth video processing specifically.

Step-by-Step Adjustments for Smooth Video Streams

Step 1: Click the three-dot menu → Settings → Video

During an active call.

Step 2: Lower the "Send resolution" setting

As a direct test — a lower send resolution reduces the processing and bandwidth demand on your own device specifically.

Step 3: Close other applications and browser tabs

Not actively needed during the call, particularly anything downloading, streaming, or otherwise using significant bandwidth or CPU.

Step 4: Turn off background blur or virtual backgrounds

If enabled, since this AI-based processing adds meaningful additional CPU load on top of the base video stream.

Step 5: Switch to a wired Ethernet connection

If currently on Wi-Fi, since a wired connection is typically more stable and less prone to the kind of intermittent congestion that causes visible lag. ↑ Confirm improved performance with the widget above.

Checking Your Actual Bandwidth

Running a basic internet speed test shortly before or during a problematic call gives you real, concrete numbers to compare against Meet's general guidance — Google publishes recommended bandwidth figures for different Meet video quality tiers, and comparing your actual measured speed against those figures quickly tells you whether bandwidth itself is a realistic bottleneck or whether the cause lies elsewhere, in device performance or a specific setting.

If multiple people in your household or office share the same internet connection, running a call during a time when others are also streaming or downloading heavily is worth testing separately from a quieter period, since shared connection congestion is a common, easily overlooked contributor to inconsistent call quality.

Browser choice itself can matter too — Meet is a Google product, and Chrome has historically received Meet-specific optimizations first, meaning a persistent performance gap between Chrome and another browser on identical hardware, while not guaranteed, is worth testing for if lag continues despite ruling out bandwidth and background load.

A Few More Things to Check on Windows

How do I reset the Windows Camera app itself?

Go to Settings → Apps → Installed apps, find Camera, open its three-dot menu, and choose Advanced options → Reset. This clears the built-in Camera app’s own cache and settings without uninstalling it, which can fix a stuck, frozen, or permanently black preview even when the underlying device and driver are both working correctly. It only resets that one app — not your camera driver, and not other applications that use the camera.

Could my antivirus be silently blocking my camera?

Many third-party security suites — Bitdefender, Kaspersky, Norton, and ESET among others — include their own webcam-protection feature that runs independently of Windows’ own privacy settings. That means Windows can show camera access as fully permitted while the antivirus software blocks it anyway, at a layer Windows has no visibility into. Check the antivirus program’s own settings, usually under a Privacy, Webcam Protection, or similarly named section, and confirm your browser or conferencing app is on its allow-list.

How do I re-enable my camera in Device Manager if it's disabled?

Right-click the Start button → Device Manager, expand Cameras or Imaging devices, and look for a greyed-out icon or a small down-arrow badge. Right-click that entry and choose Enable device. This is a different action from updating a driver — a disabled device won’t respond to any other fix until it’s explicitly re-enabled here first, so it’s worth checking before assuming the problem is a driver or a permission.

Is Windows' own camera privacy toggle blocking access, separately from anything else?

Windows keeps a system-level camera permission at Settings → Privacy & security → Camera, completely separate from Device Manager, the Camera app, and any antivirus software. This one screen has a master Camera access switch plus a per-app list beneath it — both need to be on. It’s worth checking directly, since a camera can show as fully enabled and working in Device Manager while this toggle silently blocks every app from reaching it.

If you want to check your camera’s actual resolution and frame rate outside of this specific issue, the main webcam test reports both live.