Who causes the freeze? How to tell whose side a video call froze on

You are two minutes into a good conversation and the other person turns into a statue. Mouth half open, one hand up mid-gesture. Maybe their voice keeps going for a few seconds, maybe it cuts out with the picture. The first thing most of us do is apologise for our own internet — and often enough, we are apologising for somebody else's.

A live video call has three places it can break: your device, their device, and the long path between the two. Those three failures look similar for the first half second and then behave completely differently. You do not need a network tool or a speed test to tell them apart. You need to look at the right things in the right order, and the whole check takes less time than typing "sorry, my wifi" into the chat box.

What follows is that order — cheapest, fastest checks first, so you usually have your answer within four steps and never have to run the last six. Work through it once properly and you will find yourself diagnosing freezes automatically for the rest of your calls.

Reading a freeze, step by step

Do these in order. Each one rules something out, so by the time you reach the bottom there is almost nothing left to blame.

1. Step 01Look at your own preview before you look at anything else

   Find the little picture of yourself in the corner of the call and watch it for two or three seconds. Is it moving normally? Wave a hand at the camera if you cannot tell. That image is the one thing on your screen that never touches the internet — it goes from your camera to your screen and stops there.

   Why this first — if your own preview is also stuttering, no amount of router-fiddling will help, because nothing you are looking at has left the building. A frozen self-view points at your camera, your browser, or a machine that is too busy to draw frames. That is a completely different repair job, and it is the single fastest fork in the whole diagnosis.

2. Step 02Say something and find out whether the audio survived

   Talk. "You have gone still for me — can you still hear me?" Then listen. Sound and picture travel as two separate streams, and the sound one is tiny by comparison: a voice needs a small fraction of what a moving image needs. When a connection starts to struggle, everything involved sheds video quality first and hangs on to the voice for as long as it possibly can.

   Listen to how the voice sounds, too. A voice that carries on cleanly while the picture sits still is a healthy link doing triage. A voice that turns robotic, chops into syllables or arrives in bursts is a link that is running out of room for both, and the picture is not coming back until something changes.

   Why it matters — a frozen picture with working audio means nothing has actually disconnected. The link narrowed, the video was thrown overboard to keep the conversation alive, and there is a good chance it climbs back by itself. That is a call worth staying in. Silence in both directions is a different story.

3. Step 03Count to five before you touch anything

   Do not reload. Do not skip. Do not start clicking buttons. Just count. A large share of freezes are a brief burst of lost packets, and they end the way they started — the picture jumps forward and catches up to the voice.

   Why it matters — reloading costs you far more than five seconds. You lose the connection, the camera permission handshake, the reconnect, and on a service that pairs you with a random person, you lose the person. There is no way back to a stranger you have walked out on. Waiting is the cheapest move available and it works surprisingly often.

4. Step 04Check whether the rest of the page still moves

   Scroll the page a little, or hover over a button and see whether it responds. If the entire interface is stuck — nothing animates, nothing reacts — the freeze is not about data arriving. Your browser tab has stopped being given enough processor time to draw anything at all.

   The everyday causes are dull and easy to fix: far too many tabs open, a video playing somewhere behind the call, a photo editor or a game left running, an update installing itself. Any of them can push a browser into drawing one frame a second while insisting the connection is perfect.

   Why it matters — a starved tab and a starved connection look identical from the outside and have opposite fixes. One is repaired by closing the twelve other tabs, the video playing in the background, or whatever is busy exporting; the other is not repaired by any of that. Two seconds of scrolling tells you which room the fire is in.

5. Step 05Take the next hello as a voice-only call

   Your outgoing video is the heaviest thing your connection is being asked to carry, and you cannot put it down from inside a call — the camera control during a call draws a cover over the picture at both ends, it does not stop your video being sent. To take your own video out of the equation you have to start without it: pick the voice-only mode for the next hello and see whether it holds steady.

   Why it matters — home connections are lopsided: the download side is often ten or twenty times fatter than the upload side, while a call needs both. If voice-only calls run cleanly all evening and video calls fall apart within two minutes, the shortage is on your upload — not on their side, and not on the path. That is a diagnosis you can act on, and it is not one you will ever get by staring at a frozen picture.

6. Step 06Find out what else is uploading right now

   Photo backup, a cloud folder syncing a big file, a game downloading a patch, someone else in the flat on their own call, a console updating quietly in the corner. Pause the one you can pause.

   Why it matters — background transfers do not politely leave room for a conversation. They are built to use whatever they can get, and a phone quietly pushing last weekend's photos to the cloud can eat the exact capacity your camera needed. This is the most common invisible cause of a freeze that has no obvious explanation.

7. Step 07Look at where you are physically sitting

   How far are you from the router, and how many walls are in the way? Are you on the crowded 2.4 GHz band that every neighbour and every microwave shares? Did the freeze start when you wandered into the kitchen? Move six metres and see whether the problem follows you.

   Why it matters — a weak wireless link produces exactly the same symptoms as a bad internet connection, but the fault is in the last few metres, which is the one part of the whole chain you fully control. People spend evenings blaming their provider for a problem that a different chair would have solved.

