VDOT Calculator

Every serious runner eventually asks the same question: how fit am I really, and what training paces should I actually be running? This VDOT calculator answers both questions using Jack Daniels’ proven running formula: enter a recent race result, and get your VDOT score, estimated aerobic capacity, personalized training pace zones, and predicted equivalent race times across every standard distance. Whether you’re a marathon runner building a training cycle, a coach setting paces for an athlete, or a 5K or 10K runner curious how your fitness translates to other distances, this Jack Daniels VDOT calculator gives you a scientifically grounded, immediately actionable answer.

Six dedicated modes cover the different ways VDOT actually gets used in training. The VDOT Calculator is the default: full race-result-to-VDOT calculation with training zones and race predictions in one place. The Training Pace Calculator generates pace zones directly from a known VDOT score. The Race Predictor estimates equivalent performances across every standard distance. The Pace Converter converts between min/km, min/mile, km/h, and mph. The Performance Comparison mode compares two runners’ VDOT scores side by side. The Progress Tracker stores race results locally in your browser and visualizes your VDOT trend over time.

This tool serves the full range of people who train seriously for distance running: marathon and half marathon runners building structured training cycles, 5K and 10K runners tracking fitness progression, coaches and running clubs setting individualized paces across a roster of athletes, and triathletes and sports scientists applying the same evidence-based framework to the running component of broader endurance training. The underlying Jack Daniels methodology stays mathematically identical across every one of these contexts, what changes is which race distance, training goal, and pace zones matter most for a specific runner’s current training focus.

This calculator supports every standard race distance runners actually train and compete across, from a fast 1 Mile time trial through 3K, 5K, 8K, and 10K road races, 15K and 10 Mile distances, half marathon and marathon, and out to approximate 50K ultramarathon territory, plus a fully custom distance option for races not covered by the standard presets. Whether a runner’s most recent quality effort was a track 5K, a road 10K, or a full marathon, this calculator generates a complete VDOT-based training and racing picture from that single result.

How the VDOT Calculator Formula Works

This calculator measures one thing: what your recent race performance implies about your current running fitness, expressed as a single comparable number. It doesn’t measure oxygen consumption directly. It works backward from a race result to estimate what VO₂ value would have produced that exact time at that exact distance.

Step	Formula	Meaning
Velocity	v = (distance in metres) ÷ (time in minutes)	Average race pace in metres per minute
Oxygen cost	VO2(v) = -4.60 + 0.182258v + 0.000104v²	Oxygen needed to sustain that pace
Sustainable %	%VO2max(t) = 0.8 + 0.1894393e^(-0.012778t) + 0.2989558e^(-0.1932605t)	Percentage of max oxygen use sustainable for that duration
VDOT	VDOT = VO2(v) ÷ %VO2max(t)	Standardised fitness score

These are the original Daniels and Gilbert equations, referenced in peer-reviewed research on predicting distance-race performance. v is race velocity in metres per minute. t is race duration in minutes. VO2(v) is the oxygen cost of sustaining that pace. %VO2max(t) is the fraction of maximum oxygen uptake a runner can sustain for that specific duration, since a runner can hold a much higher percentage of their ceiling for 4 minutes than for 3 hours.

Step-by-step calculation walkthrough

Step 1: Identify the inputs. Race: 10K (10,000 metres). Time: 45:00 (45 minutes).

Step 2: Apply the formula. Velocity = 10,000 ÷ 45 = 222.22 m/min. VO2(v) = -4.60 + 0.182258(222.22) + 0.000104(222.22)². %VO2max(45) = 0.8 + 0.1894393e^(-0.012778×45) + 0.2989558e^(-0.1932605×45).

Step 3: Perform the calculation. VO2(222.22) = -4.60 + 40.50 + 5.14 = 40.95… (working through the full precision) gives approximately 41.15 mL/kg/min. %VO2max(45) works out to approximately 90.9%. VDOT = 41.15 ÷ 0.909 = 45.3.

Step 4: Interpret the result. A VDOT of 45.3 falls in the “Intermediate” performance category. Feeding that VDOT back through the same equations, in reverse, for the marathon distance predicts a finish time of approximately 3 hours 27 minutes, and generates a marathon training pace of roughly 4:53/km.

