Browser Has No Sound?
No browser sound can come from a muted tab, low site or system volume, the wrong output device, Bluetooth routing, an unplugged cable, or an application-specific mixer setting. Separate “the browser generated audio” from “you physically heard it.”
Common causes
Tab mute controls, autoplay restrictions, per-app volume mixers, HDMI displays, Bluetooth headsets, docking stations, and stale output routes are frequent causes. A browser may play correctly while the operating system sends audio to a device you are not listening to.
Try these checks in order
- Unmute the tab and site, raise browser and system volume, inspect the per-app mixer.
- Select the correct output device. Disconnect unused HDMI or Bluetooth outputs, reconnect headphones.
- Play left then right test tones. Compare with another browser and a known working local audio file.
Change one thing at a time and repeat the browser test. That makes it easier to identify which permission, connection, or routing change actually restored the signal.
What the browser test can confirm
The test can generate tones, target left and right channels, and record your confirmation that you heard them. A web page cannot listen to its own physical speakers, verify acoustic loudness, certify frequency response, or prove that silence is a hardware fault.
Limits and privacy
The test generates audio locally and does not require microphone permission. Keep volume moderate before starting, especially with headphones.
A successful browser result means the expected event or stream reached this page during the test. It is useful evidence, but it is not a repair, calibration, warranty, or manufacturer certification.
Left/right separation requires StereoPannerNode support. Without it, this implementation may play both tones centrally; that alone does not prove a device fault.
Frequently asked questions
Does a playing status prove sound is audible?
No. It shows that audio is being generated. You must listen to the physical output and confirm what you hear.