Google Meet can't find the camera: the order to check on a Mac

A meeting starts in three minutes and Meet reports that it cannot find a camera. The camera is physically there, above the screen, and it worked yesterday. The temptation is to start clicking through every settings pane at once, which is how five minutes disappear without learning anything.

There is a better order, and it comes from the fact that four separate layers have to agree before a picture appears: the hardware, the macOS permission list, the browser's own permission and device list, and the device Meet happens to have selected. Each layer can be ruled in or out with one check. Done in the right sequence, the cause is usually located in under two minutes.

What the wording already rules out

Meet does not use one phrase for every camera problem, and the phrase on screen narrows the search before anything is touched.

The web platform underneath draws the same distinction. MDN's reference for getUserMedia lists separate errors: NotFoundError when no media tracks of the requested type were found, NotAllowedError when permission was refused, and NotReadableError when permission was granted but a hardware error at the operating system, browser or page level prevented access.

What the message says	What it means	Skip straight to
Cannot find a camera, no camera found	The device list came back empty	Step one, the hardware
Camera is blocked	A stored permission said no	Step three, the browser
Camera failed	A device exists but could not be opened	Step two, then what else is using it

The distinction is worth ten seconds of reading because the three point in different directions. An empty list is not a permission problem, and no amount of permission changing will populate it.

The sixty second path, with a call already waiting

When a meeting is about to start, skip diagnosis and go for a picture by any means.

Meet keeps a check for exactly this moment. Google's documentation describes a green room self-check before joining: on the meeting preview, the peripheral devices such as mic, speaker and camera appear at the bottom of the preview tile, and clicking the dropdown arrow selects a different device. Google states the test for each one, and for video it is simply this: click Camera, and if the video appears in the preview tile, the camera works.

That gives two fast moves. Open the dropdown and choose the built-in camera explicitly rather than trusting whatever is selected. If the list itself is empty, close the tab, open the meeting again, and check once more, because a page refused a device on load does not always ask again.

If neither works with a minute left, join with the camera off and say so. A muted tile is a smaller problem than a late arrival, and the rest of this can be done afterwards with no audience.

Step one: does anything on the Mac see a camera

This step separates hardware from software and takes ten seconds. Open Photo Booth or FaceTime and look at the preview.

If a picture appears there, the camera works and the fault is above it, in one of the permission layers. Skip to step two. If nothing appears there either, the problem is not Meet at all, and the next things to check are physical: a privacy shutter or a sticker over the lens, and, for external cameras, the cable and the port.

Apple's guide confirms what the indicator means while doing this. It states that the camera automatically turns on when an app that can use it is opened, that a green light beside the camera glows to indicate the camera is on, and that the camera and the green light turn off when all apps that can use the camera are closed or quit. A green light with no picture in Meet is therefore evidence that something already holds the camera.

For anyone using an external camera, Apple's page on choosing an external camera names where the selection lives in each app: in FaceTime, click Video in the menu bar and choose a camera, and in Photo Booth, click Camera in the menu bar. QuickTime Player offers the same via File, then New Movie Recording. Confirming the external camera works in one of those apps before blaming the browser saves a long detour.

Step two: the macOS list that only shows apps that asked

The system permission for the camera is per application, and the list has a behaviour that causes a lot of pointless searching.

Apple's instructions are to choose Apple menu, then System Settings, then Privacy & Security in the sidebar, then Camera, and to turn access on or off for each app in the list. The sentence that follows is the important one: the list shows apps that have been installed and have asked to use the camera, and if there are no apps in the list, no app that uses the camera has been installed. FaceTime, Photo Booth and other apps that come with the Mac have access automatically.

Two consequences follow for a browser. A browser that has never requested the camera will not be listed, so an absent entry is not proof of a block. And a browser installed recently, or a second browser used only for meetings, needs its own entry here, because permission granted to one browser says nothing about another.

Safari adds a second gate of its own. Apple's page notes that in Safari, allowing a website to use the camera is done by choosing Safari, then Settings, then Websites, then Camera. Granting Safari system access does not grant a site access inside Safari, and both have to be set.

