Jitter is one of the main reasons a video call turns choppy or a voice call sounds robotic, even when your connection looks fast on paper. It describes how much the delay between data packets varies as they cross a network, and it matters most for real-time traffic like video conferencing, VoIP and online gaming. This article explains what jitter is, how it differs from latency, what causes it, what counts as good jitter, and how to reduce it.
Table of Contents
Jitter is the variation in the time it takes for data packets to arrive across a network. On a healthy connection, packets arrive at steady, even intervals; with jitter, some arrive early and some late, and that unevenness is the jitter.
Picture a video call between two offices. The audio is split into packets that should arrive at regular intervals, say every 20 milliseconds. If network congestion holds some packets back, they bunch up and arrive unevenly. The receiving device sees that uneven timing as jitter, and the call starts to sound choppy.
Because jitter is a timing problem, it hits latency-sensitive applications hardest: video conferencing, voice calls and gaming all rely on a steady stream of packets. Monitoring jitter helps network teams spot congestion and track down the problems that affect time-sensitive traffic.
Jitter and latency are related but not the same thing. Latency, often measured as ping, is the total time a packet takes to travel from one point to another, usually given as a one-way delay or a round trip. Jitter is the variation in that delay from one packet to the next.
You can have low latency but high jitter: packets arrive quickly on average, but at uneven intervals, which still disrupts a live call. For real-time media, steady timing (low jitter) often matters as much as raw speed (low latency).
Jitter comes from anything that makes packets take different amounts of time to reach their destination. The common causes are:
Regular jitter tests help pin down which of these is at play, so you can manage traffic, cut interference and check that your network hardware is in good shape.
Jitter hits real-time applications hardest, because they need packets delivered on a steady schedule. When timing becomes erratic, quality drops in predictable ways:
Keeping jitter low is what keeps these experiences smooth. Left unchecked, it can turn an otherwise fast connection into an unreliable one for anything happening in real time.
'Good' jitter is simply a level low enough that users don't notice a problem. As a rule of thumb:
These figures are rules of thumb rather than hard standards, and they are separate from latency: one-way latency for a good voice call should stay under about 150 ms, and packet loss under 1 per cent. Some small, passing jitter is normal on any network; the goal is to keep it within bounds your applications can absorb, usually with help from a jitter buffer.
Excessive jitter can disrupt real-time apps, but it is usually manageable. A few practical steps help:
If you are building video conferencing into your own app, you don't have to solve jitter from scratch. Digital Samba's embedded video SDK manages it for you, using a jitter buffer and adaptive bitrate to smooth out uneven packet timing in real time.
Because it runs on WebRTC, the SDK reacts to changing network conditions on each connection, adjusting video quality to keep calls stable rather than letting them stutter or drop. A call degrades gracefully on a weak connection instead of failing outright.
You can start building with a free developer account and add real-time video to your product with a few lines of code.
Jitter is a normal part of how networks behave, but too much of it quietly ruins real-time communication. Once you know what causes it, from congestion to Wi-Fi interference, you can keep it in check with wired connections, QoS, a jitter buffer and the right hardware. For anything happening in real time, steady packet timing is what keeps calls clear, video smooth and gameplay responsive.
Jitter under 30 ms is generally good and works well for VoIP, video calls and gaming. Between 30 and 50 ms you may notice minor choppiness, and over 50 ms usually causes dropped audio or frozen video. These are rules of thumb rather than hard limits.
Latency, often measured as ping, is the total time a packet takes to travel across a network. Jitter is how much that delay varies from one packet to the next. You can have low latency but high jitter, and for real-time media the steadiness of the timing matters as much as the raw speed.
Yes. 20 ms of jitter is within the good range (under 30 ms) and should give clear voice and video calls for most users. You are only likely to notice problems once jitter climbs past about 30 to 50 ms.
High jitter makes packets arrive unevenly, which causes choppy or robotic audio, frozen or stuttering video, and lag in games. It can make a fast connection feel unreliable for anything happening in real time.
Most internet speed tests report jitter alongside download speed, upload speed and ping. For ongoing monitoring, network tools can track jitter over time and flag spikes before they affect users.
Use a wired connection instead of Wi-Fi, turn on Quality of Service (QoS) to prioritise real-time traffic, rely on a jitter buffer to even out packet timing, and upgrade older hardware or bandwidth if congestion is the cause.