Logo

MonoCalc

/

Jitter Calculator

Networking

Jitter is within acceptable range — Good quality (MOS 4.28).

Input Parameters

Mean Jitter

10.556 ms

Average |D[i] − D[i−1]|

RFC 3550 Jitter

4.720 ms

RTCP/RTP estimator

Peak Jitter

27.000 ms

At packet 7

Std Deviation

8.800 ms

Of inter-arrival delays

Delay Statistics

Min Delay

18.000 ms

Max Delay

45.000 ms

P50 (Median)

20.500 ms

P95

40.500 ms

P99

44.100 ms

Packets

10

VoIP Quality (MOS)

4.28

Good

MOS 1 (worst) – 4.5 (excellent). ITU-T G.114 recommends < 30 ms jitter for VoIP. Codec tolerance (G.711 (PCMU/PCMA)): 30 ms.

Jitter Buffer Headroom

Buffer Used

27.000 / 50 ms

Headroom: 23.000 ms — Buffer can absorb peak jitter.

Packets

10

Mean Jitter

10.556 ms

RFC 3550

4.720 ms

Quality

Good · MOS 4.28

Per-Packet Breakdown

MOS Score vs Jitter Reference

Estimated VoIP quality at various jitter levels. Current mean jitter (10.556 ms) is highlighted.

Mean Jitter (ms)MOS ScoreQuality
0 ms4.41Excellent
5 ms4.36Excellent
10 ms4.29Good
15 ms4.22Good
20 ms4.14Good
30 ms3.95Fair
40 ms3.74Fair
50 ms3.51Poor
75 ms2.88Poor
100 ms2.22Bad

About This Tool

Jitter Calculator – Network QoS Analysis for VoIP and Real-Time Traffic

Network jitter is the variation in the arrival time of successive packets traveling across a network path. While a small, consistent delay is manageable for most applications, irregular packet spacing causes audio glitches in VoIP calls, frame drops in video conferences, and rubber-banding in online games. This Jitter Calculator quantifies that variation so you can diagnose problems, size playout buffers, and verify whether a link meets the quality-of-service (QoS) requirements of delay-sensitive traffic.

What Is Jitter and Why Does It Matter?

When packets travel from sender to receiver they traverse routers, switches, and queues that each introduce variable processing time. Even on a low-latency link, two consecutive packets sent 20 ms apart may arrive 18 ms and 27 ms apart — a 9 ms jitter spike. At low rates this is imperceptible; at sustained high rates it overwhelms playout buffers and degrades call quality. The ITU-T G.114 recommendation defines a maximum one-way jitter of 30 ms for toll-quality VoIP. Online gaming engines typically require jitter below 15 ms to maintain smooth frame synchronization.

Calculation Modes Explained

Mean Absolute Jitter

The most straightforward metric. Given a series of inter-arrival delays D[1], D[2], … D[n], the per-packet deviation is d[i] = |D[i] − D[i−1]| and Mean Jitter is Σ d[i] / (n − 1). This gives an unweighted statistical average over the entire series — useful for post-capture batch analysis.

RFC 3550 (RTCP) Jitter Estimator

RTP/VoIP endpoints report jitter using the exponentially weighted moving average defined in IETF RFC 3550: J(i) = J(i−1) + (|d[i]| − J(i−1)) / 16. The divisor 16 gives the estimator a memory of roughly 16 recent packets, making it responsive to sudden spikes without being destabilized by isolated anomalies. This is the metric you will see in RTCP Receiver Reports, Wireshark RTP streams, and SIP quality dashboards.

Peak Jitter

The single worst inter-arrival deviation in the measurement window. While mean jitter governs steady-state audio quality, peak jitter determines the minimum buffer depth needed to prevent any packet from arriving too late for playback. The calculator highlights which packet caused the worst spike so you can correlate it with bursts, routing changes, or queue events.

Jitter Buffer Headroom

A playout buffer delays media rendering to smooth out jitter. Its required size is determined by the worst-case peak jitter, not the mean. The Headroom indicator shows how much buffer capacity remains after the peak spike: Headroom = Buffer Size − Peak Jitter. A negative headroom means the buffer is too small and packets will be discarded at the tail, producing audible clicks or video artifacts. A common starting point is to set the buffer to 2× the Peak Jitter observed in your environment.

VoIP Quality and MOS Score