8. Step 08Watch the pattern across several different people

   One frozen call tells you nothing. Three in a row, all freezing in the same way, tells you almost everything. Keep a rough note of it across a session: did the last few conversations break at the same moment, in the same style?

   Why it matters — when you are meeting people at random, everyone you talk to has a different device, a different provider and a different country. They are, in effect, a random sample of connections around the world. If all of them freeze, the one thing they have in common is you. This is the closest thing to a controlled experiment you will get without installing anything.

9. Step 09When it really is their side, say so once, then move on

   Tell them plainly: "You are frozen for me — I can hear you but you are not moving." Give it another fifteen seconds or so. If nothing changes, leave kindly: "I think your connection has gone, sorry, this was nice." Then take the next hello.

   Why it matters — you cannot repair a stranger's router, and sitting in silence hoping helps neither of you. Saying it out loud is genuinely useful to them, because a frozen picture usually looks perfectly normal on the sending end and they may have no idea. Skipping is not rude here; it is the design. Wondering whether to stay is a question of etiquette, and the etiquette is: be clear, be brief, do not vanish mid-sentence if you can help it.

10. Step 10Fix your baseline once instead of every call

    If step 08 pointed at you, spend fifteen minutes on it outside of a conversation. A cable instead of wireless, if the socket is anywhere near you. A restart before a session rather than a browser that has been open since Tuesday. Battery saver off, because power-saving modes throttle exactly the work that video encoding needs. Laptop on a hard surface rather than a duvet, because a machine that overheats quietly slows itself down and drops frames long before it warns you.

    Why it matters — a live conversation is the worst possible moment to debug anything. One quarter of an hour spent on the setup removes the problem from the next hundred calls, and it removes the reflex of apologising for your internet to every new person you meet.

Where people get stuck

The steps above cover the ordinary cases. These are the ones that keep sending people down the wrong path.

"It freezes for a second right at the start of every call."

That is usually the beginning behaving normally rather than something breaking. The first moments of any call are spent working out the route and starting cautiously, and the picture quality climbs from there. A stutter in the first second or two that never comes back is not a fault. A stutter that arrives at minute four is.

"My picture looks fine on my screen, so the problem must be theirs."

Your picture on your screen is the local preview from step 01 — it proves your camera works and nothing else. The two directions of a call are independent: your outgoing stream can be falling apart while their incoming one is flawless, and you would never see it. This is why "you are frozen for me" is worth saying out loud in both directions.

"Reloading always fixes it, so I reload immediately."

Reloading does sometimes rebuild a connection that had gone bad. It also fixes every freeze that was about to resolve on its own five seconds later, which makes it look far more effective than it is. Meanwhile it costs you the conversation you were having. Count first, reload second.

"My speed test says 200 Mbps, so bandwidth cannot be the issue."

A speed test measures how fast a big download went, once, in one direction, at one moment. A call needs something else entirely: a small, steady, uninterrupted flow in both directions at the same time. A connection can post an enormous number and still deliver packets in lumps, which is what a freeze actually is. The number that matters for calls is consistency, and consistency is not what a speed test reports.

"I am on a VPN, but that only affects privacy."

A VPN adds a stop along the way, and sometimes that stop is on another continent, which quietly turns a short trip into a long one. It is often worth it for other reasons — just know that it is in the picture. How much distance costs you is covered in what a cross-continent call really costs in delay.

"It only happens on my phone."

Mobile data is not a steady thing. Signal strength changes as you move, cells hand you over to each other, and a bar of coverage in a lift is not the same as a bar of coverage in a window seat. Sitting still near a window while on cellular removes a surprising number of freezes. So does plugging in — some phones throttle hard when the battery drops low.

"We both froze at exactly the same moment."

Simultaneous is the one pattern that genuinely points at the middle rather than at either end. Two independent connections do not usually fail in the same second by coincidence, so something on the route between you hiccuped. There is nothing to fix and nothing to apologise for. Wait it out, and if it repeats every few minutes with the same person, take it as a sign that this particular pairing has a rough road between it and try the next one.

"It started freezing after I plugged something in."

Worth noticing when a freeze arrives with an event rather than out of nowhere. New headphones, a docking station, a second monitor or an external camera all change what the machine has to do, and some of them change which camera and microphone the browser has chosen without telling you. If a freeze begins the minute hardware changed, unplug it and see whether the call recovers before blaming anything further away.

"The video is fine but they say I sound terrible."

Then this is not a freeze problem at all, and no amount of network work will fix it. Sound quality is decided long before the network gets involved, mostly by where the microphone is sitting. That is a separate and much cheaper repair: where you put the microphone matters more than what it cost.

The honest summary

Most freezes are not caused by the ocean. They are caused by the last ten metres — a wireless link fighting through two walls, a laptop that is too busy, a backup that chose the worst moment, a phone doing its best on three bars. That is good news, because the last ten metres belong to you and the ocean does not.

It also means the polite reflex of apologising for your connection is usually premature. Run steps 01 and 02 instead. Two seconds of looking, and you will know which of the three you are dealing with: something you can fix, something that will fix itself, or something on the other side of the world that you should simply say one sentence about before taking the next random video chat.