Assumptions and limitations: the formula assumes the input race was a genuine, well-paced maximal effort. A race run well below capacity (holding back, or racing conservatively) underestimates true VDOT, while an unusually strong outlier performance can overestimate it. The equations don’t directly incorporate age, sex, temperature, or course profile into the base VDOT number, though this calculator’s optional condition-adjustment inputs apply a separate, modest correction on top of the base calculation for context.

3 Real-Life Examples

Three different runners and calculator modes, worked through with verified numbers.

Situation	Inputs	Result	What it means
Recreational runner checking fitness after a 5K	VDOT Calculator mode: 5K in 24:00.	VDOT: approximately 40.2. Category: Intermediate.	This runner can use their Easy, Threshold, and Interval paces generated from this VDOT to structure the next block of training around evidence-based intensities rather than guesswork.
Setting training paces from a known VDOT	Training Pace Calculator mode: VDOT 50.	Easy pace, Marathon pace, Threshold pace, Interval pace, and Repetition pace are generated directly, no race time needed.	Useful for a runner who already knows their VDOT from a lab test or a previous calculation and wants updated paces without re-entering a race result.
Comparing two training partners	Performance Comparison mode: Runner A, half marathon in 1:35:00. Runner B, half marathon in 1:42:00.	Runner A: VDOT approximately 47.9. Runner B: VDOT approximately 44.1. Difference: approximately 3.8 points.	The comparison quantifies the fitness gap between two training partners at the same distance, useful context for group training decisions like who should lead a tempo run.

These are illustrative calculations using the same Daniels-Gilbert formula the calculator above applies. They’re a training-planning tool, not a substitute for actual race-day performance or laboratory testing.

Important Notes

• VDOT is derived from performance, not measured directly. It’s calculated entirely from a race time and distance, not from an oxygen mask or laboratory equipment, even though the formula is grounded in oxygen-consumption physiology.
• Rounding. VDOT displays to one decimal place; predicted times round to the nearest second.
• Race quality matters more than distance choice. A well-executed 5K produces a more representative VDOT than a poorly paced marathon, since the formula assumes a genuine maximal effort at whichever distance is entered.
• The condition adjustment is a modest correction, not a full recalculation. Course difficulty, temperature, and elevation inputs shift the VDOT estimate slightly to account for tougher conditions, but they don’t replace the core Daniels-Gilbert formula.
• Age and sex aren’t built into the base VDOT number. Two runners of different ages with identical race times at the same distance receive identical VDOT scores, since VDOT measures current demonstrated fitness rather than age-relative performance.
• Data privacy. Calculations run entirely in your browser. Progress Tracker entries are stored in your browser’s local storage, not on a server, and the PDF export is generated locally as well.

What Is VDOT?

VDOT is a running fitness metric developed by exercise physiologist Jack Daniels that estimates a runner’s current aerobic running fitness from a single race performance, then uses that fitness estimate to generate personalized training paces and predict equivalent performances at other distances. Working through the worked example from the step-by-step solution above: a 10K finished in 45:00 (an average pace of 4:30/km) calculates to an estimated VDOT of approximately 45.3, suggesting a recommended marathon training pace of roughly 4:53/km and a predicted marathon finish time of approximately 3 hours 27 minutes. This single number, VDOT, becomes the foundation for an entire personalized training plan once calculated from a genuine, well-executed race effort.

The name “VDOT” itself comes from the scientific notation V̇O₂ (V with a dot above it, denoting a rate of volume, oxygen consumption per unit time), simplified to “VDOT” for practical typing and communication purposes. This naming reflects VDOT’s conceptual grounding in oxygen consumption physiology, even though, as explained further in the VDOT vs VO₂ Max section below, VDOT itself is calculated from race performance rather than measured directly in a laboratory. Understanding this naming origin helps clarify why VDOT and VO₂ Max are so closely associated in runners’ vocabulary, despite being methodologically distinct measurements.

Interpolation and Calculation Precision

Jack Daniels’ originally published VDOT tables presented discrete values at specific race times and distances, requiring runners to look up the closest matching row for their specific result, a workable but imprecise approach when an actual race time fell between two published table entries. This calculator implements the full underlying mathematical formulas directly rather than relying on discrete table lookups, meaning it calculates a precise VDOT value (and correspondingly precise training paces and race predictions) for literally any entered race time and distance combination, effectively providing continuous interpolation across the full range the original discrete tables only sampled at specific points.

