Left and right speakers reversed, and which side is wrong

Before you start

Left and right speakers reversed is the most reported version of this problem, but a silent side and a mono collapse produce similar complaints. Set a moderate volume before generating any test tone, and keep headphones off your head until you know how loud the output is. Test tones are pure sine waves, which are far more fatiguing and more revealing of level than music.

Identify the physical left and right outputs, and note anything in the chain: an interface, a receiver, a switch box, a Bluetooth adapter. Each is a place where left and right can be exchanged.

Disable spatial audio, virtual surround, room correction and any equaliser for the first baseline. Those features deliberately mix channels, and a channel test carried out with them enabled measures the processing rather than the routing.

Run the check

Open the sound test and play left alone. The tool generates a tone locally and routes it into one explicit merger input while the other gain stays at zero, so nothing but the selected channel receives energy. If you press left and hear the right speaker, the swap is downstream of the browser.

Play right alone, then both together. Three separate observations are needed because a swap and a silent channel produce a different pattern: left and right speakers reversed gives you sound on the wrong side twice, while a silent channel gives you nothing on one side and correct output on the other.

Move to the speaker test when you want to record what you heard. It plays one position at a time and asks you to confirm, keeping confirmation state separate from playback state so a generated tone is never counted as proof that a physical speaker works.

Now change exactly one thing. Swap the left and right cables at the speaker end and repeat. If the fault follows the cable, it is the cable or that channel of the amplifier; if it stays on the same side, the problem is upstream in the system or the application.

Read your result

A swap that follows a physical cable is physical routing, and the fix is a cable or a connection. A swap that stays put through a cable change is a system or software route: check your operating system's balance and channel-mapping settings before suspecting hardware.

A swap that appears in only one application is that application's own routing or its spatial processing. Nothing in the shared audio path is wrong, which is why every other program sounds correct.

One silent side needs a balance check first. System balance sliders drift, and a fully deflected balance produces a perfectly silent channel with no hardware fault at all.

Measurement limits

The browser knows which channel signal it created. It does not know your physical speaker arrangement, because the operating system, the interface, the cabling and the amplifier all decide where that signal finally arrives.

This is stereo only. Independent centre, rear and subwoofer channels are assigned after the browser and cannot be addressed from a page, so a surround-speaker check needs your system's own configuration panel.

Bluetooth adds an unpredictable layer. Some adapters silently collapse stereo to mono when a microphone profile activates, which explains channel checks that pass on a cable and fail wirelessly.

What to do next

If the fault follows the cable, replace or reseat that cable and retest; it is the cheapest confirmed fix in audio.

If it stays on one side through a cable swap, work upward through system balance, output device selection and driver settings before considering the speakers themselves faulty.

If everything passes here but one application still sounds wrong, that application's audio settings are the remaining suspect. Reset its output device and disable its own spatial processing.

Symptom table

Common questions