


# Jitter Measurement Guide: RMS, Peak-to-Peak and TIE

_Published: 2026-11-21_

Table of Contents

Toggle

- Jitter measurement unit: seconds and unit intervals
- Period jitter vs TIE: the same edges produce different numbers
- RMS jitter vs peak to peak jitter: compare matching statistics
- Jitter measurement oscilloscope: control the acquisition first
- Jitter measurement techniques: match the instrument to the question
- Random jitter vs deterministic jitter: keep the model visible
- Noise and slew rate: why the crossing time changes
- Clock jitter applications: what to measure and how to judge it
- Jitter measurement checklist: make the report reusable
- Jitter Measurement FAQs
- Custom High-Speed PCBs with Engineering DFM Support
- Technical References

For a useful jitter measurement, define the timing event, reference, measurement bandwidth and reported statistic before comparing numbers. A result of “10 ps jitter” is incomplete: 10 ps of period RMS, time-interval-error RMS and observed peak-to-peak timing variation can describe different behavior.

This guide covers electronic clock and data-edge timing, not packet-delay variation in a network. It explains the main measurements, compares instruments and shows how to use the results for clock distribution, serial links and ADC sampling. All numerical examples below are synthetic calculations, not measurements from a customer PCB.

![Jitter Measurement title over an illustrative clock PCB and bench oscilloscope arrangement](https://www.bestpcbs.com/blog/wp-content/uploads/2026/11/project422-jitter-measurement-hero.jpg)Illustrative measurement setting. Instrument appearance and the pictured PCB do not establish a measured jitter value.

## Jitter measurement unit: seconds and unit intervals

Timing jitter describes variation in when an edge reaches a defined event, usually a voltage-threshold crossing, relative to the chosen timing reference. State the threshold, edge polarity and reference because changing them can change the result. A fixed propagation delay and a variation of that delay are not the same quantity.

Time results commonly use seconds, picoseconds or femtoseconds: 1 ps = 10⁻¹² s and 1 fs = 10⁻¹⁵ s. A unit interval, UI, expresses time relative to the symbol interval used by the link. For an assumed 1 Gb/s NRZ stream, UI = 1/(10⁹ s⁻¹) = 1 ns = 1,000 ps. A 20 ps timing width is therefore 0.02 UI, or 2% of that UI.

Do not use the clock frequency to define data UI without checking the interface. A DDR or multilevel link can have a different relationship between clock, symbol rate and bit rate. Use the applicable interface definition before converting a compliance limit.

Also separate skew from jitter. A consistent arrival-time difference between two clock branches is a relative timing offset; variation over time is another effect. A design may need both checks, but combining them into one unlabeled “jitter” number obscures what should be corrected.

## Period jitter vs TIE: the same edges produce different numbers

Let tn be the measured time of the nth rising edge and T the chosen reference period. Period error is **(tn+1 − tn) − T**. Time interval error, TIE, compares an edge with its reference position: **tn − (t0 + nT)** for the fixed reference used in this example.

Cycle-to-cycle period variation compares consecutive periods. It highlights a different behavior from the accumulated displacement shown by TIE. A reference recovered from the signal can track some timing variation; its recovery method and bandwidth therefore belong in the measurement definition.

**One synthetic edge record**
**Derived quantity and interpretation**

Reference period: 1,000 ps
Ideal edge times: 0, 1,000, 2,000, 3,000 and 4,000 ps.

Actual times: 0, 1,010, 2,000, 2,990 and 4,000 ps
TIE: 0, +10, 0, −10 and 0 ps relative to that fixed reference.

Measured periods
1,010, 990, 990 and 1,010 ps; mean period is 1,000 ps.

Period errors
+10, −10, −10 and +10 ps; their RMS is 10 ps.

Adjacent-period differences
−20, 0 and +20 ps. These are cycle-to-cycle differences, not the TIE sequence.

TIE population statistics for these five edges
Mean 0 ps, RMS about the mean 6.32456 ps, observed peak-to-peak 20 ps. Five edges do not characterize a production clock’s distribution.

The example explains why two instruments can disagree without either being numerically broken: they may be reporting different observables or using different references. First align the definitions; only then investigate acquisition or instrument errors.

![Synthetic TIE values at five edge indices: zero plus ten zero minus ten and zero picoseconds](https://www.bestpcbs.com/blog/wp-content/uploads/2026/11/project422-jitter-measurement-tie.jpg)The same five-edge teaching record used in the table. This is a calculated TIE sequence, not an oscilloscope capture.

## RMS jitter vs peak to peak jitter: compare matching statistics

RMS about the mean describes the spread of timing-error samples. For N samples ei, calculate the square root of the mean of (ei − mean(e))² when that is the specified population statistic. Some tools use a sample-standard-deviation estimator or report RMS without removing the mean; record the actual definition.

Observed peak-to-peak is the largest recorded value minus the smallest. In the five-edge example, +10 − (−10) = 20 ps. Its ratio to the 6.32456 ps RMS is a property of this tiny record, not a universal conversion factor.

Under a Gaussian random-jitter model, the theoretical tails are unbounded. Collecting more edges can expose larger extremes even when the underlying RMS remains similar. Therefore a measured peak-to-peak value needs a record length or event count. A total-jitter estimate at a specified BER needs the statistical model and BER as well.

Do not multiply every RMS jitter result by six, fourteen or another remembered factor. Such factors have specific assumptions and probability definitions; mixed random and deterministic jitter does not become a Gaussian distribution merely because a histogram looks smooth.

## Jitter measurement oscilloscope: control the acquisition first

At the bench, identify the actual measurement node and required loading. A probe or cable can alter the waveform, and the oscilloscope’s own vertical noise and timebase behavior can contribute to the reported crossing times. Choose a setup capable of resolving the required effect, not only one whose screen shows a clean clock.

1. Confirm clock rate or data pattern, signal amplitude, termination and threshold. Record rising, falling or both edge selections.
2. Define the timing reference. For recovered-clock measurements, retain the recovery method and loop settings required by the application.
3. Set and record acquisition rate, analog bandwidth, filtering and record length. Verify that the waveform and edges are adequately captured for the chosen method.
4. Inspect the timing trend and distribution as well as summary values. A time-dependent modulation can disappear inside one aggregate number.
5. Repeat under controlled conditions to check repeatability, then change one suspected influence at a time.

Begin by ruling out a measurement artifact. If moving the probe ground connection changes the result substantially, investigate the connection and loading before redesigning the oscillator. If changing the threshold produces a large timing shift, inspect waveform shape, noise and edge slope rather than assuming the timebase is the sole cause.

For a hypothetical uncorrelated-error model, suppose measured timing RMS is 12 ps and a separately characterized measurement contribution is 8 ps under matching conditions. Quadrature subtraction gives √(12² − 8²) = **8.94427 ps**, not 12 − 8 = 4 ps. This estimate is valid only when the components and statistics support that model; correlated errors or unmatched bandwidth invalidate the simple subtraction. Near the instrument floor, report the limitation.

## Jitter measurement techniques: match the instrument to the question

A time-domain waveform, an oscillator phase-noise spectrum and a bit-error test expose different aspects of timing behavior. Choose the method by the decision you need to make, then state its limitations. An instrument’s ability to display a result does not establish that its noise floor is low enough for your clock.

**Technique**
**Use it for this decision; verify these conditions**

Real-time oscilloscope timing analysis
Examine individual edges, TIE trends, distributions and relationships with data or supply events. Verify probing, timing reference, event count and instrument contribution.

Phase-noise analysis
Characterize oscillator noise versus offset frequency and derive integrated phase/time jitter over a stated band. Verify carrier frequency, integration limits, spur treatment and analyzer floor.

Bit-error-rate testing
Evaluate link errors or timing margin with a defined pattern, receiver setup and test duration. It does not identify every physical cause and is not interchangeable with a clock RMS specification.

Simulation
Compare modeled channel, driver, receiver and noise effects before hardware changes. Validate inputs and compare with measurements; a simulated eye is not a production measurement.

For phase-derived time jitter, the small-phase relation is **σt = σφ/(2πf0)**, with phase RMS in radians and carrier frequency f0 in hertz. A hypothetical integrated phase RMS of 0.001 rad at a 100 MHz carrier gives 1.59155 ps RMS. The integration band must accompany that result; a single phase-noise value at one offset cannot supply the whole integrated jitter.

Analog Devices’ MT-008 explains the phase-noise integration workflow. Use an appropriate implementation and its documented treatment of sidebands and spurs rather than integrating displayed dB numbers directly. Do not compare two integrated results from different offset bands as though they represented the same measurement.

## Random jitter vs deterministic jitter: keep the model visible

Random jitter, RJ, is commonly treated with a Gaussian model and summarized by an RMS quantity. Deterministic jitter, DJ, represents bounded systematic contributions such as periodic modulation, duty-cycle distortion or data-dependent effects. The decomposition is an analysis model, not a photograph of physically isolated noise sources.

A periodic component in a timing trend suggests a repeatable influence worth correlating with known activity. A data-dependent timing shift suggests examining pattern history and channel response. Neither observation uniquely names the failed component. Change the suspected influence in a controlled test and check whether the corresponding timing feature changes.

Keysight’s dual-Dirac description explicitly distinguishes RJ RMS from a model-dependent DJ(δδ) quantity used to estimate TJ at a specified BER. Do not relabel that DJ estimate as the directly observed peak-to-peak span of all deterministic behavior. Keep the instrument algorithm, settings and target BER with the report.

For a serial link, a favorable decomposition result does not override the receiver’s required compliance method. Follow the applicable interface procedure, including pattern, recovery and equalization settings. There is no single general-purpose IPC jitter limit for every PCB interface.

## Noise and slew rate: why the crossing time changes

Near a locally linear threshold crossing, a small voltage error can produce a timing error approximately equal to **δt ≈ δV / |dV/dt|**. The relation explains an important distinction: limiting bandwidth can reshape or delay a repeatable edge, while noise acting on that edge can change when its threshold is crossed.

Assume 5 mV RMS voltage noise at the crossing and a local slope of 0.5 V/ns. The approximate noise-derived timing RMS is 0.005/0.5 ns = **10 ps**. If the same noise acts on a 1 V/ns slope, the estimate is **5 ps**. These are local illustrative calculations, not a complete instrument uncertainty budget.

A bandwidth limit is therefore not automatically “jitter = 1/bandwidth.” But changing bandwidth can change both edge slope and admitted noise, so its net effect must be evaluated under the actual setup. Reducing noise by filtering while making the edge much slower is a trade-off, not a guaranteed improvement.

![Analytical comparison of five millivolt noise producing ten picosecond timing shift at half a volt per nanosecond and five picoseconds at one volt per nanosecond](https://www.bestpcbs.com/blog/wp-content/uploads/2026/11/project422-jitter-measurement-slope.jpg)Local linear-crossing example with the same 5 mV noise input. It illustrates a mechanism, not measured total jitter.
When comparing board revisions, preserve amplitude, threshold, load, measurement bandwidth and probe arrangement. Otherwise an apparent improvement may come from the measurement setup rather than the circuit. Recheck the waveform and the timing distribution after any change.

## Clock jitter applications: what to measure and how to judge it

**Clock distribution.** A clock feeding several devices must satisfy the relevant input timing and signal-level requirements at the receiving pins. Measure the selected period or TIE quantity under the stated load and operating condition. Examine branch skew separately. Compare the results with the receiving device’s actual specification, not a universal “good clock” number.

**Serial PCB links.** Preserve enough horizontal and vertical margin for the specified receiver and link conditions. Evaluate the required patterns, channel condition, clock recovery and equalization; inspect error behavior or the specified eye/jitter metrics. Keep termination and fixture boundaries controlled. The site’s [signal integrity software guide](https://www.bestpcbs.com/blog/2026/11/signal-integrity-software/) explains how to choose a modeling workflow, while the [eye diagram guide](https://www.bestpcbs.com/blog/2026/07/eye-diagram/) covers the display’s interpretation. An eye that looks open in a short acquisition is not proof of an arbitrarily low BER.

**ADC sampling.** Sampling-time uncertainty changes the sampled voltage most strongly where the input waveform is steep. For a sinusoidal input and the usual small, uncorrelated timing-error approximation, the jitter-only limit is **SNRjitter = −20 log10(2π fin σt)**. Here fin is the analog input frequency, not the sampling-clock frequency.

With an assumed total sampling jitter of 1 ps RMS, a 20 MHz sine input gives a calculated jitter-only limit of **78.0158 dB**; a 100 MHz input gives **64.0364 dB**. The higher-frequency input is more sensitive to the same time uncertainty. These values are not predicted total ADC SNR: quantization, thermal noise, distortion and other effects remain.

To verify the ADC application, use the intended input frequency and amplitude, clock path and acquisition method, and compare the appropriate spectral performance with the device/system requirement. Combine independent jitter contributions by root-sum-square only when the assumptions hold. A low-jitter oscillator datasheet does not include every effect added by the board and converter.

## Jitter measurement checklist: make the report reusable

Use this worksheet before accepting a comparison or releasing a design change. The first row is filled with the synthetic record above so the calculation can be reproduced. Fill the remaining rows with the actual project conditions and criteria; blank fields are unresolved information, not passes.

**Record this input or condition**
**Decision and next action**

Example: fixed 1,000 ps period; TIE [0, 10, 0, −10, 0] ps
Mean 0 ps; population RMS about mean 6.32456 ps; observed peak-to-peak 20 ps. This verifies arithmetic, not a device’s long-term distribution.

Node, load, threshold and edge polarity
Match the intended receiver or measurement definition. Resolve differences before comparing board revisions.

Metric, reference and recovery settings
Distinguish period, cycle-to-cycle and TIE. Retain the method and any loop/filter settings.

Bandwidth, record length and event count
Compare like acquisitions. Do not call a larger observed peak-to-peak value a degradation until the measurement conditions match.

Instrument contribution and repeatability
Show the measurement can resolve the required margin. Report floor/uncertainty limitations rather than subtracting incompatible values.

Requirement, test procedure and result
Identify the device/interface document and its version. Use its applicable acceptance method; record any extrapolated BER model separately from direct observations.

A useful conclusion says which timing requirement was tested, under which conditions, how much margin remains and what was not established. If the report only says “jitter improved,” it is not yet a dependable engineering handoff.

## Jitter Measurement FAQs

### Can I compare 10 ps RMS with 10 ps peak-to-peak?

No. They are different statistics. Obtain the same metric, reference, bandwidth and event count or model definition before comparing the two results.

### Why does peak-to-peak jitter increase with a longer record?

A longer observation can include more extreme events. Under a Gaussian RJ model the tails are theoretically unbounded, so an observed peak-to-peak value is tied to the acquisition, not a guaranteed worst-case bound.

### Is period jitter the same as time interval error?

No. Period error concerns each edge-to-edge interval; TIE concerns edge displacement from the selected reference. The five-edge example gives 10 ps period-error RMS but 6.32456 ps TIE RMS.

### Does lower oscilloscope bandwidth always reduce timing jitter?

No. It can reduce admitted noise while also slowing the crossing slope. Compare the resulting timing error under the required bandwidth and signal conditions rather than assuming one direction of change.

### Can a phase-noise analyzer replace every oscilloscope jitter test?

No. Phase-noise analysis is useful for oscillator spectral behavior and integrated jitter, while a waveform capture can expose edge-by-edge and data-correlated behavior. Select the method required by the application.

### What information is needed with an integrated RMS jitter value?

Include carrier frequency, offset-frequency integration limits, spur treatment and the instrument/method. A single phase-noise point does not define the integral.

### Why can the same 1 ps jitter matter more to a higher-frequency ADC input?

The sinusoid’s slope increases with input frequency. In the stated jitter-only model, 1 ps gives 78.0158 dB at 20 MHz but 64.0364 dB at 100 MHz; total ADC performance includes other limits.

### Does a better jitter result prove the PCB construction is acceptable?

No. It supports the defined timing test. The fabricated board still needs the agreed construction, dimensional, connectivity and other applicable acceptance evidence.

## Custom High-Speed PCBs with Engineering DFM Support

Ready to manufacture the board behind your timing-sensitive design? EBest Circuit supports custom multilayer and high-frequency PCB manufacturing with engineering DFM review. Reviewing the stackup and controlled-impedance geometry before fabrication helps keep the released construction aligned with your design assumptions; PCB assembly support can connect the fabrication and BOM discussion in one project.

Send your Gerber or ODB++ files, stackup, material requirements, impedance notes, quantity and delivery needs to [sales@bestpcbs.com](mailto:sales@bestpcbs.com). Add the BOM and placement data for assembly. **Request a manufacturing review and quotation** with the construction, inspection requirements and open engineering questions clearly identified.

## Technical References

- Tektronix: Choose the Right Platform for Jitter Measurements, timing observables and platform differences.
- Tektronix: Characterizing and Troubleshooting Jitter, trends, distributions and analysis.
- Tektronix: Jitter Timing Fundamentals, jitter components and threshold-related mechanisms.
- Keysight: Dual-Dirac Model, RJ/DJ and Q-Scale, model-dependent decomposition and TJ(BER).
- Analog Devices MT-008, Rev. A, converting oscillator phase noise to time jitter.
- Analog Devices: Sigma-Delta ADC Clocking—More Than Jitter, application dependence and uncorrelated contributions.