This formula-based approach also enables the reverse calculation the Race Predictor mode relies on, solving for what race time at a target distance corresponds to a given VDOT score, which requires iteratively searching for the time value that produces the matching VDOT when run through the same underlying equations. This iterative solving approach ensures race predictions stay mathematically consistent with the VDOT calculation itself, rather than relying on a separate, potentially inconsistent set of prediction tables layered on top of the core VDOT formula.

Jack Daniels Running Formula

Jack Daniels, along with physiologist Jimmy Gilbert, published the mathematical formulas underlying VDOT in the 1970s, refining them over decades of subsequent research and coaching experience documented in Daniels’ influential book “Daniels’ Running Formula.” The core insight behind the formula is that oxygen consumption during running relates predictably to running velocity, while the percentage of maximum oxygen consumption a runner can sustain relates predictably to how long they’re running for, combining these two relationships allows a single race performance (a specific distance covered in a specific time) to be converted into a standardized fitness score that’s comparable across different race distances and durations.

Two mathematical relationships work together in the underlying formula: first, an equation relating running velocity to oxygen cost (faster running requires proportionally more oxygen consumption, following a specific curve rather than a simple straight-line relationship); second, an equation relating race duration to the percentage of maximum oxygen consumption a runner can sustain for that duration (shorter, more intense efforts allow a higher percentage of maximum capacity to be sustained briefly, while longer efforts require settling into a lower sustainable percentage). Dividing the oxygen cost of the race pace by the percentage of maximum capacity that duration allows yields VDOT, effectively backing out what a runner’s theoretical maximum oxygen consumption would need to be to produce the observed race performance at that specific pace and duration.

VDOT vs VO₂ Max

VDOT and VO₂ Max are related but distinct concepts, and understanding the difference matters for interpreting your results correctly. True VO₂ Max is a laboratory-measured physiological value, the maximum rate of oxygen consumption an individual’s body can utilize during intense exercise, measured directly through specialized equipment during a controlled maximal exertion test. VDOT, by contrast, is a race-performance-derived approximation that folds in not just theoretical aerobic capacity but also the percentage of that capacity a runner can actually sustain for a given race duration, meaning VDOT partially reflects running economy and fatigue resistance alongside pure aerobic ceiling, in a way that’s arguably more directly useful for setting training paces than a lab-measured VO₂ Max figure alone would be. This calculator explicitly labels its aerobic capacity output as an “estimated VO₂ Max” alongside VDOT specifically to be transparent that this is a performance-based approximation, not a clinical or laboratory measurement.

This distinction has a practical implication worth understanding: two runners with genuinely identical laboratory-measured VO₂ Max values can post meaningfully different race times and therefore calculate to different VDOT scores, because VDOT also captures running economy (how efficiently a runner converts oxygen consumption into forward speed) and fatigue resistance (how well a runner sustains a high percentage of their capacity over the race duration). This is precisely why Daniels designed VDOT as a practical training and racing tool rather than attempting to precisely replicate laboratory VO₂ Max testing, for the purpose of setting training paces and predicting race times, a runner’s actual demonstrated race performance is arguably more directly relevant than their theoretical aerobic ceiling measured in a lab setting under different conditions than actual competitive racing.

Training Pace Zones

Once VDOT is calculated, it generates five distinct training pace zones, each targeting a specific physiological adaptation. Easy (E) pace, the slowest, most conservative zone, builds aerobic base and capillary density with minimal fatigue cost. Marathon (M) pace develops race-specific fueling and pacing familiarity for marathon-distance goals. Threshold (T) pace, run at or near the fastest sustainable effort for an extended duration, directly trains the body’s ability to clear and buffer lactate. Interval (I) pace (faster, shorter, repeated efforts with recovery) targets VO₂ Max improvement, while Repetition (R) pace (the fastest, shortest efforts) develops running economy and neuromuscular speed. The Training Pace Calculator mode above generates all five zones directly from any VDOT score, giving a complete, evidence-based training pace framework in one place.

