Guides2026-05-237 min read

Why Can't I Hear Myself on Mic? How to Enable Mic Monitoring

Can't hear your own voice through your headphones while recording or on a call? That's mic monitoring (sidetone). Here's how to enable it on Windows, Mac, and in your apps — and when not to use it.

N

By Naren · Founder, MicCheck Online

Software Engineer · Last reviewed:

Diagnose the issue yourself in seconds — no download needed.

Mic Test

You're recording a podcast, gaming with friends, or on a call — and you want to hear your own voice in your headphones in real time. You can't. This feature is called mic monitoring (or sidetone on headsets), and it doesn't work automatically on most setups. Here's exactly how to enable it and why it's disabled by default.

What Is Mic Monitoring?

Mic monitoring routes your microphone's live audio signal back to your headphones or speakers so you can hear yourself as you speak. Without it, most people raise their voice without realising it — because you can't gauge your own volume when you can't hear yourself relative to the audio around you.

The same feature is called sidetone on gaming headsets and direct monitoring on audio interfaces. They all do the same thing: feed the mic signal back to your ears with near-zero delay.

There are two ways to achieve this: hardware-level (built into your headset or interface) and software-level (your OS routes the audio). Hardware is always lower latency. Software introduces a small delay (typically 10–30ms) which can feel like an echo if it's too long.

Method 1: Windows "Listen to This Device" (Software)

Windows has a built-in mic monitoring feature hidden in the advanced recording settings. It routes your microphone input to your default audio output device.

  1. Right-click the speaker icon in the taskbar
  2. Select Sound settings → scroll down and click More sound settings
  3. Go to the Recording tab
  4. Double-click your microphone
  5. Click the Listen tab
  6. Check Listen to this device
  7. In the dropdown, select your headphones as the playback device
  8. Click Apply → OK

You should immediately hear yourself speaking. Adjust your system volume to set the monitoring level.

Latency warning: Windows software monitoring introduces around 20–40ms of delay. This is long enough to feel like a slight echo. If it feels distracting, switch to Method 3 (hardware) instead.

To turn it off: Uncheck "Listen to this device" in the same menu.

Method 2: macOS Input Monitoring

macOS does not have a built-in software mic monitoring toggle like Windows. The cleanest options are:

Option A — QuickTime Player:

  1. Open QuickTime Player
  2. Go to File → New Audio Recording
  3. Click the dropdown arrow next to the record button
  4. Select your microphone as the input
  5. Drag the volume slider in the QuickTime window up from zero
  6. You will now hear your mic through your speakers or headphones

Option B — Audio MIDI Setup aggregate device:

  1. Open Audio MIDI Setup (Applications → Utilities)
  2. Click the + button → Create Aggregate Device
  3. Check both your microphone and your output device
  4. In your DAW or audio app, select this aggregate device
  5. Enable direct monitoring in the app

Option C — Use a USB audio interface (see Method 3 below — interfaces handle this at hardware level on both Windows and Mac).

Method 3: Hardware Direct Monitoring (Best Quality, Zero Latency)

If you use a USB audio interface (Focusrite Scarlett, Behringer, SSL, etc.) or a gaming headset with a hardware monitoring knob, this is the correct way.

USB audio interfaces:

Most interfaces have a Direct Monitor button or a Mix knob on the front panel. The Mix knob blends between the live microphone input (Direct) and the computer playback (USB). Turn it toward Direct to hear more of yourself, toward USB to hear more playback audio.

This path never goes through the computer's OS — the signal goes from mic capsule → preamp → your ears entirely in hardware. Latency is effectively zero.

Gaming headsets with sidetone:

Many gaming headsets (SteelSeries, HyperX, Logitech G, Astro) have a hardware sidetone feature controlled through their companion software or a physical knob. Look for "Sidetone," "Mic Monitoring," or "Voice Feedback" in your headset's settings software. This also runs at hardware level with zero latency.

Method 4: App-Level Monitoring

Some recording and communication apps offer their own mic monitoring:

Discord:

Settings → Voice & Video → scroll to Input Sensitivity → enable Mic Test to hear yourself temporarily. Discord does not have a persistent monitoring toggle — the mic test runs for 30 seconds.

OBS Studio:

In the Audio Mixer, click the gear icon on your microphone source → Advanced Audio Properties → set Audio Monitoring to Monitor Only or Monitor and Output. This routes the mic through your desktop audio output.

DAWs (Audacity, GarageBand, Reaper):

Most DAWs have a software monitoring toggle per track. In Audacity: click the microphone dropdown → enable Software Playthrough. In GarageBand: enable the Monitor button (headphone icon) on your track.

Why Mic Monitoring Is Off by Default

Mic monitoring creates an echo problem on calls. If your microphone is monitoring back to your speakers (not headphones), the speaker output is picked up by the mic and retransmitted — creating an echo loop for everyone else on the call. This is why it's disabled by default in conferencing apps.

Rule: only use mic monitoring with headphones. Never monitor through open speakers during a call.

How to Check Your Mic Is Working Before Enabling Monitoring

Before adjusting monitoring settings, confirm your microphone is actually capturing audio correctly at miccheckonline.com/mic-test. If the level meter moves when you speak, the hardware is fine — the issue is only in the monitoring routing. If the meter shows nothing, fix the mic detection problem first.

Common Monitoring Problems

I hear myself but with an annoying echo delay:

Software monitoring latency is too high. Switch to a USB interface with direct monitoring or a headset with hardware sidetone. Software paths through Windows typically have 20–40ms delay.

I can hear myself but so can everyone else on the call:

You're monitoring through speakers, not headphones. The mic picks up the speaker output and sends it to call participants. Plug in headphones and the echo disappears.

I enabled "Listen to this device" but hear nothing:

Check that the correct playback device is selected in the Listen tab dropdown. Also check that your headphones are set as the active output device in Windows Sound Settings.

The monitoring volume is too quiet even at 100%:

Windows monitoring volume is tied to the microphone's input gain. Increase the microphone input volume in Sound Settings → your mic → Device Properties. The monitoring level scales with the input level.

Test your devices now — free