What is VDOT in running?

Runner using VDOT data to maximize his performance

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’s 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’s still widely used in calculators, coaching systems, and training apps today.

VDOT vs VO2 max: what’s 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’s 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’s why VDOT is often more useful than VO2 max for day-to-day training.

It is not trying to be a perfect lab number. It is trying to help you train at the right pace.

Why VDOT matters for training

The biggest value of VDOT is not the number itself.

It’s 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.

Two runners jogging side-by-side on a scenic trail, smiling and talking comfortably to demonstrate a low-intensity recovery pace.

When runners don’t 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. Your own cheat sheet makes this point clearly: recent results from the last 4–6 weeks are best, and using an old PR often leads runners to train too fast. VDOT

That lines up with current coaching guidance too. Runner’s World recently emphasized that training paces should reflect what you can run right now, not an aspirational time, and pointed runners toward recent race times or time trials to estimate current fitness.

This matters even more for newer runners.

Why?

Because many race-equivalent calculators and pace systems were developed from stronger, higher-volume runners. Runner’s World notes that 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

A runner catching their breath with hands on knees after a hard track workout, with a race clock in the background showing their finish time.

The simplest way is this:

  1. Take a recent all-out race result or time trial

  2. Use a VDOT calculator or pace table

  3. Find the corresponding VDOT value

  4. Use that number to set your pace zones

V.O2’s calculator still works this way: you enter a recent or estimated race result, and it returns your VDOT and training paces.

Your cheat sheet uses the same logic and recommends using a recent race or time trial, ideally from the last 4–6 weeks, on a flat course in decent conditions.

Example: a 25:00 5K

Using your cheat sheet, 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’s 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’s the gap we wanted to solve with RunFitCoach.

How RunFitCoach uses FIT Score

runner at sunset, thoughtfully reviewing training data on his watch to adjust his future workout intensity.

RunFitCoach’s FIT Score is inspired by VDOT, but it is not a static one-time pace table.

It starts from the same smart idea: use a real performance to anchor training paces.

Then it goes further.

Instead of only relying on a race result, FIT Score can also adapt using:

  • workouts

  • heart rate

  • HRV

  • perceived feeling

  • how your training is progressing over time

So if your fitness is improving, your training can progress with you.

And if you are dragging, accumulating fatigue, or trending toward overload, the system can make micro-adjustments before one bad week turns into a bad month.

That directly supports the positioning in your website playbook: pace, strength, and recovery should all respond to the athlete’s real-time state, not just a fixed plan created weeks ago.

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 V.O2’s own training guidance notes 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.

That’s the philosophy behind FIT Score:
start with a proven pace framework, then keep adjusting so the training stays productive and sustainable.

When should you update your VDOT?

Your cheat sheet gives the right practical answer:

  • after a full-effort race

  • after a time trial

  • after a tune-up race mid-cycle

  • about every 4–6 weeks if training is going well

That also lines up with current coaching guidance that tune-up races, benchmark workouts, and recent performances can help assess when fitness has changed enough to justify pace updates.

The bigger point is simple:

Training paces should be alive, not frozen.

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.

Your cheat sheet says it bluntly, and correctly: many runners run their easy days too fast.

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’s what RunFitCoach is building with FIT Score.

If you want a simple way to understand your training zones and stop guessing at your paces, grab the free cheat sheet below.


  • VDOT is a performance-based measure of current running fitness developed by Dr. Jack Daniels. It uses a recent race result to estimate training paces and equivalent performances.

  • No. VO2 max is a physiological measurement of oxygen uptake, usually measured in a lab. VDOT is a practical estimate based on race performance that also reflects running economy and how fitness shows up in actual racing.

  • Use a recent race result or time trial and enter it into a VDOT calculator or compare it against a pace table. Your VDOT number can then be used to set training paces.

  • Use a recent all-out effort, ideally from the last 4–6 weeks. A flat course in normal conditions will usually give the most useful result.

  • A good rule is after a race, after a time trial, after a tune-up effort, or every 4–6 weeks if your fitness is changing.

  • Yes, especially as a way to learn the difference between easy, threshold, and interval effort. Beginners do not need to obsess over the number, but understanding it can help them avoid running too hard too often.

  • FIT Score is inspired by VDOT, but instead of staying static, it can adjust using race results, workouts, heart rate, HRV, and perceived effort so training stays aligned to where the athlete is right now.

Stop guessing at your paces.
Get early access to RunFitCoach plus a free VDOT cheat sheet that shows how to set your training zones from a recent race result.


About RunFitCoach
RunFitCoach is building a more personalized kind of running app: one that adapts pace, strength, and recovery around the athlete instead of forcing the athlete to fit the plan. Built under one brand, the app is the core product and coaching serves as the premium layer, which is exactly the structure your site playbook recommends.

Created by Johnny Crain
Four-time Olympic Trials qualifier, 2:12 marathoner, and coach who has worked with thousands of runners, including hundreds of Boston qualifiers. Learn more about working with Johnny here

Previous
Previous

The Science of Speed: Why The Best Running Plan Demands App Integration