Why Watch Crystals Are 32,768 Hz (and Why Not Higher)
The first quartz wristwatch on sale, Seiko's Astron of December 1969, did not run at 32,768 Hz. Its crystal vibrated at 8,192 Hz. Two years later Girard-Perregaux's Caliber 350 ran at 32,768 Hz, and almost every quartz watch, wall clock and real-time-clock chip since has used the same number. If the only point of the number were "it is a power of two", 8,192 would have been fine, and so would 65,536. So why did the industry settle on 215 in particular?
The usual answer, the one on most of page 1, is a three-line summary: power of two, above human hearing, small and low power. All true, and none of it quantified. Below we put numbers on each argument, then look at the part that the summaries skip: a 32,768 Hz crystal is not especially accurate, and its error follows a parabola that costs you about a minute a month in winter.
Why a power of two?
A watch needs one tick per second. The cheapest circuit that divides a frequency by two is a single toggle flip-flop: its output changes state on every rising edge of its input, so it completes one cycle for every two input cycles. Chain them and each stage halves the frequency again.
That is from 15 identical flip-flops and no other logic.
Any other frequency can be divided to 1 Hz too. A 32,000 Hz crystal would need a counter that resets at 32,000, which takes comparison logic on top of the flip-flops. In 1970 every gate cost area, current and yield, so the simple ripple chain won. That fixes the family (2n Hz) but not the member. For that we need the two physical constraints that pull in opposite directions.
Why not lower? The tuning fork gets big
A watch crystal is not the thin quartz slab of a megahertz crystal. It is a tiny tuning fork, cut from quartz and plated with electrodes, whose two tines flex sideways like the prongs of a musical fork. The ABS07 data sheet lists the mode as "Flexural Mode (Tuning Fork)", in a 3.2 × 1.5 × 0.9 mm package. Rakon's RTF2012 squeezes one into 2.0 × 1.2 × 0.6 mm.
For a flexing bar fixed at one end, beam theory gives the fundamental frequency as proportional to thickness over length squared:
For quartz, E ≈ 78 GPa and ρ = 2,650 kg/m3 (our values; quartz is anisotropic)
(t and L in metres)
With t = 0.1 mm, solve for 32,768 Hz:
A 1.6 mm tine fits a 2 mm package, which is a reassuring sanity check for a back-of-envelope model. Now slide the frequency down at the same tine width: length goes as , so each halving of frequency makes the fork times longer. 8,192 Hz needs 3.3 mm tines; 1,024 Hz needs 9.3 mm; a 1 Hz fork with the same cross-section would be long, which is the joke Jauch makes about a 1 Hz crystal belonging in Big Ben. You could make the tines thinner instead, but then they get fragile and harder to cut accurately, and the motional resistance rises.
The hearing argument sits on the same axis. 16,384 Hz, the next power of two down, is inside the range a young person can hear, and the Wikipedia history of quartz clocks gives "just high enough to exceed the human hearing range" as one reason for 215. We would rate it as a secondary reason: the fork sits in a sealed, evacuated can, and the dominant pressures are size and power. But 215 does clear the hearing limit with margin, and 214 does not.
Why not higher? Oscillator power rises with frequency squared
The crystal oscillator in a watch or a microcontroller is a Pierce circuit: an inverting amplifier with the crystal and two load capacitors in its feedback loop. It only starts if the amplifier's transconductance gm beats a critical value set by the crystal's losses. ST's oscillator design note AN2867 gives it as:
Frequency enters squared. Plug in real parts. The Abracon ABS07 has a maximum ESR of 70 kΩ, shunt capacitance C0 up to 1.2 pF typical, and a 12.5 pF load. Compare with a 16 MHz crystal at 40 Ω and , the example used in our crystal load capacitor calculation:
32.768 kHz watch crystal:
16 MHz crystal:
Ratio: about 320 times more transconductance for the megahertz crystal
Transconductance costs bias current, so the oscillator's current follows the same trend. The watch crystal's ESR is 1,750 times higher than the megahertz part's, yet its advantage (a factor of about 240,000) wins easily. This is why microcontrollers keep a separate 32.768 kHz oscillator running in sleep and shut the fast one down, a habit that dominates the sleep-current numbers in any honest battery-life calculation. And it is why low-power RTC crystals are sold with 6 or 7 pF loads instead of 12.5 pF: drop from 13.7 to 7.2 pF and gm,crit falls by times.
The dividers add their own cost. TI's note on CMOS power gives the switching power as : proportional to frequency. In a binary chain, each stage runs at half the speed of the one before it, so the whole chain burns only twice what the first stage does:
Stage k output switches at , so with C per stage:
That is twice the first stage alone.
Example (our assumed 10 fF per stage, 1.5 V):
Under a nanowatt for the dividers. Run the same logic from a 4,194,304 Hz (222) crystal and the first stages alone cost 128 times more, plus a much hungrier oscillator. Figure 3 puts the two pressures on one chart: going down in frequency, the fork grows as ; going up, the oscillator's demand grows as . 215 is the first power of two clear of the audible band where the fork is still under 2 mm.
The misconception: “32,768 Hz crystals are very accurate”
Quartz has a reputation for precision, and the page-1 answers lean on it. A watch crystal is good compared with a pendulum, but as a frequency reference it is mediocre, and the reason is its temperature curve. A tuning fork crystal has a parabolic frequency-temperature characteristic. It runs fastest at a turnover temperature T0 and slower on both sides:
ABS07: β = −0.036 ppm/°C2 typical (−0.040 limit), T0 = 25 ± 5 °C
Rakon RTF2012: β = −0.03 ± 0.01 ppm/°C2, T0 = 25 ± 5 °C
Now evaluate it where people actually keep clocks, with β = −0.036 and T0 = 25 °C:
Indoors at 20 °C, a cold room at 10 °C, outdoors in winter at 0 °C, and −10 °C:
60 °C (car dashboard in summer): also −44 ppm, also slow
Two consequences follow. First, a quartz watch is designed around your wrist. Worn, it sits within a few degrees of its turnover point (we assumed 32 °C, which costs under 2 ppm), and it keeps good time. Left in a drawer in a cold room it loses half a minute a month. Wikipedia's quartz clock article puts the same point as about 110 seconds per year for a 10 °C deviation, consistent with the numbers above. Second, the error is always in one direction, so it accumulates: a microcontroller RTC in an outdoor enclosure will drift slow all winter and all summer, and only the spring and autumn are good.
Temperature is not the only term. Figure 4 adds the manufacturing tolerance and ageing from the ABS07 data sheet.
The ±20 ppm tolerance is the biggest bar, 52 s/month, and it is the one that bites hobby projects: a microcontroller with an untrimmed crystal and load capacitors chosen by guesswork can easily be 20 to 30 ppm off before temperature does anything. Getting the load capacitance right (see how to calculate crystal load capacitors) removes the pulling error; trimming in firmware removes the rest of the room-temperature offset. Neither touches the parabola.
The crystal is an LC circuit with an absurd inductor
Electrically, a crystal near resonance looks like a series R, L and C (the "motional" arm) in parallel with the package capacitance C0. Rakon's RTF2012 lists a motional capacitance of 5.0 fF and a maximum ESR of 80 kΩ. The LC resonant frequency formula tells you the inductance that must go with it:
The Q figure is at the maximum ESR.
Four thousand henries, from a sliver of quartz you could lose under a fingernail. No wound coil comes close, and the Q of at least 12,000 is a hundred times better than a good inductor. That Q is why the oscillator locks so tightly to the crystal's frequency that a few picofarads of load only pull it by tens of ppm, and why the same idea, a clean binary or near-binary reference, shows up whenever timing has to be exact, from UART baud rates to the 8,388,608 Hz (223) AT-cut crystal in Citizen's Caliber 0100, rated at ±1 second per year. Higher-frequency AT-cut crystals have a flatter, cubic temperature curve, so the most accurate movements pay the power cost to escape the 32 kHz parabola.
What this means if you are designing with one
For a microcontroller RTC, pick a 6 or 7 pF load crystal if your chip's low-power oscillator supports it, calculate the load capacitors properly, and keep the traces short and guarded, because the oscillator is running at a few µA/V of transconductance and a little leakage or noise can stop it. Budget ±20 ppm initial tolerance plus the parabola for your worst-case temperature, and remember that 10 ppm is 26 seconds a month. If that is too much, either trim against a reference (GPS, NTP or mains, see why mains is 50 or 60 Hz) or buy a temperature-compensated RTC. And do not expect a 555 timer or an RC oscillator to compete: they drift by percent, not ppm.
FAQ
Why are watch crystals 32,768 Hz?
32,768 is 215, so a chain of 15 divide-by-two flip-flops turns it into exactly one pulse per second. Among the powers of two, 215 is the lowest that sits above the range of human hearing while keeping the quartz tuning fork small enough for a wristwatch, and low enough that the oscillator and dividers draw only nanowatts to microwatts.
Why not use a higher frequency crystal for a watch?
Power. The transconductance an oscillator needs to start rises with the square of frequency, and CMOS divider power rises in proportion to frequency. A 16 MHz crystal needs roughly 300 times more oscillator transconductance than a 32.768 kHz watch crystal. Some high-accuracy movements do use higher frequencies, such as 8,388,608 Hz (223), and accept the extra drain.
How accurate is a 32.768 kHz crystal?
Typical parts are specified at ±20 ppm at 25 °C, which is up to 52 seconds per month before any trimming. Temperature adds a parabolic error of about −0.036 ppm/°C2 away from 25 °C: about 21 seconds per month slow at 10 °C and 58 seconds per month slow at 0 °C.
Does temperature make a quartz watch run fast or slow?
Slow, in both directions. A tuning fork crystal runs fastest at its turnover temperature, about 25 °C, and slows down whether it gets hotter or colder. Worn on a wrist the watch stays near its turnover point; left in a cold car or drawer it loses time.
Related on The Science 360
Sources
- Abracon, ABS07 32.768 kHz SMD crystal data sheet, revised 08-10-22 (flexural tuning fork mode, ±20 ppm at 25 °C, −0.036 ppm/°C2 typical and −0.040 limit, turnover 25 ± 5 °C, R1 70 kΩ max, C0 0.9 to 1.2 pF typical, CL 12.5 pF, ageing ±3 ppm first year, 3.2 × 1.5 × 0.9 mm): abracon.com/Resonators/ABS07.pdf
- Rakon, RTF2012 SMD tuning fork crystal data sheet, issue D, 2022 (−0.03 ± 0.01 ppm/°C2, turnover 25 ± 5 °C, C1 5.0 fF, ESR 80 kΩ, 2.0 × 1.2 × 0.6 mm): xpress.rakon.com RTF2012 PDF
- STMicroelectronics, AN2867 "Guidelines for oscillator design on STM8AF/AL/S and STM32 MCUs/MPUs" (; formula as quoted in our crystal load capacitor post, the PDF itself returned an error when we re-checked): st.com AN2867
- Texas Instruments, SCAA035B "CMOS Power Consumption and Cpd Calculation" (): ti.com/lit/an/scaa035b/scaa035b.pdf
- Wikipedia, "Quartz clock" (32,768 Hz above hearing yet low power; −0.035 ppm/°C2, about 110 s/year at 10 °C off turnover; Girard-Perregaux Caliber 350 in 1971 at 32,768 Hz; Citizen Caliber 0100 at 8,388,608 Hz, ±1 s/year): en.wikipedia.org/wiki/Quartz_clock
- Wikipedia, "Astron (wristwatch)" (8,192 Hz XY-type quartz oscillator, hybrid IC, ±5 s/month, December 1969): en.wikipedia.org/wiki/Astron_(wristwatch)
- Jauch, "Why Do Tuning Fork Crystals Always Have A Frequency of 32.768 kHz?" (15 T flip-flops; typical page-one explanation; 1 Hz crystal "more suitable for the Big Ben clock tower"): jauch.com/blog/en/tuning-fork-crystal-frequency-32768-khz
Method note: Figures 2 to 4 were computed with Python from the equations shown. The tine-length curve and divider power are our own scaling models; the temperature curve uses the ABS07 typical coefficient.
Header image: NASA/Kim Shiflett (image KSC-20160301-PH-KLS02_0003), regraded for this article.