Headphones or Speakers on a Video Call? What Actually Changes

The short version

Headphones solve one specific problem. They stop the other person's voice from coming out of your speakers, bouncing off the wall behind you, and travelling straight back into your microphone. That round trip is what they hear as echo — and the person causing it never hears it, which is why it survives entire calls unfixed.

Speakers are fine in a narrow set of conditions: you are alone, the room has soft surfaces, the volume is low, and your microphone is not sitting a few centimetres from the speaker grille. Change any one of those and headphones win by a distance, and by more than better lighting or a better camera would give you.

The eight steps below are a one-time setup per device. Run them once on the laptop and once on the phone and you stop having to think about audio at all, which is worth more than it sounds — bad sound is the one fault the other person will not usually tell you about.

Step 1 — Connect the headphones before you open the call

Put them on, or connect them, before you load the page. Then open the site and start the call.

Browsers generally take the audio devices that exist at the moment a call starts. Plug in halfway through and the sound often keeps coming out of the laptop until you reload the page, which people reasonably misread as broken headphones. Connecting first removes that entire class of confusion before it happens.

On a phone this matters more, not less. Wired earbuds and Bluetooth earbuds are two different routes through the system, and switching between them mid-call is one of the most reliable ways to lose thirty seconds of a conversation you were enjoying.

Step 2 — Check the browser is actually using them

Before the conversation starts, play any sound at all — a video in another tab does the job — and confirm it arrives in the headphones rather than the laptop.

Connected is not the same as selected. A Bluetooth headset can be paired and showing as connected while the call audio still routes to the built-in speaker. Ten seconds of checking beats two minutes of "can you hear me?" at the start of every call.

If it is coming out of the wrong place, fix it in your system sound settings rather than inside the page. That is where the routing decision actually lives, and fixing it there means it stays fixed for the next call too.

Step 3 — Decide which microphone you are using, not just which speaker

Headphones change two things at once: where the sound comes out and, if they have a mic, where your voice goes in. Choose the microphone deliberately, because the better one is not automatically the headset.

A cheap headset mic dangling at your chest can sound thinner than a modern laptop microphone sitting twenty centimetres from your face. If your voice comes back muffled, try the laptop mic while keeping the headphones on your ears — you keep the echo fix and drop the bad microphone.

That combination — laptop microphone, headphones for output — solves the most problems for the fewest changes. Echo becomes impossible, because nothing is coming out of a speaker for the mic to pick up, and you are using whichever of the two microphones is actually better.

Step 4 — Ask once whether they can hear themselves

In the first thirty seconds, ask one question: "Can you hear yourself at all?" Once is enough.

This is one audio fault you generally cannot diagnose alone. Echo produced by your speakers exists entirely on their side of the call — your own ears never receive it. Their answer is the only instrument you have, and it costs one sentence.

It works in both directions. If you are hearing a faint copy of your own voice a beat behind you, they are on speakers and the fix is theirs to make. Say it plainly and without apologising: "I am getting an echo, are you on speakers?" Very few people take offence at being asked.

Step 5 — Staying on speakers? Drop the volume first

If headphones genuinely are not an option, turn the output volume down until you can just comfortably follow the conversation, and no further.

Browsers do run echo cancellation and it works, up to a point. Past a certain volume the sound arriving back at your microphone is loud enough that the cancellation cannot keep up, and the loop gets through. Every notch you take off the volume is one less thing for it to remove.

The instinct when the other person is quiet is to turn yourself up. Do the opposite and ask them to move closer to their microphone. Raising your own volume to compensate for their level is exactly what turns a faint echo into a call neither of you can use.

Step 6 — Move the laptop, not the microphone

If you are on a laptop's built-in audio, shift or angle the whole machine so the speakers are not firing straight across the microphone holes, and get it off a bare hard desk.

Laptop microphones sit within a few centimetres of the speakers, which is a design compromise you cannot undo. What you can change is the surface underneath. Glass and lacquered wood reflect sound back up into the mic; a book, a cloth or a mousepad under the front edge does not.

You are not building a studio. You are breaking the shortest path between the speaker and the microphone, and moving the laptop twenty centimetres is usually enough to do it. Test it by asking the same question from step four again.

Step 7 — Go wired if the timing feels wrong

If the two of you keep starting sentences at the same moment and then both stopping, swap the Bluetooth earbuds for wired ones and try the next call again.

Bluetooth adds a delay between sound arriving at your device and reaching your ear. It is small, and for music it is irrelevant, but conversation runs on timing. You answer a fraction late, they assume you did not hear, you both restart, and the rhythm never settles. Wired removes that delay outright.

This one is worth knowing precisely because it does not feel like an audio problem. It feels like the two of you have no chemistry, which is a very easy thing to blame on the other person and then never test.

Step 8 — Choose by the room, not by preference

Decide per room rather than per mood. Kitchen, bathroom, an empty room with bare walls, anywhere with other people in it — headphones. Carpeted bedroom, alone, curtains closed, volume low — speakers are fine.

The room does most of the work. Hard parallel surfaces give sound somewhere to bounce; soft furnishings absorb it. This is why the same laptop sounds clean in one room and unusable in the next with absolutely nothing changed on the device.

If you keep only one line from this page: the more your own voice rings when you speak out loud in a room, the more headphones matter in it. You can test any room in two seconds, without a call, just by talking to the wall.

Where people get stuck

Only one earbud connects. The audio sounds fine so you carry on, but on some sets the microphone lives in the bud you left in the case. Put both in, or check that the mic being used is the one you think it is.

The case opens and the sound jumps back to the laptop. Opening a charging case can hand the connection back mid-call. If the audio suddenly changes character for no reason, that is usually what happened.

"You sound far away." Usually the output moved to the headphones while the microphone stayed on the laptop, and then you leaned back in the chair. Either use the headset mic or stay within arm's reach of the machine.

Creeping volume. They are quiet so you turn up, the echo worsens, they turn up too, and five minutes later neither of you can hear anything. Break that loop early by asking them to get closer to their mic instead.

An inline mic scraping a collar. The small control box on wired earbuds picks up every brush against fabric and turns it into a rustle on their end. Clip it to your shirt or let it hang free of everything.

Holding the phone at arm's length. That puts the microphone a metre from your mouth in a room with an open speaker — the worst possible arrangement. Earbuds fix the distance and the echo in the same move.

One person on headphones, one on speakers, and both of you confused. Only the speaker end produces the echo, so the two of you are having genuinely different experiences of the same call. Whoever is not hearing the problem is the one who has to change something, which is counterintuitive enough that it usually needs saying out loud.

Blaming the connection for an audio problem. Choppy, robotic audio is bandwidth. Hollow, ringing, doubled audio is a room. They sound nothing alike once you have heard both, and only one of them is fixed by moving closer to the router.