VO2 Max on Your Watch: What It Actually Means and Whether You Should Trust It

You glance at your Garmin after a hard tempo run. The number has ticked up: 52. Or maybe your Apple Watch shows a little trend line creeping toward 48. You feel a flash of satisfaction. Then a question you've probably had before: what does that number actually mean, and should you be making decisions based on it?

VO2 max is the single most-referenced metric on endurance wearables. It appears on every Garmin Forerunner, every Apple Watch with watchOS 7 and later, and every Polar and COROS device. But most runners can't explain what it measures, don't know how accurate their watch's estimate is, and have no idea how it should affect the way they train or fuel.

This is the guide that fixes that.

What VO2 max actually measures

VO2 max stands for maximal oxygen uptake — the maximum volume of oxygen your body can transport and use during intense exercise, expressed in millilitres of oxygen per kilogram of body weight per minute (ml/kg/min).

Think of it as the size of your aerobic engine. A higher number means your cardiovascular system can deliver more oxygen to working muscles, and those muscles can use it more efficiently to produce energy.

For context, an untrained adult typically falls between 30 and 45 ml/kg/min. A well-trained recreational runner might sit at 45–55. Competitive club runners often range from 55–65. And elites — the Kipchoge-level outliers — can exceed 80.

But here is the part that gets lost in the headlines: VO2 max is a ceiling, not a speedometer. Two runners with identical VO2 max values can have wildly different race times because VO2 max doesn't account for running economy, lactate threshold, or fueling strategy. It tells you how big the engine is, not how efficiently it runs.

How your watch estimates it

Your watch has never measured your oxygen consumption. It can't. A true VO2 max test requires a lab, a treadmill or bike, a metabolic cart that analyses inhaled and exhaled gases, and a protocol that pushes you to absolute failure.

Instead, your watch estimates VO2 max using two things it can measure: your heart rate and your pace (or, for cycling, your power output).

Garmin uses the Firstbeat Analytics algorithm, which models VO2 max from the relationship between heart rate and speed during runs. It looks for segments where you're running at a steady effort — ideally above 70% of your max heart rate — and calculates how much oxygen consumption would be needed to produce that pace at that heart rate. Apple Watch uses a similar approach, estimating VO2 max from outdoor walk and run data by correlating heart rate response with speed and elevation.

Both approaches rest on the same assumption: if your heart rate is lower at a given pace, your aerobic fitness is higher. That assumption is broadly correct but comes with significant caveats.

Where watch estimates go wrong

Studies comparing wrist-based VO2 max estimates with laboratory measurements typically find agreement within 5–10%. That sounds reasonable until you realise what 5–10% means in practice. For a runner with a true VO2 max of 50, the watch might read anywhere from 45 to 55 — a range that spans the difference between "decent recreational runner" and "competitive age-grouper."

Several factors systematically skew watch estimates:

Heat and humidity. When it's hot, your heart rate rises to maintain the same pace because blood is being diverted to your skin for cooling. Your watch sees a higher heart rate at the same speed and interprets it as lower fitness. A single hot run can drop your estimated VO2 max by 2–4 points. This is why runners in Phoenix and Singapore often see artificially low estimates all summer.

Altitude. Lower oxygen availability at altitude raises your heart rate for the same effort. If your watch doesn't correct for elevation (most don't), training at 1,500 metres or above will depress your estimate.

Wrist-based heart rate accuracy. Optical heart rate sensors are good enough for steady-state running but struggle with intervals, cold weather, and darker skin tones. An inaccurate heart rate reading feeds directly into an inaccurate VO2 max estimate. A chest strap improves this significantly.

Terrain and wind. Trail runs with variable footing, steep climbs, or strong headwinds all change the pace-to-effort relationship. Your watch doesn't know you're running into a 30 km/h wind — it just sees a slow pace with a high heart rate and concludes your fitness has dropped.

Fatigue and overtraining. If you're carrying residual fatigue from a heavy training block, your resting and exercise heart rates will be elevated. Your VO2 max estimate drops even though your actual aerobic capacity hasn't changed. This is one reason why your number often dips mid-training block and rebounds during taper.

Caffeine and medication. Anything that raises or suppresses heart rate independent of effort — coffee, beta-blockers, decongestants — changes the input your watch uses to model fitness.

So should you trust it?

Yes, with conditions.

Watch-based VO2 max is useful as a trend indicator over weeks and months. If your number is climbing steadily over a 12-week training block, your aerobic fitness is almost certainly improving. If it's been flat for six months despite consistent training, that's a signal worth investigating.

