Camera Freeze in Google Meet: When the Picture Stops Mid Call

Twenty minutes into the call the picture stops. Not a black tile and not an error, just the same frame held still while the audio carries on perfectly. Someone eventually says that you have frozen, and by then nobody is sure whether it started ten seconds ago or ten minutes ago.

The same three words also get searched by people who want the opposite: a deliberately frozen frame, so a call can run while they are elsewhere. Both groups end up on the same results page, which is why advice on this subject reads as though it is answering two questions at once. This covers the accidental freeze first, because that is the one that is diagnosable, and then says plainly what the deliberate version involves.

A frozen stream is not a lost permission

The distinction decides where to look, and it is visible from the tile itself.

A permission failure shows an absent picture: a tile with a name or an initial, a crossed out camera icon, or a device that Meet says it cannot find. Nothing was ever delivered.

A freeze shows a picture that arrived and then stopped. The last frame is still on screen, which means the camera was open, the stream was flowing, and something interrupted it while it was running. Permission cannot be the cause, because permission was granted long enough for the frame to appear.

The camera indicator light on the Mac separates the two further. If the green light next to the camera is still on while the picture is frozen, the camera is still open and the failure is downstream of the device. If the light has gone out, the capture itself ended, which points at the device, the cable, or another application taking it.

A third case masquerades as a freeze and is neither. If the audio also stopped, and the other faces stopped moving as well, nothing about the camera is involved. That is a connection that dropped, and Meet will usually reconnect on its own within a few seconds and show a message when it does.

Which side froze

A freeze on a video call happens in one of two places, and asking one question in the chat narrows it immediately: does the freeze show up in your own self view as well, or only for everyone else?

Self view	What others see	Where the freeze is
Frozen	Frozen	Capture. The camera or the app holding it stopped producing frames
Moving normally	Frozen	Encoding or upload. Frames are being captured but not sent
Frozen	Moving normally	Display only. The page stopped drawing, the stream is fine
Moving normally	Only one person sees it frozen	That person's connection, not yours

The second row is the most common of the four and the most misdiagnosed, because the Mac looks completely healthy from the inside. Frames are being captured and encoded, and the upload is the part that cannot keep up. Nothing in the camera settings will change it.

The third row is the one that looks worst and matters least. A page that has stopped repainting its own preview is a rendering problem in the tab, not a broadcasting problem, and switching to the tab and back, or reloading it, clears it. Asking rather than assuming is the whole trick here, and it is worth doing before touching a single setting.

Load is the usual cause

Meet encodes video continuously, and encoding is the part that competes with everything else running on the Mac. A freeze that happens twenty minutes in, rather than at the start, is nearly always a load story: the machine got hot, or something expensive started, or the battery got low.

Google states the requirements in tiers, and they are worth reading as a load budget rather than as a compatibility check. The stated minimum is a dual core processor with 2GB of memory. The minimum recommendation for high quality video alongside other work is a 10th generation Intel i3, i5 or i7 class chip, or an AMD 3000 series Ryzen. The optimal tier lists a high performance CPU such as an 11th generation Intel i5 or i7, an AMD 5000 series chip, or Apple Silicon, together with a 1080p camera and a graphics card with WebGL 2.0 support. A Mac near the bottom of that range will freeze under load without any setting being wrong.

The two settings that reduce the load are in the same place. In Meet, open Settings, then Video. Send resolution is the quality other people see and is the one that costs upload bandwidth and encoding time, and Receive resolution is the quality you see and is what costs decoding time in a large call. Lowering the send resolution is the single most effective change when a Mac freezes for others but looks fine locally. Closing the panel with Done applies it.

Visual effects are the other lever. Background blur and background replacement are processed continuously on the same machine, for the whole call, and they are the first thing to turn off on a Mac that freezes when a second person turns their camera on. Chrome's Energy Saver, under Settings then Performance, switches itself on when the Mac is unplugged or the battery is low and reduces background tab activity, and Google notes that video conferencing and audio playing tabs are not affected by it. That exclusion is genuinely useful to know, because it removes a suspect: a call that freezes on battery is freezing because of thermal and power limits, not because the browser throttled the call.

