The Idea Behind VDOT
In the 1970s, exercise scientist Jack Daniels wanted a practical way to compare runners of different abilities and connect their performances across distances. He developed VDOT — a shorthand for the oxygen cost of running at a given velocity. Technically, it's derived from VO₂max (maximal oxygen uptake) adjusted for running economy, but for practical purposes you can think of it as a single number that captures your current aerobic fitness level.
The critical insight is that runners with the same VDOT perform similarly across all distances, from 1500 meters through the marathon. A runner with a VDOT of 50 will run approximately 19:22 for 5K, 40:22 for 10K, 1:29:42 for a half marathon, and 3:09:28 for a marathon — not because of a coincidence, but because all those times reflect the same underlying aerobic capacity.
This lets a 5K time serve as a reasonable proxy for marathon fitness. It also means that if your marathon significantly underperforms your 5K-derived VDOT prediction, something is wrong with your preparation — usually insufficient mileage, inadequate long run volume, or poor pacing strategy.
VDOT Is Not Exactly VO₂max
It's a common misconception that VDOT equals VO₂max. The actual relationship is more nuanced. Daniels defined VDOT as the functional VO₂max — the oxygen consumption you actually use when running at race velocity, incorporating your running economy.
Two runners with identical laboratory VO₂max values can have different VDOTs if one runner is significantly more economical — using oxygen more efficiently per unit of distance. This is why some elite Kenyan and Ethiopian runners achieve world-class race times with VO₂max values that wouldn't stand out in a lab but with exceptional running economy. Conversely, a physically large runner may have a high absolute VO₂max but a modest VDOT because their body weight increases the oxygen cost per kilometer.
For practical training purposes, this distinction rarely matters. VDOT is best understood as a fitness score derived from actual race performances — it captures what you can do, not what your physiology predicts you should be able to do.
How the Tables Work
Daniels built his VDOT tables by modeling the oxygen demand at various running velocities and connecting those to race times across distances. The underlying math uses the relationship between running speed and oxygen cost, adjusted for the aerobic fraction at different race durations.
Shorter races are run at a higher percentage of VO₂max. A 1500m might be run at ~98% VO₂max; a 5K at ~97.5%; a 10K at ~95%; a half marathon at ~90%; and a marathon at around 75–80%. These percentages are well-established from performance data across hundreds of athletes. Daniels' tables encode all of these relationships, so a single performance maps to a single VDOT, which then maps out to equivalent performances at every other distance.
Example: A 22:00 5K runner has a VDOT of approximately 44. The VDOT tables predict their equivalent marathon fitness at roughly 3:35 — assuming equivalent marathon-specific fitness. The reason many 5K runners find their marathon time significantly slower than predicted is that marathon performance also requires high mileage, fat adaptation, and glycogen management that a 5K does not test. VDOT captures aerobic capacity; it doesn't capture marathon readiness.
Training Zones From VDOT
One of the most practical applications of VDOT is setting training paces. Daniels defined five training intensities, each tied to a specific physiological purpose:
| Pace type | % of VDOT velocity | Purpose |
|---|---|---|
| Easy (E) | 59–74% | Aerobic development, recovery, mileage accumulation |
| Marathon (M) | ~80% | Goal marathon pace, aerobic and glycogen stress |
| Threshold (T) | 83–88% | Raise lactate threshold, comfortably hard |
| Interval (I) | 95–100% | Develop VO₂max, hard effort at ~5K race effort |
| Repetition (R) | 105–120% | Speed and running economy, short fast reps |
These percentages are not arbitrary — they're designed so each workout type produces specific physiological adaptations without creating excessive recovery debt. Easy runs at 59–74% are low enough to allow daily training without accumulating fatigue. Threshold runs at 83–88% sit just below lactate threshold, driving adaptation without burning out the aerobic system. Interval work at 95–100% provides VO₂max stimulus in short enough doses to be repeatable.
Where VDOT Breaks Down
VDOT is a powerful tool but it has important limitations, particularly as race distances grow:
- Mileage requirements scale non-linearly. A 5K needs a few weeks of base training. A marathon demands months of specific preparation. Two runners with identical VDOTs will run very different marathons depending on whether they've run 30 or 60 miles per week in training. The VDOT tables assume equivalent distance-specific preparation.
- Single-distance VDOT estimates aren't always stable. A runner who excels at 5K speed but has never trained for the marathon may have a 5K-derived VDOT of 52 and run a 3:45 marathon. Their "true" marathon VDOT is closer to 46 until they develop the specific endurance the distance requires.
- Heat, hills, and pacing errors aren't captured. VDOT tables assume optimal conditions and perfect pacing. A 5K PR on a flat course in cool weather may overestimate fitness for a hilly marathon in summer heat.
The best way to use VDOT is as a starting estimate that gets refined by race experience at the target distance. Use it to set training paces and make rough predictions — and adjust based on how those predictions perform in reality.