App-Specific Video & Camera Conflicts
Why Google Meet Says "No Camera Found" While Online Tests Work
Google Meet runs entirely inside your browser rather than as a separate native app, so "no camera found" while a different browser-based test works fine usually means Meet's own specific site permission was denied independently — browsers save a completely separate permission decision for each individual site, even within the exact same browser and even for two sites that both just use the standard camera API.
What Causes Google Meet Media Enumeration Failures?
It's a reasonable assumption that if one website can access your camera, every website should be able to — but browsers deliberately don't work that way. Each individual site's domain gets its own independent permission entry, meaning a working browser test at one URL says nothing definitive about whether meet.google.com specifically has been granted the same access.
This most commonly happens when a previous visit to Meet resulted in an accidentally dismissed or denied prompt, which the browser then remembers indefinitely for that exact domain until manually reset — regardless of how many other, unrelated sites work perfectly fine with the same camera.
A second, Meet-specific possibility is having multiple Meet tabs open simultaneously, even ones you've forgotten about — since only one tab can typically hold an active camera connection at once, a second tab attempting to join a different call can report "no camera found" purely because an earlier tab already claimed it.
Step-by-Step Solutions
Step 1: Click the padlock or site-info icon in your address bar
While on meet.google.com specifically.
Step 2: Check the Camera permission entry
And confirm it's set to "Allow" rather than "Block" or "Ask."
Step 3: Reload the Meet tab
After any permission change.
Step 4: Check for other open Meet tabs
In any browser window, and close any you're not actively using.
Step 5: Fully restart your browser
If the issue persists, which clears any lingering tab-level camera lock. ↑ Test with the widget above to confirm the camera works outside Meet.
Checking Incognito Mode Separately
If you use Chrome's Incognito mode (or a similar private browsing mode in another browser) for Meet specifically, be aware that camera permissions in that mode are discarded entirely once the window closes, by design — meaning you'll be prompted fresh every single time rather than a permission persisting the way it would in a normal browsing window. This is expected privacy behavior, not something to troubleshoot as if it were broken.
It's also worth checking whether a browser extension, particularly one related to privacy, ad-blocking, or video conferencing itself, might be interfering specifically with Meet's own permission request flow — temporarily disabling extensions via your browser's extensions page and testing again helps rule this out.
If you're signed into multiple Google accounts simultaneously in the same browser, double-check you're actually testing with the account you intend to use for the meeting — camera permissions in Chrome are tied to the browser profile and site, not to which specific Google account happens to be active, but account mix-ups are a surprisingly common source of confusion when troubleshooting Meet specifically.
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 the camera works elsewhere but you’re not sure it’s actually fine, the online webcam test is a fast way to rule hardware in or out.