Jack Daniels VDOT Training Paces Explained

One race result, five training paces

VDOT is the performance index Jack Daniels and Jimmy Gilbert built from race times. It places any result on a shared scale of equivalent performances across distances, and Daniels uses that number to set five training intensities: Easy, Marathon, Threshold, Interval and Repetition. As a common language for intensity, the system is excellent. Its weak point is the input. A race time describes one day, and the paces it produces assume your current training load can absorb them.

Worth saying before the detail: for nearly all runners, running more, consistently, over months and years is the big lever, and the exact training paces are a second-order refinement. The material below is useful for runners who already string together steady weeks, and it sits on top of that foundation.

Key takeaways

• VDOT is a performance-derived "pseudo VO2max". Daniels says it won't necessarily match a lab test, because runners with the same race ability can combine aerobic capacity and economy in different ways.

• All five paces are fractions of the same number, so they move together. Change VDOT and every pace in the week changes with it.

• Each pace has a stated purpose and a session ceiling: about 10% of weekly mileage at Threshold, the lesser of 10 km or 8% at Interval, and the lesser of 8 km or 5% at Repetition.

• Daniels' rule is to train at current fitness. Use a recent race run in good conditions, and without a race, raise VDOT by one unit no more often than every four to six weeks.

• The weakest conversions are stale results, tapered one-off performances and marathon pace derived from short races.

Where VDOT comes from

Daniels and Gilbert published Oxygen Power: Performance Tables for Distance Runners in 1979. The tables rest on two regression equations. The first relates the oxygen cost of running to velocity. The second describes the fraction of maximum oxygen uptake a runner can sustain for a given duration, which is high for a race of a few minutes and falls towards a floor of about 80% over several hours. Solving the two together links a race time at one distance to equivalent times at every other distance through a single reference value.

That reference value is VDOT, a contraction of "V-dot-O2max". In Oxygen Power, Daniels describes it as a rough estimate of the VO2max that would allow those performances, and adds that a mismatch with a lab value doesn't matter, because the performances still relate to each other accurately. In his own later framing, two runners who race equally get the same VDOT even if one has a modest VO2max and excellent economy and the other has the reverse.

Daniels also sets limits on the input. VDOT is most accurate for races lasting roughly three and a half minutes to three and a half hours. The race should be on a flat course with good footing and good weather. If several recent races give different values, he says to train from the highest.

For scale, his published table puts a VDOT of 50 at 19:57 for 5K, 41:21 for 10K, 1:31:35 for the half marathon and 3:10:49 for the marathon.

The five paces and what each one is for

Each pace targets a different adaptation and comes with a ceiling on how much of it belongs in one session. The intensity figures below are the ones most widely reproduced from Daniels' work. Editions and summaries differ by a few percentage points, particularly for Threshold.

Why the paces work as a system

Because every pace comes from one number, the week stays internally consistent. Threshold sits a little faster than marathon pace and corresponds to an effort most runners could race for 50 to 60 minutes. For slower runners, Daniels notes, Threshold can land close to 10K race pace, since their 10K takes nearly an hour.

Duration matters inside a pace band too. Daniels' tempo table slows T pace as the run gets longer. At VDOT 50, his 20-minute tempo pace is 6:51 per mile, and a 60-minute tempo is 7:13 per mile. He also recommends planning quality work by time spent at each intensity, so slower runners on the same group session aren't accumulating far more work than faster ones.

Where runners overfit one race result

The tables are internally coherent. Most problems come from the number that goes into them.

A single good day becomes a standing prescription

The "train from your highest VDOT" rule makes sense for a runner whose results are all recent and comparable. It works less well when the best result came on tapered legs, in cool weather, on a quick course. Daniels' own caveats about conditions point in this direction. Our reading is that a tapered race reflects a level of freshness the runner won't have in the middle of a heavy block, so paces derived from it can be set for a rested athlete and then applied to a tired one.

Marathon equivalence is the shakiest conversion

Converting a 5K or 10K into marathon pace assumes the runner has marathon-specific endurance to match their speed. Evidence on race-equivalence formulas suggests that assumption often fails for recreational runners. Vickers and Vertosick (2016) surveyed 2,303 recreational runners and found the widely used Riegel formula was well calibrated up to the half marathon but predicted marathon times at least 10 minutes too fast for about half of runners. Models that added typical weekly mileage did noticeably better. That study tested Riegel, a different formula from VDOT, so applying it here is an inference. It still supports checking a VDOT-derived M pace against what your long runs and recent mileage show.

The table has no input for load or fatigue

A VDOT lookup has no field for weekly volume, sleep, heat, travel or a recent illness. The official V.O2 app, built on Daniels' system, states that paces only change when a race result is entered or VDOT is updated manually, and do not adapt to completed workouts. Daniels' own advice on mileage is that if you feel more tired or stressed as volume rises, it isn't the time to keep increasing. The paces are best treated as targets for a runner who is absorbing the current load.

Goal paces entered as current paces

V.O2's guidance is explicit: train at the VDOT of your current fitness, ideally from a recent race or time trial. Entering a goal time raises every pace at once, including Threshold and Interval work that was meant to be controlled.

Using VDOT well in practice

• Choose the input carefully. Use a recent race between roughly 3.5 minutes and 3.5 hours, run on a flat course in reasonable weather. If the only fast result followed a taper, consider the next most representative race as well.

• Respect the session ceilings. For a runner averaging 60 km a week, the rules work out to about 6 km of Threshold, up to 4.8 km of Interval and up to 3 km of Repetition running in a single session.

• Update slowly. Without a race, Daniels' guidance is a one-unit increase about every four to six weeks at most, and only while training is going well.

• Cross-check with effort. V.O2 says Easy pace should feel conversational and quality sessions hard but doable. If the paces consistently feel otherwise, re-estimate VDOT.

• Adjust for terrain and wind. V.O2 notes that Threshold speed will vary on hills or in wind, and that running harder than the intended effort doesn't add benefit.

What we know, and what we're inferring

The origin of VDOT, the two equations behind it, the purposes of each pace, the session ceilings, the conditions for a valid race input and the one-unit update guidance are all documented in Daniels' writing and the official V.O2 material. The current reference text is Daniels' Running Formula, fourth edition (Human Kinetics, 2022).

The exact percentage ranges are less settled. We've used the figures most commonly reproduced from Daniels and from V.O2, and published summaries of earlier editions give Threshold as low as 80–85% of VO2max. Treat the percentages as approximate.

Two points are our interpretation. The first is that tapered or ideal-condition races overstate the paces a runner can sustain mid-block. The second is that the marathon-prediction gap found for the Riegel formula is likely to apply to VDOT-derived marathon pace as well. Both are reasonable, and neither has been tested directly for VDOT in the sources we reviewed.

Keeping the pace table in proportion

For nearly all runners, running more, consistently, matters far more than the details in this post. A pace that is a few seconds per kilometre off changes the load of a week only slightly, while an extra easy run each week adds to the running that accumulates over the months. VDOT works best as a way to organise the running you are already doing.

Where kaizen fits

VDOT gives you a precise vocabulary for intensity. kaizen works on the part a pace table leaves out: it quantifies your training load, knows your current fitness from the training you're actually doing, sets weekly targets toward your goal race and adapts the plan when life gets in the way. If your current paces came from one race months ago, open kaizen on iOS or Android and compare your fitness with what that result implies.