Using Continuity Camera in Chrome and Google Meet

The short answer

Continuity Camera works with Google Meet in Chrome on a Mac. Chrome does not need special support for it. macOS exposes the iPhone as an ordinary system camera and a separate system microphone, so Chrome lists it like any other webcam. Select it in Meet's camera setting, and select its microphone separately if you want the iPhone to capture your voice. The main limit is platform. Continuity Camera is an Apple feature that pairs an iPhone with a Mac. It does not make an iPhone available to Chrome on Windows, Linux or ChromeOS.

A note on evidence: no tested measurements were available for this guide. That includes audio quality, latency and connection stability. The guidance below comes from how Apple documents the feature and how browsers handle media devices. Inferences are labeled as such.

What Continuity Camera is

Continuity Camera lets a Mac use a nearby iPhone as its webcam. Apple introduced it with macOS Ventura and iOS 16. The phone usually connects wirelessly, though a cable also works. Once connected, the iPhone shows up in the Mac's list of video inputs and in its list of audio inputs. Any app that reads those lists can use it, and Chrome is one of those apps.

Apple's documented requirements may change, so check Apple's current support information. In general they are:

• A Mac running macOS Ventura or later.
• A supported iPhone running iOS 16 or later.
• The Mac and iPhone signed in to the same Apple Account, with two-factor authentication turned on.
• Wi-Fi and Bluetooth turned on for both devices, or the iPhone connected by cable.
• The iPhone nearby, locked, and held steady, typically in a mount.

Setting it up in Chrome and Google Meet

• In macOS System Settings, under Privacy & Security, make sure Chrome is allowed to use the Camera and the Microphone.
• Open Meet in Chrome. When the browser asks, allow camera and microphone access for the site.
• Mount the iPhone near the Mac with its rear camera facing you, then lock the phone.
• In Meet, open Settings before or during a call. Under Video, choose the iPhone as the camera.
• Under Audio, choose your microphone. The iPhone's microphone is listed as its own entry. Choosing the iPhone camera does not switch the microphone for you.
• If the iPhone doesn't appear in the list, reload the Meet tab or restart Chrome. Chrome may not notice devices that were added after the page opened.

What it means for capturing speech

The camera and the microphone are separate choices. Meet will keep using whatever microphone was selected before, often the Mac's built-in mic, unless you change it. This matters because the best spot for the camera is not always the best spot for the microphone.

• Distance: an iPhone mounted at the top of a laptop or monitor is usually about as far from your mouth as the Mac's own microphones. Don't assume the phone will sound better. Test both.
• Noise sources: a phone mounted on a monitor sits away from the keyboard. Inference: that may pick up less typing noise than a laptop's built-in mic. This has not been measured here.
• Processing: Meet can apply its own noise suppression, depending on your account and settings. macOS also offers microphone modes such as Voice Isolation through Control Center. Whether those modes apply to audio going into Chrome has not been confirmed for this guide. Check Control Center during a call to see whether the option appears.
• Consistency: if the wireless link drops, both the video and the iPhone microphone can disappear at once. If you need reliable audio, a wired or built-in microphone avoids that shared point of failure.

The practical way to decide is to compare. Join a test meeting or record a short clip once with the iPhone microphone and once with your usual input. Use the same distance and the same room noise each time, then listen back on headphones. Without published measurements, a test like this in your own room is the most reliable evidence available.

Track lifecycle: what happens when the iPhone disconnects

For anyone building or debugging a browser app, it helps to know that the iPhone behaves like a removable device. Chrome gets it through the standard media capture interfaces. If the phone is unlocked, moved out of range or loses its connection, the device leaves the system list. Any audio or video track opened from it then ends. Meet handles this on its own terms. In your own web app, listen for the end of the track and for device-list changes, and don't assume the device will stay available.

const stream = await navigator.mediaDevices.getUserMedia({ audio: true, video: true });

for (const track of stream.getTracks()) {
  track.addEventListener('ended', () => {
    // Device went away (e.g. iPhone disconnected); prompt the user to reselect
    console.log(`${track.kind} track ended: ${track.label}`);
  });
}

navigator.mediaDevices.addEventListener('devicechange', async () => {
  const devices = await navigator.mediaDevices.enumerateDevices();
  // Refresh camera/microphone pickers from the current device list
  console.log(devices.map(d => `${d.kind}: ${d.label}`));
});

Device labels are only filled in after the user has granted permission. Don't hard-code the iPhone's name, because it matches whatever the user named their phone. Store the device ID the user chose, and fall back cleanly if that ID is no longer in the list.

Gaps in the available evidence

Several questions could not be answered from the material available for this guide. How the iPhone microphone compares with Mac built-in mics or dedicated webcams for speech. The audio and video latency over wireless versus wired connections. Whether macOS microphone modes affect audio sent to Chrome. Test these yourself, or check current Apple and Google documentation, before relying on them for important calls.