Your resting heart rate is the slowest number your cardiovascular system runs at when nothing is asking it to do anything else. It is one of the few numbers on a wearable that has been clinically meaningful for a hundred years before the wearable existed, which is part of why it has stuck around as the headline metric on almost every tracker shipped since the original Fitbit.
It is also, on close inspection, a slightly slippery number. Two devices on the same wrist can disagree by 5 bpm. The same device can read differently if you slept badly, drank a glass of wine, or sat in a sauna the night before. And the number a cardiologist would write down — the one taken at the doctor’s office while you sit still for a few minutes — is not exactly what your watch is reporting either.
This article is the long version of what we tell friends who text us a screenshot of their morning RHR and ask if 71 is good.
What “resting” actually means
The strictest definition is the one used in clinical research and in old physical exam textbooks: a “true” resting heart rate is taken first thing in the morning, before you have stood up, eaten, drunk coffee, or thought too hard about your day. Lie still for a minute or two. Count the pulse. That is your true RHR.
Almost no consumer device measures it that way. Wearables instead compute a derived number — usually the lowest sustained heart rate they observe across a window of inactivity. Apple Watch takes the lowest 30-minute average during periods when the accelerometer says you have not moved. Fitbit uses a similar lowest-window approach across the 24-hour day. Garmin attempts a “true rest” detection, looking for periods where both motion and physiological signals indicate genuine rest rather than just sitting at your desk. Oura skips the daytime entirely and reports the lowest RHR observed during sleep.
These definitions are not interchangeable. The lowest 30 minutes of an Apple Watch’s day will usually come from deep sleep, when parasympathetic tone is highest and your heart slows the most. Garmin’s true-rest reading is closer to the “lie still in the morning” textbook number. Oura’s sleep-based reading sits somewhere between the two, biased toward the night’s low. That is one of the main reasons two trackers on the same person can come back with numbers that differ by several bpm even when both sensors are working correctly.
The normal range
The American Heart Association puts the normal adult resting heart rate at 60 to 100 bpm. That band is wide on purpose. A healthy 28-year-old at 58 and a healthy 64-year-old at 78 are both inside it.
Most people without a regular aerobic habit land somewhere in the 65 to 80 range. Recreational endurance athletes — people running 25 to 40 miles a week, or cycling roughly the same — typically drop into the 50s and low 60s. Well-trained competitive endurance athletes sit in the 40s. The published numbers for elite cyclists and cross-country skiers go remarkably low: Miguel Indurain was famously reported at 28, and Tour-level riders in the low 30s are not unusual.
The flip side is that a slow heart rate in someone who has not earned it through training is a different story. Sinus bradycardia in a 45-year-old desk worker — an RHR of 48 with no athletic background — is a finding, not a victory. It can be entirely benign, or it can reflect a medication effect (beta blockers and certain calcium channel blockers slow the rate substantially), hypothyroidism, an electrolyte abnormality, or an early conduction problem. The combination of low RHR plus symptoms — fatigue, dizziness on standing, exercise intolerance, fainting — is the one that warrants prompt evaluation. The low number alone, in someone who feels fine, is usually still worth a mention at the next routine visit.
On the high end, a resting heart rate consistently above 100 (tachycardia) deserves attention regardless of how you feel. Persistent tachycardia at rest can be a sign of thyroid disease, anemia, dehydration, structural heart problems, or anxiety. It is also commonly caused by stimulants — caffeine, decongestants, some asthma medications, and ADHD stimulants will all raise it.
What lowers your resting heart rate
The single biggest lever is aerobic conditioning. The mechanism is well understood: regular endurance work increases stroke volume, the amount of blood pumped per beat, which means the heart needs fewer beats to deliver the same cardiac output at rest. The same training also raises parasympathetic (“vagal”) tone, the brake side of the autonomic nervous system, which slows the resting rate further.
For a previously sedentary adult who starts a real aerobic program — three to five sessions a week at conversational intensity, plus one harder effort — the typical observed drop in RHR is 5 to 10 bpm over three to six months. Most of that drop is concentrated in the first 8 to 12 weeks. After that, further reductions are smaller and harder to win.
Other things that nudge RHR down, less dramatically but measurably:
- Adequate hydration. Even mild dehydration raises resting heart rate by a few bpm as plasma volume contracts and the heart compensates.
- Consistent sleep. Sleep debt is a sympathetic stressor; eliminating it lets the parasympathetic side dominate, and RHR follows. Our sleep stages explainer covers why the deep-sleep window is where RHR bottoms out.
- Cooler ambient temperature. Heat raises RHR because the body uses circulation to dump heat at the skin.
- Reduced psychological stress. Sustained cortisol exposure keeps the sympathetic side elevated; relief from it, including from things as boring as a week off work, often shows up as a 2 to 4 bpm drop.
What raises it
The mirror image. Acute illness — a cold, flu, COVID, urinary tract infection, anything inflammatory — raises resting heart rate, usually by 3 to 10 bpm and often before you feel symptoms. Dehydration, alcohol the night before (one of the most reliable RHR-raisers in the wearable data), heat, poor sleep, jet lag, large meals close to bedtime, and acute stress will all push the number up.
Alcohol deserves its own sentence. Two glasses of wine in the evening will raise the following night’s resting heart rate by 5 to 10 bpm in most adults, and the effect is plainly visible on any reasonable tracker. People often discover this for the first time when they get a Whoop or an Oura ring; it is one of the most consistent findings in the consumer wearable literature.
Stimulant medications, decongestants (pseudoephedrine in particular), and pre-workout supplements will lift RHR for the duration of their action and sometimes a few hours after. Pregnancy raises it substantially — 10 to 20 bpm above baseline is normal by the third trimester. Thyroid issues, anemia, and structural heart disease will raise it persistently and are the reasons a sustained, unexplained increase warrants a workup.
RHR as a fitness marker
The reason coaches have watched morning resting heart rate for decades is that it is a cheap, reliable signal that tracks training adaptation over time. When the number is dropping, the training is working. When it stalls or climbs slightly despite consistent effort, you may be accumulating fatigue faster than you are recovering. A 5+ bpm sustained rise over your baseline, with no other obvious explanation, is a classic overreaching marker.
A useful habit: look at your seven-day rolling RHR average, not yesterday’s number. Day-to-day noise is high; the trend is what matters. Most decent tracker apps will show this — Garmin and Oura present it well, Apple buries it slightly in the Health app, Fitbit puts it on the main heart-rate screen.
RHR as an illness early-warning
The most-cited paper on this is Mishra et al., “Pre-symptomatic detection of COVID-19 from smartwatch data,” published in Nature Biomedical Engineering in 2020 by the Stanford group running the long-term wearable cohort study. They found that resting heart rate elevations on consumer wearables — primarily Fitbit, with some Apple Watch and Garmin data — preceded a positive COVID test by a median of several days in the cases where their algorithm fired. The effect was strongest when measured against each individual’s own baseline rather than a population average.
Two important caveats. First, the signal is not specific to COVID. The same RHR bump shows up for influenza, gastroenteritis, a UTI, hangovers, heat stress, and a hard interval session the day before. Second, the false-positive rate matters: most days your RHR is 5 bpm above baseline, you are not getting sick. The value of the signal is highest when it is sustained for more than a single night and you cannot point to an obvious reason.
The downstream products that tried to operationalize this — Fitbit’s “Health Metrics” screen, Oura’s illness-detection nudges, Garmin’s training-status warnings — are doing roughly the same thing under the hood: watching your own RHR drift against your own baseline.
Why two devices on the same wrist disagree
There are two reasons. The first is definitional, which we covered above: Apple, Fitbit, Garmin and Oura are all answering slightly different questions. The second is sensor accuracy.
Wrist-based optical heart rate (photoplethysmography, or PPG) is good at rest but not perfect. Skin tone, wrist hair, tattoos, ambient temperature, watch fit, and bony wrists all degrade the signal. We covered the underlying problem in our piece on wearable sensor accuracy, and the Basis Peak heart-rate accuracy post-mortem is a useful case study in what happens when the optics are not quite good enough. A modern Apple Watch, Garmin Fenix, or Fitbit Charge will typically agree within 1-2 bpm at rest, but with motion the gap can widen quickly.
For ECG-based readings, the story is different again. A 30-second wrist ECG from an Apple Watch or Withings ScanWatch gives you an instantaneous heart rate that is essentially as accurate as a clinical lead. That is also the reading a cardiologist will pay attention to. Our explainer on smartwatch ECG goes into how those devices actually work.
Put all of this together and a 3 to 5 bpm spread between two reasonable trackers on the same wrist is normal and not a sign that either is broken. If you care about the trend — and the trend is what matters for fitness and illness signals — pick one device and stick with it. Cross-device comparison is mostly noise.
What to do with your number
The practical version, after all of that:
- Find your baseline. Wear one device consistently for two to three weeks. Look at the seven-day average, not any single day. That number is your starting point.
- Watch for sustained drift. A 5+ bpm increase over your baseline that lasts more than two or three nights, with no obvious cause (alcohol, poor sleep, a hard workout, travel), is worth paying attention to. A sustained decrease over months, if you are training, is the signal you are looking for.
- Anchor to symptoms, not just numbers. A resting heart rate of 56 in someone who feels fine and exercises regularly is almost always fine. The same number in someone who is dizzy on standing or short of breath on stairs is not.
- Bring real data to your doctor. If something looks off, the export from your Health app or the Fitbit dashboard is a useful starting point. It is not a diagnosis, but it is far better than “I think my heart rate has been weird.”
The thing we tell people most often: your RHR is a slow signal. It is more useful as a long-term marker of conditioning and a baseline for spotting illness than it is as a daily readiness score. If you want a day-to-day “should I train hard today” number, heart-rate variability is the better metric. Use them together, and ignore neither.