Skip to content
RoundMeet

How to survive a video call on a bad connection

Freezing video, robot audio and a call that drops every few minutes are usually one problem wearing three costumes: not enough bandwidth for the number of video streams you are receiving. Here is what to change, in the order that helps most.

Founder & Platform Engineer, RoundMeet · Builds and operates the RoundMeet stack end to end — Jitsi/WebRTC media, the Django API, and the React meeting client.

8 min read

Ask ten people to describe a bad video call and you get ten descriptions: video that freezes into a still frame, audio that turns robotic, a green flicker across somebody's face, echo, being told repeatedly that you are breaking up, and a call that quietly drops every few minutes. They sound like different faults. Almost always they are the same one.

The one cause behind most of it

In a group call you are not sending one video stream. You are *receiving* several — one per person whose camera is on — and each of those is a continuous download that never pauses.

That is the asymmetry people get wrong. Your camera sends a single stream, and modern codecs are good at squeezing it. But a five-person call means four incoming streams, and unlike a file download they cannot slow down and arrive late: a video frame that arrives late is a video frame that is thrown away. When the pipe is not wide enough, the software starts discarding, and *discarding is what all those symptoms are*. Frozen video is discarded frames. Robotic audio is discarded audio packets. The dropped call is the connection giving up after discarding too much.

Which is why the first thing everyone tries — turning off their own camera — is close to useless for their own experience. It helps the *other* people slightly. It does approximately nothing for you, because your problem is what is coming in.

What to do, in the order that helps most

1. Turn on Low bandwidth mode

Open More (⋮) in the control bar and choose Low bandwidth mode.

This is the single most effective control in the product, and it is worth knowing exactly what it does rather than treating it as a vague "try harder" switch. It makes two changes at once:

  • You receive video from at most three people — whoever is currently active — instead of everyone.
  • Every stream you receive, and the one you send, is capped at 180p instead of the usual 720p.

Those two together cut your incoming data by roughly an order of magnitude in a busy room. Faces get soft. That is the trade, and in a call that is currently freezing it is not close: 180p that keeps moving beats 720p that stops.

It takes effect immediately, it applies only to you, and nobody else can tell you have turned it on.

2. If that is not enough, use Car Mode

Also in the More (⋮) menu. Car Mode receives no video at all — zero streams — and turns the call into audio with a simple overlay showing who is speaking and how long you have been in the meeting.

The name comes from its original purpose, but the mechanism is what matters here: if audio is still breaking up in Low bandwidth mode, there is not enough connection for any video, and continuing to receive some is what is breaking the audio. Car Mode is not a lesser experience with video removed; it is the experience that works when nothing else does.

If you need to see a shared screen, this is not the mode for you — Car Mode drops incoming video, including the screen share.

3. Move closer to the router, or use mobile data

This is unglamorous and it is the most common actual fix.

A 100 Mbps connection is a fact about the cable outside your house. What reaches your laptop at the far end of two walls may be a fraction of it, and — this matters more than raw speed — much less *steady*, which is what real-time video actually needs. Video calls tolerate a slow, consistent connection far better than a fast, erratic one.

So before you blame the platform: stand next to the router and rejoin. If the call is suddenly fine, the internet was never the problem. Wired Ethernet, if you have it, removes the variable entirely.

Mobile data is often better than weak Wi-Fi for exactly this reason. A 4G connection with two bars is usually steadier than Wi-Fi at the edge of its range.

4. Close the other tabs

Video decoding is CPU work, and a laptop that is thermally throttling drops frames in a way that looks identical to a network problem. Twenty Chrome tabs, a video playing in one of them, and a build running in the background will each take their cut.

If your fan is loud and the video is choppy, try the laptop-side fix before the network-side one.

5. Check the actual numbers

More (⋮) → Meeting Statistics shows what is really happening rather than what it feels like. Look at packet loss and the connection quality indicator for each participant.

The useful thing here is that it tells you *whose* problem it is. If everyone in the room looks bad to you but you look fine to everyone else, it is your download. If one person looks bad to everybody, it is theirs — and no amount of you switching modes will fix it.

Symptom to cause

What you seeUsually meansTry
Video freezes, audio fineIncoming video exceeds your downloadLow bandwidth mode
Audio robotic or cutting outNot enough for audio eitherCar Mode, then move to a better network
Fine one-to-one, bad in groupsStream count, not connection speedLow bandwidth mode
Gets worse over timeWi-Fi drift or a laptop heating upMove closer; close tabs
Everyone says *you* are breaking upYour upload or your Wi-FiMobile data; wired if possible
Screen share unreadable but video fineShare is capped by the senderAsk them to share a window, not the whole screen
You hear yourself echoSomeone has speakers on with a live micFind them from Participants and ask for headphones

What does not help as much as people think

  • Turning your own camera off. Helps the room a little, helps you almost not at all.
  • Rejoining. Sometimes it works, because it re-picks a media path. Usually you land in the same place. Try it once, not four times.
  • Switching browsers. Modern Chrome, Edge, Firefox and Safari all handle this comparably. It is worth a try only if one specific browser is misbehaving for you generally.
  • "Turning off HD" in some other app. Video calls are not competing with your settings; they are competing with your neighbours' streaming and your own downloads.

How much bandwidth does a video call actually need?

There is no single number, because it depends entirely on how many people have their cameras on. The useful way to think about it is per incoming stream: cutting the number of streams you receive from eight to three, and their resolution from 720p to 180p, is what Low bandwidth mode does, and that is the change that matters.

Does Low bandwidth mode affect what other people see of me?

Slightly. It caps your outgoing video at 180p as well, so others see you at a lower resolution. Everything else about their call is unchanged.

Can the host turn on Low bandwidth mode for everybody?

No, and deliberately so. It is a per-person setting because the constraint is per-person — the participant on hotel Wi-Fi needs it and the one on fibre does not.

Will Car Mode let me still hear a screen share?

You will hear the audio, but you will not see the shared screen — Car Mode receives no video, and a screen share is video.

Is mobile data really better than Wi-Fi?

Often, yes, when the Wi-Fi is weak. Real-time video cares more about consistency than peak speed, and a mobile connection at the edge of a city is usually steadier than Wi-Fi at the edge of a house.

My video is fine but everyone says I sound bad. Why?

That is your upload, or your microphone. Try headphones with a mic first — a laptop's built-in microphone is doing noise suppression that struggles in a room with any echo in it.

The short version

Your download is the bottleneck, not your upload. Turn on Low bandwidth mode first, drop to Car Mode if audio is still breaking up, and move closer to the router before you blame anything else. Turning off your own camera is the fix everyone tries and the one that helps you least.

About Astik Gabani

Founder & Platform Engineer, RoundMeet · Builds and operates the RoundMeet stack end to end — Jitsi/WebRTC media, the Django API, and the React meeting client.

Astik builds and runs RoundMeet: the WebRTC media tier, the Django control plane that mints room tokens, and the React client people actually meet in. He writes here about how the platform works, from the operator's side of it.

More from Astik Gabani →