VDOT, demystified — what it is, how to find yours, and why it matters

VDOT shows up in every serious running conversation, and yet most of what gets said about it is wrong. People mix it up with VO2max, treat it as a fixed "tier" they belong to, or trust calculators built on bad assumptions. Here's the actual story, stripped of the math you don't need.

Daniels' insight

Jack Daniels — coach, exercise physiologist, two-time Olympic medalist — wanted a way to compare runners without dragging them into a lab. His move was simple:

> "If two runners run the same 10K time, they have the same effective VO2max for that race. Let's call that number VDOT."

The catch is VDOT doesn't measure your absolute aerobic ceiling. It measures the slice of that ceiling you're actually expressing today. It rolls VO2max, running economy, mental toughness, and whatever else is gating your race performance into a single number.

A VDOT of 48 says: *"right now you're racing like an athlete with a 48 ml/kg/min functional VO2max."* If a lab pegs you at 55 but you race like a 48, your VDOT is 48. The lab number is your ceiling. VDOT is the floor of the lift you've installed under it.

How it's computed

The full math is gnarly, but the idea is straightforward:

1. Take a recent race time (5K, 10K, half, or marathon).

2. Solve the system Daniels built — VO2 as a function of pace, and sustainable %VO2max as a function of duration.

3. The number that pops out is your VDOT.

The easy path: punch your time into [Vetta's VDOT calculator](https://vettatrainer.com/herramientas/vdot). Feed it "10K in 42:30" and you get the VDOT plus projected times for every other distance.

What you do with it

### 1. Forecast race times you haven't raced

If you ran a 10K in 42:30 (VDOT 48), Daniels projects:

5K: 20:25

Half: ~1:34

Marathon: ~3:16

Projection, not prophecy. It assumes you've actually trained for that distance. If you've never gone past 10K, your real marathon will be slower than the Daniels number because you're missing distance-specific endurance.

### 2. Set your training paces

Every VDOT comes with paces for each zone (E, M, T, I, R). At VDOT 48:

E (easy): 8:00–8:50 / mile (5:00–5:30 / km)

M (marathon): 7:15 / mile (4:30 / km)

T (threshold): 6:42 / mile (4:10 / km)

I (VO2max): 6:10 / mile (3:50 / km) in 3–5 min intervals

R (reps): 5:45 / mile (3:35 / km) in 200–400 m reps

### 3. Track real progress

If your VDOT went from 45 to 48 over three months, you're getting faster — regardless of what distance you raced. One number, one trend, no noise.

The mistake everybody makes

You can't compute VDOT from a random training run. It has to be a near-max sustained effort: a race, a time trial, a tested workout. Pull it from a conversational long run and the number is garbage, and your zones will be garbage downstream.

Vetta uses the median of your top three VDOT estimates from the last 28 days to keep the metric stable. So if last month you raced a 10K in 42:30, did a chill hour run, and ran a 5K time trial in 19:50, the system grabs the hard efforts and ignores the easy ones automatically.

Does it work for trail?

Partly. VDOT is a flat-road model. On real trail with vert, [GAP (Grade Adjusted Pace)](https://vettatrainer.com/herramientas/vdot) re-prices your splits so VDOT keeps making sense. But if your race has 6,500 ft of climb in 25 miles, don't expect the flat VDOT projection to hold — add 25–40% depending on terrain.

And altitude?

For every 1,000 ft above 5,000 ft, you lose roughly 1% of pace at the same effort (unacclimatized). At 14,000 ft (Pikes Peak summit, Cusco) that's about 9%. Vetta's [VDOT calculator](https://vettatrainer.com/herramientas/vdot) takes an "altitude" input and applies the correction to your projections.

Try it

[Find your VDOT here](https://vettatrainer.com/herramientas/vdot) — free, no signup. If you want a coach engine to build your training week from those zones automatically, [create an account](https://vettatrainer.com/signup) — 7 days Pro on the house.