Headphone Test

Headphone Tester - Test Your Headphones Online Free

Test your headphones instantly with this free online tool. Confirm both earpieces work, verify left and right channels are on the correct sides, sweep through bass to treble frequencies, and dial the volume up or down to hear how your cans handle low and high levels — all in your browser with nothing uploaded. Uses the Web Audio API to generate clean test tones locally on your device.

Get Easily Started With Your Test

1. Press Play Left — you should hear a tone only in the left earpiece. If you hear it on the right, your headphones are on backwards or the cable is wired in reverse.
2. Press Play Right — you should hear a tone only in the right earpiece.
3. Press Auto L ↔ R to alternate sides automatically every 1.5 seconds. Useful for a hands-free check.
4. Try each frequency preset (100 Hz bass, 440 Hz A4, 1 kHz mid, 4 kHz presence) to hear how your headphones handle the low-to-high range.
5. Adjust the volume using the slider or + / − buttons. Start low — headphones can be much louder than laptop speakers.

Why Test Your Headphones Online

Headphones can fail in ways that are easy to miss. A wire inside the cable breaks and the left channel goes silent only when you rotate your head. A driver diaphragm develops a hairline tear and the bass distorts only at high volume. The channels get swapped when a replacement cable is soldered wrong. An earbud's adhesive seal fails and the right driver plays at half the volume of the left. You won't notice any of these in ordinary use until you are already three minutes into a mix or a phone call.

This tester exposes each problem directly. The left/right tone check verifies channel routing and driver health. The frequency presets let you sweep across the audible range to find dead spots, driver rattles, or distortion that only appears in certain bands. The volume control lets you verify smooth response at low AND high levels — some cheap headphones sound fine quiet but break up at anything above 60% volume.

Everything runs through the Web Audio API: AudioContext → OscillatorNode (pure sine wave) → GainNode (volume) → StereoPannerNode (L/R routing) → your speakers. No audio files are downloaded; every tone is synthesized in your browser tab.

Common reasons to run a headphone test:

• Pre-purchase check on used headphones — flag dead channels or driver distortion before keeping them
• Post-repair verification — confirm a recable, driver swap, or solder repair is correct before reassembly
• Channel-swap diagnosis — surround mixes sound wrong because L and R are reversed somewhere in your chain
• Frequency-response spot check — find dead bands or rattles in cheap earbuds
• Volume balance test — verify both channels are equally loud at the same volume setting
• New DAC or amp — confirm the entire signal chain (source → amp → headphones) passes clean audio
• Warranty evidence — if one side is genuinely dead, a recording of the test with one channel silent is strong RMA evidence

How to Test Your Headphones in 3 Simple Steps

Step 1: Plug in and set a low starting volume

Connect the headphones, put them on the correct way (most headphones have L/R letters printed on the inside of each earcup or on the headband), and make sure your OS volume and this page's volume slider are both low to start. In-ear headphones can hit 100+ dB SPL at max volume — start quiet and raise gradually.

Step 2: Run the left/right check

Press Play Left. You should hear the tone in the left ear only. Press Play Right. The tone should move to the right ear. If either channel is silent, or if left and right are swapped, the problem is one of:

• The headphones are on backwards — check L/R markings
• One driver is dead (no sound from that side) — usually cable or driver failure
• Left and right are wired in reverse — common after a cable replacement, or on cheap headphones straight from the factory
• Your OS has a balance slider shifted one way — check System Settings > Sound > Output > Balance

Step 3: Sweep frequencies and volume

Click each frequency preset in turn (100 Hz, 440 Hz, 1 kHz, 4 kHz) with the side set to Both. Listen for:

• Distortion or rattle — especially at 100 Hz on cheap headphones; usually indicates a loose driver or a damaged diaphragm
• Uneven level between frequencies — a tone that is much quieter than the others can indicate a frequency-response dip (normal on some budget models) or a damaged driver
• Channel imbalance — one ear noticeably louder than the other at the same preset suggests the drivers are not matched (one may be damaged)

Then raise the volume gradually with the + button and listen for distortion appearing only at high levels. Reduce with − and make sure the tone remains clean all the way down to 10% without disappearing entirely.

