Confirm the camera with the WebRTC Test
Open the WebRTC Test. Look for Camera: allowed and a live preview. If the preview is blank or the permission is blocked, stay on the page and re-run the test after each fix. Meet usually surfaces this as "Camera is blocked", a spinning loading circle, or a black self-view tile.
Fix 1: Allow the camera for meet.google.com
Meet will not request the device if it was blocked earlier.
- Click the lock icon in the address bar while on Meet.
- Set Camera to Allow. If it shows Blocked, click Reset permissions and reload the page.
- In Chrome/Edge, open Settings > Privacy and security > Site settings > Camera and remove
https://meet.google.comfrom the blocked list. - Reload Meet and check the self-view tile. Then rerun the WebRTC Test.
Fix 2: Grant OS-level camera permission
Even if the browser allows access, the OS can block the camera.
- Windows 10/11: Settings > Privacy & security > Camera. Turn on Camera access and enable access for your browser.
- macOS Ventura or later: System Settings > Privacy & Security > Camera. Toggle your browser to On, then fully quit and reopen it.
- Linux: confirm the camera is detected with
lsusband not disabled by a hardware kill switch.
Fix 3: Choose the correct camera
Dual webcams or capture cards can confuse Meet.
- In the Meet lobby, open More options > Settings > Video and pick the intended camera.
- In Chrome/Edge, visit chrome://settings/content/camera and set your preferred camera as the default device.
- Unplug unused USB webcams to force a clean selection, then retest.
Fix 4: Close apps that already own the camera
The OS blocks sharing a camera between apps.
- Quit Zoom/Teams desktop, Discord, FaceTime, OBS, or any background capture apps. On Windows, check Task Manager for stray camera processes.
- Wait for the camera LED to turn off, reopen Meet, and check the preview.
Fix 5: Disable extensions that interfere with video
Privacy and virtual camera extensions can block or hijack the feed.
- Temporarily disable extensions like WebRTC Control, privacy blockers, Snap Camera/virtual cams, and any user-agent spoofers.
- Open Meet in an Incognito/InPrivate window with extensions off. If the camera works, re-enable extensions one at a time or add Meet to their allowlists.
Fix 6: Update graphics and camera drivers
Outdated drivers cause green frames or failed camera starts.
- Install the latest GPU driver from NVIDIA/AMD/Intel.
- Update the webcam driver: Windows Device Manager > Cameras → right-click your webcam → Update driver. For Logitech or Elgato devices, install their latest utility.
- Restart the browser and rerun the WebRTC Test.
Fix 7: Tweak hardware acceleration only if the preview is glitchy
If the preview is green, flickers, or shows blocks, toggle acceleration to isolate the issue.
- Chrome/Edge: Settings > System and performance > Use hardware acceleration when available → toggle Off → Restart. If it fixes the preview, update GPU drivers and try turning it back On.
- Firefox: Settings > General > Performance → toggle hardware acceleration and test both states.
Fix 8: Clear site data and rebuild permissions
Corrupted cached permissions can block the prompt.
- In Chrome/Edge, open Settings > Privacy and security > Cookies and other site data > See all site data and permissions.
- Search for
meet.google.comand remove stored data. - Reload Meet, allow camera again, and rerun the WebRTC Test.
Verify after each change
Return to the WebRTC Test. You want green checks for Camera and a live preview. Then join a Meet call and confirm your tile appears without delays. If the camera only fails on a work profile, check chrome://policy for camera restrictions and ask IT to relax them.