Each zone corresponds to a specific percentage range of VO₂ Max intensity, calibrated through decades of exercise physiology research on how different training intensities produce different physiological adaptations. Easy pace sits at roughly 59-74% of VO₂ Max, comfortable enough to sustain a conversation, and specifically calibrated to build aerobic infrastructure without accumulating excessive fatigue that would compromise quality on harder training days. Marathon pace sits higher, around 75-84% of VO₂ Max, reflecting the genuinely challenging but still aerobically-sustainable effort required for marathon-distance racing. Threshold pace, at roughly 83-88% of VO₂ Max, approximates the effort a well-trained runner can sustain for about an hour, the physiological “lactate threshold” point beyond which lactate accumulates faster than it can be cleared. Interval pace, near 95-100% of VO₂ Max, and Repetition pace, extending beyond 100% of VO₂ Max into anaerobic territory, both represent progressively shorter, faster, more intense efforts appropriate only in limited quantities within a well-structured training week.

Interpreting Age and Course Adjustments

VDOT’s core formula, as published by Daniels and Gilbert, is calculated purely from race distance and time: it does not directly incorporate age, sex, or course conditions into the base calculation. This calculator’s optional age, gender, course difficulty, temperature, and elevation gain inputs exist to provide additional context alongside the base VDOT calculation and to support a modest adjustment reflecting how challenging conditions can slow an otherwise-representative race effort, rather than to fundamentally alter the core Daniels formula itself. A hilly, hot race genuinely does produce a slower time than the same fitness would produce under ideal conditions. This calculator’s condition adjustment acknowledges that reality without claiming to precisely quantify it, since the exact magnitude of weather and course effects varies considerably by individual and specific conditions.

Age-related performance decline is a well-documented phenomenon in exercise physiology, with average competitive performance generally peaking in the late 20s to mid-30s for distance running before gradually declining with advancing age, though the rate and pattern of decline varies considerably between individuals based on training history, genetics, and other factors. This calculator’s VDOT calculation itself remains age-neutral: a 60-year-old and a 25-year-old with identical race times at the same distance receive identical VDOT scores, since VDOT is designed to measure current demonstrated fitness rather than fitness relative to age-expected norms. Runners interested in age-graded performance comparison (evaluating a time relative to age-adjusted expectations rather than absolute performance) should consult dedicated age-grading tables and tools designed specifically for that comparison, layering that analysis on top of, rather than replacing, the age-neutral VDOT figure this calculator generates.

Race Prediction

Because VDOT represents a standardized fitness score rather than a distance-specific result, it can be used to predict equivalent performance at any other standard racing distance, the Race Predictor mode above generates predicted times across the Mile, 3K, 5K, 10K, Half Marathon, and Marathon directly from a VDOT score. These predictions assume comparable training and conditioning across distances; a runner who has trained specifically for shorter, faster racing may find longer-distance predictions optimistic without dedicated endurance-specific training, since VDOT-based race prediction reflects theoretical aerobic-fitness-driven potential rather than accounting for distance-specific training history.

This distance-independence is one of VDOT’s most practically useful properties: a single race result, at essentially any standard distance, generates a complete set of predictions across every other distance, without needing separate fitness testing for each individual race type a runner might be curious about. That said, the accuracy of these predictions generally improves when the known result and target distance are reasonably close together: a 5K result predicting a 10K or half marathon time tends to be more reliable than the same 5K result predicting a 100-mile ultramarathon, since very different race durations place different demands on endurance, fueling, and pacing strategy that a pure aerobic-fitness-based prediction doesn’t fully capture.

Pace Conversion and Unit Flexibility

Running data arrives in inconsistent units depending on the source: a GPS watch might default to pace in minutes per mile, a treadmill display might show speed in miles per hour, and international race results might report times relative to kilometer splits. The Pace Converter mode above handles this inconsistency directly, converting freely between min/km, min/mile, km/h, and mph so that a figure from any single source translates cleanly into whichever unit is most relevant for a specific training log, race analysis, or comparison against a VDOT-derived training pace target expressed in a different unit system.

This unit flexibility extends throughout the calculator: every mode that accepts a distance supports both kilometers and miles, and every pace or speed output displays in both metric and imperial units simultaneously rather than forcing a single system. This is particularly useful for runners training with equipment or apps that default to one unit system while racing in a country or context that uses the other, removing the mental conversion burden that would otherwise complicate comparing training paces against race-day pace targets.

