Camera or microphone not working? Diagnose the state before retrying.

Start with the browser indicator

Open the site permission control near the address bar and confirm camera and microphone are allowed for whocam.live. If you changed a denial to allow, reload from a clean page state. Private-browsing modes and embedded browsers may apply separate rules.

On Safari and iOS, also check the operating-system permission for the browser. On Android, confirm the browser app itself can access the camera and microphone.

If your camera works but the picture is hard to see, the guide on how to look better on video chat covers light and framing. A dim picture and a blocked camera need different fixes.

If the problem appears only when you switch apps or move between Wi-Fi and mobile data, use the random video chat on mobile guide to check the phone-specific parts of the setup.

Release devices held elsewhere

Close meeting apps, camera tools and duplicate WhoCam tabs. Bluetooth headsets can change the selected microphone when they connect; choose the intended input before retrying. A physical privacy shutter or mute switch can look like a software failure.

After a failed call, verify the device activity indicator turns off. If it does not, close the page before opening another session.

Separate media problems from network problems

A visible self-preview with no remote video points to a different problem than a black local preview. If both audio and video freeze after connecting, reduce competing network use and try a more stable connection.

Do not clear all browser data as the first step. Begin with the smallest reversible change so you know what fixed the issue.

Know when the device is managed

A school, workplace or family-managed device may lock camera and microphone settings even when the browser shows the usual controls. Repeated retries cannot override an administrator policy. Use a device you are allowed to configure or ask its administrator.

In-app browsers can also behave differently from Safari, Chrome, Edge or Firefox. If permission controls are missing, open whocam.live directly in a supported browser before changing operating-system settings.

Identify whether the local preview exists

A visible self-preview means the browser is receiving video from a selected camera. A black or missing preview points first to site permission, operating-system permission, physical shutter, wrong input or another application holding the device. Start there before changing the network.

If local preview works but the remote image does not, keep the working permission in place. The failure is later in the route. This one distinction prevents many broad resets that erase useful settings without addressing the actual state.

Check site permission and operating-system permission separately

The icon beside the browser address controls access for whocam.live. The operating system also controls whether that browser application may use camera and microphone. Both layers must allow the intended device. Changing one denial may require a clean reload before the page sees it.

Do not grant camera access to unrelated sites while troubleshooting. Confirm the domain and change only the permission needed. If an in-app browser hides site controls, open WhoCam directly in Safari, Chrome, Edge or Firefox before altering wider system settings.

Release hardware held by another process

Close meeting software, camera utilities and duplicate WhoCam tabs. Some systems allow only one process to use a camera at a time; others expose a frozen frame or no input. A physical privacy shutter can create the same symptom as software denial.

After closing competing apps, wait for the device indicator to turn off and reload one WhoCam tab. Reopening several tabs at once recreates the conflict. On managed devices, do not install an unofficial driver or extension to bypass an administrator rule.

Select the intended camera and microphone

Laptops, docks, monitors and phones can expose multiple inputs. Choose the camera that matches the desired preview and speak to confirm the microphone level. A Bluetooth connection may silently switch audio to a headset with a muted or distant microphone.

Connect the headset before entering when possible. If routing changes during a call, end the active state before adjusting several inputs. One change at a time shows which selection solved the problem and prevents a working camera from being reset unnecessarily.

Handle mobile interruption as a state change

Incoming calls, screen lock, battery saving and moving the browser to the background can suspend media. Return to WhoCam and check whether the call is live, ended or waiting for permission. The previous frame may remain visible after an interruption, so look at the status rather than the image alone.

On iOS and Android, verify the browser app has system camera and microphone access. If the page was opened inside another app, move to the full browser. Embedded browsers may expose different permission controls and recovery behaviour.

Diagnose network only after local media works

When self-preview and microphone response work but remote audio or video freezes, reduce competing downloads and try a stable connection. A speed-test headline cannot capture packet loss, changing mobile signal or the other endpoint, so describe the observed state rather than declaring a required speed.

If only audio fails, check mute and routing before resetting video. If both sides fail after connecting, end cleanly and retry once. Repeated rapid Start or Next actions can make a delayed state look like several different faults.

Use the smallest reversible reset

Reload one clean tab after a permission change. Restart the browser only when the tab remains stale. Restart the device only after input conflicts and system permission have been checked. Clearing all cookies and storage should not be the first step because it can remove account state without fixing hardware.

Record what changed and whether local preview, microphone or remote media improved. A controlled sequence produces a useful support report. Randomly toggling every setting may eventually work while leaving no explanation for the next failure.

Know when to stop troubleshooting the device

A school, workplace or family administrator may intentionally block media. Hardware may also be absent or damaged. Do not bypass policy or install software from an unknown prompt. Use a device you are authorised to configure or ask the responsible administrator.

For support, include browser, operating system, selected device, permission state and whether self-preview appeared. Remove passwords, payment details and participant images. The technical facts should make the issue reproducible without creating a new privacy problem.

Verify the fix in a preview before starting another match

After changing permission or input, confirm one local preview and microphone response in a clean WhoCam tab. Do not enter repeated live matches simply to see whether the camera works. A preview isolates the device from participant availability and keeps strangers out of the diagnostic process.

Then start the real flow once. If the failure returns only after connecting, record that boundary. It tells support that device capture works and the problem occurs later, which is more useful than another complete reset.

Keep the working browser and device details with that report.