WebRTC, the technology behind video calls, is built to adapt to a weak connection rather than just dropping the call — it automatically scales the video quality down to fit whatever bandwidth is actually available. There are also a few genuinely useful things worth doing on your end, including one trick about your background that sounds odd but is real.
Video quality comes down to bitrate — how much data is being sent per second to describe the picture. When your connection can't support a high bitrate, WebRTC automatically reduces resolution and detail to keep the call going rather than letting it fail outright. This is by design — a blurrier picture that stays connected is generally more useful than a sharp one that keeps dropping. On a genuinely poor connection, audio tends to be prioritized over video, since keeping the conversation audible matters more than keeping it visually crisp.
This one sounds like a minor styling tip but is genuinely rooted in how video compression works. Most video codecs don't re-send the entire picture frame by frame — they mostly send what's changed since the last frame. If you're sitting in front of a plain, still wall, there's very little changing in the background from one frame to the next, so most of your limited bandwidth goes toward describing your face and movements clearly. A busy, moving, or high-contrast background, by contrast, gives the encoder more to describe every single frame, competing for the same limited bandwidth your face needs.
On a strong connection this barely matters. On a weak one, it can be the difference between a reasonably clear picture and a blurry, blocky one.
Good, even lighting on your face does something similar to the still-background trick, for a related reason. Poor or uneven lighting creates more visual noise — grain, shadows shifting slightly, inconsistent color — which the encoder has to spend bandwidth describing, the same way a busy background does. Sitting facing a light source, rather than backlit by a window or in dim ambient light, gives the encoder a cleaner, more consistent image to work with, which on a constrained connection means clearer video rather than wasted bandwidth on noise.
Anything else using your connection at the same time is competing directly with your video call for the same limited bandwidth. Background downloads, other devices streaming video on the same network, and even browser tabs that quietly check for updates in the background all add up. Closing what you can before a call, and asking others on the same network to pause anything bandwidth-heavy if that's an option, genuinely helps — this isn't a minor placebo tip, it's the same limited pipe being shared.
Some troubleshooting advice suggests changing your device's DNS settings (to something like Google's 8.8.8.8 or Cloudflare's 1.1.1.1) to improve video call performance. It's worth being precise about what this actually affects: DNS resolution speed influences how quickly your browser initially finds and loads a page, not the ongoing quality of a video stream once the call has already started. It's a reasonable thing to try if pages in general feel slow to load, but it isn't a fix specifically for blurry or choppy video during an active call.
Yes. WebRTC automatically lowers resolution and bitrate to keep the connection going rather than dropping it entirely.
WebRTC reduces resolution and detail to fit the available bandwidth, prioritizing keeping the call connected over keeping it sharp.
Yes, genuinely. Video compression mostly sends the parts of the image that change between frames. A still background means less data per frame, leaving more of your limited bandwidth for keeping your face clear.