Google Meet showing a black camera preview, showing “Can’t access your camera,” or showing a frozen or blurry feed — camera problems in Meet specifically (when the camera works in other apps) almost always come down to browser permissions or a competing app that has the camera locked. Let’s check the most common causes quickly before going deeper. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Start: open a new tab → go to https://webcamtests.com → does your camera work there? If yes, the camera hardware is fine. If not, the issue is the camera or its driver, not Meet specifically. That distinction saves a lot of troubleshooting time.
Browser permission — the first thing to check
Chrome, Edge, and Firefox all have per-site camera permissions. If Meet was accidentally denied camera access, it will never prompt again — it just shows no camera. Look for the camera icon in the address bar when you’re on meet.google.com. A crossed-out camera means it’s blocked.
In Chrome: click the lock icon (or crossed camera) in the address bar while on meet.google.com → Camera → “Allow” → reload the page. Or: chrome://settings/content/camera → remove meet.google.com from the “Not allowed” list if it’s there.
System-level camera permission in Windows 11 also matters: Settings → Privacy & security → Camera → “Let apps access your camera” must be On → also check that your browser (Chrome, Edge) is listed and has permission. If Chrome shows as Off here: toggle it On → restart Chrome → try Meet again. Windows 11 added system-level permission controls that sit above the browser’s own permissions.
Another app has the camera locked
Only one application can typically use the camera at a time. If Teams, Zoom, Skype, OBS, or any other camera-using app has the camera active — even in the background — Google Meet can’t access it.
Check Task Manager → look for video conferencing or streaming apps → end any that shouldn’t be running. Better: right-click the taskbar → check the system tray for camera-using apps. After closing them: reload Meet → the camera should appear.
Windows 11 sometimes shows a small camera LED indicator (on laptops with a physical camera-on light) even when no obvious app is using it. If the LED is on with nothing running: check Background apps. Settings → Privacy & security → Camera → scroll down to see which apps have recently used the camera. An unexpected app in that list is the culprit.
Camera selection inside Meet
Google Meet has its own device selector. Click the three dots → Settings → Video → Camera → confirm the correct camera is selected. If it shows “No camera” or the wrong device: change it. This especially matters on laptops with an external webcam connected via USB — Meet might default to the built-in camera while you intended the external one, or vice versa.
Also check: if you recently connected an HDMI monitor or USB device: Windows may have rerouted the camera to a different device path. The camera selector in Meet reflects what Windows currently exposes; sometimes a reconnect of the USB camera resolves it.
Browser cache and Meet session state
A stale browser session can hold on to an old camera permission state or a broken media session. Hard refresh (Ctrl+Shift+R) on the Meet page first. If that doesn’t help: Ctrl+Shift+Delete → clear cached images and cookies → reload Meet → re-grant camera permission if prompted.
Incognito mode is useful as a quick test: Ctrl+Shift+N → navigate to meet.google.com → join a meeting → does the camera work? If yes in Incognito but not normal mode: an extension is interfering (or the profile’s cached permissions are broken). Test each extension by disabling them one at a time.
Our guide on Windows 11 webcam not working covers the device-level camera detection issues when the camera doesn’t work anywhere, and our video call troubleshooting covers the broader video call connectivity issues beyond just camera access. For Meet-specific settings and known compatibility issues, Google’s Meet support page documents browser compatibility requirements and camera troubleshooting steps for each supported browser.
Camera driver reinstall for Meet-specific failures
If the camera works in the Windows Camera app but shows black or “no camera” in Meet specifically: the browser’s access to the camera driver has an issue — not the camera itself. This can happen after a Windows Update that replaced the camera driver, or after a browser update that changed how it interfaces with camera hardware.
Device Manager → Cameras → right-click your camera → Uninstall device → confirm → unplug any external webcam or restart for a built-in → Windows reinstalls the driver on reconnect/boot. After reinstall: test in Windows Camera app first, then Meet. If the Camera app works but Meet doesn’t after driver reinstall: it’s a browser-level issue, not a driver issue.
Hardware acceleration and Meet’s camera rendering
Chrome and Edge use hardware acceleration for rendering video content including camera preview. With certain GPU drivers, hardware acceleration can cause the camera feed in Meet to show as black or to freeze, even though the camera itself is delivering a signal.
In Chrome: chrome://settings → System → “Use hardware acceleration when available” → toggle Off → Relaunch. Test Meet again. If the camera now works: the GPU driver has an issue with video rendering in Chrome. Update the GPU driver from the manufacturer’s site (not Windows Update). After updating: re-enable hardware acceleration in Chrome and test — the newer driver usually resolves the conflict.
Meet in the Google Chrome vs other browsers
Google Meet is optimised for Chrome. In Firefox and Edge it works but with some feature differences. If the camera works in Chrome but not Firefox (or vice versa): the browser-specific camera API implementation differs. Meet uses WebRTC for camera access; older browsers or browsers without the latest WebRTC support have more issues.
If you’re using Firefox and experiencing camera issues in Meet: check that getUserMedia is not blocked (about:config → media.navigator.enabled → must be true). Firefox also has its own camera permission layer at about:permissions → look for camera permissions for meet.google.com.
Edge with Internet Explorer compatibility mode: if Edge accidentally applied IE compatibility mode to meet.google.com (visible as a page icon in the address bar), WebRTC won’t work — Meet requires a modern Chromium rendering mode. Disable IE mode for Meet: edge://settings/defaultbrowser → never use IE mode for that site.
Corporate and school Google Workspace accounts
Google Workspace for Education and Enterprise accounts have admin controls over Meet. Camera access can be restricted at the admin level, or certain Meet features (background blur, camera settings) may be disabled by the organisation’s Google Workspace admin.
If camera permissions show as allowed in Chrome and Windows, but Meet still won’t access the camera on a school or work account: the restriction may be at the Google account level. Check: try meeting with a personal Google account on the same device. If the personal account works and the work/school account doesn’t: the admin has applied a restriction. Report to IT or the school’s tech support team — it’s a Workspace admin policy, not a device issue.
Camera freeze vs black screen vs no camera
Different symptoms in Meet point to different causes:
- Black screen (camera active, no image): usually hardware acceleration or a driver issue — the camera is sending data but the rendering fails. Try disabling hardware acceleration first.
- “Can’t access your camera” error: permission denial (browser or Windows-level) or another app has the camera locked. Check both permission layers and close other camera apps.
- Camera freeze (shows image, then freezes): often a USB bandwidth or power issue on external webcams, or a network/session issue. Try reconnecting the camera or refreshing the Meet session.
- Low quality / blurry: not a camera access issue — check the guide on webcam image quality. Meet may also reduce resolution when bandwidth is constrained.
| Symptom in Meet | Cause | Fix |
| “Can’t access camera” | Permission denied (browser or Windows) | Reset camera permission in Chrome; check Windows Privacy settings |
| Black preview | Hardware acceleration conflict | Disable hardware acceleration in Chrome settings |
| Wrong camera shown | Incorrect device selected in Meet | Meet settings → Video → select correct camera |
| Camera works in Camera app, not Meet | Browser-level access issue | Hard refresh; clear cache; test in Incognito |
| Another app locked the camera | Competing application using camera | Close Zoom, Teams, OBS, etc. → reload Meet |
| Works in Chrome, not Edge/Firefox | Browser-specific WebRTC issue | Use Chrome for Meet; check browser camera permissions |
The two-layer permission model (Windows privacy settings AND browser permissions) is the source of most Google Meet camera problems. Both need to allow access. After that: the competing-app check and the hardware acceleration toggle cover most remaining cases. The webcamtests.com test at the start quickly confirms whether the camera itself is functional, which keeps troubleshooting focused on the right layer.
Meet background blur and virtual background camera issues
Background blur and virtual backgrounds in Google Meet use the camera feed for processing before display. If background blur is enabled and the camera shows black or freezes: the blur processing may be failing. Click the three dots → Turn off background blur → see if the camera feed reappears. Meet’s background processing requires sufficient GPU or CPU resources; on older hardware, enabling it can cause the camera feed to fail.
Similarly: if background blur works but causes the camera to freeze periodically: the CPU/GPU is struggling to process the blur in real time. Disable it, or use a simpler virtual background (solid colour rather than a complex image). On modern hardware (2021 or newer): blur should work without issues. On machines from 2018 or earlier: blur may be too demanding.
Meet camera in the desktop app vs browser
Google Meet is primarily browser-based, but a desktop app (PWA) can be installed. The PWA version shares Chrome’s permissions but behaves slightly differently. If the camera fails in the browser but works in the PWA, or vice versa: the permission contexts differ. Check camera permissions separately for each (the PWA has its own entry in Chrome’s site permissions list at chrome://settings/content/camera).
For the most reliable camera access in Meet: using Chrome browser (not the PWA, not another browser) tends to have the fewest permission conflicts and the best camera driver integration. The PWA is convenient for desktop shortcut access but occasionally adds a permission layer that causes “camera not accessible” errors that don’t appear in the regular browser session.
Camera access notification indicator
Windows 11 shows a small green camera icon in the system tray when a camera is actively in use. This indicator is useful: if the icon appears when you join a Meet call, the camera is transmitting to the browser. If no icon appears: Windows doesn’t see the camera as in use, which means the browser isn’t accessing it (permission blocked or camera not detected).
If the icon appears (camera is in use) but Meet shows black: the signal is reaching the browser but rendering fails — hardware acceleration or a browser issue. If no icon (camera not in use): permission is blocked somewhere. This LED and taskbar indicator check takes 5 seconds and tells you exactly which layer of the problem you’re dealing with.
Testing with Google’s camera diagnostic
Go to https://meet.google.com/diagnose before joining a meeting → this runs Google’s own diagnostic on your audio and video setup. It tests camera access, microphone access, and network quality for Meet specifically, and gives specific error messages rather than just “camera not working.” For users who encounter the same issue repeatedly: running this diagnostic first and noting the specific error code saves significant troubleshooting time.
The diagnostic also tests which camera devices are available and which one Meet plans to use — useful for catching the “wrong camera selected” issue before joining a meeting rather than discovering it mid-call. Running it 60 seconds before an important meeting is reasonable habit for anyone who regularly uses Google Meet professionally.
Camera issues in Google Meet are almost always in one of three places: the permission layer (Windows or browser), the competing-app layer (another app has the camera), or the rendering layer (hardware acceleration with a problematic GPU driver). The webcamtests.com test and the two-layer permission check address the first two quickly; hardware acceleration handles the third. For most users, the issue is resolved within one of those three checks. Our guide on Teams Camera Not Working covers an adjacent issue.
