VoIP Calls
Voice calls send audio in a steady stream of small packets. When those packets arrive unevenly, the result is choppy or robotic-sounding audio, even if every packet eventually gets there.
Guides
Jitter is the variation in how long each packet takes to arrive, measured from one round trip to the next. A connection can have a perfectly good average ping and still feel unpredictable if its jitter is high — which is exactly why gaming, VoIP calls, video conferencing and live streaming care about it as much as raw speed.
Written by the Pingvero team · Last updated September 11, 2026
The Basics
Network jitter is the variation in delay between packets that are meant to arrive at a steady pace. If everything worked perfectly, every packet in a stream would take exactly the same amount of time to arrive. In practice, some arrive a little early, others a little late — and that inconsistency, not the delay itself, is what jitter measures.
A simple way to think about it: latency is how long the trip takes. Jitter is how much that trip time changes from one packet to the next. A courier who always takes 20 minutes has low latency and low jitter. A courier who sometimes takes 10 minutes and sometimes 40 has a similar average, but much higher jitter — and is far harder to plan around.
Jitter is almost always expressed in milliseconds (ms), the same unit used for ping and latency. A low, steady jitter value means a connection behaves predictably; a high or erratic one means the timing between packets is swinging around, which is what real-time applications notice first.
The formal definition comes from real-time streaming protocols: RFC 3550, which specifies RTP (the Real-time Transport Protocol used for most VoIP and video calls), defines jitter as the statistical variance of the packet interarrival time — the same idea described in plain language above.
Under the Hood
A conceptual look at the same four packets on two very different connections.
| Packet | Round-trip time |
|---|---|
| Packet 1 | 20 ms |
| Packet 2 | 21 ms |
| Packet 3 | 20 ms |
| Packet 4 | 22 ms |
| Packet | Round-trip time |
|---|---|
| Packet 1 | 20 ms |
| Packet 2 | 45 ms |
| Packet 3 | 18 ms |
| Packet 4 | 60 ms |
The first sequence stays close to its average the whole way through; the second swings widely even though none of its individual values are unusually high on their own. That swing is what applications built around a steady timing budget — voice, video, games — end up reacting to. This is a conceptual illustration rather than a fixed formula: the exact way jitter is calculated can vary between tools, protocols (such as RTP for VoIP) and network conditions.
Reading a Result
General reference points, not fixed industry standards.
| Jitter | General interpretation | Typical experience |
|---|---|---|
| Under 10 ms | Excellent | Very stable, ideal for gaming, VoIP and video calls |
| 10–30 ms | Good | Smooth for most real-time use |
| 30–50 ms | Fair | Occasional stutter in sensitive applications |
| 50+ ms | High | Potentially problematic for real-time use |
The impact of jitter depends on the application, network conditions, and how the application handles packet timing — these ranges are general guidelines, not universal thresholds. Run the Jitter Test to see where your own connection falls.
The Other End
High jitter means the timing between packets is inconsistent, even if the average delay looks fine.
High jitter is not the same thing as high ping. Ping is the delay itself; jitter is how much that delay moves around. A connection can have a perfectly reasonable ping and still feel rough in a call or a game if its jitter is high, because it is the inconsistency — not the average delay — that real-time applications struggle to absorb.
Troubleshooting
Any of these can contribute, and often more than one is at play at once.
Not every case will trace back to one of these on its own — congestion and queueing are the classic, most common causes, but jitter is often the result of several smaller factors adding up rather than a single fault.
Related Terms
| Metric | What it measures | Lower is better? | Why it matters |
|---|---|---|---|
| Ping / Latency | The response time for a single round trip | Yes | Determines how quickly a device gets a reply |
| Jitter | How much that response time varies from one round trip to the next | Yes | Determines how consistent and predictable a connection feels |
Think of ping as one single measurement and jitter as how much that measurement bounces around over several attempts. A connection can have low ping but high jitter — responding quickly on average while still feeling unpredictable moment to moment. Checking both together with our ping tool and Latency Test, alongside the Jitter Test, gives a fuller picture than any one of them alone.
Related Terms
| Metric | What it measures |
|---|---|
| Jitter | Variation in the timing of packets that do arrive |
| Packet loss | The share of packets that never arrive at their destination at all |
Jitter is about when packets show up; packet loss is about whether they show up at all. A connection can have low jitter and still lose data outright, or have high jitter while every packet eventually arrives. Both independently affect call and stream quality, which is why it is worth checking each on its own with the Packet Loss Test — see our What Is Packet Loss? guide for the full explanation.
Gaming
Yes. Online games depend on a steady stream of small, timing-sensitive updates to keep the game state in sync between your device and the server. When jitter is high, those updates stop arriving at a predictable pace, which can make movement, hits and reactions register late or out of order — even when the average ping looks fine.
This matters most in competitive and fast-paced games, and it extends to in-game voice chat, which is just as sensitive to inconsistent timing as the gameplay itself. No specific jitter number guarantees a smooth match — game engines, server tick rate and your own ping all play a part too — but lower and steadier is consistently better.
Check your own connection with the Jitter Test, the Ping Test, or a full Internet Speed Test.
Calls & Streaming
Real-time audio and video are some of the most jitter-sensitive uses of a connection.
Voice calls send audio in a steady stream of small packets. When those packets arrive unevenly, the result is choppy or robotic-sounding audio, even if every packet eventually gets there.
Apps like Zoom or Teams face the same problem across both audio and video, which can show up as frozen frames, lip-sync drift or audio that briefly cuts out under high jitter.
Most real-time apps try to hide moderate jitter with a jitter buffer — a small delay that holds incoming packets for a fraction of a second and plays them back at a steady pace, smoothing out minor timing differences before you notice them. A larger buffer absorbs more jitter but adds a little extra delay; if jitter is high enough or spikes unpredictably, the buffer runs out of room to compensate and the audio or video quality suffers anyway.
Related Terms
No. Download and upload speed describe how much data your connection can move per second — the number reported by an Internet Speed Test. Jitter describes something entirely different: how regularly the timing of individual packets holds up, regardless of how much data is moving.
A connection can be very fast and still have high jitter, and a comparatively slow connection can have very low, stable jitter. This is why a fast plan does not automatically guarantee a smooth video call or lag-free game — bandwidth and timing consistency are separate properties of the same connection. If you are sizing a connection for real-time use, our Bandwidth Calculator can help estimate the throughput you actually need.
Fix It
None of these guarantee a specific result, but they address the most common causes.
Use a wired Ethernet connection when possible.
Move closer to your WiFi router.
Reduce WiFi interference from other networks and nearby electronics.
Pause unnecessary background downloads or uploads.
Check your router’s firmware and settings for updates.
Restart or troubleshoot your networking equipment.
Test at different times of day to see whether it changes.
Compare a WiFi result with a wired result to isolate the cause.
Check whether other devices on the network are causing congestion.
Contact your ISP if instability persists across several tests.
Methodology
Jitter is calculated from a series of latency samples taken one after another, rather than from a single measurement. A tool sends several requests, times each round trip, and looks at how much those round-trip times differ from one another — a tightly clustered sequence produces a low jitter value, while a sequence that swings widely produces a high one.
The exact method varies by tool and context: real-time protocols like RTP (used for VoIP) calculate jitter as defined in RFC 3550, the standard that specifies RTP itself, while browser-based tools like this one use their own comparable approach over a short test run. Whatever the method, the result is reported in milliseconds so it can be compared directly against ping and latency.
Try It Yourself
Everything above is easier to judge once you have a real number in front of you.
FAQ
Short answers to the questions people ask most about jitter.
In networking, jitter is the variation in the delay of packets arriving one after another. If packets are meant to arrive at a steady pace but some come early and others late, that inconsistency is jitter — a separate measurement from the delay itself.
As a general reference, under 10 ms is excellent and 10–20 ms is usually fine for competitive play, though these are indicative ranges rather than a fixed standard. What feels acceptable also depends on the game and on your ping. Check both with our Jitter Test and ping checker.
10 ms is generally considered good jitter. Most real-time applications, including gaming and video calls, handle that level of variation without a noticeable effect, though very latency-sensitive uses may still be able to tell the difference from a near-zero result.
30 ms is on the higher side. It is not extreme, but it is enough that some real-time applications — particularly voice calls and fast-paced games — may show occasional stutter or inconsistency. It is usually worth investigating rather than ignoring.
Common causes include network congestion, buffering and queueing on network equipment, WiFi interference, an overloaded router, heavy simultaneous network usage, and unstable routing on your ISP’s network. See the causes section above for the fuller list.
WiFi can contribute to jitter more than a wired connection does, since wireless signals are affected by distance, walls, interference from other networks and shared airtime with other devices. A wired Ethernet connection is generally more consistent.
Ping (or latency) is the delay of a single round trip. Jitter is how much that delay varies from one round trip to the next. A connection can have a low average ping and still have high jitter if that delay swings widely between requests.
Yes. Ping and jitter measure different things, so a connection can respond quickly on average while still being inconsistent from one moment to the next. That inconsistency is often what makes a connection feel unpredictable even when the ping result looks good.
Use a wired Ethernet connection where possible, move closer to your WiFi router, reduce WiFi interference, pause large downloads or uploads, check your router’s firmware and settings, and test at different times of day. See the full checklist above, and measure the effect with our Jitter Test.
Jitter is calculated from a series of latency measurements taken one after another, by looking at how much those measurements vary. The exact method can differ between tools and protocols, but the result is generally expressed in milliseconds (ms).
Yes. Online games depend on a steady stream of timing-sensitive updates, so high jitter can make gameplay feel inconsistent even when average ping looks acceptable, with actions that register late or out of order.
Yes. Video and voice calls rely on packets arriving at a steady pace to reconstruct audio and video smoothly. High jitter can cause choppy audio, robotic-sounding voices and video that stutters or falls out of sync, even when a jitter buffer is smoothing some of it out.
Get started
Run the free Jitter Test to get a real number, then pair it with a ping and latency test for the full picture.