What is VDOT, in plain English
In simple terms, VDOT is a number that represents your current running ability.
It is based on performance, not just raw physiology. If you enter a recent race result into a VDOT calculator, it gives you:
- a VDOT number
- estimated equivalent performances at other distances
- recommended training paces for different workout types
That is why runners like it. It turns one recent result into practical training guidance.
So instead of asking "should my tempo pace be 8:10 or 8:30?" you have a system. And that system is usually a lot better than guessing, running everything too hard, or using paces from a PR you ran two years ago.
Who created VDOT?
VDOT comes from Dr. Jack Daniels, one of the most influential endurance coaches in running. The system was designed to connect race performance with training intensities in a practical way, which is why it is still widely used in calculators, coaching systems, and training apps today.
VDOT vs VO2 max: what is the difference?
This is where a lot of runners get confused.
VO2 max is your body's maximum ability to use oxygen during exercise. In a lab, it is a physiological measurement.
VDOT is a performance-based estimate built from race results. It reflects not only aerobic ability, but also running economy and how that fitness actually shows up on race day. Dr. Daniels explicitly describes VDOT as a practical stand-in for a pure lab-based VO2 max value, because equal race performances can come from different mixes of economy and physiology.
That distinction matters.
Two runners can have similar lab VO2 max numbers and still race very differently. One may be more efficient. One may handle threshold work better. One may simply convert fitness into performance more effectively.
That is why VDOT is often more useful than VO2 max for day-to-day training.
Why VDOT matters for training
The biggest value of VDOT is not the number itself. It is what the number does.
A good VDOT estimate helps set training intensities for:
- easy runs
- marathon pace work
- threshold runs
- interval sessions
- repetition work
Those pace buckets matter because different workouts are meant to create different adaptations. Easy running should feel conversational. Threshold work should feel comfortably hard. Intervals should be hard, but not an all-out race. Repetition work is about speed and economy, not turning every rep into a death march.
When runners do not know their current training paces, one of two things usually happens:
- they run too hard too often
- they train too generically to get the right stimulus
That is one reason pace-based systems remain useful, especially for runners training for a specific race.
The biggest mistake runners make with VDOT
A lot of runners do not misuse VDOT because the concept is bad. They misuse it because they use the wrong input.
The most common mistake is using an outdated race result.
If your pace zones are built from a PR you ran a year or two ago, your training paces may be way too aggressive for your current fitness. The best practice is to use a recent result from the last four to six weeks. Anything older and you risk training off an aspirational time instead of your current capability.
Current coaching guidance lines up with this. Training paces should reflect what you can run right now, not a number from a fitter version of you. Recent race times and time trials are the most reliable inputs.
This matters even more for newer runners. Many race-equivalent calculators and pace systems were developed from stronger, higher-volume runners. Predicted marathon performances in particular can be optimistic for recreational runners training on lower mileage.
That is exactly why a more adaptive model matters.
How to calculate your VDOT from a race result
The simplest way is this:
- Take a recent all-out race result or time trial
- Use a VDOT calculator or pace table
- Find the corresponding VDOT value
- Use that number to set your pace zones
Most VDOT calculators work the same way: you enter a recent or estimated race result, and they return your VDOT and training paces. Ideally use a race or time trial from the last four to six weeks, on a flat course in decent conditions.
Example: a 25:00 5K
A runner around 24:39 for 5K corresponds to VDOT 39, while 26:22 corresponds to VDOT 36. So a 25:00 5K would land roughly between those two and point to training paces in that general range.
That means their paces would likely be around:
- Easy pace: roughly low-10s to mid-11s per mile
- Threshold pace: around the high-8s to low-9s
- Interval pace: around 2:00 per 400m, give or take
You do not need to obsess over every second. The point is that one recent 5K gives you a much better starting point than guessing, training by ego, or copying a plan built for someone else.
Why VDOT is useful, but not enough on its own
VDOT is extremely useful. But by itself, it is still a snapshot.
It tells you a lot about your current fitness from one performance, and that is valuable. But it does not automatically know:
- whether you are carrying fatigue
- whether your heart rate is unusually elevated
- whether you are absorbing training well
- whether your threshold sessions are trending easier
- whether life stress is making the original paces too aggressive this week
That is the gap a real coach closes.
How a coach keeps your VDOT alive
VDOT is the right place to start, but it was never meant to be a static one-time pace table. When Johnny coaches you, your race-anchored paces are the starting point, not the whole plan.
It starts from the same smart idea: use a real performance to anchor training paces. Then it goes further.
Instead of leaning on one race result forever, Johnny reads the rest of the picture week to week:
- how your workouts are actually landing
- heart rate and HR variability
- sleep and training load
- how you tell him the runs are feeling
- how your fitness is trending across the cycle
So if your fitness is improving, your paces move with you. And if you are dragging, accumulating fatigue, or trending toward overload, he adjusts the plan before one bad week turns into a bad month.
Why this matters for non-elite runners
Classic VDOT systems are smart, but many non-elite runners still struggle with them in practice. Not because the theory is wrong. Because real life gets messy.
Work stress, poor sleep, inconsistent mileage, heat, strength training, missed workouts, and uneven experience levels all affect what a runner can actually handle. Even traditional VDOT guidance acknowledges that easy pace can vary day to day based on how you feel, plus weather and terrain.
That is one reason a rigid pace prescription can feel too hard for recreational runners.
A strong system should still give structure, but it should not force runners to pretend they are robots.
Start with a proven pace framework like VDOT. Then keep adjusting so the training stays productive and sustainable, week to week, day to day.
When should you update your VDOT?
The right practical answer:
- after a full-effort race
- after a time trial
- after a tune-up race mid-cycle
- about every four to six weeks if training is going well
Tune-up races, benchmark workouts, and recent performances can all help you assess when fitness has changed enough to justify updating your paces.
If your fitness changes, your training should change too.
Do newer runners need to know their VDOT?
Yes, with one caveat.
Newer runners do not need to become obsessed with formulas. But they absolutely benefit from learning what the number represents:
- current fitness
- appropriate training intensity
- why easy should be easy
- why threshold should not become race pace
- why pace targets should come from reality, not wishful thinking
That knowledge helps newer runners avoid one of the most common mistakes in training: running moderate-to-hard effort on almost every run and wondering why they never feel fresh.
Put plainly: many runners run their easy days too fast. Knowing your VDOT, and knowing what easy pace actually feels like at that fitness level, is the cheapest training fix in the sport.
The bottom line
If you are asking "what is VDOT running?", here is the simple answer:
VDOT is a practical way to estimate your current running fitness from a recent race result so you can train at the right paces. That makes it one of the most useful concepts in running.
But for most runners, the future is not static pace charts. The future is a training system that starts with a smart benchmark like VDOT, then adjusts as your body, fitness, and life change.
That is exactly how Johnny coaches every athlete on his roster: a smart benchmark to start, then a plan that keeps moving with you.
Want this dialed in by an actual coach?
Johnny writes your paces, workouts, and recovery into a plan rebuilt every week, calibrated to your fitness and the week you're actually having. No templates, no guesswork.
Book a free intro callGet the next training note
One email when a new post drops. Pacing, plans, and the patterns Johnny watches for. No spam, unsubscribe anytime.