The calculator estimates a Mean Opinion Score (MOS) — a 1–4.5 quality scale standardized by ITU-T P.800 — using a simplified E-Model proxy. Jitter is the primary input; the formula applies R = 93.2 − (jitter / 2) and maps R to MOS via the standard cubic approximation. Scores of 4.3–4.5 are Excellent, 4.0–4.3 are Good, 3.6–4.0 are Fair, 2.5–3.6 are Poor, and below 2.5 are Bad. The codec profile selector (G.711, G.729, G.722, Opus, H.264) auto-fills the typical packet interval and tolerance threshold for each codec so the quality assessment is contextually correct.

How to Use This Tool

Paste your data in either Delay Series mode (inter-arrival delays already computed, e.g. from a tshark or iperf3 report) or Timestamps mode (absolute packet arrival times extracted from a packet capture). Use comma- or newline-separated values in milliseconds. Set your jitter buffer size and alert threshold, then click Calculate. The tool delivers mean, RFC 3550, and peak jitter alongside a per-packet breakdown table and MOS score — all computed locally in the browser with no data upload required.

Typical Jitter Benchmarks by Application

VoIP (SIP/RTP):< 30 ms (ITU-T G.114). < 10 ms for HD voice codecs like G.722 or Opus. Video Conferencing:< 30 ms for smooth rendering; < 15 ms for 1080p/60fps. Online Gaming:< 15 ms for competitive play; < 5 ms for fast-action titles. Live Streaming:< 50 ms with adaptive bitrate; jitter is absorbed by the CDN buffer. IPTV:< 50 ms; higher values are handled by the STB's de-jitter buffer.

Common Causes of High Jitter

Network jitter typically originates from queue congestion at overloaded routers, Wi-Fi contention in wireless cells with many active clients, traffic bursting when bulk transfers compete with real-time flows, and route flapping where packets take different paths with different latencies. Mitigations include QoS traffic prioritization (DSCP marking, traffic shaping), deploying dedicated VLAN or MPLS paths for real-time traffic, and tuning playout buffer depths on endpoints and media gateways.

Frequently Asked Questions

Is the Jitter Calculator free?

Yes, Jitter Calculator is totally free :)

Can I use the Jitter Calculator offline?

Yes, you can install the webapp as PWA.

Is it safe to use Jitter Calculator?

Yes, any data related to Jitter Calculator only stored in your browser (if storage required). You can simply clear browser cache to clear all the stored data. We do not store any data on server.

How does the Jitter Calculator work?

The tool accepts a series of packet inter-arrival delays or absolute timestamps in milliseconds, then computes mean absolute jitter, RFC 3550 jitter, peak jitter, and standard deviation. For Mean Jitter it averages |D[i] - D[i-1]| across consecutive delays. RFC 3550 jitter uses the exponentially-weighted estimator J(i) = J(i-1) + (|d[i]| - J(i-1)) / 16 specified for RTP/VoIP streams.

What is the difference between Mean Jitter and RFC 3550 Jitter?

Mean Jitter is a simple average of all absolute inter-arrival deviations, giving a flat statistical view. RFC 3550 Jitter uses an exponentially-weighted moving average that weights recent packets more heavily — this matches the algorithm embedded in VoIP endpoints and RTCP receiver reports, making it the standard metric for SIP/RTP diagnostics.

What jitter values are acceptable for VoIP calls?

ITU-T G.114 recommends one-way delay under 150 ms and jitter under 30 ms for toll-quality VoIP. A Mean Jitter below 10 ms is considered Excellent, 10–20 ms is Good, 20–30 ms is Fair, and above 30 ms causes audible glitches or dropped packets. The calculator rates your result against these thresholds and estimates a simplified MOS score.

Should I enter timestamps or inter-arrival delays?

Use Timestamps mode when you have raw packet capture data (absolute arrival times in ms). Use Delay Series mode when you already have the gap between consecutive packets. In Timestamps mode the tool automatically derives the inter-arrival delays before running all calculations.

How is the Jitter Buffer Headroom calculated?

Headroom = Buffer Size − Peak Jitter. A positive value means the buffer can absorb the worst spike without causing audio or video artifacts. A negative value indicates the buffer will overflow, leading to packet drops even with buffering active. As a rule of thumb, set your playout buffer to at least 2× the Peak Jitter.

What is the maximum number of data points supported?

The calculator supports up to 10,000 inter-arrival delay values per session to ensure UI responsiveness. For larger packet captures, consider pre-processing the data in a terminal with tools like tshark or tcpdump and pasting the aggregated delay series here.