When another app is already using your camera

It has happened to me four or five times now and it goes the same way each time. The call sets itself up, there is a pause slightly longer than usual, and then instead of a picture I get a failure. Nothing is wrong with the connection. Nothing is wrong with the account. The camera itself is fine, in the sense that it worked an hour ago and will work again in a minute. Something else on the machine simply got there first and has not let go, and the polite fiction that a computer is one thing doing one job at a time falls apart quietly in the background while you sit looking at a message that does not explain any of it.

The first thing worth saying, because I spent an evening being annoyed at the wrong party, is what this site can and cannot tell you when it happens. If the failure is a busy camera you land on a plain error screen — Connection Failed, with whatever short phrase the browser handed over underneath it. That is the honest limit of what a web page knows. The browser refuses to open the device and gives back a terse error; the page shows what it got. It cannot see the list of programs on your computer, so it cannot name the one holding your camera, and no site can.

The short phrase underneath is worth reading rather than dismissing, because it is the browser talking rather than the site, and browsers have their own vocabulary for this. Chrome tends toward something about not being able to start the video source. Firefox says the device could not be allocated or is in use, and sometimes names the error class outright. Safari is the least forthcoming of the three and often gives you almost nothing. None of them will tell you which program is responsible, but any of those phrasings is a strong hint that you are dealing with an occupied camera rather than anything to do with the site, the network or your account.

The distinction that untangles nearly all of this is between two failures that look almost identical from the outside. In one, permission is the problem: the browser has never been allowed to use the camera on this site, or it was refused at some point and remembered. In the other, permission is perfectly fine and the hardware is simply occupied. Same black screen, same sinking feeling, completely different fixes — and trying the fix for one on the other is how people end up in the state where neither works.

Fortunately they are distinguishable here, if you know what you are looking at. A permission problem gets its own treatment: before the browser asks, you see a short panel explaining why the camera and microphone are needed, and if the browser has the permission blocked you get a specific guide pointing you at your settings to turn it back on. That is a designed path with its own screen. If instead you have fallen through to a bare Connection Failed, permission was probably never the issue and you should stop poking at it, because the camera was granted and then found to be unavailable.

Once I stopped suspecting permissions, finding the culprit became routine, and the shortlist is shorter than you would expect. In descending order of how often it has been the answer for me: a video-meeting application that I minimised instead of quitting, hours earlier, in a different context entirely. A browser tab in another window sitting on a page that had already opened the camera. The operating system's own camera app, left open on a phone. A streaming or recording tool with a virtual camera. And once, memorably, a second profile of the same browser running in a window I had forgotten was open behind everything else.

The single most useful diagnostic is not on your screen at all — it is the indicator that the operating system controls, because that one cannot be lied to. Modern machines light something up whenever the camera is genuinely in use: a small green dot beside the camera on a Mac, a green dot in the status bar on a phone, an indicator in the system tray or the privacy settings on Windows. If that light is on while you are not in a call, you have your answer without any further investigation: something is using the camera, and the only remaining question is what.

On a Mac that question has a direct answer — the menu bar tells you which application is currently using the camera if you look at the control centre while the dot is lit. On Windows the privacy settings page keeps a list of recent camera access by app, which is close enough. Failing either, the task manager or activity monitor sorted by memory usually surfaces the offender, because meeting software is not shy about its footprint. It is a thirty-second check that I now do first, and it has saved me from a great many pointless reloads.

The thing I most consistently got wrong was assuming that closing a window closes a program. It does not, and meeting applications are the worst offenders — they are designed to be always ready, so a window with a red button pressed frequently leaves the process alive, sometimes still holding the camera, sometimes only waiting to grab it back. Quitting properly, from the menu or the tray icon rather than the window corner, is the difference between a fix and a five-minute reprieve.

Browser tabs deserve their own paragraph because they are the least visible cause. A tab you navigated away from generally releases the camera; a tab still sitting on a page that opened one does not. Every major browser marks these tabs — a recording dot, a coloured indicator, something small in the tab strip — and scanning the tab strip for it is faster than closing everything at random. That includes windows you have minimised, other browser profiles, and the browser you do not think of as your browser but which is definitely running.

There is a specific version of this trap that follows you around on video-calling sites, and it is worth understanding rather than merely suffering. Ending a call is supposed to tear the camera stream down deliberately, and it does — releasing the device properly matters enough that it is handled explicitly here, because some browsers will otherwise hang onto the hardware after the call is over and refuse to hand it to the next thing that asks. But a tab left parked on a live call page has not ended anything. From the machine's point of view that call is still happening, and the camera belongs to it.

Restarting the computer works, and I want to be honest about why it is the last resort rather than the first: it works because it stops everything, which means you learn nothing and will have the same problem next week. If you are five minutes from a conversation you actually want to have, restart and get on with your evening. If it is the third time this month, spend the extra two minutes finding the process, because the process will otherwise keep coming back at exactly the wrong moment.