Step three: the browser's own permission and device list

With the hardware and the system layer cleared, the remaining state lives in the browser, and Chrome keeps three separate things here that are easy to confuse.

Google's page on using the camera and microphone in Chrome describes the prompt as offering Allow while visiting the site, Allow this time, or Never allow. An earlier Never allow is sticky, and the practical effect is silence: the prompt stops appearing and the call quietly has no video.

The per-site state is changed from Settings, then Privacy and security, then Site settings, then Camera under Permissions. The same screen lists sites that are allowed and not allowed, allows an existing exception to be deleted so that the prompt returns, and lets a site under the not allowed heading be switched to Allow.

The third thing on that screen is the one worth setting deliberately. Google documents a default camera selection there: under Camera, use the down arrow to select a default camera or switch to a different one. Pinning this to the built-in camera removes a whole class of surprise, because the built-in camera is the one device that never walks away from the desk.

One more possibility belongs here, and it saves time when nothing else explains the situation. Google's page states that for Chrome used at work or school, a network administrator can set camera and microphone settings, and that it may not be possible to modify them. If the settings screen refuses to hold a change, the answer is a request to IT rather than another attempt.

Step four: the camera that left the list

When the list was populated yesterday and is empty today, something was removed from it, and on a Mac the list genuinely changes during the day.

Continuity Camera is the most common cause. Apple's requirements are specific: both devices need Wi-Fi and Bluetooth turned on, both have to be signed in to the same Apple Account, and they have to be within 30 feet, or 10 meters, of each other. The iPhone is expected to be mounted in landscape orientation with its rear camera facing the user.

The removal is equally specific. Apple describes tapping Disconnect on the iPhone and confirming, after which the iPhone is removed as a webcam or microphone option for the Mac. Carrying the phone out of range has a similar effect. If Meet had selected the iPhone, the selected device no longer exists, and the error arrives without anything on the Mac having been touched. To stop the iPhone being offered at all, the switch is on the phone: Settings, then General, then AirPlay & Continuity, then Continuity Camera.

Wired hardware moves for duller reasons. A webcam behind a hub or dock can be renegotiated when another device is plugged into the same hub, and connecting the camera directly to the Mac is a quick way to find out whether the hub is the variable. Virtual camera utilities from recording and streaming software also insert entries into the list, and removing or quitting that software changes what the browser sees.

Fixing the selection inside Meet, not just the browser

Meet keeps a device choice of its own, separate from the browser's default, and this is where a mid meeting recovery happens.

Google's documentation for the settings panel describes it: in a web browser, open the Meet page, click Settings, then Video, and choose the setting to change. Under Camera, select the camera device, and the page states the confirmation to look for, which is that if the camera is working, the video feed appears to the right of Video. The same panel holds send and receive resolution, which are worth lowering when the picture arrives but stutters.

That panel is also the fastest place to recover when a device vanishes during a call. Choosing the built-in camera there restores video without leaving the meeting, and the confirmation is immediate rather than something to discover when the next person speaks.

Keeping the call where it can be found

One arrangement makes all of the above less frequent rather than merely faster to diagnose, and it is about where the meeting runs.

A call in its own window, rather than tab nineteen of thirty, is easier to reload, easier to return to when a device has to be switched mid meeting, and safer to share a screen from. Reloading is the step most often skipped under time pressure, and a window makes it a single deliberate action instead of a hunt through a tab strip. Keeping each web app in a window of its own is what a browser designed around separate workspaces does by default, and the Workspaces page sets out how that separation is held. The list of services that can be kept that way is on the Supported apps page.

What to change first

Read the message, then run the ten second test. Open Photo Booth: a picture there means the hardware is fine and the cause is a permission or a selection, and no picture there means nothing above the hardware will help.

After that, stop leaving the device choice to defaults. Select the built-in camera explicitly in Chrome's site settings and in the Meet preview, and turn off Continuity Camera if an iPhone keeps being chosen unasked. Platform and pricing details for keeping meetings in a window of their own are on the SpaceDeck page.