VDOT Explained: How a Race Time Becomes Your Training Paces

VDOT is a fitness number developed by coach Jack Daniels that turns a recent race time into one value, and that value sets five training paces with distinct jobs: easy, marathon, threshold, interval, and repetition. A 22:00 5K gives a VDOT of about 44.5. A 20:00 5K gives about 50. Daniels built the system so that one honest race, rather than a laboratory test, sets every pace in your week.

What VDOT represents

VDOT is a pseudo-VO2max, a value that reflects both oxygen uptake and running economy, calibrated by performance rather than by gas exchange. Two runners can share a laboratory VO2max and race differently because one wastes less energy per stride. VDOT folds both into one number because both show up in the finishing time.

That design has a practical consequence. You do not need a treadmill test to prescribe training. You need a recent, honest race effort, and the paces follow. It also means VDOT is only as good as the input. A race run in 86°F (30°C) heat, on a hilly course, or after three broken nights understates your fitness, and paces built on it will feel too easy.

How a race time becomes a VDOT

The calculation has two parts, both published by Daniels and Gilbert and reproduced in Daniels' Running Formula.

First, estimate the oxygen cost of your race speed. Speed in meters per minute is converted to a VO2 value in milliliters per kilogram per minute using a regression from treadmill data. Faster running costs more oxygen.

Second, estimate the fraction of VO2max a runner can sustain for the race's duration. A runner can hold close to 100 percent of VO2max for about ten minutes, and a smaller fraction the longer the race lasts. This curve depends only on time, not on distance.

VDOT is the first number divided by the second. A worked example: a 22:00 5K is 227 meters per minute, which costs about 42 mL/kg/min. A 22-minute effort can be held at about 95 percent of VO2max. Dividing gives a VDOT of about 44.5. Run the same distance in 20:00 and the speed is 250 meters per minute, the cost about 47.5 mL/kg/min, the sustainable fraction about 95 percent, and the VDOT about 50.

You will not do this arithmetic by hand. Daniels publishes tables that map race times to VDOT values and VDOT values to paces, and calculators do the same. Vitadel Run computes VDOT from the race or time trial you enter and updates it as you race again. The formula is worth knowing because it explains the two limits of the system: it trusts the time you give it, and it assumes the race distance was run at a sustainable effort.

Which race should set your VDOT

Use the most recent hard effort at a distance between 3K and 10K, on a flat course, within the past six weeks. Shorter races lean on anaerobic contribution that does not describe your aerobic ceiling. Longer races reward endurance you may not yet have and understate fitness in runners whose weekly volume is still building.

If you have no recent race, run a 5K time trial on a track. Warm up for 15 minutes with a few short accelerations, run the effort evenly rather than starting fast, and record the conditions. Expect a solo trial to land 2 to 4 percent slower than a race with a field and a taper, and keep that offset consistent so your progression is comparable over time.

The five paces and what each one does

Two rules govern the table. Each pace has one job, and a session run between two paces usually does neither. Threshold work run at interval pace ends early and leaves you too tired for the long run. Interval work run at threshold pace never reaches the oxygen demand that makes it worthwhile. And the durations exist to protect the intensity. Threshold pace is defined by being sustainable for about an hour in a race, which is why 40 minutes of threshold work is broken into cruise intervals rather than run straight through. The tempo vs threshold guide covers that pace in depth.

Faude and colleagues (2009) reviewed 25 lactate threshold definitions and found that thresholds correlate strongly with endurance performance, particularly in running, which is the physiological reason a pace anchored near threshold transfers so directly to race results.

How the paces fit into a week

VDOT tells you how fast. It says nothing about how often. That comes from intensity distribution. Seiler (2010) summarized descriptive studies of competitive endurance athletes and found a consistent split of about 80 percent of sessions at low intensity and 20 percent dominated by high-intensity work, with little time at threshold. For a recreational runner training four to six times a week, that means two quality sessions and the rest easy.

A five-day week for a 10K build:

• Tuesday: interval session, for example 5 x 1000 m at interval pace with 3 minutes jogging
• Wednesday: easy 45 to 60 min
• Thursday: threshold session, for example 4 x 8 min at threshold pace with 2 minutes jogging
• Saturday: long run, 80 to 100 min easy
• Sunday: easy 40 min, with 6 x 20 s hill sprints if the legs allow

The easy days make the two hard days possible, and they are the sessions most often ruined by running slightly too fast. The easy runs guide covers why.

Reading the equivalence table

One VDOT value implies a finishing time at every distance. Here are four rows from Daniels' tables, rounded.

Read the gaps, not the numbers. If your 5K matches a row but your half marathon is four minutes slower than that row predicts, you have speed without the endurance to hold a fraction of it for 90 minutes, and the fix is weekly volume plus longer threshold blocks. If your half marathon matches but your 5K is 40 seconds slower, you have a large aerobic base and no top end, and the fix is interval and repetition work.

The marathon column deserves caution. Daniels notes that the marathon prediction assumes appropriate training volume, and a runner on 28 miles (45 km) a week will not run the equivalent marathon time regardless of what a 10K result implies. Treat the shorter distances as reliable and the marathon column as a ceiling that training volume has to earn.

Updating VDOT without chasing noise

Recalculate every four to eight weeks, or after any race that implies a change of more than one VDOT point. Two guardrails help.

Do not raise VDOT because one interval session felt easy. Interval sessions feel easy on good days, and a pace jump applied to every session compounds into a week that is 3 to 5 percent too hard everywhere. Do not lower it after one bad race in heat. Heat costs measurable time, and rebuilding paces around a hot-weather result will make autumn training too gentle.

When VDOT moves up, apply it to quality paces first and leave easy pace alone for a week or two. Easy pace is the least sensitive to fitness and the most sensitive to fatigue, so it is the wrong place to test a new number.

Common mistakes with VDOT paces

• Setting VDOT from a personal best run two years ago. Those paces punish you now, and the first casualty is the easy run.
• Running repetition sessions with short recovery. Repetitions target mechanics and speed, which needs near-full recovery. Cutting the recovery turns them into a badly designed interval session.
• Treating marathon pace as a staple in a 5K block. Marathon pace has narrow value outside marathon preparation, and it eats the recovery interval sessions need.
• Converting every session to a percentage of maximum heart rate. Age-based maximum heart rate estimates carry error of roughly 10 beats, which makes derived zones less accurate than paces from a recent race.
• Trusting GPS pace on trails and hills. Run those by effort and duration, with pace as an outcome. The Apple Watch guide covers where the watch is accurate and where it is not.

The system works because it is a loop: race, derive, train, race again. Each cycle recalibrates the paces with better information than the last. The race-day pacing guide covers how to turn the current VDOT into a goal pace you can hold.