Bluetooth Audio Test – Sound Test & Headphone Test Online
Overview
Bluetooth Audio Test. The Bluetooth Audio Test checks whether your headphones connected in the full-quality media profile or the degraded voice profile, which is what actually causes muddy, mono-sounding Bluetooth audio. Click Play, listen for separation between the two channels, and answer the on-screen question to get a clear verdict on which profile you're stuck in and how to fix it. The bass test online runs entirely in your browser via the Web Audio API — nothing is uploaded anywhere.
Dialogue that lands behind the lips, one earbud quieter than the other, or buzzing on bass notes: a Bluetooth audio test catches all three. Run it with your Bluetooth headphones, earbuds, portable speakers or a wireless subwoofer to get a measured delay in milliseconds and a channel-by-channel check, so you know whether the fault is the fit, a rattling driver or the wireless link.
How the Bluetooth Audio Test Checks Your Headphones
This sound tester generates test tones in your browser and sends them to whichever output is active, so you can test your audio gear without installing anything. For deeper checks, a tone generator, a surround sound test and a real-time spectrum analyzer (using an FFT) show whether your Bluetooth equipment cuts off the highest tones. The left right stereo sound test online takes under a minute and needs nothing but your browser.
Left Right Test for Each Earbud
The left right test is the core headphone test: Left should play only in your left ear, Right only in your right ear. The pan slider (a panorama control on some tools) moves the tone across the left and right channels, so panning exposes a side that drops out halfway. A failed stereo test matters in games and films, where direction tells you where a footstep is coming from.
Frequency Sweep and Bass Test
A frequency sweep glides a sine tone from 20Hz to 20kHz, the nominal human frequency range, revealing how evenly your headphones handle low frequencies, the mid-range where vocals sit, and the treble. The bass test holds tones such as 60Hz to judge deep bass; small buds often roll off bass frequencies before 30 Hz, a size limit rather than a fault. High frequencies above about 16 kHz fade with age, so a silent top end may be your ears. For a more musical frequency test, try triangle or sawtooth waves, or a concert recording, which exposes harsh high-pitched tones fast.
Phase Test with Square Wave Bursts
A 100Hz square wave or short bursts shake each driver hard enough to expose enclosure resonances and housing resonances: rattling plastic or ear cups that buzz. Pulses also reveal overshoot and pumping, where the level swells after each burst. The phase test plays one tone in phase, then out of phase. In phase, the center image sits solidly mid-head; in counterphase it turns thin. If both sound identical, a channel is wired backwards or distortion is masking the difference.
Measuring Bluetooth Latency with the Audio Latency Test
Latency is what sets a Bluetooth check apart from a generic sound check: every link buffers, compresses and decodes the signal, so audio reaches you after the picture or key press that caused it. The tool measures it with tap-on-beat, comparing each tap with the moment its click was sent. A delay that is fine for music shows up quickly in gaming and on Zoom or Teams calls. Use the free audio output device switcher for a quick pass or fail answer, right in your browser.
The Wireless Delay Formula and a Worked Example
To isolate the wireless delay, run the test once on a wired connection (headphones on the 3.5mm jack, or the laptop's own speakers) and once over Bluetooth, then subtract the averages:
$$\text{Latency} = \bar{t}_{\text{Bluetooth}} - \bar{t}_{\text{wired}}$$
Here \(\bar{t}\) is the mean gap between each click and your tap. Tapping 12 beats at 90 BPM (one click every 667 milliseconds), your wired taps average 41 ms late and your Bluetooth taps 228 ms late, so the audio latency of the link is 228 − 41 = 187 ms, roughly 5.6 frames of 30 fps video.
ITU-R BT.1359 puts the point where viewers notice sound lagging the picture at about 125 ms, and the limit of acceptability at about 185 ms. At 187 ms, lip sync will look off unless the player compensates. Switching the buds to game mode and retesting gives a 159 ms Bluetooth average, or 118 ms of latency: under the point where most viewers notice.
How Bluetooth Codecs Change Sample Rate and Delay
Bluetooth codecs set how hard the signal is compressed, shaping quality and delay. Your phone and headphones negotiate the best one they both support, usually at a sample rate of 44.1kHz or 48kHz.
| Codec | Maximum bitrate | Bit depth | Where you find it |
|---|---|---|---|
| SBC | 345 kbps | 16-bit | Every A2DP headset |
| AAC | 320 kbps | 16-bit | iPhone, iPad, many Android phones |
| aptX | 384 kbps | 16-bit | Qualcomm-based phones and laptops |
| aptX HD | 576 kbps | 24-bit | Higher-end Qualcomm phones |
| LDAC | 990 kbps | 24-bit | Sony headphones, many recent phones |
More bitrate means less compression, not less delay: the codec in use sets the latency you measure, so rerun the tap test whenever it changes.
Reading Your Audio Check Results
An audio check only helps if you know what a pass looks like. Keep the volume fixed while comparing, since a 3 decibel change alters how the treble sounds, and note what fails: on a new pair, those notes support a warranty claim.
Frequency Response and Dead Spots
Frequency response is how evenly a pair reproduces the range. On a healthy pair the sweep changes smoothly; dead spots, sharp dips, crackling at higher volume or a tone that cuts out point to dead drivers. If both earphones fade at the same point, that is your hearing range, not the hardware.
Stereo Balance and Channel Balance Problems
If both tones play but one side is quieter, check the audio balance first: the balance slider in accessibility settings is easy to nudge off center, and stereo panning should put the tone dead center once it is centred. Channel imbalances that follow the bud to a second phone usually mean earwax on the mesh, a worn tip or, on wired models, a loose cable.
Syncing an Edit Suite After a Bluetooth Latency Measurement
I'm cutting a 23.976 fps interview on a laptop with over-ear wireless headphones, and the clapperboard's snap lands visibly after the slate closes. Before touching the timeline, I want one number: how late the headphones play, and whether the editor's audio output offset can absorb it. The answer turns out to be 226.7 ms, about 5.4 frames late.
I run tap-on-beat twice at 104 BPM, 16 taps each. Wired, through the laptop's headphone jack, my taps average 52.6 ms after each click: that is my own reaction lag. Over Bluetooth they average 279.3 ms. Subtracting gives 226.7 ms of Bluetooth latency. One frame at 23.976 fps lasts 1001/24000 s, or 41.71 ms, so the lag is 5.43 frames, and 41.7 ms past the 185 ms acceptability limit in ITU-R BT.1359. I check the subtraction by rerunning the Bluetooth pass once more; it lands within 6 ms of the first.
The tighter reference for editing is EBU R37, which allows sound at most 40 ms early or 60 ms late. Here is how each offset choice measures up:
| Offset applied | What you hear | Within EBU R37? |
|---|---|---|
| None | 226.7 ms late | No |
| 279.3 ms (raw Bluetooth taps) | 52.6 ms early | No |
| 5 frames (208.5 ms) | 18.2 ms late | Yes |
| 227 ms | 0.3 ms early | Yes |
The second row is the trap: skip the wired run and you shift by your reflexes as well, overshooting into audio that leads the picture, which looks stranger than lag. I set the monitoring offset to 227 ms. If the editor only accepted whole frames, I'd take 5 frames rather than 6, because 6 frames (250.2 ms) would put sound 23.6 ms early and early sound is the less natural error.
Two caveats. The offset only fixes what I monitor; the exported file is untouched, so nothing gets baked into the edit. And the number belongs to this link at this moment: after a reconnect the laptop sometimes falls back from AAC to SBC, so I rerun the tap test whenever the headphones re-pair rather than trusting the old figure.
Bluetooth Headphones Troubleshooting When Nothing Plays
When the sound test plays nothing at all, work from the connection outward.
Device Pairing and the Output Device
Paired is not the same as connected. On your smartphone or computer, confirm the device pairing shows Connected; if not, remove it and pair again. Then make the headphones the active audio device: Android's media output panel and the iOS AirPlay menu pick the output device, and a computer can keep its old default output after a reconnect. Charge the earbuds too.
Playback Device and Audio Output in System Settings
In system settings, set the headphones as the playback device, then check the system volume and the app's own volume level. If tones still don't play:
- Make sure the browser tab isn't muted.
- Reload or refresh the page after switching audio output.
- Try a different browser.
- Check the per-app mixer your operating system keeps in sound settings.
Audio Drivers and the Microphone Test Trap
If wired headphones work but Bluetooth fails on a PC, update the Bluetooth and sound card software from the laptop maker. Then watch for one trap: once an app opens the headset microphone (a microphone test, a call), the headset leaves its stereo music profile for the hands-free profile, and playback drops to phone quality.
Audio Testing Safely with a Free Online Sound Test
A check takes under a minute, so it is easy to repeat a headphone test or speaker test before important calls. Two habits keep that audio testing safe.
Protect Your Hearing During a Sound Test
Start quietly and raise the volume slowly. Set the output to 60–70% before playing tones, because tones between 2,000 and 5,000 Hz sound far louder than low ones at the same setting. Take breaks, keep speakers in a room at a moderate level, and stop if your ears ring: that means the level was too high for your hearing.
Web Audio API, Privacy and Mobile Browsers
Tones come from the Web Audio API in your browser and play locally, with no uploads and nothing recorded, so privacy isn't at stake. It runs in current Chrome, Safari, Firefox and Edge, on desktop or mobile.
Frequently Asked Questions
- Can I test Bluetooth headphones with this tool?
- Yes. Pair and connect them, make sure they are the active output device in your system settings, and run any test. Bluetooth compresses audio slightly, which doesn't affect channel or frequency checks, and the latency tap test measures the extra delay the wireless link adds.
- Why do I only hear sound on one side?
- Play Left, Right and Both, and set the pan control to the centre. If one side stays silent or quieter, check the balance slider in your system's sound or accessibility settings, clean earwax from the mesh, and try the earbuds on another device. A side that stays quiet everywhere is usually a hardware fault.
- What does the frequency sweep show?
- It glides a tone evenly from low to high frequencies so you can hear dips, dead spots, rattles or the point where the sound fades out. Small earbuds often can't reproduce very deep bass, and high frequencies fade with age, so a silent end isn't always a faulty headphone.
- How is Bluetooth latency measured here?
- You tap along to clicks twice: once on a wired connection or built-in speaker, then over Bluetooth. Subtracting the wired average from the Bluetooth average removes your own reaction time and leaves the delay added by the wireless link.
- What latency is too much for watching video?
- Broadcast guidance in ITU-R BT.1359 puts the point where viewers notice sound lagging the picture at about 125 ms, and the acceptable limit at about 185 ms. Above that, lip sync looks off unless the video player compensates, so try your headphones' low-latency or game mode.
- What are the 100 Hz square wave and burst tests for?
- Both drive the speakers hard to expose mechanical faults. A rattle on the square wave points to loose parts or housing resonances; bursts that swell, pump or overshoot point to distortion. Lower the volume and check the fit if anything rattles.
- Is a browser-based audio test accurate?
- For everyday checks, yes. The Web Audio API produces precise, consistent tones, enough to catch dead drivers, channel imbalances and frequency problems. Studio calibration still needs dedicated measurement equipment.
- Is any of my audio uploaded?
- No. Tones are generated and played locally in your browser, and nothing is recorded or sent to a server.