Bluetooth headphones connected but no sound? Find where audio is going

“Connected” does not always mean “selected for playback.” Before resetting or re-pairing anything, check the system output, lower the volume, and play one short reference. Then compare whether the silence occurs in every app or only in the browser. Those observations tell you where to test next without assuming the headphones are broken.

Start with the selected output

Open your device sound settings and select the Bluetooth headphones as the output. Confirm they are powered, in range, and not muted. If they can connect to more than one device, check whether another phone or computer is currently taking the playback path. A successful Bluetooth connection and a usable audio route are different observations.

On Windows, Microsoft's connected-but-no-sound guidance begins with output selection and related sound settings. On a Mac, Apple explains how to choose a device in Sound Output. Android can switch audio between outputs, as described in Google's audio-switch help. Use the controls that match your device, not a generic sequence of resets.

Use one browser reference as a control

With the headphones selected and the level low, open the WaveLocus headphone test. Play a short both-channel reference. If you hear it, the current browser-to-headphone playback path works for that reference. This does not prove that a call or media app is routed to the same output. If nothing is audible, leave the hardware and output selection unchanged while you try a second app you already know should make sound.

Do not use a high-volume sweep as your first check. A simple short reference is easier to compare and safer if the route suddenly becomes active. The browser generally waits for your click before starting audio. MDN documents the user-activation rules for audible playback. That delay is not itself a Bluetooth failure.

Read the comparison before changing settings

If the browser alone is silent

Keep the Bluetooth output selected. Check the tab is not muted and that the browser is not muted in the operating system's app-volume controls. Retry the same reference with one other browser or a fresh tab. If the second browser works, the first browser's site or audio state deserves attention. Follow the browser audio troubleshooting guide for a controlled sequence. Avoid re-pairing the headphones before you have checked the simpler browser branch.

If everything is silent

Test a different known output from the same computer without changing the source. If that works, return to the Bluetooth headphones and inspect their connection and selected-output state. You can then test the same headphones on a second source device, if available. Record whether the result followed the headphones or stayed with the original computer. This swap is more informative than a single restart because it changes a defined part of the path.

If one side is silent but the other plays, use the left/right test rather than treating it as total connection loss. Verify the headphones' physical orientation. Record the result before changing accessibility balance or mono settings. The browser can send distinct channel references, but it cannot inspect every wireless or operating-system processing stage.

What if sound disappears during a call?

A headset may behave differently when its microphone becomes active. If playback works until a call or browser microphone test starts, run the combined headset test. It compares stereo playback before and during input capture and records browser-visible settings where available. A change may be consistent with an input-related route or mode change. It does not, by itself, prove which Bluetooth profile was selected.

Do not change microphone permissions, output selection, app volume, Bluetooth pairing, and enhancements in one pass. Change one item, replay the same short reference, and note the outcome. If you need to contact support, that record can say exactly when sound stopped and which path still worked.

Keep the limit clear

WaveLocus is a browser reference, not a Bluetooth packet analyser. It cannot verify radio strength, inspect firmware, certify drivers, or name a codec from what you hear. Browser APIs may not expose the exact output route or wireless profile, and output-selection controls differ across systems. If the headphones disconnect repeatedly, follow your device maker's instructions for updates or service. Do not invent a fault from the word “connected” alone.

If sound is unexpectedly loud when a route returns, stop playback and lower the physical volume before another attempt. Digital level is not a measure of what reaches your ears. NIOSH's noise guidance explains why both level and duration matter. Short tests at a conservative level are sufficient for routing comparisons.

Next step

Write one sentence about the strongest comparison: “Bluetooth headphones were selected; the browser reference was silent; the same headphones played from a phone,” or “The browser reference played, but the call app did not.” Put that evidence into guided diagnosis and change one remaining variable. The purpose is to narrow the signal path, not to guess a component.

Sources and method

This guide combines official output-selection guidance from Microsoft, Apple, and Google with a short WaveLocus playback reference and controlled swaps. MDN documents the browser playback interaction. NIOSH supports the conservative volume advice. The method establishes what was audible in named paths. It cannot diagnose a particular Bluetooth profile, hardware defect, or radio problem on its own.