Definition

What Is Jitter? Network Jitter in Calls, Explained

Choppy audio on a fast connection is usually jitter. Here's what it is, how apps hide it with a jitter buffer, and how much of it a call can take.

Jitter vs latency

Jitter

Latency

What it measures

How much the delay changes from packet to packet

How long one packet takes to get from sender to receiver

Unit

Milliseconds of variation

Milliseconds, one-way or round trip

What users notice

Choppy, robotic or clipped audio; stuttering video

People talking over each other; a lag before replies

Main causes

Congested queues, busy Wi-Fi, route changes

Distance, number of hops, processing time

How apps cope

A jitter buffer that waits a little before playing

Shorter routes, nearby servers, fewer processing steps

Trade-off

A bigger buffer hides more jitter but adds latency

Can't be buffered away; only reduced

Acceptable for calls

Under 30 ms (Microsoft Teams target, client to edge)

Under 150 ms one-way (ITU-T G.114)

What is jitter?

Real-time audio travels as a stream of small packets. A voice app might send one packet every 20 ms, each carrying 20 ms of sound. If every packet took exactly the same time to arrive, the receiver could play them the moment they landed.

That never happens on a real network. One packet waits behind a large download in a router queue. The next one gets through straight away. A third takes a slightly different route. The result is that packets sent 20 ms apart arrive 5 ms apart, then 45 ms apart, then 15 ms apart. That variation is jitter.

Jitter is sometimes called packet delay variation. It's measured in milliseconds, and it's separate from latency: a link can have high latency and low jitter (a long but steady satellite hop) or low latency and high jitter (a short but congested Wi-Fi link).

How jitter buffers work

Because audio has to play at a constant rate, the receiver can't just play packets as they arrive. Instead it puts them in a jitter buffer: a short queue that holds packets for a few tens of milliseconds, puts them back in order and releases them on a steady clock.

Static and adaptive buffers

A static buffer always waits the same amount of time. It's simple, but it's either too small for a bad network or adds needless delay on a good one. Most modern calling stacks use an adaptive buffer that grows when jitter rises and shrinks when the network calms down. WebRTC's audio engine, NetEq, works this way.

Late packets count as lost

A packet that arrives after its playback slot is useless, so the buffer throws it away. To the listener, a late packet and a lost packet sound the same. That's why high jitter often shows up as packet loss in call stats.

How jitter is calculated

RTP, the protocol that carries most call media, defines interarrival jitter as a running average of how much the spacing between packets differs from the spacing they were sent with (RFC 3550). Receivers report this value back to senders in RTCP reports, and browsers expose it through WebRTC's getStats().

How much jitter is acceptable?

There's no single standard number, so teams usually work to vendor targets. Microsoft publishes these for Teams media, measured over any 15-second window:

  • From your network edge to Microsoft: jitter under 15 ms.

  • From the user's device to Microsoft, including Wi-Fi: jitter under 30 ms.

As a rule of thumb, under 30 ms is fine for voice and video. Between 30 and 50 ms, the buffer has to grow and calls start to feel laggy. Past that, expect dropouts unless the buffer is allowed to add a lot of delay, which pushes the call toward the 150 ms one-way limit that ITU-T G.114 recommends for natural conversation.

Rule of thumb: keep jitter under 30 ms and let an adaptive buffer handle the rest. If you need a big fixed buffer to get clean audio, fix the network instead.

Where jitter matters

  • Voice and video calls: the most sensitive case. Audio has to play on a strict clock, and any wait for a late packet is heard.

  • Live streaming with interaction: webinars, live shopping and auctions where hosts answer viewers in real time.

  • Online games and remote control: jitter makes movement feel uneven even when average latency is low.

  • Chat messages: barely affected. Messages travel over a reliable connection such as a WebSocket, and a few milliseconds of variation is invisible in a text conversation.

To check jitter in a web call, read jitter (in seconds) from the inbound-rtp entries returned by RTCPeerConnection.getStats(). Divide jitterBufferDelay by jitterBufferEmittedCount to see how long the buffer is holding audio on average.

Common causes and fixes

  • Busy Wi-Fi. Interference and many devices on one channel are the most common source. A 5 GHz band or a wired connection usually helps.

  • Uploads on the same link. Large uploads fill router queues. Quality of Service (QoS) rules that put voice traffic first reduce the queueing.

  • VPNs. They add hops and extra encryption, and often route traffic far from the nearest media server. Microsoft recommends sending call traffic around the VPN.

  • TCP fallback. When UDP is blocked, media runs over TCP, which retransmits and holds packets in order. That turns small losses into bigger delays and more jitter.

  • Over-buffering. A buffer set too high hides jitter but makes the whole call laggy. Prefer adaptive buffers over a large fixed one.

Jitter in CometChat calls

If you're adding voice or video calls to your app, you don't have to build a jitter buffer yourself. The media stack handles it, and your job is to give it a clean network path.

WebRTC calling that adapts to the network

CometChat Calls is built on WebRTC, so audio runs through WebRTC's processing pipeline with Opus as the preferred codec. The docs list adaptive bitrate, automatic quality adjustment based on network conditions and automatic reconnection after network interruptions. Media prefers UDP on ports 10000 to 20000 and falls back to TCP on port 443 through TURN, so check that firewalls allow UDP to avoid the extra jitter TCP adds. CometChat recommends 100 to 300 kbps for a voice call.

Check network requirements · Start building free

Frequently asked questions

What is a good jitter level?

Under 30 ms is good for voice and video calls, and under 15 ms is excellent. Those match Microsoft's Teams targets for the full client path and for the network edge.

What is the difference between jitter and latency?

Latency is how long a packet takes to arrive. Jitter is how much that time changes from one packet to the next. A link can have one without the other.

Does jitter cause packet loss?

Indirectly. A packet that arrives after the jitter buffer has already played its slot gets discarded, so heavy jitter shows up as loss even when every packet arrived.

How do I reduce jitter?

Use a wired connection or 5 GHz Wi-Fi, keep large uploads off the same link, set QoS to prioritize voice, avoid VPNs for call traffic and make sure UDP isn't blocked.

How do I test for jitter?

Run a test call and read the jitter value from WebRTC stats, or use a network test tool that reports jitter over a period of time rather than a single ping.

Related terms