The camera itself, and what else might have taken it

When the self view froze and the indicator light went out, the capture ended, and there is a short list of reasons.

External USB cameras that draw power from the bus can stop delivering frames without disconnecting cleanly, particularly through a hub shared with a display and a drive. The picture holds its last frame and the device stays listed. Unplugging and replugging restores it, and moving the camera off a shared hub stops it recurring.

An iPhone used as the Mac's camera through Continuity Camera is a wireless device with its own conditions. It stops when it moves out of range, when it is picked up and used, or when it loses charge, and the frozen frame is what remains. For a call that matters, a wired camera or the built in one is the safer choice.

A second application taking the camera produces the same result. Anything that opens the camera holds it while it runs, including a second meeting window, a recording tool, or a virtual camera utility left running from a previous call. The indicator light being on before Meet is even opened is the tell.

Thermal behaviour is worth one line of its own, because it explains the timing. A Mac that freezes reliably at around the twenty minute mark, and never in the first five, is a Mac that has reached the point where it reduces clock speed to stay within its thermal limits. A laptop on a soft surface, a machine with a build or a sync running in the background, and a call with background replacement turned on will all arrive there sooner. Closing the expensive work rather than adjusting the call is the fix in that case, and it is easy to confirm: a call that behaves perfectly with nothing else running was never a Meet problem.

Finally, the device selection itself. In Meet, Settings then Video shows which camera is in use, and if the camera is working the video feed appears to the right of Video. A stored selection pointing at a camera that has since been unplugged will not produce a live picture at all, which is a stopped stream rather than a frozen one, but it is worth checking here because the symptoms get reported interchangeably.

When a frozen frame is what you actually want

A large share of the searches behind these words are not troubleshooting. They are looking for a way to hold a still frame on purpose, so a call continues showing a plausible face.

The honest description of how that is done: browser extensions in the Chrome Web Store and standalone virtual camera applications for macOS both exist for it, and they work either by replacing what the page receives or by presenting a fake camera device that the meeting selects instead of the real one. They are not a Meet feature and Google does not provide one.

Two things are worth knowing before installing either kind. An extension that can replace a camera stream has permission to see what the camera produces, which is a meaningful amount of access to grant to a small tool in exchange for a convenience. And a virtual camera application appears in the camera list as a device, which means the real camera can end up unselected after the tool is removed, producing exactly the empty tile described earlier.

The documented alternative costs nothing and carries no risk: turning the camera off in Meet. A tile with a name on it is a clear signal rather than a frozen mouth, and most calls treat it as unremarkable. If the concern is being seen to be absent rather than being absent, that is a different problem and no software solves it.

The window the call is running in

Any of the above is easier to hold steady when the meeting is not sharing a window with everything else in the working day.

A browser holding thirty tabs is a browser whose memory, processes and attention are divided, and a call is the one thing running there that cannot pause and resume without anyone noticing. Chrome's Memory Saver deactivates tabs that are not in use and reloads them when they are opened again. Google's exemption list means a tab in an active call is protected, and a Meet tab waiting in the join screen is not, which is how a meeting that was open and ready turns into a reloading page at the moment it starts. The list named Always keep these sites active, under Settings then Performance, removes that specific surprise.

A browser that gives each web application its own window and its own container removes the crowding rather than managing it. The call sits in one place, reachable by a keystroke, not competing with a tab strip and not liable to be closed by accident while reaching for something else. The feature list covers the parts that apply here, including one notification bell for everything instead of badges hidden among tabs, and the meeting services are on the supported applications list.

What to change first

Ask in the chat whether the freeze shows in your own self view too, because that single answer eliminates half of the possibilities. Then open Settings, then Video, and lower Send resolution, and turn off background blur or replacement if either is on. Those two changes address the most common cause, which is load rather than configuration.

If the call keeps competing for space with everything else open on the Mac, the window is the thing worth changing, and SpaceDeck was built for that.