How to Improve Your VDOT

VDOT improves through consistent, well-structured training that appropriately balances the five training zones described above rather than defaulting to a single training intensity for every workout. Building aerobic base through a majority of easy-paced running, incorporating regular threshold and interval work to raise the sustainable-effort ceiling and VO₂ Max respectively, and allowing adequate recovery between harder sessions all contribute to genuine VDOT improvement over a training cycle. Since VDOT is fundamentally a fitness measurement, meaningful improvement happens gradually over weeks and months of consistent training, retesting via a genuine race effort every 4-8 weeks during a focused training block gives a realistic picture of actual fitness trend without over-interpreting normal day-to-day performance variability.

The rate of VDOT improvement typically follows a predictable pattern tied to training experience: newer runners often see relatively rapid VDOT gains in their first months and years of structured training, as their bodies adapt to the basic demands of consistent running load. More experienced runners with years of training history typically see slower, more incremental VDOT gains, since much of the “easy” adaptation has already occurred, and further improvement increasingly depends on more sophisticated training periodization, targeted weaknesses, and marginal gains rather than broad general fitness development. Understanding this pattern helps set realistic expectations, a beginning runner might reasonably expect several points of VDOT improvement over a training season, while an experienced competitive runner might celebrate a single point of genuine VDOT gain after a demanding training cycle.

Common Running Metrics and Measuring Progress

VDOT sits alongside several other commonly tracked running metrics, each measuring a related but distinct aspect of running performance and fitness. Pace and average speed describe a single run’s performance directly, without reference to broader fitness context. Heart rate during training and racing provides a physiological intensity signal that complements pace-based training zones, particularly useful for easy-day pacing discipline and for accounting for heat, fatigue, or altitude effects that shift heart rate relative to pace on a given day. Cadence (steps per minute) and other biomechanical metrics speak to running form and efficiency rather than aerobic fitness directly. VDOT’s particular value lies in synthesizing race performance into a single, actionable fitness score that directly drives training pace prescriptions, a role none of these other individual metrics fill on their own.

Measuring genuine fitness progress over time benefits from consistency in both testing conditions and interpretation. Using comparable race distances, similar course conditions, and comparable effort levels (a genuine, well-paced race rather than a casual training run) when calculating VDOT at different points in a training cycle produces a more reliable trend than comparing wildly different testing conditions. The Progress Tracker mode above supports exactly this kind of longitudinal tracking, storing race results locally in your browser and visualizing VDOT trend over time, useful both for confirming that a training block is producing genuine fitness gains, and for catching a concerning downward trend early enough to investigate potential causes like overtraining, inadequate recovery, or illness before it becomes a larger setback.

Common Running Mistakes

The most common mistake is using treadmill results incorrectly, treadmill running can feel and perform differently from outdoor road or track running due to the belt’s assistance and controlled environment, sometimes producing a VDOT estimate that doesn’t fully reflect outdoor race fitness. Ignoring weather and ignoring elevation similarly skew VDOT calculations, since a race run in adverse heat or on a hilly course will produce a slower time (and lower calculated VDOT) than the same fitness would produce under favorable conditions. Using outdated race times, calculating VDOT from a result months or years old, misrepresents current fitness, particularly for runners who have trained significantly (in either direction) since that race. Confusing VO₂ Max and VDOT, training too hard (running easy days at a harder-than-appropriate pace, undermining the aerobic-base-building purpose of easy running), ignoring recovery, poor pacing during the race used to calculate VDOT, comparing across age groups without accounting for expected age-related performance differences, and treating VDOT as a medical measurement rather than a training tool round out the most common, most avoidable VDOT-related mistakes.

The “training too hard” mistake deserves particular emphasis since it’s both extremely common and directly counterproductive to the physiological logic underlying VDOT-based training zones. Many runners, especially those newer to structured training, instinctively run their prescribed Easy days at a pace considerably faster than the calculated Easy zone suggests, a pace that feels appropriately “easy” for that individual session, but accumulates enough fatigue across a training week to compromise the quality of scheduled Threshold, Interval, or Repetition sessions. This pattern, sometimes called “gray zone” training (consistently running at a moderate-hard intensity that’s neither properly easy nor properly hard), tends to produce less overall fitness improvement than genuinely respecting the full range of prescribed intensities, running Easy days meaningfully easier than feels natural, specifically to preserve the capacity for genuinely hard efforts on designated hard training days.

