Crystal PPM Tolerance & Frequency Error Calculator
Convert crystal tolerance in ppm to absolute frequency error in Hz. Stacks initial tolerance, temperature stability, and aging into worst-case and RSS budgets, with clock drift in seconds per day.
Worst-case sum and RSS ppm budget · linear agingAPI slug frequency-ppm-tolerance
Linked values
Type in any field — the others follow.1 Hz to 1 GHz
0 to 1 000 ppm
0 to 100 ppm/yr
0 to 30 years
0 to 1 000 ppm
24 to 1 020 ppm
17.5 to 1 000 ppm
600 Hz to 25.6 kHz
25 MHz to 25 MHz
25 MHz to 25 MHz
1.2 kHz to 51.2 kHz
2.07 to 88.5 s/day
12.6 to 538 min/year
Reference values
Select a row to load it| Initial Tolerance @ 25 °C | Total Error (worst case) | Total Error (RSS) | Frequency Deviation | Minimum Frequency | Maximum Frequency | Total Frequency Span | Clock Drift | Clock Drift |
|---|---|---|---|---|---|---|---|---|
| ppm | 25.000ppm | 17.521ppm | 625.000Hz | 24.999MHz | 25.001MHz | 1.250kHz | 2.160s/day | 13.140min/year |
| ppm | 29.000ppm | 18.193ppm | 725.000Hz | 24.999MHz | 25.001MHz | 1.450kHz | 2.506s/day | 15.242min/year |
| ppm | 34.000ppm | 20.149ppm | 850.000Hz | 24.999MHz | 25.001MHz | 1.700kHz | 2.938s/day | 17.870min/year |
| ppm | 44.000ppm | 26.571ppm | 1.100kHz | 24.999MHz | 25.001MHz | 2.200kHz | 3.802s/day | 23.126min/year |
| ppm | 54.000ppm | 34.728ppm | 1.350kHz | 24.999MHz | 25.001MHz | 2.700kHz | 4.666s/day | 28.382min/year |
| ppm | 74.000ppm | 52.972ppm | 1.850kHz | 24.998MHz | 25.002MHz | 3.700kHz | 6.394s/day | 38.894min/year |
| ppm | 124.000ppm | 101.518ppm | 3.100kHz | 24.997MHz | 25.003MHz | 6.200kHz | 10.714s/day | 65.174min/year |
Formula
IEEE 177 quartz resonator definitions; typical AT-cut crystal datasheet parameters
| Symbol | Quantity | Your value |
|---|---|---|
| f₀ | Nominal frequency (Hz) | 25 MHz |
| Δf | Absolute frequency deviation (Hz) | — |
| ppminit | Initial calibration tolerance at 25 °C (ppm) | — |
| ppmtemp | Stability over the operating temperature range (ppm) | — |
| ppmage | Aging rate (ppm/year) | — |
| t | Service life (years) | 3 years |
Assumptions
6 items
- 01Three ± terms from the datasheet are stacked: the initial tolerance at 25 °C, the stability over temperature, and aging, which accumulates linearly as the yearly rate times the years; real crystals age roughly logarithmically, so beyond the first years this overstates aging, and the page warns past 5 years.
- 02The worst case is the arithmetic sum of the three terms; the RSS figure is the square root of the sum of their squares, which assumes they are independent.
- 03The frequency figures use the worst-case total: Δf = f₀ × ppm/10⁶, with the minimum and maximum frequency at f₀ ∓ Δf and a span of 2Δf, symmetric about the nominal.
- 04Clock drift is the worst-case ppm applied to 86 400 s per day and 525 600 min per year, a 365-day year.
- 05Load-capacitance pulling, supply and drive-level sensitivity, and any trim against a reference are not included.
- 06Warnings flag a worst case above 50 ppm and above 100 ppm.
Worked example
Initial tolerance for a 25 MHz Ethernet PHY clock
An Ethernet PHY asks for a 25 MHz reference within ±50 ppm over its life. The crystal holds ±15 ppm over temperature and ages ±3 ppm a year for 5 years. Starting from the ±50 ppm budget, find the initial tolerance to buy.
| Step | Expression | Result |
|---|---|---|
| Aging over 5 years | 3 ppm/yr × 5 | 15 ppm |
| Initial tolerance left in the budget | 50 − 15 − 15 | 20 ppm |
| Worst-case total: the whole budget | 20 + 15 + 15 | 50 ppm |
| Worst-case deviation in hertz | 25 MHz × 50 / 10⁶ | 1.25 kHz |
| Realistic spread (RSS) | √(20² + 15² + 15²) | 29.15 ppm |
How it works
Parts per million is a fractional error: one ppm means one millionth, so . That single relationship is why the same crystal grade can be excellent in one design and unusable in another. At 32.768 kHz, ppm is Hz — invisible. At 25 MHz the same ppm is Hz, and at a 2.4 GHz carrier synthesised from that reference it becomes kHz, comfortably enough to fail a channel-accuracy requirement.
A crystal datasheet does not give one tolerance number, it gives three, and they are specified independently. Initial or calibration tolerance is the trim accuracy at 25 °C — how close the part is to nominal on the day it ships. Frequency-versus-temperature stability describes how much it moves across the operating range; for an AT-cut crystal this is a cubic curve with an inflection near 25 °C, which is why the spec is quoted as a total excursion rather than a coefficient. Aging is irreversible long-term drift from stress relief in the mounting and mass transfer at the electrodes, quoted per year and largest during the first year.
The three combine in two different ways depending on what you need. The arithmetic sum is the guaranteed limit: no unit in any condition at any point in its life will exceed it. That is the number a protocol margin or a regulatory frequency-accuracy requirement must survive. The root-sum-square assumes the three mechanisms are uncorrelated, which they largely are, and describes the realistic spread across production. It is always the smaller of the two, and using it where a guaranteed limit was required is how designs pass qualification and fail in the field.
Because ppm is a fractional rate, it maps directly onto timekeeping without any extra physics. One ppm is one microsecond per second, 86.4 milliseconds per day, and 31.5 seconds per year. That conversion is what makes ppm the natural unit for real-time clocks: a ppm RTC drifts up to s/day and minutes per year, which is why calendar-accurate products need either a ppm TCXO or periodic network time correction.
Practical tips
- Size the crystal against the tightest consumer of the reference, not the average one. A single design may feed a UART that tolerates thousands of ppm and a radio synthesiser that tolerates ten
- For real-time clocks, convert straight to seconds per day early in the design — plus or minus 20 ppm is 1.73 s/day, which most people find far easier to judge against a product requirement than a ppm figure
- If the temperature stability term dominates, a TCXO is usually cheaper than tightening the initial tolerance. Initial trim is expensive to improve and temperature is normally the largest of the three terms in a wide-range design
- Budget aging generously for sealed or inaccessible products. A device that can be re-synchronised over the network only needs to hold accuracy between syncs; one that cannot needs the full end-of-life number
- Check the specified load capacitance before anything else. Getting CL wrong is the single most common cause of a crystal running out of tolerance, and it is a layout and component choice rather than a purchasing decision
Common mistakes
- Using only the initial tolerance from the datasheet headline — a part marked plus or minus 20 ppm usually means 20 ppm at 25 degrees C, with temperature and aging still to be added on top; the real end-of-life number is often two to three times the headline figure
- Root-sum-squaring when a guaranteed limit is required — RSS describes the production spread, not the boundary. Protocol compliance, regulatory frequency accuracy, and worst-case link margin all need the arithmetic sum
- Forgetting load capacitance mismatch — a crystal specified for 12 pF running against an actual 15 pF load is pulled by tens of ppm, frequently more than every datasheet term combined, and it appears in none of them
- Applying a per-year aging figure linearly over ten or fifteen years — this is deliberately conservative and can over-estimate by 3 to 5 times, potentially driving you to an unnecessarily expensive part
- Comparing two clocks and using only one crystal's tolerance — when two independent oscillators must stay in step, the relative error is the sum of both budgets, so two plus or minus 30 ppm parts can differ by 60 ppm
Frequently asked questions
6 questions
How many Hz is 1 ppm?
One millionth of the nominal frequency. At 32.768 kHz that is 0.033 Hz, at 8 MHz it is 8 Hz, and at 25 MHz it is 25 Hz. The shortcut is that the frequency in MHz equals the Hz-per-ppm, so a 25 MHz part shifts 25 Hz for every ppm of error.
How much does a 20 ppm RTC drift per day?
A day is 86,400 seconds, so 20 ppm gives 86,400 times 20e-6 = 1.73 seconds per day, or about 10.5 minutes per year. Products that must stay within a minute a year need roughly plus or minus 2 ppm, which means a TCXO or periodic network time sync.
Should I add the three tolerance terms or root-sum-square them?
Add them when you need a limit no unit may exceed: protocol compliance, regulatory frequency accuracy, worst-case link margin. Use RSS when estimating the real production spread, because the three mechanisms are independent and rarely all hit their limits in the same direction on the same part. RSS is always the smaller number.
Why does UART need better than 50 ppm?
An 8N1 UART samples the stop bit roughly 9.5 bit times after the start edge, so accumulated timing error must stay under half a bit — about 5 percent total between both ends. That budget is dominated by baud-rate divider rounding rather than the crystal; the 50 ppm figure exists to keep the crystal from eating into the divider allowance.
Is linear aging accumulation realistic?
No, it is intentionally pessimistic. Crystal aging is approximately logarithmic, with most of the shift occurring in the first year and the rate declining afterwards. Ten years is typically closer to 2 to 3 times the first-year figure rather than 10 times. Linear accumulation is the conservative reading of a per-year specification and is what you want for a guaranteed limit.
Does load capacitance error count as extra ppm?
Yes, and it is not included in this budget. A crystal specified for 12 pF running against 15 pF is pulled by tens of ppm, often larger than every datasheet term combined. Size the loading capacitors first with the crystal load capacitance calculator, then treat any residual mismatch as an additional tolerance term here.
Shop Components
As an Amazon Associate we earn from qualifying purchases.