Jitter vs Ping - What's the Difference?
Both are measured in milliseconds and both describe latency - But they measure completely different things, and confusing them leads to misdiagnosing your connection problems.
Quick Reference
Ping (latency)
The average time it takes a packet to travel from your device to a server and back. A fixed distance - Lower is better. Measured in ms.
Jitter
The variation in ping over time - How consistent your latency is. A measure of stability, not speed. Also measured in ms.
The one-line distinction
Ping tells you how far away the server is (in time). Jitter tells you how reliably packets reach that server on every trip.
Think of driving to work. Ping is how long the drive takes on an empty road. Jitter is whether the drive takes the same amount of time every day, or whether some days it takes 10 minutes and others it takes 45 minutes due to traffic.
How ping is calculated
A ping test sends multiple packets to a server and measures the round-trip time (RTT) of each one. The reported ping value is the average (or median) of all samples. Our Ping Test collects 14 samples, trims the outliers, and reports the trimmed mean.
Ping is primarily determined by:
- Physical distance to the server (speed of light imposes a floor)
- Number of router hops between you and the server
- Backbone routing quality of your ISP
How jitter is calculated
Jitter is calculated from the same ping samples, but instead of averaging the values, it measures how much consecutive values differ from each other. Our Jitter Test collects 20 samples and reports the mean of successive differences - The average gap between each consecutive pair of samples.
Jitter is primarily determined by:
- Wi-Fi radio interference and channel contention
- ISP congestion causing variable queue depth at routers
- Buffer bloat in your own router when downloads are in progress
- VPN encryption processing time variance
Which matters more for gaming?
Both matter, but jitter is harder to tolerate. Here's why:
If your ping is consistently 60 ms, a competitive game can compensate. Game servers use techniques like client-side prediction and lag compensation - They know your packets always arrive 60 ms late, so they account for it. The game still works well.
If your ping is 20 ms on average but spikes to 80 ms randomly (high jitter), the server can't compensate. It doesn't know when the next packet will arrive. This produces rubber-banding, ghost shots, and desync - Problems that a stable 60 ms ping never causes.
Rule of thumb for gaming: A stable 50 ms ping beats an unstable 20 ms ping almost every time.
Which matters more for video calls?
For video calls (Zoom, Teams, FaceTime, Google Meet), jitter is the dominant factor. Call applications include a jitter buffer - A small delay (20–80 ms) that smooths out arriving packets before playing them. Ping simply determines one-way delay; above 150 ms you may notice a conversational lag, but it's manageable.
Jitter above the buffer size causes packets to be discarded - Producing the choppy, cutting-out audio that makes calls painful. You can have a 200 ms ping and have a perfectly clear call. You can have a 10 ms ping with 40 ms jitter and have constant audio dropouts.
Which matters more for streaming?
Neither, meaningfully. Streaming services buffer 10–30 seconds of video. Ping and jitter values well above "acceptable" thresholds for gaming and calls are completely absorbed by the buffer. For streaming, what matters is sustained download speed relative to the stream's bitrate.
Can you have good ping but bad jitter?
Yes - And it's common. A Wi-Fi connection to a nearby server might report 15 ms average ping (excellent), but with 35 ms jitter (poor) because the wireless channel is congested. The average looks fine; the consistency is terrible.
This is why our speed tests report both metrics. A low average ping with high jitter is often more disruptive than a high but stable ping.
Can you have bad ping but good jitter?
Yes. A VPN connection to a geographically distant server might add 80 ms of ping (high) but with consistent 3 ms jitter (excellent) because the VPN tunnel is reliable. Games and calls on this connection may still work reasonably well - The delay is predictable.
Improving each independently
| Problem | Fix |
|---|---|
| High ping | Use a server/game region closer to you. Disable VPN. Check for ISP routing issues. |
| High jitter | Switch to Ethernet. Restart router. Reduce background traffic. See reduce jitter guide. |
| Both high | Start with Ethernet (fixes jitter). If ping remains high, investigate ISP or routing. |
Frequently Asked Questions
Can I have good ping but bad jitter at the same time?
Yes, and it is common. A Wi-Fi connection to a nearby server might report 15 ms average ping but 35 ms jitter because the wireless channel is congested, so the average looks excellent while the consistency is poor. This is why tests report both numbers rather than one.
For gaming, is a stable higher ping better than an unstable lower ping?
Usually, yes. A consistent 60 ms ping lets game servers compensate through client-side prediction and lag compensation because they can predict when packets arrive, while a 20 ms ping that randomly spikes to 80 ms cannot be compensated for and causes rubber-banding and ghost shots. As a rule, a stable 50 ms beats an unstable 20 ms.
Why is jitter, not ping, the bigger problem on video calls?
Call apps include a small jitter buffer, typically 20 to 80 ms, that smooths arriving packets, so a steady high ping just adds manageable conversational delay. Jitter above the buffer size causes packets to be discarded, producing the choppy cutting-out audio, so a 200 ms ping can sound clear while a 10 ms ping with 40 ms jitter drops out constantly.
If both my ping and jitter are high, what should I fix first?
Start with Ethernet, because a wired connection targets jitter directly by removing Wi-Fi channel contention. If ping is still high after that, the remaining problem is likely your ISP's routing or distance to the server, which needs a closer server region or an ISP-side fix.