Fix Google Meet Camera Not Working: Complete 2026 Guide

A camera that works in one browser tab and not in Google Meet is almost never a hardware fault. Meet asks the browser for camera permission in its own way, and a blocked permission, a competing app holding the camera, or a wrong device choice inside Meet can each silence the video while the camera itself works fine. This guide shows how to fix Google Meet camera not working by checking the permission chain from browser to meeting, in the order that finds the break fastest.

Video permission has three layers, and all three must agree. The system must allow the browser, the browser must allow Meet, and Meet must select the right camera. A failure at any layer looks identical on screen, a black tile where your face should be, which is why working layer by layer beats changing settings at random.

Why This Fault Appears

Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix Google Meet camera not working starts with that match, because the right first step depends on the symptom in front of you.

Likely cause	Sign you will see	First check
Browser permission blocked	Meet never asks for the camera	Allow camera access for the Meet site
Wrong camera selected	Preview shows another camera	Select the right camera in Meet settings
Another app holding the camera	Camera works alone but not in Meet	Close video and recording apps
Camera disabled in system	No camera listed anywhere	Check system privacy settings
Browser fault	Camera fails in one browser only	Test in another browser
Camera hardware fault	Camera fails in every app	Book a service check

Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.

Before You Open the Case

Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.

When you approach fix Google Meet camera not working, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.

Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.

Google Meet camera visual tied to the Before You Open the Case section of this guide

How to fix Google Meet camera not working in the Right Order

Working through fix Google Meet camera not working in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.

**Check the browser permission for the Meet site.** Look for a blocked camera icon in the address bar, open the site settings for Meet, and set Camera to Allow, then reload the page. A blocked site permission overrides every other setting, including the system camera permission. Test in a fresh Meet call after reloading, since a permission change needs a page reload to take effect. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Select the correct camera in Meet settings.** In Meet, open Settings, Video, and choose the exact camera you intend to use from the dropdown. Laptops often list a built in camera, a monitor camera, and a headset camera, and Meet may default to the wrong one. Watch the preview while you change the selection, since the preview confirms the choice immediately. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Close apps that may hold the camera.** Close video conferencing, recording, and camera apps fully, then rejoin Meet. Many systems allow only one app to own the camera reliably at a time, and a background app can hold it silently. If Meet works after closing another app, that app was the owner, and its camera setting deserves a review. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Test the camera outside Meet.** Open the system camera app or another video app and check whether the camera works there. A camera that works elsewhere points at Meet or the browser, while a camera that fails everywhere points at the system or the hardware. This single test decides whether the remaining steps should focus on the browser or the device. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Restart the browser fully.** Close every browser window, not just the Meet tab, and reopen the browser. A browser process can hold a camera session after a tab closes, and only a full close releases it. Rejoin Meet as the first tab after restart, so another site cannot seize the camera first. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Test Meet in another browser.** Try Meet in a second browser with camera permission allowed, and compare the result. A camera that works in one browser but not another points at the first browser profile, extension, or setting. If it fails in every browser, the fault sits at the system or hardware level. At this stage of fix Google Meet camera not working, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check system camera privacy settings.** On Windows, open Settings, Privacy and security, Camera, and confirm camera access and browser access are on. On macOS, open System Settings, Privacy and Security, Camera, and confirm the browser is allowed. A system level block overrides any site permission, so Meet cannot receive video until the system allows it. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check for a camera cover or kill switch.** Look for a physical camera cover, a keyboard camera switch, or a function key that disables the camera, and check that the cover is open and the switch is on. Many laptops now carry a hardware camera control that no software setting can override. Test again after opening the cover, since a closed cover mimics a permission fault perfectly. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Update the browser.** Update the browser to the latest version and restart it. Meet features can misbehave on an outdated browser, and camera handling changes between browser versions. Update, restart, and test in a fresh Meet call, since an update applied to a running browser may not take effect until restart. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Disable extensions for a test.** Open the browser in a private window or disable extensions temporarily, then test Meet. Privacy, camera, and conferencing extensions can block camera access or inject scripts that break Meet video. If Meet works without extensions, re-enable them one at a time to find the conflicting one. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Clear site data for Meet as a later step.** Open browser settings, clear site data for the Meet site only, then allow camera permission again and rejoin. A corrupted site permission or cached setting can block the camera even when the permission looks correct. Do not clear all browser data at this stage, since that signs you out of other sites for no benefit. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Update camera drivers or system software.** On Windows, update the camera driver through Device Manager, and install Windows updates. On macOS, install system updates, since camera drivers arrive with the system. Restart after updating, then test the camera outside Meet first, so a system fault is proven fixed before Meet is tested again. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.

