Headphone Test

Introduction

The DeviceHub Headphone Test is a free online headphone check focused on left-right channel isolation, stereo balance, and clarity. It runs in your browser with no download. Generated tones use the Web Audio API and StereoPanner so you can confirm that each earcup receives the correct channel, a critical check for wired and wireless headphones, gaming headsets, and earbuds before meetings, editing sessions, or purchases. Audiophiles verifying a cable repair, gamers ensuring positional cues work, remote workers living in headsets all day, students facing proctored exams with strict audio rules, and DJs confirming cue mixes rely on quick channel checks. The tool is especially helpful when music still “plays” but imaging feels wrong, suggesting partial wiring failure, a mono downmix setting, or a damaged TRRS plug rather than total loss of output. Travelers validating airline adapter tips, esports players confirming footstep directionality, and repair shops documenting pre/post cable solder jobs rely on hard-panned tones that make one-sided failures obvious. DeviceHub keeps the workflow short so a stereo health check fits into the minute before a ranked match or client call.

What this tool does

Wear your headphones as the system default output, then use Left-only, Right-only, Both, and optional alternate L/R playback to verify hard-panned isolation and centered content. A balance control lets you bias output gradually to expose subtle driver weaknesses that hard pans alone might miss. On-page volume works alongside system volume so you have two layers of safety when starting in a quiet room. Status feedback shows which channel mode is active so you are not guessing while troubleshooting. Stopping ends synthesis immediately. Unlike a general speaker suite aimed at room drivers, this page emphasizes ear-specific separation and balance, the questions that matter most when diagnosing one-sided headsets and intermittent earbud dropouts. Alternate L/R timing is long enough to notice dropouts yet short enough to avoid fatigue. Balance sweeps expose drivers that only fail when asked for unequal channel gain. The page stays playback-only: it will not open your microphone while you verify earcups, which keeps the permission surface minimal.

When to use it

Use the Headphone Test after repairing a cable, after buying a new headset, before a long editing or gaming session that depends on stereo imaging, when one earcup intermittently cuts out, and when accessibility mono modes might have been enabled for someone else on a shared machine. Run it when switching between speakers and headphones on a docked laptop to confirm the OS actually routed to the headset. Pair with Stereo Test for broader imaging exercises, with Left Right Speaker Test when you want a speaker-oriented channel drill, and with Bass or Treble tests when the complaint is band-specific dullness rather than missing channels. Use it after washing earpads, after firmware updates on true-wireless buds, when a TRRS splitter behaves differently on CTIA versus OMTP devices, and when a child reports “only one side works” on a shared tablet. Combine with Stereo Test when imaging feels odd even though hard pans seem fine, and with Bass/Treble when channels work but tonality does not.

How it works

User clicks resume an AudioContext and start OscillatorNode tones routed through GainNode and StereoPannerNode. Hard-left and hard-right pan values place energy almost entirely in one channel; centered playback keeps pan near zero for dual-ear content. Alternate modes schedule pan flips on a timer so intermittent cutouts surface without repeated manual clicks. Balance sliders adjust relative channel gains so you can hunt for weak drivers that only fail off-center. Browser autoplay policies require the gesture that starts each mode. Output still follows the OS default device, Bluetooth pairing, USB headset selection, and 3.5 mm jack detection all happen at the system layer before Web Audio hears anything. Virtual surround processors that upmix stereo can blur hard pans; disable them temporarily for an accurate channel read. Nothing is uploaded: tones exist only as local synthesis in your tab. Hard pan values near −1 and +1 drive near-total channel isolation on compliant stereo sinks. Crossfeed in audiophile software and natural open-back leakage can create perceived bleed that is acoustic rather than electrical, note the distinction when interpreting results. Bluetooth multipoint connections sometimes keep a second host partially active; disconnect unused hosts if one ear drops. USB headsets with hardware mute wheels can zero output without changing OS volume, check physical controls before replacing drivers.

Step-by-step instructions

1. Plug in or pair your headphones and set them as the default system output, confirming the OS mixer shows the headset, not speakers, as the active playback device for your browser.
2. Open the Headphone Test, set on-page volume low, and wear both earcups correctly oriented so left and right physical drivers match the channel labels you will hear.
3. Start Left-only playback and confirm sound appears clearly in the left earcup with silence or near-silence on the right when the headset and OS stereo path are healthy.
4. Switch to Right-only and verify the opposite pattern, then play Both to hear centered content in both ears at a similar perceived loudness when balance is centered.
5. Optionally run Alternate L/R and nudge the balance slider slightly to catch intermittent dropouts or weak drivers that only appear after a few seconds on one side.
6. Click Stop, then remove or unpair the headset only after playback ends so you do not leave a tone blasting through speakers if the OS falls back to another device.

Common problems

Both ears during a left-only test often means mono accessibility modes, virtual surround upmix, or a damaged cable collapsing stereo. One silent earcup can be a failed driver, a loose solder joint, Bluetooth one-side pairing quirks, or an off-center balance control. True wireless earbuds should be reseated or returned to the case once if one side drops during alternate mode. Combo TRRS jacks on laptops sometimes need the correct CTIA plug standard for full stereo. Dirty jacks and oxidized connectors cause intermittent cuts that alternate mode reveals quickly. If speakers still play while headphones are connected, the OS did not switch default output, fix routing before trusting channel results. Memory foam seals that are compressed unevenly change perceived loudness per ear and mimic imbalance. Spatial audio APIs on phones may remap stereo into personalized HRTFs that soften hard pans, disable spatial modes for a classic channel check. Damaged solder joints often fail only after heat buildup; alternate mode’s duration helps catch them. If Both mode is quiet but Left/Right are loud, inspect center/balance laws and any “dialogue enhancer” that attenuates correlated content. Firmware updates on true-wireless buds occasionally reset EQ or spatialize modes that blur isolation until disabled; re-check after every update cycle. Shared school Chromebooks may enforce mono for accessibility, confirm the setting before concluding the headset is defective. When documenting repairs, record whether failures appear only after several minutes of alternate mode, which often points to thermal solder issues rather than total driver death.

Privacy explanation

DeviceHub generates headphone test audio locally and does not listen through your microphone during this check. Nothing is uploaded, recorded, or stored. You control playback and can stop instantly. This privacy-first approach matches how DeviceHub handles all media diagnostics, local processing, clear permissions, no hidden capture. Closing the tab ends the AudioContext for the page. Because no microphone permission is requested, this page cannot listen to your voice while tones play. Generated audio never leaves the device as an upload. Stop playback before removing headphones so fallback speakers do not surprise a quiet room.