What the Headphone Tester Checks

Left/Right Channel Routing

The most common real-world failure is not a dead channel — it's a swapped one. When someone replaces the cable on a pair of Sennheiser HD 600s or wires up a custom IEM cable, the tip/ring conductors can easily be reversed at the 3.5 mm plug, sending the left signal to the right driver and vice versa. In stereo music the imbalance is subtle. In a surround mix for a game or film, it is immediately disorienting — gunfire from the "left" comes from the right, and spatial cues invert.

The StereoPannerNode in Web Audio pans the test tone hard left (pan = −1) or hard right (pan = +1). If you hear the left tone in your right ear, the problem is definitely before the browser — either the headphone cable, a swapped TRS plug, or an OS balance setting. If you hear it correctly in the browser but wrong in a specific application, that app has its own channel-swap bug (it happens; Microsoft Teams has shipped stereo bugs in the past).

Driver Functionality

A driver that does not produce sound at all is immediately obvious during the left/right test. A driver with partial damage can be harder to spot — it may produce sound, but at a reduced level, or only in certain frequency ranges. Running through all four frequency presets while comparing left against right catches most of these partial failures.

If one side sounds subtly quieter than the other, run the Play Both tone and move the tester's volume slider. Uneven response that stays consistent across volume levels is a driver imbalance. Uneven response that only appears at higher volumes usually indicates driver fatigue or a cone limit issue.

Frequency Response Sanity Check

Four presets cover the audibly distinct bands most listeners care about:

• 100 Hz (bass) — low-end response. Headphones with poor bass extension will sound thin or produce a buzz instead of a clean tone
• 440 Hz (A4 reference) — the standard orchestral tuning pitch; should sound clear and pure on any healthy headphone
• 1 kHz (mid) — the midrange where vocals live; should be the cleanest-feeling tone on most headphones
• 4 kHz (presence) — where consonants and snare attacks sit; some headphones have a peak here that makes the tone sound harsh

This is not a full frequency-response measurement (that requires a calibrated microphone in a coupler), but it is enough to catch major dead spots and obvious resonances in less than a minute.

Volume Handling

The volume slider runs from 0 to 100 and maps linearly to the gain node's output, capped at 50% of full scale for safety. That gives you plenty of range to test whether the headphones distort at high levels while protecting your hearing if a setting is accidentally pushed to maximum.

Good healthy headphones produce a clean tone across the whole slider range. Cheap earbuds often break up at 70–80% and introduce audible distortion, buzz, or crackle. If distortion appears at a specific slider position, try that position at a different frequency — if distortion appears everywhere at 80%, the driver is reaching its excursion limit. If it only distorts at 100 Hz at 80%, the low-frequency driver or cone is weak.

Auto-Play Mode

The "Auto L ↔ R" button cycles the test tone between left and right every 1.5 seconds. Useful if you want to put the headphones on, adjust their fit, and verify both sides sound matched hands-free. Click it again to stop.

Troubleshooting Common Headphone Problems

One earpiece is silent

In order from most to least common:

1. Cable or plug failure — twisting or plugging/unplugging the cable at the earpiece end reveals intermittent contact. Wiggle the cable where it meets the earpiece and the 3.5 mm plug; if sound comes and goes, the strain relief is worn out. Replace the cable (detachable-cable headphones) or re-solder the connection (soldered-cable headphones).
2. Balance slider in the OS — Windows: Settings > System > Sound > Properties > Levels tab > Balance. macOS: System Settings > Sound > Output > Balance slider. Any position other than dead center causes one side to be quieter or silent.
3. Dirty jack — dust or pocket lint in the 3.5 mm jack can make one channel intermittent. Unplug, blow out the jack with compressed air, and firmly re-seat the plug.
4. App-level audio routing — some calling apps route to mono on one channel only when sharing screen; this is an application bug, not a hardware issue. Test in a different app to confirm.
5. Driver failure — the actual speaker inside the cup is damaged. On glued-together consumer headphones this usually means replacement; on serviceable models (Sennheiser HD 600, many ATH-M50x versions) the driver can be swapped.