A second, quieter failure gets mistaken for this one, and the tell is that there is no error at all. If a virtual camera is installed — the kind that streaming and recording software provides — it appears in the browser's device list looking exactly like a real camera. Select it, or let the browser select it for you, and everything succeeds: the call connects, no error appears, and the picture is black or frozen because the software feeding that virtual device is not running. Everything works and nothing is visible. If you have ever installed streaming software, check which camera is actually selected before you go hunting for a culprit that does not exist.

Phones behave differently from computers and it is worth knowing which one you are holding. On an iPhone the camera is generally handed to whatever is in front of you, so the classic two-apps-fighting scenario is rarer; the failures there are usually a permission that got refused once and remembered, or a native app still up in split screen. Android is more permissive about background access and correspondingly more prone to genuine locking, and it adds its own complication in the form of aggressive battery managers that suspend a browser in the background and leave the camera in an odd state when you return.

External webcams add a physical dimension. Half of the mystery black pictures I have seen on other people's desks were a privacy shutter that had been slid closed and forgotten, which produces exactly the symptoms of a software fault and none of the software. The other half were a hub or cable that had half-disconnected — enough for the device to be listed, not enough for it to deliver anything. Neither generates a helpful error. Both are solved by looking at the thing rather than at the screen.

None of this needs to end the conversation, which is the part I wish someone had told me the first time. A video call does need the camera before it will start at all, so if something else is holding the device the answer is to move the conversation rather than to abandon it. A voice call — placed from the private message screen rather than the video button — never opens a camera in the first place, so it sidesteps the entire problem instead of fighting it. And once you are in a call, the switches for the microphone and the camera live together behind the more button, in a small panel labelled Operate, so you can see at a glance what is on.

What not to do is reload repeatedly, which is precisely what I did for the first twenty minutes of my first encounter with this. Every reload asks the same question of the same occupied device and receives the same refusal, and on some browsers a rapid series of failed requests leaves things in a worse state than a single clean one would have. One reload after you have actually changed something is worth more than fifteen reloads while nothing has changed.

Equally, resist the urge to start revoking and re-granting permissions you have not verified. It feels productive and it converts a busy-camera problem into a busy-camera problem plus a permission problem, which is how a ten-minute annoyance turns into an evening. If the permission panel never appeared and you never denied anything, permission is very unlikely to be your issue, and the settings page is not where the answer is hiding.

The hour I lost was to two browser profiles. I had opened a work profile weeks earlier for something dull, left a window running behind a full-screen editor, and forgotten it entirely. It had been holding the camera since some meeting I could not remember attending. Nothing in any interface pointed at it. I found it by closing windows one at a time and watching the little green dot, which is not clever but is reliable, and which I now do straight away when the indicator says the camera is busy and I cannot say why.

The other one that got me was an auto-start. A meeting application had installed itself into the login items at some point, and every morning it launched, sat in the tray, and helpfully warmed up the camera in case I needed it. It never once occurred to me to look for a program I had not opened. If your camera is busy first thing in the morning with a completely clean machine, look at what starts when you log in — that list has usually grown a great deal more than anybody remembers agreeing to.

There is a fast way to establish whether any of this is about the site you are on, and it takes ten seconds. Open the operating system's own camera app, or the camera preview in your browser's settings. If either one shows a picture, the camera is free and the problem is narrower than you feared. If both fail, no website is going to succeed, and you can stop testing your luck with reloads and go straight to hunting the process. Testing outside the browser first would have saved me most of my accumulated wasted time, and it is the one habit from all of this that I would hand to somebody else without any of the surrounding explanation.

Sometimes it is not your camera at all — the call is fine, the sound is fine, and their picture never arrives. There is nothing you can do from your side except say so plainly and offer to keep talking, and it is worth remembering that a picture which never appears is not necessarily a fault at all. Plenty of people are deliberately keeping the camera covered, and treating that as a technical problem to be solved is its own kind of mistake.

Prevention, in as much as it exists, is three habits rather than a setting. Quit meeting applications rather than closing their windows. Do not leave call pages parked in background tabs when the call has finished. And take two minutes once a year to look at what launches when you log in, because that is where the invisible camera-holders accumulate. Since adopting all three I have not had this happen at a moment that mattered, which is the only measure of success that counts, and it took no configuration whatsoever.

Underneath the annoyance there is something almost reassuring about this particular failure. It is not a fault in the conversation, or the connection, or anything anyone did — it is one program being possessive about a piece of hardware while another waits politely. Once you can recognise the shape of it, the sinking feeling goes away and it becomes a thirty-second errand, which is roughly what it deserves to be.

So if the picture never arrives and the screen offers you nothing, do not read it as a verdict on anything. Look at the indicator light, quit the obvious suspect, close the tab you forgot about, and try again — or start the conversation on sound alone and deal with the camera later. It is free to start either way, and the rest of the guides are here for the next small mechanical thing that gets between you and a decent conversation.