Google Meet says no camera found on a Mac: the permission to check

The meeting has started, the tile is black, and Google Meet reports that no camera was found. The camera worked yesterday. Nothing has been unplugged. The temptation is to restart the Mac, which sometimes helps and teaches nothing, because the message covers several different situations that look identical from the inside of a meeting.

The useful way to read it is as a failed handoff. A camera on a Mac reaches a meeting through three separate gates, and any one of them closing produces the same black tile. Checking them in order takes about two minutes and identifies which one is shut.

Three layers have to agree before a camera reaches a meeting

Google's own troubleshooting for camera problems is organised the same way, which is a hint about where the failures cluster. The article's steps are grouped into allowing Meet to use the camera, allowing the browser to use the camera, allowing the browser on other engines, and allowing the operating system to hand the camera to the browser at all.

Those are the three gates. The innermost is the site permission for meet.google.com in the browser. The middle one is the browser's own default behaviour for camera access. The outermost is macOS, which since macOS Mojave 10.14 requires an explicit tick for each app that wants the camera.

Only the outermost gate produces a silent, total failure. When macOS has not granted the browser camera access, the browser has nothing to offer the page, and the page reports that no camera exists. That is why the phrasing is misleading: the camera is present, the operating system simply is not passing it along.

Google also names the error text that goes with a blocked browser. A message about the camera having failed, rather than being absent, most often means the browser cannot reach the camera. Both messages point at the same list of checks.

Find out whether the camera works outside the browser first

Before touching any settings, establish which half of the problem you are in. Open a built-in camera app such as Photo Booth. Google's own instruction is this test: if the camera's self-preview shows an image there but Meet does not, the problem is permission, not hardware.

If nothing appears in Photo Booth either, the causes are physical or system level. Google's checklist covers the ordinary ones: make sure the camera is connected, on and facing the right way, that the correct camera is selected rather than a screen or another device, that other apps using the camera are closed and Meet is then reloaded, and that the browser is up to date. On laptops with a physical camera cover or privacy switch, that switch is the first thing to check, and some models show an orange, red or amber light while the switch is engaged.

The Photo Booth test is the single most valuable thirty seconds in this whole process, because it splits the problem into two branches that share no solutions.

The macOS permission that produces a total blackout

This is the gate that most often explains a camera that vanished without anyone touching Meet. Google's instructions for macOS are short: open System Settings, go to Privacy and Security, select Camera, and tick the box for the app that is being used for Meet, which may be Chrome, Firefox, Safari or Edge.

Two details make this harder than it reads. The list only contains apps that have already asked for the camera, so a browser that was installed recently, or one that has never successfully requested access, may not be in the list at all until it asks again. And the change takes effect for the app on its next launch, so the browser has to be quit and reopened rather than just reloaded.

There is a related behaviour that catches people who have recently updated macOS. Google notes that on macOS Sequoia, a cautionary prompt appears the first time a meeting is recorded or a screen is shared, and that missing the prompt means going into system settings to grant the permission by hand. Screen recording and camera access are separate permissions in the same settings pane, and granting one does nothing for the other.

The Chrome permission, and why deleting the entry beats toggling it

Inside Chrome there are two levels: the browser default, and the stored decision for meet.google.com.

For the default, Google's instruction is to enter chrome://settings/content/camera in the address bar and, under the default behaviour, choose the option that lets sites ask to use the camera. For the site itself, joining a meeting and clicking the camera control in the address bar allows access, and choosing to allow it on every visit stops the prompt from returning each time.

The part worth copying from Google's article is what to do when Meet has been allowed before and still fails. The instruction is not to toggle the permission. It is to delete the stored entry for https://meet.google.com:443 from the list of sites allowed to use the camera, then expand the entry again and set camera access to allow. A stale stored decision behaves differently from no decision at all, and deleting it forces the browser to ask again.

One more step belongs here, taken from Google's screen-sharing troubleshooting: to reset permissions, closing Chrome is not enough. A full restart is required, and entering chrome://restart in the address bar performs one, reopening the tabs and windows afterwards. Quitting from the menu leaves processes in place that keep the old state.