Google Meet camera visual tied to the How to fix Google Meet camera not working in the Right Order section of this guide

Small Details That Decide the Result

Meet camera faults sit at the intersection of three permission layers, and that layering is why they confuse people. The site permission, the browser permission, and the system permission must all allow the camera, and any one block silences video while the others look correct. Checking the layers from the site inward, rather than at random, finds the blocking layer quickly. This distinction shapes how you should approach fix Google Meet camera not working.

The preview in Meet settings is the most honest test available, because it shows what Meet actually receives rather than what the system claims to provide. A preview that stays black while the system camera app works points at the browser, while a preview that shows the wrong camera points at device selection. Use the preview after every change, since it updates immediately and needs no test call.

Hardware camera controls deserve a physical check before any software step is trusted. A closed privacy cover, a keyboard camera key, or a laptop camera switch can each block video while every software permission looks correct. Owners often forget a cover they closed weeks earlier, and that forgotten cover can waste an afternoon of browser troubleshooting.

The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.

Check the browser permission for the Meet site
Select the correct camera in Meet settings
Close apps that may hold the camera
Test the camera outside Meet
Restart the browser fully

Google publishes Meet camera and browser permission guidance through its official support pages, and the Settings paths in this guide follow those pages. See Google Support for the current Meet camera steps for your browser.

Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.

A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.

Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.

If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.

Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.

Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.

When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.

After any system or app update, retest the feature that previously failed, even if the update notes do not mention it. Updates change drivers, permissions, and background behaviour in ways that release notes rarely capture fully, and a fault that an update quietly fixed can return with the next update just as quietly. A two minute retest after each update turns that uncertainty into a known result.

A second device is the cheapest diagnostic tool you can own for this kind of fault, because it answers the device versus environment question in a single test. Borrow a second phone, headset, remote, or monitor for ten minutes, and run the same test on both. When the fault follows the accessory, replace the accessory. When it stays with the original device, focus the repair there and stop buying accessories.

Google Meet camera visual tied to the Small Details That Decide the Result section of this guide

What Not to Do First

The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.

Reinstalling the browser before checking site permission, which replaces working software for a permission fault.
Testing only in Meet, which leaves a system camera fault disguised as a Meet fault.
Clearing all browser data as an early step, which signs you out everywhere for a site level fault.
Leaving a recording app running during every test, which holds the camera and hides the real cause.
Ignoring a physical camera cover, which no software setting can override.

Avoiding those errors keeps fix Google Meet camera not working short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.

Google Meet camera visual tied to the What Not to Do First section of this guide

Knowing When to Hand It Over

Contact support when the camera fails in every app after a system permission check, a driver update, and a restart, or when the camera shows physical damage. For a Meet only fault that survives a second browser and a site data clear, check Google Meet help resources and test with another account to separate account settings from device faults. Take notes on which apps and browsers you tested.

Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.

Google Meet camera visual tied to the Knowing When to Hand It Over section of this guide

Stopping the Next Occurrence

Review camera permissions after any browser update, keep the browser current, and close recording apps before joining a call. Check the physical camera cover as part of your meeting setup, and test the Meet preview before an important call rather than during it. A short pre call check of permission, device selection, and preview prevents most Meet camera faults.

A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.

Google Meet camera visual tied to the Stopping the Next Occurrence section of this guide

A Slower Second Look at the Same Fault

A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.

During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.

The Last Checks Before You Close the Case

Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.

The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.

Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.

Frequently Asked Questions

Why did this problem start suddenly?

The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.

How long should each fix take before I move on?

Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.

Will clearing data or resetting settings delete my content?

Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.

What if the fault affects only one app, one device, or one connection?

That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix Google Meet camera not working helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.

When should I contact support instead of trying more fixes?

Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.

How do I stop this happening again?

Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.

What Matters Most From Here

Work through fix Google Meet camera not working in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.

Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.

Google Meet Camera Not Working? Fixes in Order (Permission, Browser, Device)