Why Is My Video Call So Bad? It's Probably Not Your Download

First: whose problem is it?

This is the step that gets skipped, and skipping it sends people down the wrong path more often than any other mistake here.

In a video call, your upload feeds everyone else's download. So when your picture freezes for the other person, the fault is at your end — but you may see them perfectly and have no idea anything is wrong. Conversely, when someone else is a blocky mess on your screen, there is very little you can do about it, because the constraint is on their side.

Ask directly, in the call:

• "Am I freezing for you?" If yes, it's your upload, your Wi-Fi, or your computer. Everything below applies to you.
• "Is everyone freezing for everyone?" Then it's the meeting service, or a shared network you're all on.
• Only one person is bad, and it isn't you? Nothing on your machine will fix it. Tell them to turn their camera off.
• Everyone is fine except your view of them? That's your download, which is the one case where the usual speed test is the right test.

Most calls I've seen "fixed" by someone restarting their router were cases where the person doing the restarting wasn't the one with the problem.

Upload is the number that matters

Home connections are almost always asymmetric: a lot of download, much less upload. A plan advertised as "500 Mbps" may give you 20 Mbps up, or on some cable and fixed-wireless connections considerably less. Everything you send in a call — your camera, your microphone, your shared screen — goes through that smaller pipe.

Run a speed test and this time look only at the upload figure. As a rough guide, a single one-to-one call in reasonable quality wants a few megabits per second of upload; group calls and screen sharing want more; HD video for several participants wants more again. If your upload is barely above the minimum, calls will be marginal and will collapse whenever anything else uses the connection.

Then check what else is competing for it:

• Cloud backup and sync. Photo backup, file sync, and online backup tools upload continuously and will happily consume your entire upload capacity. This is the single most common cause of "my calls got bad and nothing changed" — because something did change: your phone started backing up a holiday.
• Someone else in the house. Another call, a game console uploading, a large email attachment.
• A VPN. Routing your call through another country adds latency and often costs throughput. Turn it off for the call and see.

Pausing sync clients before an important call is a habit worth building. Most have a "pause for 1 hour" option precisely for this.

When it's your computer, not your connection

Video calls are surprisingly demanding. Encoding your camera feed, decoding several other people's, and running effects all happen in real time. If your machine can't keep up, the app degrades your outgoing video — which looks identical to a network problem from the other end.

The tells: your fan is loud, everything else on the machine is sluggish during the call, and quality improves the moment you turn your camera off.

• Background blur and virtual backgrounds are expensive. They run a segmentation model on every frame. On an older laptop this alone can be the difference between a smooth call and a slideshow. Turn them off first — this is the highest-value single change on a struggling machine.
• Close the other twenty browser tabs. Especially anything playing video or running a live dashboard.
• Use the desktop app rather than the browser where one exists. Browser-based calling generally costs more CPU for the same result.
• Check the machine isn't thermally throttling. A laptop on a bed or sofa blocks its own intake. Our slow computer guide covers how to confirm heat is the cause.
• Plug in. On battery, many laptops cap performance. For a long call, mains power measurably helps.

The Wi-Fi specifics that matter for calls

Calls are unusually sensitive to Wi-Fi problems because they cannot buffer. A video stream absorbs a two-second hiccup invisibly; a live call turns it into a freeze and a "sorry, you cut out."

• Latency and stability matter more than raw speed. A stable 10 Mbps beats an erratic 200 Mbps for calling. This is why calls can be terrible on a connection that benchmarks brilliantly.
• Use 5 GHz, and be in the same room as the router if you can. The band with less range is the right choice here.
• Ethernet solves this outright. If you take calls seriously and can run a cable, it removes an entire category of problem permanently. A cheap USB-C adapter is enough.
• Don't sit in the microwave's line of fire. On 2.4 GHz, ninety seconds of reheating is ninety seconds of a broken call.
• If your Wi-Fi drops out entirely rather than just degrading, that's a separate fault — see why Wi-Fi keeps disconnecting.
• On mobile data, signal strength is everything. One bar means the radio is retrying constantly. Moving two metres toward a window genuinely changes the call.

Audio problems are separate

Bad audio and bad video have different causes, and audio is the one that actually stops a meeting working. People tolerate a frozen picture; they cannot tolerate not hearing you.

• Echo is always someone's speakers feeding their microphone. It is never the person hearing it. If there's echo, the person causing it is whoever is not wearing headphones — and they usually can't hear it themselves. Ask everyone to use headphones; that's the entire fix.
• Robotic or underwater audio is a network problem, not a microphone problem. Apps drop video before audio, so if audio is breaking up too, your connection is in real trouble — turn the camera off immediately.
• If your voice sounds thin and distant on Bluetooth headphones, that's a profile problem: the headset switches to a low-quality two-way mode the moment the microphone is used. Our Bluetooth guide covers it. Wired headphones avoid it entirely.
• Check which microphone the app is actually using. Laptops often default to the built-in mic even with a headset plugged in, which is why you sound like you're in a corridor.

What to change mid-call, in order

The call has started and it's going badly. Do these in sequence — each one frees more capacity than the last:

1. Turn your camera off. Instantly cuts most of your upload. Nothing else comes close for effect-per-second.
2. Turn off background blur or virtual background if you're keeping the camera on.
3. Stop screen sharing, or share a window rather than a full high-resolution display.
4. Move closer to the router, or switch the phone to mobile data as a test.
5. Pause cloud sync — the backup client is the usual hidden culprit.
6. Close other applications, browser tabs first.
7. Ask the others to turn their cameras off too if your download is the constraint.
8. Dial in by phone for audio and use the computer only for the shared screen. Ugly, but meetings finish.

Looking bad is not the same as connecting badly

Worth separating, because the fixes are unrelated. If your picture is stable but grainy, dark, or washed out, your connection is fine and this is a camera and lighting problem.

• Light from the front, not behind. A window behind you turns you into a silhouette, and the camera's automatic exposure will make it worse. Face the window instead.
• More light beats a better camera. Webcams are noisy in dim rooms; a desk lamp bounced off a wall fixes more than new hardware.
• Clean the lens. Laptop cameras collect a surprising film of dust and fingerprints.
• Raise the laptop. Not a quality issue, but a camera at chest height is unflattering to everyone and costs nothing to fix with a stack of books.