MY WEBCAM TEST GUIDE

Why is my sound not working on my computer

Computer sound usually fails at mute, device selection, or microphone permission. Tell playback from capture, then test one reversible change at a time.

The essential answer

Sound on a computer fails when playback, capture, or both are broken. Playback is what you hear from speakers or headphones. Capture is what the microphone records. Those paths are independent, so a working webcam picture does not prove the microphone is working, and a working speaker does not prove an app can hear you.

The condition that changes the next step is which layer failed. The hardware may not be detected at all. It may be detected but not chosen as the active input or output. It may be chosen, yet muted, set to zero volume, or blocked by an operating-system or browser permission. Until you know which of those is true, installing new software or resetting the machine is guesswork.

Match the symptom to the layer

What you noticeWhich path is involvedWhat that usually means
Nothing from speakers or headphones, including system soundsPlayback, the output deviceVolume, mute, or the wrong speaker or headset is selected
Video in a call is fine, but nobody hears your voiceMicrophone capture, the input deviceThe mic is muted, the wrong input is selected, or the app lacks microphone permission
The computer never lists the headset, USB mic, or webcam microphoneDevice detectionThe accessory is unplugged, unpowered, unpaired, or not recognized on that port
The device appears in system settings, but one app stays silentAccess permission or that app’s own input pickerThe app is blocked, or it is still pointed at a different mic or speaker

A webcam’s camera and its microphone are separate capture devices. Granting camera access does not grant microphone access. Selecting a webcam for video does not automatically select its built-in mic for audio.

What to change, and how you will know it worked

Change one reversible setting at a time, then repeat the original symptom: play the same clip, or speak the same short phrase in the same app. If the sound returns, stop. If it does not, undo that change when it is safe to do so and move to the next check. The aim is to learn which layer failed, not to apply every fix at once.

Start with mute and volume

Physical mute on a headset, laptop, or webcam often silences capture or playback even when on-screen sliders look normal. Many microphones have their own mute button or a sliding cover that also cuts audio. Hardware volume wheels and keyboard mute keys can sit at zero without an obvious on-screen warning.

  • Unmute the headset, laptop, or webcam hardware control, then speak a test phrase or replay the same clip.
  • Raise output volume above zero in the operating system’s sound settings, and confirm the device is not set to mute.
  • If the problem is that others cannot hear you, raise input or microphone level and turn off microphone mute in both the system settings and the app you are using.
  • Watch for an input meter or a “this app is using your microphone” indicator while you speak. Motion on that meter means the computer is receiving audio, even if the other person still cannot hear you.

Success here is immediate: you hear playback again, or the input meter moves when you talk. If volume was already up and mute was already off, the device is likely undetected, unselected, or blocked.

Confirm the computer can see the device

Open the operating system’s sound settings and look for the speaker, headphone, or microphone by name. On Windows this is under Settings, System, Sound. On macOS it is under System Settings, Sound. On ChromeOS, check Sound in Settings. Linux desktops expose the same idea in their sound or PulseAudio and PipeWire controls, though the labels differ by desktop.

  • If the device is missing, reseat the cable, try another USB port, confirm Bluetooth pairing, or connect a wired headset directly so wireless dropouts are not part of the test.
  • If a USB webcam or mixer needs its own power, connect that power. An unpowered accessory can fail to enumerate as an audio device.
  • Unplug other USB audio gadgets temporarily. Some computers attach the first sound device they find and ignore the one you meant to use.
  • After the device name appears in the system list, repeat the original playback or speaking test before changing anything else.

If the device never appears, the rest of this guide will not help until detection is fixed. That is a hardware, port, or driver-recognition problem, not an app setting. This article does not include verified driver, firmware, or reset steps from the computer or accessory maker; use that maker’s official support process before you reinstall drivers or reset firmware, because those actions can drop custom settings and, on some devices, interrupt other USB or Bluetooth accessories.

Select the active speaker or microphone

Detection only means the device exists. The computer still needs that device marked as the default output for playback, the default input for capture, or both. Apps can also keep their own picker, so the system default and the in-call device can disagree.

  • In system sound settings, set the speakers or headphones you want as the output device, then play the same clip you used at the start.
  • Set the microphone you want as the input device, then speak and watch the input meter.
  • Inside the meeting, browser, or recording app, open its speaker and microphone menus and choose the same devices. Close and reopen the app if the new device does not appear until the next launch.
  • Avoid leaving “same as system” in one place and a named USB mic in another when you are testing; pick one pair and stick with it for the retest.

You will know selection was the problem if sound returns as soon as the matching input or output is chosen, with no other change. If the right names are already selected and the meter still does not move, look at permission next.

Allow the app or browser to use the microphone

Operating systems and browsers treat microphone access as a permission, separate from camera access and separate from device selection. A site or app can see that a microphone exists and still be forbidden to use it. This layer does not apply to ordinary media playback from files or streaming apps that only need speakers; it matters when you are trying to send your voice.

  • On Windows, check microphone access for the app under Privacy and security, Microphone, and confirm both the system microphone toggle and that app’s toggle are on.
  • On macOS, check System Settings, Privacy and Security, Microphone, and enable the browser or meeting app.
  • In the browser, open site permissions for the page that needs the mic and allow microphone access. Reload the page after you change the permission.
  • If you previously clicked Block on a prompt, the page will stay silent until that decision is reversed. Allowing the camera alone will not restore voice.

Retest in the same tab or app after the permission change. Success is a live input meter, a clear “microphone in use” indicator, or the other person hearing you. If permission was already allowed, the remaining causes are usually the app pointing at a different device, an in-app mute, or hardware that still is not actually capturing.

When to stop and escalate

Stop once the original symptom is gone in the same app and on the same device you started with. If playback works in system sounds but fails in one program, keep working in that program’s speaker picker and mute controls. If capture works in the system meter but fails in a call, keep working in that call’s microphone picker and permission prompt.

Escalate when the device never appears, when every app is silent after mute, selection, and permission are confirmed, or when sound fails across a reboot with the same accessory on a known-good port. At that point the next step is the computer maker, the headset or webcam maker, or your IT support, using their official diagnostic and driver guidance. Do not treat a full operating-system reset as the next small step; it is a last resort with broad side effects, including lost local settings, and it is not verified here as a required fix for ordinary mute, selection, or permission failures.

A gap in this guide is device-specific driver, firmware, and factory-reset procedure. Those steps differ by manufacturer and operating-system version, and they are not reproduced here without that official material.