It is less useful as an absolute number on any given day. The day-to-day fluctuations reflect conditions — heat, fatigue, hydration, sleep — more than actual fitness changes. Watching the 7-day or 30-day rolling average is far more informative than reacting to a single reading.

And it is not useful at all as a race predictor without context. Garmin translates VO2 max into predicted race times, but those predictions assume optimal conditions, ideal pacing, proper fueling, and a runner whose economy matches the model's averages. If any of those assumptions break — and for most runners, several do — the prediction falls apart.

The biggest limitation, though, isn't accuracy. It's that VO2 max on its own doesn't tell you what to do differently. It doesn't change your training plan, adjust your pacing strategy, or — critically — tell you how to fuel.

The connection most runners miss: VO2 max and fueling

Here is where VO2 max gets genuinely interesting for race performance, and where every watch on the market falls short.

Your VO2 max directly influences how your body uses fuel during exercise. At lower intensities, your body burns a higher proportion of fat. As intensity rises toward VO2 max, you shift increasingly toward carbohydrate oxidation. The crossover point — the intensity at which carbs become the dominant fuel — varies between athletes and is influenced by fitness level.

Athletes with a higher VO2 max can sustain faster paces while still burning a meaningful proportion of fat. This means they deplete glycogen stores more slowly at marathon pace than a less-fit runner covering the same distance. It also means their absolute carbohydrate oxidation rate at race effort may be higher, because they can sustain a higher overall metabolic rate.

What does this mean practically?

A runner with a VO2 max of 55 running a 3:15 marathon is likely burning fuel very differently from a runner with a VO2 max of 42 running a 4:30 marathon. The faster runner is probably operating at a lower percentage of their VO2 max at marathon pace, burning more fat relative to carbs, and may need a different fueling strategy than the slower runner — who is likely working closer to their crossover point and burning through glycogen faster relative to their pace.

Yet almost every marathon fueling guide gives the same advice regardless of fitness level: take a gel every 45 minutes, aim for 60g of carbs per hour. That one-size-fits-all approach ignores the metabolic reality that VO2 max directly shapes.

Your watch knows your VO2 max. It knows your training load, your pace zones, and your heart rate at every effort level. It has every input needed to estimate how you burn fuel. But no watch on the market connects those dots to tell you what to eat and drink during your race.

What you should actually do with your VO2 max number

Here's how to use your watch's VO2 max estimate intelligently:

Track the trend, ignore the daily number. Look at the 30-day average. A climb of 1–2 points over a training block is meaningful. A 3-point drop after one hot run is noise.

Use it to calibrate your training zones. A higher VO2 max shifts your pace at threshold and easy effort. If your VO2 max has increased but you haven't updated your training zones, you might be running your easy days too slowly and missing the aerobic development you've earned.

Factor it into your fueling plan. A higher VO2 max generally means you can sustain faster paces at a lower relative intensity, which means a more favourable fat-to-carb burn ratio at race pace. If your VO2 max has improved significantly during a training block, your fueling needs at race pace may have shifted too. This is the adjustment that almost nobody makes — and it can be the difference between a perfect race and a bonk at mile 22.

Don't compare across devices. A Garmin estimate and an Apple Watch estimate use different algorithms, different heart rate sensors, and different data windows. Comparing numbers between brands is meaningless. Pick one device and track your trend on that device.

Test in a lab if precision matters. If you're targeting a specific race time and want to build a fueling plan around your actual metabolic data, a lab-based VO2 max and metabolic efficiency test gives you the real numbers. For most recreational runners, the watch estimate is sufficient for trend tracking.

The missing link: from data to decisions

Your Garmin or Apple Watch collects an extraordinary amount of data — heart rate, pace, distance, elevation, training load, sleep, HRV, and yes, VO2 max. But it presents that data as numbers and graphs. It shows you what happened. It doesn't tell you what to do about it.

This is the gap that matters most on race day. You don't need to know that your VO2 max is 52. You need to know that at your goal marathon pace, in the forecasted conditions, with your body weight and training history, you should be consuming a specific amount of carbohydrates and fluid per hour — and that those amounts should shift if conditions change.

Sweatr bridges that gap. It pulls your training data from your Apple Watch, Garmin, or Strava and builds a personalised hydration and fueling plan based on your actual metrics — not generic tables. It accounts for the variables your watch tracks but doesn't act on: your training load, your pace-to-heart-rate relationship, your sweat patterns across different conditions, and how all of those interact to determine what you should eat and drink on race day.

Your watch measures your engine. Sweatr tells you how to fuel it.