Your Garmin says VO2max 55. You plug a recent 10K into a VDOT table and it says 51. Those four points translate to roughly 25 seconds per kilometre at threshold pace — a gap big enough to make your tempo sessions either pointlessly easy or dangerously hard. Understanding why the two numbers diverge, and knowing which one to trust for setting paces, is one of the highest-leverage things you can do as a self-coached runner.
VO2max is the rate at which your body can consume oxygen during maximal aerobic exercise, expressed in millilitres of oxygen per kilogram of bodyweight per minute (mL/kg/min). A lab test holds you on a treadmill at increasing intensity until you can no longer increase oxygen uptake — that plateau is your VO2max.
It is a physiological ceiling. Your aerobic engine cannot process oxygen faster than this number. Elite male distance runners cluster around 70–85 mL/kg/min. A fit recreational runner is typically 45–60. Untrained adults are in the low-to-mid 30s.
The number your watch shows is not a lab result. It is an algorithmic estimate derived from your heart rate and GPS pace during steady-state runs, using a model of how average runners perform at a given HR/pace ratio. The algorithm is surprisingly good at tracking trends — but the absolute value it prints is calibrated to an average running economy, which you may or may not have.
VDOT is Jack Daniels' performance-derived fitness equivalent. In Daniels' Running Formula, he observed that runners with the same race time share the same training pace requirements — regardless of whether their high VO2max was driven by a huge aerobic engine or by extremely efficient mechanics. So he created VDOT as a single number that maps from race performance to training paces, collapsing both variables into one.
In practice: take your 10K time, look it up in the Daniels table, and you get a VDOT value. That VDOT then yields five training paces — Easy (E), Marathon (M), Threshold (T), Interval (I), and Repetition (R). These paces are calibrated from real race data, not from models of hypothetical average runners.
VDOT is not a physiological measurement. It is a performance-to-pace translator. The name borrows VO2max terminology because Daniels' original formula was derived from the relationship between VO2max, running economy, and race performance — but the number itself is race-derived, not lab-derived.
The gap between watch VO2max and race-derived VDOT comes down to running economy — how efficiently you convert oxygen into forward motion at a given pace.
| Scenario | Watch VO2max | Race-derived VDOT | Gap driver |
|---|---|---|---|
| Efficient stride, strong aerobic base | 58 | 57–59 | None — economy matches model |
| High economy, modest aerobic ceiling | 52 | 54–56 | Economy better than model assumes |
| Overstrider, high HR at easy paces | 55 | 50–52 | Economy worse than model assumes |
| Newer runner, still developing form | 48 | 44–46 | Watch over-estimates vs actual race pace |
Use VDOT from a recent race for all structured training paces. Full stop.
The Daniels pace tables were built from real race data. When you train at T-pace (threshold) as defined by your 10K-derived VDOT, you are training at approximately 88% of your VO2max intensity — the zone that produces the greatest lactate clearance and mitochondrial adaptation per minute of stress. The watch's VO2max estimate cannot give you that guarantee because it is an indirect model, not a performance truth.
The watch VO2max is useful for a different purpose: long-term trend tracking. If your watch VO2max climbs from 51 to 56 over six months of consistent training without a corresponding race, that is a signal of real aerobic development — even if the absolute number is off. Use it as a trend indicator, not a pace calculator.
Concretely: if your watch says VO2max 57 and your last 5K gives VDOT 53, run your threshold sessions at VDOT 53 paces. Training at VDOT 57 paces would put your tempo runs a full zone too hard, accumulate excess fatigue, and likely result in mediocre race performances relative to training effort.
Calculate your VDOT free →Because VO2max and VDOT are driven by overlapping but distinct mechanisms, the training levers differ at the margin.
In practice, a well-structured training plan raises both simultaneously. But if you find your VDOT is persistently 3–5 points below your watch VO2max, economy work — two strength sessions per week, 6×20-second strides twice a week — should close the gap faster than adding more easy kilometres.
Get-Split uses race-derived VDOT as the core calibration input for every training plan it generates. Enter a recent 5K, 10K, or half marathon time and the planner outputs all five Daniels pace zones, then builds your weekly schedule around them. When you push a workout to Garmin, the step targets already reflect your current VDOT — no manual pace-zone configuration required.
If your race-derived VDOT changes (a tune-up race at week 8 of a half marathon build, for example), recalibrate in the app and the remaining plan adjusts automatically. The watch's VO2max trend is visible in the Health dashboard as a secondary signal — useful context, not a pace input.
No. VO2max is the maximum rate at which your body can consume oxygen, measured in mL/kg/min. VDOT is Jack Daniels' performance-derived number: it reflects how fast you actually run at a given aerobic effort, which incorporates running economy on top of raw oxygen uptake. A runner with poor economy can have a high VO2max but a lower VDOT.
Watch VO2max estimates are calculated from heart rate and pace during easy runs, using algorithms that assume average running economy. If your economy is below average — common in newer runners or runners who overstride — the watch overestimates. VDOT derived from a race result is honest: it measures what you actually did, not what the algorithm predicts.
Use VDOT from a recent race (within 8 weeks) for all structured training paces. It directly maps to the effort levels you will sustain in a race, and the Daniels pace tables are calibrated against it. Use your watch VO2max only as a rough trend indicator of aerobic fitness over time — not as a precision input to pacing.
Every time you run a well-paced race or hard time trial, recalculate. For athletes in an 18–20 week marathon build, updating after a tune-up race at week 8–10 is standard. Don't recalculate more than monthly — short-term variation from fatigue, weather, or course profile can make the number misleading.
Only roughly. If your VO2max is lab-measured and your running economy is average, your VDOT will sit 1–3 points below your VO2max. But the conversion is unreliable enough that you should never use it to set race paces. Run a 5K or 10K time trial and calculate VDOT directly.
Yes — and this is one of the most underrated adaptations from structured training. More miles, strides, and strength work improve your economy so that the same VO2max produces a faster pace. This is why elite runners often have VDOT scores that match or exceed their VO2max: exceptional economy makes every millilitre of oxygen count more.