The other app, and the phone on the desk

On a Mac the most common remaining cause is competition. Google's checklist says to close other apps that use the camera and then reload Meet, and that is usually enough when a video call in another application is still holding it.

The Mac-specific version of this involves a nearby iPhone. Apple documents that Continuity Camera lets an iPhone act as a webcam for the Mac, that it is turned on by default on the iPhone, and that mounting the iPhone in landscape orientation allows apps to choose it automatically. Two consequences follow. A meeting can end up showing the phone's camera rather than the built-in one without anyone asking for that, and if the phone is then carried away, Apple notes that tapping the disconnect button or moving the phone out of Bluetooth range pauses the session or switches to another camera and removes the iPhone from the camera and microphone lists.

A meeting that loses its camera in the middle, on a Mac with a phone on the desk, is worth checking against that behaviour before anything is reinstalled. Continuity Camera can be turned off from the iPhone, under General and then the AirPlay and Continuity settings.

Picking the right camera inside the meeting

Two of the items on Google's checklist are about selection rather than permission, and they are easy to skip because they sound trivial. The first is to choose the correct camera and not a screen or another device. Meet's device list can contain entries that are not cameras at all on a Mac with an external display, a capture device or virtual camera software installed, and a meeting pointed at one of those shows either nothing or a still frame. The second is to make sure the browser is up to date, which Google repeats in every one of its camera, audio and screen-sharing troubleshooting articles for the same reason: capture behaviour changes between browser releases more often than most features do.

External webcams add one more place to look. A camera connected through a hub or a dock depends on that hub being powered and recognised, and a device that appears in the system's camera list but produces no image is usually a power or cable problem rather than a permission one. Testing the same webcam in Photo Booth again, after the hub has been reconnected, separates the two in one step.

The device selection is also worth checking after any meeting that ended badly. A camera chosen once inside Meet is remembered, so a device that was connected last week can still be the selected camera this week, and an absent selected device is one of the ways a meeting reports having no camera at all.

Which check belongs to which symptom

What is seen	Most likely gate	First action
No camera found, and Photo Booth also shows nothing	Hardware, cover or another app holding the camera	Close other camera apps, check any physical cover, test again
No camera found, but Photo Booth works	macOS privacy permission for the browser	Tick the browser under Camera in Privacy and Security, quit and reopen it
A message that the camera failed	Browser or site permission	Reset the default in the browser's camera settings, delete the stored site entry
The wrong camera appears	Device selection or Continuity Camera	Choose the intended camera in Meet, or disconnect the iPhone
It worked, then stopped mid-meeting	Another app took the camera, or the phone left the desk	Reload Meet after closing the other app

When only Meet fails, and every other site is fine

If video calls work elsewhere in the same browser, the stored site decision is the prime suspect, and the delete-and-re-allow sequence above is the fix. Google also links out to equivalent permission pages for Safari, Firefox and Edge, which is worth knowing for a quick cross-check: if the camera appears in a second browser, the hardware and the operating system are both fine and the problem is confined to the first browser's stored state.

There is a structural reason this keeps happening in a busy browser. Camera permission is stored per site, but the camera itself is taken by a process. A single browser window holding a meeting, a second meeting in a background tab, a video in another tab and an extension that opens its own capture surface are all competing for one device, and the losing tab reports that no camera was found. Giving the meeting service a window of its own rather than a tab removes the competition from inside the same process, which is the same reason each web app is better off in its own workspace when several of them want the camera, the microphone or notifications.

What to change first

Run the Photo Booth test to find out which branch the problem is on, then tick the browser under Camera in Privacy and Security and quit and reopen the browser. If the camera works everywhere except Meet, delete the stored meet.google.com entry in the browser's camera settings, restart the browser fully, and allow it again on the next join. Moving the meeting out of the tab strip into a window of its own, which is how SpaceDeck treats each service, keeps the next call from losing the camera to a neighbouring tab.