The Useful Question
English

You can hear the call, so why can nobody hear you?

Hearing other people confirms that audio reaches your speakers. Your microphone follows a different path, with its own device selection, mute controls, and permissions. Check the physical mute and the call's selected microphone first, then compare the computer's input test with the app's microphone meter. Change one thing at a time, and finish by asking another participant whether your voice is clear.

Find the next useful check

Scroll the table horizontally; arrow keys work when focused.
What you observeWhat to check next
The headset or meeting shows muteRelease the relevant mute when you are ready to be heard
The intended microphone is absentCheck its connection and the computer's input-device list
The computer detects your voice, but the call does notCheck the app's input selection and its permissions
The app meter moves, but people still hear nothingCheck meeting mute, ask whether everyone is affected, then follow the service's call troubleshooting

This guide covers desktop calls, using Windows 11, Apple's current System Settings guidance, and Google Meet in Chrome as representative examples. Labels vary by release, device, language, and organization policy. It is a diagnostic order, not a claim that every app shares the same screen.

Start with the two mute controls you can see

Before unmuting, consider what is audible around you. A test can send room conversations into a live meeting. Use a pre-join screen or a quiet setting where possible, and say a neutral phrase rather than private information.

Check the headset's physical mute switch, inline control, or microphone button according to its own instructions. Then check the meeting's mute state. Do not assume changing one control always changes the other. Microsoft's microphone troubleshooting guide specifically includes a headset's mute button and connection among the first checks.

If the meeting prevents you from unmuting, ask the organizer in chat. Repeatedly changing computer settings will not establish whether an organizer restriction is responsible. For now, keep your diagnosis to what you can observe.

Select the microphone you actually intend to use

Open the call's audio settings and read the microphone name. A USB webcam, a headset, and a laptop's built-in microphone can provide different inputs. “Default” is a selection rule, not a guarantee that the device you are speaking toward is the one in use.

Choose the intended microphone explicitly when that option is available. In a fictional home-office example, headphones play the call correctly while the app is listening to a webcam across the desk. Raising headphone volume would not move the microphone closer. Switching input might help, but this example is not a diagnosis of your device or a tested fault.

Google documents microphone selection in Meet's pre-join and in-call audio controls. On its pre-join screen, select the input and speak while watching the microphone bar. Make sure it responds to your voice rather than only to nearby noise.

The diagram separates incoming sound at the speakers from outgoing microphone sound. The outgoing checks are mute and selected input, computer input, app or browser permission, app meter, and a listener's confirmation. A moving meter is not proof of remote audibility.
Original editorial illustration
Expand the diagram

Scroll within the diagram horizontally; arrow keys work when focused.

The diagram separates incoming sound at the speakers from outgoing microphone sound. The outgoing checks are mute and selected input, computer input, app or browser permission, app meter, and a listener's confirmation. A moving meter is not proof of remote audibility.
Open the diagram at full size

Figure: Original diagnostic map, not a literal software pipeline. Permissions can block access at different stages.

Compare the computer and the call

On Windows 11, open Settings, then System, Sound, and Input. Select the intended device and use the microphone test described in Microsoft's guide. Where offered, record a short neutral phrase and play it back. Check input volume if the voice is very quiet.

On a Mac, Apple's sound-input guide directs you to System Settings, Sound, then Input to select a device and adjust input volume. Available controls depend on the device. Return to the call's own microphone test afterward; changing an operating-system selection does not prove the app is using it.

If the intended input is missing or the system test gets no voice, recheck connection, power, physical mute, and the selected device. If the system test succeeds but the call stays silent, focus next on the app's selected input and access. This comparison narrows the search; it does not prove a particular component is broken.

Give access to the right app and site

For Windows 11, microphone controls are under Settings, Privacy & security, Microphone. Microsoft distinguishes app access from the separate “Let desktop apps access your microphone” setting. Desktop apps do not appear in the individually controlled app list, and that desktop setting is broader than permission for one meeting app. Understand that scope before changing it.

On a Mac, Privacy & Security, then Microphone controls access for listed apps. If you joined through Chrome, check Chrome's access; permission for a separately installed meeting app does not cover the browser session. Follow any request to quit and reopen the relevant app, after saving work and arranging a way to rejoin.

A browser call also needs permission for the particular website. Google's Meet audio guide explains the device, browser, and Meet access layers. In Chrome, inspect site information for the verified Meet page and its Microphone permission. Allow the service you intend to use; there is no need to grant microphone access to every website for this test.

If a work or school setting is locked, stop and ask the administrator. Do not disable security controls or run commands copied from a forum to bypass it. If access now works, repeat the same short test before changing anything else.

A moving bar is only part of the answer

A microphone meter responding to speech is useful evidence that the app is receiving a signal. It does not establish that the far end can hear your words clearly. A microphone-use indicator likewise reports access, not successful conversation.

Ask a participant for a quick voice check. If only one listener cannot hear you, their playback path becomes relevant. If everyone is affected despite your meter moving, check the meeting's mute state and use the provider's next troubleshooting steps. Save work before restarting an app or computer; avoid driver removal during a meeting merely to try something.

The most useful handoff is specific: device name, operating system and app, whether the system test worked, whether the app meter moved, and whether all listeners were affected. That record is more informative than “audio is broken,” and it helps you resume troubleshooting without repeating every step.

Sources and limits

Official guides were checked on October 11, 2026. No hands-on device or live-call test was performed. This guide does not cover mobile interfaces, every headset, advanced audio routing, or guaranteed fixes. Recheck the linked guide for your version before changing unfamiliar settings.