Troubleshooting
Why Do My Video Calls Freeze?
Freezing video calls can involve the network, devices or individual participants. Compare evidence to narrow down the cause.
Calls need to send, receive and process audio and video. A fast download result does not guarantee call quality. Identify whether audio, video, a shared screen or the entire app freezes, and whether others see your feed freeze or you see theirs.
Keep the conversation usable first
- If video is not needed, turn the camera off or lower quality using the app’s guidance. This reduces network and device load; better audio alone does not identify an upload bottleneck.
- Pause your own unnecessary cloud sync, backups and large transfers, then resume them after the comparison. Keep important work and other people’s calls running.
- Outside an important call, compare Wi-Fi and Ethernet with the same app and device on an appropriate LAN port. Record changes in location, band or access point; the cable and adapter can also limit the result.
- Ask whose picture or audio freezes and who notices it. A shared symptom alone does not prove a meeting-server fault.
Capture evidence while the problem occurs
Note the time, app and version, device, connection, layout and video quality. Separate sending and receiving statistics: latency, jitter, packet loss, bitrate and frame rate where available, with units. Check CPU and memory use during the symptom. Bandwidth needs vary with resolution and layout; neither 3 Mbps nor 100 ms alone diagnoses freezing. A low frame rate when sharing static content does not always indicate a problem.
Find the app’s own diagnostics
- Zoom desktop: arrow beside the video button > Video Settings > Statistics. Check Overall and the relevant Audio, Video or Screen Sharing stream. Current Zoom traffic is not your connection’s contracted capacity.
- Teams: More actions > Settings > Call health. Data updates every 15 seconds and may miss a brief spike. Send/Receive limit is not an ISP limit; different tools can measure different destinations.
- Google Meet: More options > Troubleshooting & help. Review the network and device suggestions for your version. Check the selected camera, microphone and speakers too.
- Run speedtests before or after the call to avoid adding load. NDT measures TCP to an Internet server, not the meeting stream, its jitter or the camera. A fast result does not rule out a service-specific problem.
If the local camera preview also freezes, investigate the camera and processing as well as the network. Test another camera app separately, without competing for the camera. Differences between devices or services are clues, not proof against the router or ISP. Compare similar times, participants, layout, quality and your own load.
Make a change that fits the evidence
- Check input and output devices and official app, system and driver updates. Follow guidance for your version and hardware; change one thing at a time.
- For high device load, reduce your own unnecessary apps or video effects following the service’s help. Lower quality may also reduce network traffic, so improvement alone does not identify the cause.
- Try another device or service in a controlled comparison with similar conditions. Repeat a test call after one change and record the result; restore the setting when appropriate.
- Keep observations and finish important work before restarting. Restarting a router also disconnects other users. Retain required protection, VPN and administrator rules; a factory reset or replacing equipment solely because of age is not a general fix.
For recurring problems, give the relevant support team the time, version, affected direction, statistics, load and comparisons without claiming the ISP or server is cleared. Before sharing reports privately, remove passwords, unnecessary meeting identifiers, addresses and participant data. Avoid publishing screenshots showing other people’s images or information.