Why does your mic pick up sound from your headphones?

Third round of a ranked match, and your teammate unmutes just to say it: "Dude, I can hear your game. Like, all of it." You can't hear anything wrong. Your headphones are on, your mic is on its arm, the voice chat sounds fine from your side. Yet everyone else on the call gets your footsteps, your gunfire and the announcer, a beat behind what happens on their own screens.

When sound from your headphones is going through your mic, it gets there by one of three routes. It travels through the air from the ear cups to the mic capsule. It travels through a wire or a setting, because the app is listening to the wrong input or a four-pole plug is leaking signal between its contacts. Or it slips past the app's own filters, because echo cancellation is off or the voice-activation threshold is set so low that anything opens it. Each route has a different fix, and the fix for one does nothing for the others. That is why people turn down the volume, see no change, and conclude the mic is broken.

One distinction first, because it decides which page you need. If the people on the call hear their own voices coming back through you, that is echo from the call itself, and why people hear an echo from your mic is the page for you. If what leaks is the room (a fan, a keyboard, a street), you want how to stop your mic from picking up background noise. This page is about the third case: game audio, music, a video, or desktop sounds that you hear in your headphones and that should never reach anyone else.

The two-minute test that tells you which route it is

You do not need anyone else on a call for this. Open any app that records from your mic (QuickTime Player on a Mac, any voice recorder on Windows, or Discord's Mic Test under User Settings > Voice & Video, the "Let's Check" button). Start a game or a video in your headphones at your normal volume, stay silent, and record ten seconds. Then change one thing at a time.

A clean, full-quality copy of the game in your recording gives routing away. Sound that traveled through air from an ear cup sounds small, thin and roomy. Sound that came in digitally sounds exactly like what you hear, because it is what you hear.

Route one: through the air from the ear cups

Every headphone leaks. The question is how much, and how far the leak has to travel compared with your voice.

Open-back headphones are built to leak

Open-back headphones have grilles on the outside of the cups on purpose: the driver breathes freely, and the sound goes out of the back of the cup as well as into your ear. In a quiet room the person next to you can follow the dialogue. A microphone 15 cm from your ear can too. Audio-Technica's own explainer on open-back and closed-back headphones defines leakage as how much audio escapes the headphones, and points out that low leakage matters when recording, because the signal from a wearer's headphones can be picked up by the microphones.

If you wear open-backs for gaming and a sensitive condenser sits on an arm near your face, you have built a small loudspeaker setup next to a microphone. Closed-back headphones seal around the ear and leak far less. Our guide to headphones for podcasting and calls goes through which designs leak least and which ones are comfortable for a three-hour session, because a pair you take off after an hour does not solve anything.

Noise-canceling headphones do not help here. Active noise canceling works on sound coming in from the outside world, toward your ear. It does nothing to the sound your drivers push out.

Distance is the lever, not the pickup pattern

The tempting fix is to buy a mic with a tighter pickup pattern. It helps less than people expect, and the reason is geometry. A cardioid mic rejects sound from behind it. Your headphones are not behind the mic: they sit on your head, a few centimeters from your mouth, in roughly the same direction the mic points. Whatever pattern you choose, the ear cups land inside the zone where the mic is listening. (If you want the full picture of what patterns can and cannot reject, read which pickup pattern is best for a noisy room.)

What works is the ratio of distances. In open air, sound drops by about 6 dB each time the distance doubles. Put the mic 5 cm from your mouth and the cups are maybe 15 to 20 cm from the capsule: your voice gets a head start of roughly 10 to 12 dB from distance alone, before you touch any setting. Put the mic at arm's length, 40 cm away, and your mouth and your ears are almost the same distance from it. The voice loses that head start, so you raise the input volume to compensate, and the leak gets raised with it.

A typical case of a mic picking up game audio looks exactly like this: the mic sits far from the mouth, and the gain is turned up to make the voice loud enough.

Volume and the cups-up habit

Two habits make it worse.

The first is volume. Games are mixed loud, and you turn them up to hear footsteps. Every 6 dB you take off the headphones is 6 dB less leak in the mic, with no downside except that you hear the game a bit quieter. Turning the game down inside the game, rather than the system volume, also leaves voice chat as loud as before, which is the trade most people want.

The second is where you put the headphones when you take them off. Between rounds, people pull the cans down around their neck or drop them on the desk next to the mic, and the game keeps playing. Now the drivers face up, toward the capsule, at full volume, and nothing is covering them. If teammates complain only "sometimes", check whether "sometimes" means "while your headphones are not on your head".

Route two: through a wire or a setting

If the leaked sound does not care about your headphone volume or the mic's position, air is not the route. Something is feeding the output straight into the input.

Mic picking up headphone sound but not voice

This search phrase describes a very specific failure, and it is almost always the wrong input device. The app is not recording your microphone at all. It is recording a loopback device: a virtual input whose only job is to capture what the computer plays.

On Windows, the usual suspect is a device called Stereo Mix or What you hear. Some sound cards expose it as a recording input, and the Audacity documentation on recording desktop audio describes it as exactly that, a loopback option. If it becomes the default recording device (after a driver update, or because you once used it to record a stream), every app that follows the default records the game instead of you. Fix: open the Sound Control Panel, go to the Recording tab, set your real microphone as the default device, and disable Stereo Mix if you do not use it. Then check the app's own input menu too: in Discord that is User Settings > Voice & Video > Voice > Input Device, and per Discord's troubleshooting guide the input and output device pickers live right there.

On a Mac, the equivalent is a loopback driver such as BlackHole, which passes audio from one app to another. People install it to record system audio or to send a game into OBS, then a call app picks BlackHole (or an aggregate device that includes it) as its microphone. The result is the same: the call hears your desktop and not you. Check System Settings > Sound > Input and the input menu inside the app. If you want to keep BlackHole for recording, whether BlackHole is enough to record your Mac's internal audio and what Audio MIDI Setup does explain how to route it without it ending up as your call mic.

"Mic picking up desktop audio" in a stream is often the same mistake in OBS: the desktop audio source and the mic source both exist, and the mic source is set to the desktop device. One look at the source's properties settles it.

Four-pole plugs and the shared ground

Headsets with a single 3.5 mm plug use four contacts. In the CTIA layout that most current devices follow, Audio-Technica lists them as left audio on the tip, right audio on the first ring, ground on the second ring, and the microphone on the sleeve. The headphone channels and the mic share that one ground contact.

When the ground connection is clean, that is fine. When it is worn, dirty, half pushed in, or routed through a cheap splitter, the headphone current flowing back through the ground also shows up as a small voltage on the mic line. Your teammates then hear a faint, slightly harsh copy of your game that tracks your volume knob, does not change when you move your head, and crackles when you wiggle the plug. This is a common reason a cheap 3.5 mm headset's mic picks up headset audio. The fixes are physical: push the plug fully home, try another port, replace the splitter with a better one, or move to a USB headset or a separate USB mic where the headphone and mic signals never share a contact. A Mac's headphone jack accepts this kind of headset (Apple notes that it supports stereo output and mono input), so the plug wiring matters on a Mac as much as on a PC.

Route three: past the call app's filters

Call apps expect some sound to leak from speakers into mics, and most of them run echo cancellation to remove it. It helps to know what that filter actually looks at.

In the usual design, an echo canceller compares your mic signal with the audio the app itself is playing to you, and subtracts the matching part. It knows the far end of the call because it plays it. A game running in another app is not something the call app plays, so the echo canceller has no reference for it and treats leaked game audio as part of your sound. That is why your friends' voices may be cleaned out of your mic while the gunfire still goes through.

Noise suppression does not reliably catch it either. Discord's Krisp FAQ says Krisp removes background noises that are not human voices, such as dogs barking, vacuums or doors slamming. Game music and effects may get reduced; game characters talking are human voices as far as the filter can tell, so they can pass straight through. Our page on how good Discord noise suppression is shows where it stops.

So the call app's settings are worth checking, but they are the last layer, not the fix.

Discord

Go to User Settings > Voice & Video > Voice. Make sure Echo Cancellation is on; Discord's guide lists it, along with Noise Suppression and Automatic Gain Control, as settings to toggle when the voice sounds wrong. Then look at the input mode. With Voice Activity and Automatically determine input sensitivity turned on, leaked game audio can be loud enough to open your mic by itself, so the call hears the game even while you are silent. Turn it off and set the slider by hand: Discord's input modes guide says a manual threshold belongs between your softest speaking voice and everything else your mic hears, so the leak stays below it. If the leak is close to the level of your voice, Push to Talk is the reliable answer: nothing goes out unless you hold the key.

Zoom

Zoom applies noise suppression and echo cancellation by default. Two settings defeat them. In Settings > Audio, Original sound for musicians with high-fidelity music mode disables echo cancellation and post-processing, according to Zoom's own help article; great for a cello lesson, bad if your headphones leak. In the advanced audio settings, echo cancellation has Auto, Low and High levels, and Zoom recommends disabling it only when you use headphones to isolate audio. That advice assumes headphones that do isolate. With open-backs at volume, leave it on. For a full walk through the rest of Zoom's audio panel, see the best Zoom audio settings for a clear voice.

OBS and a noise gate

A noise gate mutes the mic when the level falls below a threshold. OBS's Noise Gate filter starts with a close threshold of -32 dB and an open threshold of -26 dB, and the documentation's rule is to set the close threshold above the noise and the open threshold slightly below your voice. Measure your leak in silence, and set the close threshold a few dB above it.

Be clear about what a gate does: it silences the leak in your pauses. While you talk, the gate is open and the game goes out under your voice. A gate makes the leak less obvious; only distance, volume and closed cups make it smaller. The full settings walk-through is in the right noise gate settings in OBS.

A setup that keeps game audio out of the mic

Here is the chain, in the order that matters. For a leak through the air, the first three lines do most of the work. For a routing leak, line 4 is the whole fix. The rest is cleanup.

1. Headphones      closed-back, on your head, game volume set in the game
2. Mic position    5 to 10 cm from your mouth (about a hand's width)
3. Input level     lower the input volume until your speech peaks
                   around -12 to -6 dB in the meter, no higher
4. Input device    your real mic, never Stereo Mix / BlackHole / aggregate
5. Call app        echo cancellation ON, no "original sound" mode
6. Transmit        Discord: manual sensitivity, or Push to Talk
7. OBS (if live)   Noise Gate, close threshold a few dB above the
                   measured leak, open threshold just under your voice
8. Check           record 10 s of silence with the game running:
                   you should hear nothing, or a faint whisper

Line 3 is where people get stuck. Moving the mic close lets you lower the input volume, which is the whole point, but a close mic with low gain sounds different from what you are used to: more bass from proximity, more breath, sometimes a little dull. The Mac's input volume slider lives in System Settings > Sound > Input. If your calls run through FaceTime or another app that supports Apple's Mic Modes, the Voice Isolation mode in the menu bar's video menu filters background sound around you; it works per app and only in apps that offer it.

Where TunedMic fits, and where it does not

TunedMic is a Mac app that adds a virtual microphone called TunedMic. It takes the sound from your real mic, processes it on the Mac, and any app that lets you choose a microphone (Discord, Zoom, OBS, Telegram, a browser) can use it. Here is what that means for this problem.

TunedMic works on the signal your microphone captures. If your headphones leak into that microphone, the leak is in the signal, mixed with your voice, and the fixes above (closed cups, a closer mic, a lower volume, the right input device) are the ones that remove it. Do those first. No processing chain is a substitute for an ear cup that is spraying a game soundtrack at a condenser capsule.

Where TunedMic helps is the step after. Once the mic is close and the input level is down, your voice is cleaner but often not what you want to sound like. TunedMic's one-minute Sound Check takes more than 30 measurements of your voice, your mic and your room, and builds nine profiles from them, from Natural for calls to Broadcast for streams. What it does to steady noise you can hear for yourself during the free 7-day trial, on your own mic and in your own room. Game audio is not steady noise, which is why the placement steps still come first.

The limits: it needs a Mac with Apple silicon (M1 or newer) and macOS 14 or later. There is no Windows version, so if you game on a PC, everything above this section is your toolkit and TunedMic is not. It costs $19 once, with a free 7-day trial that starts on first launch, opens every feature and asks for no card or account. There are no refunds, so use the trial on a real call.

If you are on a Mac and the leak is fixed but your voice still sounds thin or boomy on the close mic, watch the 38-second video on the home page first to see Sound Check in action, then try it on that mic during the free trial and check the pricing page for what the license covers.

Quick answers

Why can my friends hear my game when I can't hear it in my own recording? Usually because you checked with the game muted or at a lower volume, or because your own test uses a different input than the call app. Test inside the app you use, with the game running at your real volume.

Why do they only hear it when I'm not talking? Your voice masks the leak while you speak; in pauses the leak is all there is. If Voice Activity is on, the leak may also be what keeps your mic open.

Will a headset with a boom mic fix it? Often, yes. The boom puts the capsule a few centimeters from your mouth, and closed headset cups leak less. Our guide to headsets with a good enough mic for work calls compares models. A headset with a single four-pole plug can still pick up electrical crosstalk, so a USB headset avoids one more failure.

Should I monitor my own mic in my headphones? You can, and it is useful for hearing what others hear, but keep the monitor level modest: whatever plays in your headphones can leak back into the mic. How to hear yourself in your headphones while you talk covers it.

Do this before your next match

Open your call app's mic test, start the game at the volume you actually play at, and record ten seconds of silence. If you hear a clean copy of the game, change the input device. If you hear a small, distant version of it, pull the mic in to a hand's width from your mouth, lower the input volume, and record those ten seconds again.