VO2 Max Running Calculator
Turn a race result into a VDOT score and the five training paces that actually come out of it.
VO2 Max Running Calculator
Results recalculate instantly on every keystroke. Nothing you type is transmitted.
What this result does not account for
- Assumes an evenly paced maximal effort on an accurately measured course in temperate conditions; heat alone can cost several percent.
- Most reliable for efforts of roughly 8 to 180 minutes; shorter results are inflated by anaerobic contribution and longer ones deflated by fuelling and durability limits.
- Derived largely from trained runners, so the economy assumption fits novices less well.
- VDOT is a performance-equivalent score, not a measured VO2 max, and should not be compared directly against a laboratory figure.
- Equivalent race times assume distance-specific training that you may not have done.
In short: A 10K in 50:00 gives a VDOT of 40.0. That single number sets every pace you should be training at: easy 6:07/km, marathon 5:17/km, threshold 5:05/km and interval 4:41/km. VDOT is not quite VO2 max — it is a performance-equivalent score with your running economy already baked in, which is exactly what makes it more useful than a laboratory figure for setting paces.
Formula
%VO2max = 0.8 + 0.1894393e−0.012778t + 0.2989558e−0.1932605t
VDOT = VO2 ÷ %VO2max
v is velocity in metres per minute and t is race duration in minutes. The first curve is the oxygen cost of running at a given speed; it is quadratic rather than linear because air resistance and biomechanical inefficiency grow faster than speed does. The second is the fraction of maximum you can hold for a given duration, falling from near 100% at a few minutes toward 80% over hours. Training paces are obtained by inverting the first curve at fixed intensities — solving the quadratic for velocity — at approximately 70% easy, 84% marathon, 88% threshold and 97.5% interval.
Worked Example
- Pick the distance you actually raced, not one you estimated from a training run.
- Enter the finish time in hours, minutes and seconds.
- Read the VDOT score, and read the two curves beneath it that produced it.
- Take the four training paces — these are the output that changes what you do tomorrow.
- Check the equivalent race times to see what the same fitness predicts elsewhere.
- Re-run it after every hard race; a result older than about six weeks describes a fitness you may no longer have.
A 10 km in 50:00 is 200 m/min. The cost curve gives −4.60 + 36.45 + 4.16 = 36.01 ml/kg/min, and the duration curve at 50 minutes gives 0.9001, so VDOT is 36.01 ÷ 0.9001 = 40.0. Inverting the cost curve at 70% of that gives an easy pace of 6:07/km, and at 88% a threshold pace of 5:05/km. A 10 km in 45:00 gives a VDOT of 45.3.
Strengths & Limits Of This Model
Where this engine is strong
- Reproduces a published worked example (10 km in 45:00 returns 45.3)
- Derives training paces by inverting the cost curve rather than applying rules of thumb to race pace
- Solves equivalent race times by iteration, because the sustainable fraction depends on the duration being solved for
- Bounds duration and checks implied speed against record plausibility instead of printing nonsense
- States plainly that VDOT embeds running economy and is not a laboratory VO2 max
Where it stops
- Requires a genuine race result; a training run will understate you
- Blind to terrain, weather, altitude and pacing quality
- Long-race inputs conflate aerobic capacity with fuelling and durability
- Cannot replace a laboratory measurement if a true VO2 max is what you need
Practical Use Cases
Setting training paces from a race you actually ran
This is the reason the VDOT system exists. A capacity figure on its own changes nothing; the paces are the deliverable. Because they are derived by inverting the same oxygen-cost curve that produced the score, they are internally consistent with your result rather than being percentage rules of thumb applied to a race pace. Runners most often discover their easy pace should be considerably slower than they have been running it.
Comparing performances across different distances
A 21:30 5 km and a 1:40 half marathon are hard to rank by inspection. Converting both to VDOT puts them on one scale and shows which represents the better run, which is also how you find your weaker distance. A runner whose 5 km VDOT sits well above their marathon VDOT has a specific endurance problem rather than a general fitness problem, and that is a trainable diagnosis.
Tracking aerobic progress across a season without a laboratory
Repeating the same race and recomputing VDOT is a practical proxy for a treadmill test that most runners will never do. Because economy is embedded in the score, an improvement reflects everything that made you faster rather than oxygen uptake alone — which for training purposes is the more relevant question. Use the same distance each time so the duration curve is not doing different work between tests.
Setting a realistic goal time for a target race
The equivalent-times output holds your current VDOT constant and solves for each distance. That is a defensible starting point for a goal, with the important caveat that it assumes you have done the specific training for the new distance. A 5 km runner's predicted marathon is what their engine could support, not what their long runs have prepared them to execute.
Methodology & Editorial Standards
Implements the Daniels-Gilbert equations as published: an oxygen-cost curve VO2 = −4.60 + 0.182258v + 0.000104v² with v in metres per minute, and a sustainable-fraction curve %VO2max = 0.8 + 0.1894393e−0.012778t + 0.2989558e−0.1932605t with t in minutes. VDOT is their quotient. The implementation was checked against an independently published worked example: a 10 km in 45:00 returns 45.3, which this engine reproduces. Training paces are derived by INVERTING the cost curve rather than by applying percentage rules to race pace: for a target intensity the quadratic 0.000104v² + 0.182258v − (4.60 + intensity × VDOT) = 0 is solved for velocity, taking the positive root. Equivalent race times are solved by fixed-point iteration rather than in a single pass, because the sustainable fraction depends on duration and duration is the unknown being solved for; a single-pass calculation would silently use the wrong fraction. Race duration is bounded in the engine at 2 to 420 minutes and the implied speed is checked against world-record plausibility, because both extremes produce authoritative-looking numbers from a model that no longer describes anything. This page uses no heart rate at any point, which is the deliberate separation from the Uth-Sørensen VO2 max calculator in the health category.
Computation runs in IEEE-754 double precision at full internal precision; rounding to two decimal places occurs strictly at the display layer, so no cumulative drift enters the result. All monetary outputs use accounting presentation — grouped thousands, two decimals, negatives in parentheses — so figures can be transcribed directly into a model or working paper. Division-by-zero and out-of-domain inputs return an em-dash rather than a misleading number.
This engine was reconciled against an independent reference implementation and hand-verified for the worked example above before release. Our full five-stage review process is published on the About Us page.
Disclaimer. This calculator is provided for informational and modelling purposes only and does not constitute financial, tax, legal, medical, or engineering advice. Verify all figures with a qualified professional before acting on them.
VO2 Max Running Calculator — 20 Expert FAQs
20 analyst-written answers to the questions practitioners actually ask — optimised for voice and answer-engine retrieval.
What is VDOT and how is it different from VO2 max?
VO2 max is a measured physiological ceiling on how much oxygen you can use. VDOT is a performance-equivalent score: the aerobic capacity a runner with textbook running economy would need in order to have run your race. That means economy, lactate threshold, biomechanics and pacing are all baked into it. Two runners with identical laboratory VO2 max values can have quite different VDOTs, and the VDOT is the better predictor of what they will run and the better basis for setting their paces.
Which race distance gives the most accurate result?
Something in the 8 to 60 minute range, which for most runners means 5 km to the half marathon. Shorter races carry a substantial anaerobic contribution that the model attributes to aerobic capacity, inflating the score. Longer races are limited by fuelling, hydration and muscular durability as much as by oxygen uptake, which deflates it. A 10 km is the usual best single choice.
Why are my easy paces so much slower than I expected?
Because easy is meant to be easy, and the model prescribes roughly 70% of your VDOT for it — usually about a minute per kilometre slower than marathon pace. This is the single most common source of surprise, and running easy days too fast is the most common self-coaching error in distance running. The purpose of an easy run is aerobic development with minimal fatigue cost, and running it 20 seconds per kilometre faster buys almost no additional stimulus while compromising the sessions that matter.
How accurate are the equivalent race times?
They are accurate as a statement about your current aerobic fitness, and less accurate as a prediction of what you will actually run. The model assumes you have trained specifically for the target distance. A 5 km specialist's predicted marathon reflects their engine, not their long-run preparation, and the gap between those two things is where most first marathons go wrong. Predictions between adjacent distances are considerably more reliable than a large extrapolation.
Does the VDOT formula account for hills, heat or wind?
No. It sees a distance and a time, so anything that made those conditions harder shows up as a lower score rather than as an adjustment. Heat is the largest common distortion and can cost several percent on a hot day; a hilly course, strong wind or running alone without pacing all push in the same direction. If your race conditions were poor, your true VDOT is higher than the figure here, and the paces derived from it will be slightly conservative.
Is a VDOT of 40 good?
It is a solid recreational figure — roughly a 50-minute 10 km or a 3:38 marathon equivalent. But the useful comparison is against your own previous results rather than a population table, because VDOT changes with training in a way that is directly visible. Beginners frequently gain 5 to 10 points in a first structured season; experienced runners fight for one or two.
How often should I recalculate my VDOT?
After every hard race, and at minimum every 6 to 8 weeks during consistent training. A VDOT from a race more than a couple of months old is describing a fitness you may no longer have, and stale paces are worse than no paces: they are either too easy to develop you or too hard to recover from. If you are not racing, a hard time trial at a consistent distance serves the same purpose.
Why does the calculator need the race duration and not just the pace?
Because the model has two curves and duration drives the second one. The oxygen cost curve needs only your velocity, but the fraction of maximum you can sustain depends on how long you sustained it — near 95% for a 20-minute effort, closer to 80% over several hours. The same pace held for 20 minutes and for two hours therefore implies very different capacities, and dividing by the correct fraction is what separates the two.
Can I use this if I run on a treadmill?
With caution. Treadmill belts assist your stride slightly and there is no air resistance, so a treadmill time typically overstates outdoor performance — a 1% incline is the conventional correction, though it is a rough one. Treadmill speed calibration also drifts, sometimes considerably. If you can, use an outdoor result on an accurately measured course.
What are threshold and interval paces actually for?
Threshold pace, around 88% of VDOT, is comfortably hard: the fastest pace you could hold for roughly an hour, used in tempo runs and cruise intervals to improve lactate clearance. Interval pace, around 97.5%, is where you stress aerobic capacity directly, typically in repetitions of three to five minutes with recovery between. Running either one at the wrong pace turns it into a different session: threshold run too fast becomes a bad interval workout, and intervals run too slow become a mediocre tempo.
How does this differ from your other VO2 max calculator?
The health-category page uses the Uth-Sørensen method, which estimates aerobic capacity from the ratio of maximum to resting heart rate. It requires no running at all and is framed around cardiorespiratory fitness and health outcomes. This page requires a race result, uses no heart rate whatsoever, and exists to produce training paces. If you want to know roughly where your fitness sits, use that one. If you want to know what pace to run tomorrow, use this one.
Does the Daniels-Gilbert model work for beginners?
The arithmetic works for anyone, but two cautions apply. The formulas were derived largely from trained runners, so the economy assumption fits a novice less well and the score tends to run low for someone with poor mechanics. And a beginner's race result is more likely to reflect pacing inexperience than aerobic capacity — going out too fast and fading distorts the input more than any modelling error distorts the output. Race a few times before treating a VDOT as a stable measurement.
Is this vo2 max running calculator free to use?
Yes. It is free, requires no account, and has no usage limits. ApexConverter is funded by contextual advertising, never by selling user data.
Is my data sent to a server?
No. The engine runs as Vanilla JavaScript inside your browser under our Zero-Server Client-Side Execution model. Your figures are computed locally and are never transmitted, logged, or stored.
How accurate is this calculator?
It applies the standard closed-form formula in IEEE-754 double precision, rounding only at the display layer. The engine is reconciled against an independent reference implementation before release.
Does it work on mobile?
Yes. The interface is mobile-first with numeric keypad hints and is tested down to a 320-pixel viewport with no horizontal scrolling.
Can I use it offline?
Largely, yes. Because computation is client-side, the page continues to calculate without a network connection once it has loaded.
Which currency does it use?
Amounts display in US$ accounting format, but the underlying mathematics is currency-agnostic. The result is identical in any currency, so simply read the figures in your own.
Why does a result show an em-dash?
An em-dash indicates the calculation is not defined for the inputs given — typically a division by zero or a value outside the valid domain. We show a dash rather than a misleading number.
How do I report an error?
Email apexconverter.praxiscalc@gmail.com with the tool URL, your exact inputs, the output received and the output you expected. Verified mathematical errors are patched within 72 hours.