Channels are swapped

• Headphones are on backwards — check L/R markings on the inside of each earcup
• Cable was soldered wrong — the TRS plug's tip and ring were reversed; easy fix if you can re-solder, or return the cable for warranty
• Source device is swapping — rare but real on some sound cards; check the OS channel mapping in advanced audio properties (Windows)

Distortion at high volume

Not always a hardware fault. Check in order:

1. OS volume at or near 100% — raising the OS output to max and using the app volume to reduce makes any residual noise more audible. Set OS volume to ~70% and use app volume for fine control.
2. Source signal clipping — the audio source itself may be clipping before it reaches the headphones. The pure sine tones in this tester do not clip; if you hear distortion here, the fault is downstream of the browser.
3. Driver reaching its limit — budget headphones reach mechanical excursion limits at high levels and distort. The only fix is turn it down or upgrade.
4. Bluetooth codec — SBC-encoded Bluetooth can produce noticeable compression artefacts at high volume. If your headphones support AAC, aptX, LDAC, or LC3, switching codec in OS Bluetooth settings can help.
5. Loose driver inside the cup — a driver that has partially detached from its housing produces rattle on bass-heavy content. Carefully opening the cup (on serviceable models) and re-gluing is the fix.

Bluetooth headphones sound muddy or delayed

• Codec downgrade — many headsets use low-bandwidth codecs (HFP for calls, SBC for music) as a fallback; verify you are on the best codec your headset supports
• Crowded 2.4 GHz band — other Wi-Fi and Bluetooth devices compete for the same spectrum; try moving closer to the audio source or disabling nearby Wi-Fi briefly
• Battery low — some Bluetooth headsets degrade audio quality at low battery to extend runtime
• Wrong connection mode — macOS in particular can put Bluetooth headsets into "headset" mode (HFP 16 kHz mono) instead of "headphones" mode (A2DP stereo). System Settings > Sound > Output > select the A2DP-mode entry

No sound at all even when OS volume is up

• Wrong output device selected — the OS may be routing audio to a monitor's speakers or an HDMI output; select the headphone device explicitly
• Exclusive-mode lock — some applications can take exclusive control of the audio device, leaving other apps silent. Close other audio apps and try again.
• USB DAC not initialised — if your headphones connect through a USB DAC, unplug and re-plug the USB connection and confirm the DAC shows up as an output device
• Audio service not running — Windows: Services > Windows Audio > Start. macOS: killall coreaudiod in Terminal forces a re-init.

Bass sounds weak

• Seal problem — over-ear and in-ear headphones lose significant low-end when the ear seal is broken. Press both earcups lightly against your head; if the bass suddenly appears, the seal is the issue (reseat, replace pads, or try larger in-ear tips)
• EQ preset in the OS or app — check Windows Sonic, Apple Spatial Audio, or app-level EQ
• Source is compressed to mono — some podcasts and phone calls collapse stereo to mono and roll off low frequencies to save bandwidth
• Small driver size — earbuds with 6 mm or 8 mm drivers simply cannot move enough air to reproduce deep bass; this is a hardware limit, not a fault

Privacy and Safety

This tester runs entirely in your browser. Every test tone is synthesized on your device using the Web Audio API — there is no audio file download and no analytics collecting playback patterns. Open the browser's developer tools (F12 > Network tab) while running tests and you will see zero audio-related network requests.

On the safety side: the volume slider is capped at 50% of full digital scale on purpose. Even so, in-ear headphones connected to a laptop at full OS volume can still exceed 100 dB SPL, which causes hearing damage within minutes. Always start with the OS volume and the page slider low, raise gradually, and take breaks. If the tone starts to feel loud enough to be unpleasant, you are already at a level that can damage your hearing over extended listening.

Frequently Asked Questions

Does this headphone tester work with any headphones?

It works with any headphones, earbuds, earphones, or speakers the operating system recognises as an audio output. That includes 3.5 mm wired, USB, Bluetooth, and HDMI/DisplayPort audio. The test does not care about brand or model — Apple AirPods, Sony WH-1000XM series, Bose QuietComfort, Sennheiser, Audio-Technica, Beats, HyperX, SteelSeries, Razer, JBL, Shure, and every other headphone brand all work identically because the test is produced at the browser and OS level, upstream of the headphone.

