VDOT Explained: How Jack Daniels Turns One Race Into Every Training Pace

If you run, there is a good chance someone has told you your "VDOT". It sounds like jargon, but it is one of the most useful numbers in endurance training: a single value that takes one honest race result and hands you every training pace you need. Here is what it actually means, why it works, and where it quietly falls down.

What VDOT actually is

VDOT comes from Jack Daniels, the exercise physiologist behind Daniels' Running Formula, and his earlier work with Jimmy Gilbert. The notation is shorthand for "V-dot-O₂max", written V̇O₂max, where the dot means "per minute". True VO₂max is your maximum rate of oxygen use, and measuring it properly needs a lab.

Daniels' insight was that you do not need the lab. How fast you actually race already reflects two things at once: your aerobic engine and how economically you run. So instead of a pure physiological VO₂max, VDOT is a performance-based VO₂max: the effective number that explains your race time once economy is folded in. Two runners with the same lab VO₂max but different running economy will, correctly, get different VDOT values, because they race at different speeds.

That is why VDOT travels so well. It is anchored to something you can verify on any given weekend: a race.

One race in, five paces out

Plug a recent all-out result into the model and it returns a VDOT, then reads your training paces straight off that single number:

• Easy (E): conversational aerobic running that builds your base and aids recovery.
• Marathon (M): the pace you could hold for 42.2 km, used for race-specific work.
• Threshold (T): "comfortably hard", right around your lactate threshold, trained as tempo runs or cruise intervals.
• Interval (I): hard running near VO₂max, in repeats of roughly 3 to 5 minutes, to lift the ceiling.
• Repetition (R): short, fast reps for speed, economy and mechanics, with full recovery.

Each pace maps to a physiological purpose, not a vibe. That is the whole appeal: the model decides how fast so you can focus on showing up.

Try it with your own race below:

Why VDOT works so well

It is self-calibrating. Because the input is a real race, the output already accounts for your economy, your event, even the weather you raced in. You are not estimating a percentage of an estimated maximum heart rate; you are starting from a result.

It is purpose-built, not generic. Every pace ties to an adaptation. Threshold work clears lactate; interval work stresses VO₂max; repetition work sharpens mechanics. Spend time in the right band and you train the system you meant to train.

It is portable across distances. Daniels' tables lean on the same race-equivalence idea Pete Riegel formalised: a strong 5K predicts a credible 10K or half. That lets the model translate one result into paces for races you have not run yet, which is exactly what our race time predictor does too.

Where VDOT can mislead you

VDOT is a model, and every model has edges. Three are worth knowing.

1. It assumes a balanced, well-trained runner. The equivalence between distances holds best if your endurance matches your speed. A fast-twitch 800m runner will get a flattering VDOT from a 5K and then drown trying to hold the predicted marathon pace. A pure ultra-plodder sees the opposite. The further the goal race sits from your input race, the more the prediction drifts.

2. Garbage in, garbage out. A VDOT from a race you ran on tired legs, in the heat, or on a hilly course understates you; a downhill or perfectly paced PR can flatter you. Feed it your most representative recent effort, not your best-ever or your worst.

3. Paces are not zones, and they ignore the day. VDOT hands you target paces, but it knows nothing about today's fatigue, altitude, or a headwind. On a hard day, a heart-rate or RPE check stops you turning an easy run into a threshold run by accident. Pace tells you the plan; your body tells you the reality. Many runners pair VDOT paces with heart-rate zones for exactly this reason.

How to use it without overthinking

Race something honest in the last few weeks, ideally close to your goal distance. Drop the result into the VDOT calculator, note your five paces, and build your week around them: most volume Easy, a weekly Threshold session, Interval or Repetition work as the race nears, and Marathon pace if you are aiming long. Re-test every four to six weeks and let your paces move with your fitness.

VDOT will not run the miles for you. But it answers the one question that derails most training, "how fast should this run be?", with a number you earned on the road. That is why, four decades on, it is still the cleanest starting point in running.