Headset Test

How to use

1. Check the left and right earcups. Set a comfortable volume, then play L and R one at a time. Each tone should come only from the earcup you pressed. Hit Both channels for a centered tone to check the balance.
2. Test the boom mic. Allow microphone access, then talk at your normal call volume. The input bar should move and stay green. If it doesn't move, your mic isn't reaching the browser.
3. Place the fault. A dead earcup or a flat mic tells you where to look next: the cable, the OS sound settings, or the headset itself. Swap the cable or port before you blame the hardware.

Why test this

A headset can fail in two directions at once, and the two hide from each other. A dead left driver never shows up on a call, because voice runs through the mic. A muted mic never shows up in a game, because you only hear output. So you plug in, something sounds off, and you can't tell if the fault is the earcup, the mic, the cable, or a setting three menus deep. This test puts both directions on one screen. Play a tone through each earcup, watch the mic pick up your voice, and you have checked the whole headset in under a minute. Run it on a new headset before the return window closes, on a used one before you buy, or on the headset you already own the moment a call or a game sounds wrong. Seeing output and input side by side is what lets you place the fault instead of guessing at it.

What the results mean

Press L and the left earcup should play clean, with nothing bleeding to the right. Press R to check the right side on its own. Both channels together should land dead center and match in volume. If the left tone plays on the right, your channels are crossed, so check the headset seating, the cable, and any flipped OS setting. If one side is weak or silent, recenter the OS balance slider first. A lopsided slider looks identical to a dead earcup, so rule it out before you suspect the hardware. For the mic, talk at call volume and the input bar should move and stay green. A bar that never leaves gray means your mic isn't reaching the browser: check permissions, the selected input, and whether noise cancellation is swallowing a quiet signal. The sample rate and channel readout confirm the browser sees a live input at all. When output plays clean here but your game or call still sounds wrong, the fault is in that app, not the headset.

FAQ

Both earcups are silent. Is the headset dead?

Usually not. Start with the OS volume and the output device, since a headset that isn't selected plays nothing here. Then try a different cable and port. Only when both sides stay silent across ports and devices is the hardware the likely cause.

The mic works in Discord but reads nothing here. Why?

Two common reasons. Noise cancellation can suppress a quiet input, and many headsets expose two microphones, so the browser may be reading the wrong one. Pick the other device in the selector and talk again. If Discord set its own input, this test reads the OS default instead.

The left tone comes out of my right ear. What causes that?

Your channels are crossed. The headset is on backwards, a cable or adapter swaps the wires, or a mono or balance setting is flipped in your OS. Re-seat the headset first, then work back through the cable and your sound settings.

Can I test a Bluetooth headset?

Yes, though the codec sets the limit. On a call profile the output drops to mono and the mic runs at low quality, which is normal for Bluetooth voice. For clean stereo output plus a usable mic at the same time, a wired or USB headset is the surer test.

Does this test a 7.1 surround headset?

It checks the two stereo channels those headsets play through. Most 7.1 gaming headsets are virtual surround built on a single stereo pair, so this still confirms the real drivers. A true multi-speaker setup routes its center and rear channels in your OS, not here.