VDOT is a performance-based measure of a runner’s current fitness. It was created in the 1970s by Dr. Jack Daniels, an Olympic coach and exercise scientist often called “the world’s best running coach,” in his book Daniels’ Running Formula.
VDOT is your running fitness on a single scale. It’s an “effective VOβ max,” your aerobic engine adjusted for how efficiently you race. The higher it climbs, the faster every predicted race time and training pace becomes.
Scientifically, VOβ max measures the maximum rate at which the body can take in, transport, and use oxygen during intense exercise. It is usually expressed as milliliters of oxygen per kilogram of body weight per minute.
VOβ max is often described as the size of a runner’s aerobic engine because it reflects the upper limit of the body’s oxygen-powered energy system. The lungs bring oxygen in, the heart pumps oxygen-rich blood, the blood carries it, and the working muscles use it to produce energy.
Runners with similar lab scores could produce different race times, while runners with different lab scores could perform similarly. The lab number was useful, yet incomplete. It measured aerobic capacity, not how effectively that capacity became speed on race day.
In the 1970s, Daniels worked with Jimmy Gilbert, his mathematically skilled collaborator, to build a better model. Their 1979 book, Oxygen Power: Performance Tables for Distance Runners, connected race performances to a VOβ max index called VDOT.
They compared runners’ lab data, oxygen cost at different speeds, and real race performances. Instead of ranking runners only by lab VOβ max, they grouped runners by actual race results. If two runners ran the same time, they were treated as having the same “effective” VOβ max. That performance-based number became VDOT.
Gilbert put runners on treadmills and measured exactly how much oxygen they burned at many different paces. He expected a straight line, but the data curved upward: each step faster costs disproportionately more oxygen than the last. That’s why nudging your pace up a little can feel dramatically harder, and why holding a quick pace for a long time is so demanding. VDOT uses this curve to turn any speed into the true energy it costs you.
Daniels tracked how long runners can sustain a hard effort and found the drop-off is remarkably predictable. You can run near 100% of your capacity for only a few minutes; over an hour it slips toward the high 80s; for a marathon most people hold only about 80%. The longer the race, the smaller the slice of your full engine you can use, no matter how fit you are.
VDOT is useful because it ties physiology to real race results. It captures more than oxygen capacity alone. Since it starts with what a runner actually ran, it also reflects running economy, pacing, race execution, and the ability to sustain effort.
Daniels and Gilbert’s work became the Daniels-Gilbert Oxygen Power tables and was later popularized through Daniels’ Running Formula. Today, runners use VDOT by entering a recent race result into a table or calculator. The result gives a VDOT score, equivalent race predictions, and training paces for easy runs, threshold work, intervals, and repetition sessions.
VOβ max tells you the size of the aerobic engine. VDOT tells you how that engine, efficiency, and race execution show up in an actual performance.
Enter a recent race and time to compute your VDOT from a real result. No race? Leave it on “No recent race” and we’ll estimate from your profile.
These paces come straight from your VDOT. Each one trains a different system, and together they prepare your body for race day. As your VDOT rises, every pace gets faster with it.
| Zone | Pace | Purpose |
|---|
Your plan works at three zoom levels: the whole season, each week, and each day.
We count backward from race day and divide the weeks into four phases. Each phase builds on the one before it.
The weeks alternate: one steps your mileage up, the next eases it back down so your body absorbs the work, and the last 3 weeks taper down into race day.
Hard days are spaced out with easy days and rest, so you never stack two hard efforts back to back. A typical week looks like this:
Each calendar day shows the distance, the target pace, and what to do during recovery (shown in parentheses):
Read it as: a 6-mile session that includes five 1000-meter reps at interval pace, jogging 400 meters between each one to recover. Whatever is in (parentheses) is your rest or slow jog.
Pick your goal race and we set the target time from your predicted equivalents, then scale the plan to the distance. It ramps mileage safely, schedules workouts, and tapers into race day.
Dr. Jack Daniels was an exercise physiologist, distance-running coach, author, and former Olympic medalist. He won team silver in the modern pentathlon at the 1956 Olympics and team bronze in 1960, then earned a Ph.D. in exercise physiology from the University of Wisconsin in 1969. He later became one of the most influential distance-running coaches in the world, and Runner’s World named him “the world’s best running coach.”
His most influential contribution to running was VDOT: a practical way to turn race performances into equivalent race predictions and training paces.
To calculate your VDOT score, you divide the Oxygen Demand of your race pace by the Percentage of Aerobic Capacity you are capable of sustaining for that specific race duration.
VDOT = VOβ Max / % VOβ MaxThe variables inside this primary equation are determined by two separate, highly specific equations:
This equation calculates how much oxygen (in ml/kg/min) a runner requires to move at a specific velocity (v), measured in meters per minute:
VOβ = -4.60 + 0.182258 · v + 0.000104 · vΒ²This equation calculates the drop-off in a runner’s sustainable intensity based on the duration (t) of the race in minutes:
% VOβ Max = 0.2989558 · e-0.1932605t + 0.1894393 · e-0.012778t + 0.8408931. Tracking Real Energy Cost. Daniels put elite runners on lab treadmills and attached them to metabolic carts to measure their literal oxygen consumption at various steady-state speeds. He mapped out the raw data points of velocity versus oxygen cost. Jimmy Gilbert noticed that the data points formed a gentle upward curve rather than a perfectly straight line. Air resistance and the breakdown of running mechanics at high speeds mean you burn exponentially more energy the faster you go. Gilbert used a quadratic regression to model this curve.
2. Profiling the “Fatigue Curve.” Daniels knew that a runner can operate at 100% of their aerobic capacity for only about 8–10 minutes. For a marathon, they can only sustain roughly 80% of it. He logged the race times of elite runners across various distances alongside their lab profiles to find out exactly how much they slowed down over time. Gilbert looked at the rate of decay. Humans do not tire out at a constant linear rate; the exhaustion curve drops quickly at first, then flattens out for long distances. Gilbert used exponential decay functions to build a mathematical model of fatigue.
3. Erasing the Lab Error (the “Pseudo-VOβ Max”). This was Daniels’ breakthrough leap. Instead of plugging a runner’s laboratory VOβ max score into the system, he and Gilbert used the two formulas to reverse-engineer a “Performance VOβ Max.” If a runner finishes a 5K in exactly 20 minutes (t = 20, v = 250 m/min), the first equation says they required 47.46 ml/kg/min of oxygen to move that fast. The second equation says a human can only maintain 95.2% of their maximum capability for a 20-minute effort.
By dividing the cost (47.46) by the capacity factor (0.952), the math reveals that the runner performed with the efficiency and engine of someone with a 49.8 VDOT. By tying the math to real race times, the formula automatically builds in running efficiency, stride mechanics, and racing strategy, elements that traditional laboratory tubes and treadmills inherently ignore.
VDOT is brilliant for predicting your shorter races, but on its own it tends to predict an unrealistically fast marathon, because it assumes you can hold a high share of your capacity for the full 26.2 miles. Almost nobody can.
In 1977 the engineer Pete Riegel studied race records across many distances and found a simple, reliable pattern for how runners slow down as a race gets longer. We use his model to project your marathon time from a race you’ve actually run, so it accounts for real-world fatigue instead of assuming you hold your short-race intensity forever.
Your 5K, 10K, and half-marathon estimates come straight from your VDOT. Only the marathon uses Riegel, projected from the race you entered, which is why it reads a little more conservatively (and more honestly) than a pure VDOT guess. If you haven’t entered a race, every distance falls back to the VDOT estimate.