Training Tips

Beyond the core training zone framework, several practical habits improve how effectively VDOT-based training actually translates into real fitness gains. Running the vast majority of weekly mileage at genuinely easy, conversational pace, resisting the common temptation to run easy days faster than the calculated Easy zone, preserves the recovery capacity needed to execute harder Threshold, Interval, and Repetition sessions at full quality when they’re scheduled. Spacing hard training sessions with adequate easy or rest days between them, rather than stacking multiple demanding workouts close together, allows the specific physiological adaptations each zone targets to actually consolidate. Finally, treating a calculated VDOT and its associated paces as a living, periodically-updated reference rather than a fixed number locks in the benefit of continuing to train at paces that reflect genuinely current, rather than outdated, fitness.

Building a training week around a small number of purposeful hard sessions (typically one to three, depending on experience level and training phase) surrounded by easy running and adequate rest, rather than treating every run as an opportunity to push pace, reflects how most successful evidence-based training plans are actually structured. This approach, sometimes summarized as “hard days hard, easy days easy”, avoids the common trap of moderate-intensity training that’s too hard to provide genuine recovery but not hard enough to drive the specific adaptations targeted training intends to produce. Combining this pacing discipline with the VDOT-derived training zones above gives a complete, evidence-based framework for structuring an effective training week at any fitness level.

Running Insights

Aerobic fitness and running economy together determine how efficiently a runner converts a given level of physiological capacity into actual running speed, two runners with similar theoretical VO₂ Max can post meaningfully different race times if their running economy (biomechanical efficiency, essentially how much oxygen a given pace costs) differs, which is part of why VDOT’s performance-based approach captures real-world running potential more directly than a pure VO₂ Max lab measurement would. Threshold pace and tempo runs (typically run at or near threshold intensity) train the specific physiological systems responsible for sustainable, extended-duration effort, directly relevant to half marathon and marathon race performance. Intervals, shorter, faster, repeated efforts, target VO₂ Max improvement more directly than steady-state running can, while long runs build the aerobic and muscular endurance base necessary for marathon and half marathon distances specifically.

Race pacing discipline, executing a race at genuinely sustainable effort rather than starting too fast, directly affects both race outcome and the accuracy of any VDOT calculated from that race. Recovery, nutrition, and hydration all support the training adaptations VDOT-based training zones are designed to trigger; inadequate recovery or fueling undermines even a well-structured training plan’s effectiveness. Training load management, balancing volume and intensity appropriately across a training cycle, and ongoing attention to running efficiency (both biomechanical and pacing-related) round out the broader context within which VDOT-based training operates most effectively.

Real-Life Applications

This running VDOT calculator supports training and racing decisions across the full spectrum of running goals. Marathon training and half marathon preparation both benefit directly from VDOT-derived training zones and race predictions, giving structure to what would otherwise be guesswork-based pace selection across a multi-month training cycle. 5K training and 10K improvement similarly benefit from VDOT-based training zones tailored to shorter-distance racing goals. Triathlon athletes can apply the running-specific portion of their training using the same VDOT framework, integrated alongside swim and bike training.

Trail runners and endurance athletes pursuing longer ultramarathon distances can use VDOT as a useful starting reference for training pace, while recognizing that trail-specific and ultra-distance-specific factors (technical terrain, extended time-on-feet, fueling logistics) introduce additional considerations beyond what a road-race-calibrated formula fully captures. This makes VDOT most directly applicable to road and track racing distances up to the marathon, with reasonable but increasingly approximate extension into trail and ultramarathon contexts.

Running clubs and athlete coaching contexts use VDOT extensively for setting individualized, evidence-based training paces across a roster of athletes with different fitness levels, rather than applying a single blanket pace target to an entire training group. Performance analysis and goal race planning both benefit from VDOT’s ability to translate a recent result into concrete future targets and training prescriptions. Training plans built around VDOT-derived zones give structure and evidence-based intensity targets throughout a training cycle, while fitness testing (periodic race-effort retests) and endurance development more broadly benefit from tracking VDOT trend over time using the Progress Tracker mode above.

Frequently Asked Questions

Related Running Calculators