Browser Permissions & WebRTC Diagnostics
Why Your Browser Webcam Test Shows 0 FPS or a Frozen Screen
0 FPS or a frozen browser webcam stream is most often a GPU hardware-acceleration conflict rather than a genuine camera fault — the video pipeline stalls somewhere between decode and render. Checking chrome://gpu for a blocklisted or disabled status, then toggling hardware acceleration off as a direct test, resolves the majority of cases.
Primary Causes of 0 FPS WebRTC Video Stream Stalls
Modern browsers offload video decoding and rendering work to your graphics card whenever possible, since it's dramatically more efficient than doing the same work purely in software on the CPU. When that GPU path has a driver conflict, an outdated driver, or hits a known compatibility issue Chrome has specifically blocklisted, the video pipeline can stall completely — the camera itself is often working perfectly fine, but the rendering pipeline responsible for actually displaying its frames on screen isn't functioning.
This produces exactly the frozen, 0 FPS symptom described here: the permission was granted, the stream technically connected, but no new frames ever actually paint to the screen. A single static frame or solid black rectangle, rather than an error message, is the typical visual result.
Step-by-Step Fixes for Frozen Browser Webcam Streams
Step 1: Check
chrome://gpu in a new tab. Look at the "Graphics Feature Status" section for any entry related to video decode showing "Disabled" or "Blocklisted" rather than "Hardware accelerated."
Step 2: Try toggling hardware acceleration off as a direct test.
Settings → System → turn off "Use graphics acceleration when available," then restart Chrome fully.
Step 3: Update your graphics drivers
Through your GPU manufacturer's own updater (NVIDIA, AMD, or Intel) rather than relying solely on Windows Update, which often lags behind the manufacturer's own releases.
Step 4: Close other GPU-intensive tabs or applications
That might be competing for the same graphics resources, particularly other video calls, games, or video editing software running simultaneously.
Step 5: Restart Chrome completely
(not just the tab) after any of the above changes, since GPU process state doesn't always refresh with a simple page reload. ↑ Test with the widget above.
Two Less Obvious Causes Worth Ruling Out
It's also worth ruling out a simple resource-exhaustion cause before assuming a driver conflict specifically: an unusually large number of open tabs, especially several other tabs also using the camera or heavy JavaScript, can occasionally starve the tab actually trying to render your video stream of the processing time it needs, producing the same frozen appearance for a completely different, non-driver-related reason.
If frozen frames happen specifically and consistently after your laptop has been running for a long stretch, check whether thermal throttling might be a contributing factor — search your system's thermal management settings, or simply feel whether the laptop is running unusually hot, since sustained high temperatures can cause a graphics driver to become unstable in ways a fresh, cooler boot does not reproduce.
Testing the same camera in a second, different browser is also a genuinely fast way to narrow down whether the freeze is specific to Chrome's own rendering pipeline or reflects a more fundamental driver or hardware issue that would show up anywhere — if a second browser streams smoothly, that points the investigation squarely back at Chrome's own settings rather than your graphics hardware in general.
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.