What VDOT Actually Tells You About Your Running (And How to Use It)

If you've used almost any structured running plan in the last 25 years — Runna, TrainingPeaks, McMillan, half a dozen indie apps — you've used VDOT, whether you knew it or not. It's the engine running quietly underneath. It's also one of those things that gets thrown around as if everyone obviously understands it, when in fact most runners I talk to are vague about what the number actually means.

The good news: it's not complicated. The bad news: misunderstanding it is the difference between a training plan that fits you and one that quietly grinds you into the ground.

Where VDOT comes from

Jack Daniels — the running coach, not the whiskey — is one of the most influential exercise physiologists in distance running. In the 1970s and '80s, he tested hundreds of runners in a lab to measure their oxygen uptake at various paces. What he discovered was a remarkably tight relationship between race performance and oxygen cost: if he knew how fast you ran a 5K, he could predict, with surprising accuracy, what your maximum oxygen uptake (VO2 max) was, and what paces you should be hitting in training.

He published this as a set of tables, which are now widely known as the Daniels VDOT tables. The "V" stands for volume, the "DOT" for "per unit time" — VDOT is your effective oxygen consumption rate when racing all-out. In practice, you don't think about it that way. You just look up your recent race time, find your VDOT, and the table tells you the paces you should be running for easy days, threshold work, intervals, and long runs.

Daniels' insight was that training paces should be derived from current fitness, not from a target time. Most beginner-to-intermediate plans you'll find on the internet do the opposite — they prescribe paces based on what you want to achieve, which is why so many runners blow up trying to follow them.

What VDOT actually measures

The tempting interpretation of VDOT is that it's your VO2 max. It isn't, quite. It's an estimate of your effective VO2 max — what your race performance implies about your oxygen uptake, taking into account both your raw aerobic capacity and your running economy.

Running economy is the often-overlooked part. Two runners with identical lab-measured VO2 max scores can run very different race times because one is more efficient — uses less oxygen at any given pace. Think of it like fuel economy in a car. Both engines have the same horsepower, but one's getting 12 km per litre and the other's getting 18. The fuel-efficient one will go further on the same tank.

VDOT captures both engine size and engine efficiency in one number, which is why it predicts race performance better than lab VO2 max alone. It's also why your VDOT can change without your VO2 max changing meaningfully — by improving your running economy through consistent training, drills, and strength work, you can run faster races at the same physiological ceiling.

How to find yours

The simplest way: take a recent all-out race result, ideally between 5K and the marathon, and plug it into a VDOT calculator (Daniels' original tables, or any of the free online versions). You'll get a number — typically between 30 and 70 for amateur runners, with elites pushing 75–85.

A few caveats:

• The race needs to be a genuine effort. A controlled tempo run or a "fun run" with friends will underestimate your VDOT. The tables assume you've raced at your true current limit.
• Different distances give slightly different numbers. A 5K-derived VDOT is often a touch higher than a marathon-derived one, because race performance over longer distances is more affected by fuelling, pacing discipline, and heat than by raw fitness. If your numbers diverge, the shorter-distance VDOT is usually a more reliable estimate of physiology.
• Hard time trials count. If you don't have a recent race, a 5K solo time trial run flat out can substitute. It won't be as accurate as a real race (no race-day adrenaline), but it's better than nothing.

If you're tracking your runs in a structured app, the VDOT calculation usually happens automatically. The Running Genie, for example, watches your race results and time trials and updates your VDOT — and therefore all your prescribed training paces — without you having to do anything.

What the table tells you to do

Once you have a VDOT, the Daniels tables give you five training paces:

E (Easy) pace. The pace for your daily aerobic runs. Targets the development of your aerobic engine and recovery. For a runner with VDOT 45, this is around 5:30/km. For a runner with VDOT 55, around 4:50/km. Note: the easy pace is set by your current fitness, not your goal fitness — so as you improve, easy pace gets faster automatically.

M (Marathon) pace. The pace you'd run a marathon at given your current fitness. Used in long runs and race-specific workouts to teach your body to handle that pace efficiently.

T (Threshold) pace. The pace you could hold for about an hour in a race — roughly your lactate threshold. Used for tempo runs and long-interval work to push your sustainable speed upward.

I (Interval) pace. The pace at which you can sustain efforts of about 3–5 minutes at a time, hitting close to your VO2 max. Used for VO2 max intervals like 5 × 1000m or 4 × 1200m.

R (Repetition) pace. Faster than I pace — typically the pace you could hold for a mile or so. Used for short, fast reps with full recovery, sharpening neuromuscular coordination and running economy.

The most common ways runners misuse VDOT

Using a goal VDOT instead of a current one. The cardinal sin. If you ran a 22-minute 5K and want to run a 19-minute one, you might be tempted to use the VDOT for a 19-minute 5K when picking your training paces. This is the express route to overtraining and injury. Daniels designed the tables specifically to prevent this — train at the paces your current fitness supports, and your fitness will improve toward the next VDOT bracket.

Treating the paces as exact. The tables give you a target pace, but your day-to-day pace should fluctuate based on terrain, weather, sleep, and how you feel. A threshold run on a windy day at 5:05/km when the table says 5:00/km is not a failed workout — it's a smart workout. The intent matters more than the number.

Ignoring the easy pace. Many runners use the table for their hard sessions but ignore the prescribed easy pace, running their easy days at whatever feels right (which is usually too fast). This is the same mistake the 80/20 framework tries to fix. Easy means easy, even when the table says you "should" be running 5:30/km.

Updating too rarely. Fitness changes. If your last VDOT update was six months ago and you've been training consistently, your paces are probably stale — too easy now, undercutting your hard sessions. Re-test or re-race every couple of months.

Where VDOT falls short

VDOT is a powerful tool, but it has blind spots worth knowing about.

It assumes flat, neutral conditions. Hilly terrain, heat, humidity, altitude — all of these change your effective pace at any given effort, but VDOT doesn't account for them. Modern training apps (including the Running Genie) often layer environmental adjustments on top of VDOT-derived paces. If you're using raw tables, learn to translate: if it's 30°C and humid, your "threshold" pace today might be 10–20 seconds per km slower than the number on the page.

It assumes a well-trained runner. Beginners often find the easy pace too fast — their aerobic systems aren't yet developed enough to support it. The general advice: if your prescribed easy pace makes you breathless, ignore the table and use heart rate or talk-test effort instead until your fitness catches up.

It doesn't capture fatigue and life stress. The tables tell you what your fitness could support on a fresh day. They don't know you slept four hours and skipped breakfast. Adaptive plans factor in recent training load and recovery; static VDOT tables don't. Use the numbers as a guide, not a verdict.

VDOT vs. heart rate vs. perceived effort

The three main ways to prescribe intensity all have trade-offs.

VDOT-based pace is precise and easily measured, but doesn't adjust for daily readiness or environment. Best when you're fresh, conditions are stable, and you trust your recent fitness benchmark.

Heart rate automatically accounts for fatigue, stress, heat, and altitude — your HR will be higher when you're tired, even at the same pace. But it lags behind effort by 30–60 seconds, drifts upward over the course of long runs (cardiac drift), and is sensitive to caffeine, sleep, and hydration. See our complete guide to heart rate zone training.

Perceived effort (how hard the run feels on a 1–10 scale) is the most adaptive and the most "honest." Skilled runners can prescribe their entire training week from feel alone. The drawback is that it takes years to develop, and ego often interferes — what you call "easy" might really be moderate.

The best approach blends all three: use VDOT to get the right pace target, use heart rate to verify the effort matches that pace today, and use perceived effort to override both if your body is telling you something the numbers miss.