The page must be on HTTPS for audio generation to work reliably in all browsers.

Will this work on my phone or tablet?

Yes. iOS Safari and Chrome, Android Chrome/Firefox/Samsung Internet/Edge all support AudioContext and StereoPannerNode. Wired headphones, Bluetooth headsets, and USB-C audio devices all work.

One platform quirk: iOS Safari requires the first play to happen inside a user gesture — tapping the "Play Left" button satisfies this automatically. If nothing plays on the first tap, tap again.

Why does the volume cap before the slider reaches 100?

The gain node output is mapped from 0–100 on the slider to 0–0.5 on the Web Audio gain node, to keep the absolute output comfortably below full-scale. In combination with your OS volume, this still produces plenty of range to test loud — but protects against an accidental full-scale tone reaching your ears. If you need more headroom for a specific test, raise the OS volume.

Which frequency should I use?

For a quick left/right confirmation, 440 Hz is pleasant and instantly recognisable. For a full headphone health check, cycle through all four presets. If you hear clear, clean tones at all four, your drivers are moving air across the whole band. If one preset sounds dramatically different from the others (especially quieter or distorted), note which one and investigate the corresponding driver or frequency-response concern.

Can I download the test tone?

Not from this tester — it generates the tones on-the-fly rather than serving audio files. If you want a static reference tone for offline use, ffmpeg can generate a perfectly clean sine wave with ffmpeg -f lavfi -i "sine=frequency=440:duration=5" -ac 1 tone_440.wav, or Audacity can do the same via Generate > Tone.

Is my audio output sent to any server?

No. The test tones are generated entirely inside the browser using the Web Audio API. They play out to your headphones through the OS audio path and are never captured, recorded, or uploaded anywhere. You can verify this by checking the browser's network tab — no outbound audio data appears at any point.

Can I use this to test headphone amplifiers?

Indirectly. The tester confirms that the signal chain from the browser to the amp to the headphones passes clean audio. If you hear distortion on the pure sine tones that were not there at lower gain, the amp is the suspect (either it is clipping, or the gain staging is wrong). For full amplifier testing — frequency response, THD+N, noise floor — dedicated tools like the Audio Precision APx series or a cheap loopback measurement with REW and a calibrated DAC are required.

Does auto-play work without clicks between sides?

Each side change creates a new oscillator with a 20 ms gain fade-in and fade-out, so there is a brief silent gap between the left tone ending and the right tone starting. This intentional gap makes it easier to hear that left finished cleanly before right begins. If you hear clicks or pops during the transition, that is a driver distortion issue rather than a browser issue — the fade ramps are long enough to avoid digital discontinuity.

Related Testing Tools

If you are preparing a full audio or communication setup, test every component in turn:

• Microphone Test — Test your mic with a level meter, waveform, FFT visualiser, and record clips with MediaRecorder.
• Webcam Test — Test your camera, preview live video, capture still photos, and download them without uploading anywhere.
• Keyboard Test — Test every key on your keyboard, detect stuck keys, verify NKRO rollover, and see KeyboardEvent.code / KeyboardEvent.key values in real time.
• Mouse Test — Test every button and scroll wheel on your mouse, diagnose double-click failure, and capture MouseEvent and WheelEvent values.
• PS4 Controller Test — Test DualShock 4 buttons, analog sticks, triggers, and vibration via the HTML5 Gamepad API.
• PS5 Controller Test — Test the DualSense controller including all face buttons, triggers, touchpad, and haptic feedback detection.
• Xbox Controller Test — Test Xbox One, Xbox Series X/S, and Xbox 360 controllers across all buttons, bumpers, triggers, and thumbsticks.

When to Use Multiple Audio Testers

Before recording a podcast, streaming a game, or joining an important video call: test both the microphone and the headphones. If either one has a problem, the other cannot compensate — a great mic with dead headphones means you cannot monitor what you are saying, and great headphones with a dead mic means nobody can hear you. Two minutes of testing catches almost every common failure.