Choppy Google Meet calls almost always come from one of four places: your network (latency, jitter or packet loss, not just raw speed), an overloaded device or browser, a Meet setting, or the other person's connection. The fastest fix is to work out which one it is before changing anything. This guide gives you a ten-minute order of operations, the numbers Google itself publishes, and the changes that actually help.
TL;DR
- Choppy video on a connection that "should be fast" is usually a latency, jitter or packet loss problem, not a bandwidth problem. A plain download number will not show it.
- Use Meet's own Troubleshooting and Help panel during a call to see whether CPU load or network stability is the culprit.
- Google says video quality is best when round-trip latency to Google is under 100 ms and drops at 300 ms or more.
- If several people see you choppy, the problem is on your side. If only one person does, look at theirs.
- Fix in this order: wired or closer Wi-Fi, close tabs and apps, update the browser, check Send and Receive resolution, then test the network.
Table of Contents
- Why Google Meet gets choppy in the first place
- Step 1: Find out whose problem it is
- Step 2: Use Meet's built-in diagnostics during the call
- Step 3: Measure what actually matters
- Step 4: Fix the network
- Step 5: Fix the device and browser
- Step 6: Check Meet's own settings
- A ten-minute routine for a bad call
- Our perspective: stop trusting a single speed number
- Test your connection for video calls
- When to contact your ISP or IT team
- FAQ
- Sources
Why Google Meet gets choppy in the first place
Meet runs in real time. Unlike a YouTube video, it cannot buffer ten seconds ahead and hide a bad moment. Every frame and every slice of audio has to arrive within a fraction of a second, or it is dropped or delayed. That is what you experience as freezing, stuttering voices, robotic audio or a picture that turns to blocks.
Google explains that Meet shares processing power and network connections with other applications and browser tabs, and that severe or persistent resource shortages or a bad network can cause blurry video or stuttering audio. So there are two broad families of cause:
- Network: latency that is too high, jitter (latency that keeps changing), packet loss, a congested Wi-Fi channel, or a router that queues traffic badly when someone else uploads a file (bufferbloat).
- Device: a CPU that is maxed out by the camera, background effects, screen sharing and twenty open tabs, or a browser that has not been updated.
A third factor is the other end of the call. Meet is a two-way system, so a perfect connection on your side can still look terrible if the person you are watching has a weak one.
Step 1: Find out whose problem it is
Before touching your router, spend two minutes on triage. Google's own guidance gives a simple rule: if multiple viewers receive poor quality from one participant, the issue is likely on the sender's side; if only one viewer is affected, it may be on the receiver's side.
Turn that into a quick test:
| What you see | Most likely cause | Where to look |
|---|---|---|
| Everyone says you freeze or sound robotic | Your upload, Wi-Fi or CPU | Your network and device |
| Only one person says you are choppy | That person's connection or device | Ask them to run the steps below |
| One participant is choppy for everybody | That participant's setup | Ask them to switch to wired or close apps |
| Everyone is choppy for you, but others say you are fine | Your download, Wi-Fi or CPU | Your network and device |
| Choppy only when you share your screen or play a video | CPU or upload bandwidth on your side | Presentation settings, second device |
The last row matters more than people think. A common complaint in Meet communities is choppy sound while presenting a YouTube video. Encoding a screen share plus your camera plus the video you are playing is heavy work. Presenting a video from a second laptop with the microphone muted and camera off, or embedding the video in a slide instead of streaming it live, takes load off the machine that is running the call. Treat those as practical workarounds rather than guaranteed fixes.
Step 2: Use Meet's built-in diagnostics during the call
Meet has a tool most people never open. In the three-dot menu during a call, you will find Troubleshooting and Help. Google says it shows CPU load and network stability over time, which answers the biggest question quickly: is the machine struggling, or is the connection?
- CPU line high and the network line steady: your device is the bottleneck. Go to the device fixes below.
- Network line unstable and the CPU line low: the connection is the bottleneck. Go to the network fixes.
- Both look fine and the call is still choppy: suspect the other participant, or a Meet resolution setting.
Open this panel while the problem is happening. A reading taken after the call ends tells you very little.
Step 3: Measure what actually matters
Most people run a speed test, see "200 Mbps," and conclude the network cannot be the problem. That is the trap. A video call needs a modest amount of bandwidth but is extremely sensitive to delay and instability. We cover this in detail in why 5 Mbps still gets choppy on video calls, but the short version is that the quality of the connection matters more than its size.
The numbers worth knowing come straight from Google:
- Meet video quality is highest when round-trip latency between the client and Google is under 100 ms, and media quality is reduced at 300 ms or more.
- For good video, both the sender and receiver devices need enough CPU power and memory.
Those are the thresholds to test against. A good test shows more than download speed, so use one that reports upload speed, latency, jitter and packet loss together. Our GrandSpeed speed test measures all of those, plus bufferbloat and DNS resolution time, in a browser on a phone, tablet or laptop, so you can test on the same Wi-Fi your call uses.
How to read the results
| Metric | What it does to a Meet call | What to do if it looks bad |
|---|---|---|
| Upload speed | Limits how clearly others see and hear you | Close uploads and cloud backups, move closer to the router |
| Latency | Adds delay and talk-over | Use wired, check the route, try a different network |
| Jitter | Causes stutter and robotic audio even when average latency is fine | Reduce Wi-Fi interference, see the VoIP jitter fixes |
| Packet loss | Causes frozen frames and missing words | Replace a bad cable, change Wi-Fi band, contact the ISP if it persists |
| Bufferbloat | Calls degrade when anyone else is downloading or uploading | Enable smart queue management on the router if it has it |
If you want to check latency to Google specifically, Google's documentation suggests you ping lens.meet.l.google.com over a long period, at least four hours, and run a traceroute if latency is too high to see where along the path the delay builds up. That is a job for IT teams chasing an intermittent fault. For a one-off bad call at home, a few speed tests at different times of day usually tell you enough.
Step 4: Fix the network
Work through these in order. Stop when the call is smooth.
Get off weak Wi-Fi
This fixes more choppy calls than anything else. Wi-Fi gets worse through walls, with microwaves running and with neighbors on the same channel. Jitter and packet loss show up long before the signal bars look bad.
- Plug in an Ethernet cable if you can. Google recommends a wired network connection for the best sound and video quality on its Meet hardware.
- If you cannot, sit in the same room as the router for a test call. If it clears up, your problem is coverage.
- Prefer the 5 GHz band for calls when you are close to the router. It is usually less crowded than 2.4 GHz.
- A reader on a Ubiquiti community thread described how switching one user to a tethered phone connection fixed Meet latency immediately, which points to the local network or access point rather than Meet itself. It is a useful diagnostic: if your phone's hotspot makes the call smooth, your home network or ISP is the suspect.
Stop competing traffic
A cloud backup, a game download or a family member streaming 4K can starve a call, especially on slow upload. Pause them and test again. If the call improves only when the house is quiet, you have either low upload capacity or bufferbloat. Our guide on why upload speed is slow and how to fix it walks through causes in more detail.
Restart the right things
Restart your router and modem, then your computer. It is dull advice, but routers that have run for months do accumulate problems, and a restart clears queues and stale connections.
If you manage a work or school network
Admins have extra levers. Google says enterprises should allow outbound UDP ports 3478 and 19302 to 19309 for audio and video, so that Meet can use its preferred media path rather than falling back to something slower. The same page advises avoiding QoS unless there is a compelling reason and an end-to-end QoS model can be maintained. Google's later QoS guidance goes further: you shouldn't use QoS for Meet because it adapts automatically to network conditions. If calls are choppy only on the office network and fine on a phone hotspot, a firewall or proxy blocking UDP is a good first suspect.
Step 5: Fix the device and browser
If Troubleshooting and Help showed a high CPU line, the network is not your problem.
- Close everything you do not need. Meet competes with every tab and app. Close heavy tabs, video editors, games and sync tools.
- Turn off background blur and effects. Effects are processed on your computer and can be the difference between smooth and stuttering on an older laptop.
- Update your browser. Chrome and other browsers get regular media fixes. A stale browser is a common reason Meet misbehaves, and Google's support community often points to software updates as a possible culprit in video lag threads.
- Check hardware acceleration. In Chrome, go to Settings, then System, and make sure "Use hardware acceleration when available" is on, then relaunch. Some users find that toggling it off and on again, or trying a different browser, clears camera lag that only affects one browser.
- Plug in the laptop. Battery saver modes throttle the processor, and video calls feel it first.
- Reboot. A computer that has been running for weeks with a camera driver glitch will often behave after a restart.
- Use a headset. Google notes that headsets can isolate background noise and prevent audio leakage, which cuts echo and the clipped sound that makes a call feel broken even when the connection is fine.
On a Mac with distorted audio, Google also mentions that unchecking "Use ambient noise reduction" in System Preferences, Sound, Input may improve audio quality.
Step 6: Check Meet's own settings
If the picture is blurry or grainy rather than frozen, resolution may be the cause. Google says poor video can come from network issues or poor lighting, and recommends setting Send and Receive resolution to High definition, checking that your camera meets quality requirements, and measuring bandwidth and latency.
A few practical notes:
- Light your face. Cameras compress dim, noisy images badly, and the result looks grainy even on a perfect connection. A window in front of you or a desk lamp beats any setting.
- Lower the resolution on purpose when the network is weak. A steady 360p picture beats a 720p picture that freezes every few seconds. Smooth motion matters more in conversation than sharpness.
- Turn your camera off for big meetings if you do not need it. It frees bandwidth and CPU for audio, which is what people actually need.
Watching your data cap? A call uses far more data than most people expect. Our breakdown of video call data usage shows the range and how to cut it.
A ten-minute routine for a bad call
When a call is breaking up and the meeting is still running, do this in order:
- Ask one other participant: "Am I choppy for you, and is anyone else?" This tells you which side to fix.
- Open Troubleshooting and Help from the three-dot menu and read CPU against network stability.
- Turn off your camera for 30 seconds. If audio recovers, your upload or CPU is the limit.
- Close extra tabs and apps, and pause any backup or download.
- Move closer to the router or switch to Ethernet.
- Run a test after the call, with upload, latency, jitter and packet loss, and compare with a second test at a different time.
- If packet loss or jitter persist on a wired connection, gather your results and contact your ISP.
The same method works for other platforms. If you also use other tools, see our guides for Zoom connection problems and Teams call lag.
Our perspective: stop trusting a single speed number
We see the same pattern again and again: someone pays for a fast plan, runs a speed test, gets a big download figure and cannot understand why Meet still stutters. Our view is that the headline number is the least useful part of the result for calls. A connection can have plenty of megabits and still deliver packets late, out of order or not at all.
So we suggest reading results in a different order for video meetings. Start with latency, jitter and packet loss. Then check upload, because on a call you are a sender as much as a receiver. Then look at bufferbloat, which explains why calls fall apart exactly when someone else in the house starts a big upload. Only after that does the download figure matter.
We also think test timing is underrated. Run tests at the time your meetings actually happen. A 9 a.m. result tells you little about a 4 p.m. problem when the neighborhood is online. Keep a history so you can show a pattern to your ISP or IT team rather than describing a feeling. That is exactly why we built result history into GrandSpeed.
Finally, fix the cheap things first: cable, router position, closed tabs. They cost nothing and solve most cases.
— Peter D
Test your connection for video calls
If you want a clear answer on whether your connection can carry a call, run the GrandSpeed test. It reports upload, download, latency, jitter, packet loss, bufferbloat and DNS resolution time, and it works on any modern browser over Wi-Fi or cellular, so you can compare rooms or compare Wi-Fi with mobile data. Saved results let you spot patterns across the day. For a deeper approach to making calls count, see our video call productivity guide.
When to contact your ISP or IT team
Some faults are not yours to fix. Contact your internet provider when:
- Packet loss or high jitter shows up on a wired connection, with the same result across several tests and several times of day.
- Latency is consistently far above Google's 100 ms guideline even though a hotspot on a different carrier is fine.
- Upload speed is far below what your plan promises, even with everything else paused.
Contact your IT team when Meet works on home Wi-Fi or a phone hotspot but not on the office network. Give them your test results and the Troubleshooting and Help screenshots. If you are shopping for a plan, our internet speed recommender can help match a plan to how you work.
FAQ
Why is my Google Meet choppy when my internet speed is fast?
Because speed is only one factor. Calls depend on low latency, steady jitter and almost no packet loss, and those can be poor on a connection with a high download number. Weak Wi-Fi, bufferbloat and a busy CPU are the usual hidden causes. Check the Troubleshooting and Help panel during the call, then test upload, latency, jitter and packet loss.
How do I know if the lag is on my side or theirs?
Look at who is affected. If several participants see you as choppy, the problem is probably your upload, Wi-Fi or device. If only one participant has trouble, it may be on that person's receiving end, according to Google's troubleshooting guidance. Asking one other person is the quickest check.
What latency is too high for Google Meet?
Google says video quality is highest when round-trip latency to Google is below 100 ms, and media quality is reduced at 300 ms or more. Anywhere between those figures you may notice delay and talk-over. Wired connections usually give the lowest and steadiest numbers.
Does turning off my camera help?
Often, yes. Video is the heaviest part of a call, so turning your camera off frees upload bandwidth and CPU. If audio becomes clear when the camera is off, your upload or processor is the limit and the fixes above apply.
Should I set up QoS on my network for Meet?
Google advises against it for most cases. Its guidance says Meet adapts automatically to network conditions, and QoS only makes sense with a compelling reason and an end-to-end model. Fixing Wi-Fi and reducing competing traffic works better in a home setup.
Sources
- Google Workspace Updates: new tools to troubleshoot network and performance issues in Meet
- Troubleshoot Meet network, audio and video issues (Workspace knowledge base)
- Troubleshoot Meet network, audio and video issues (Google Workspace Admin Help)
- Prepare your network for Meet meetings and live streams
- Meet QoS best practices
- Google Meet hardware requirements