The Prediction Gap Is Real — And Predictable
Race prediction tools based on Jack Daniels' VDOT system are accurate over short distances. A runner's 5K and 10K times tend to align closely with their VDOT-derived predictions. But the marathon routinely breaks this pattern for recreational runners. The gap between predicted and actual marathon time — almost always in the direction of slower — isn't random. It follows a consistent pattern that becomes more pronounced as weekly training mileage falls.
The reason is that VDOT captures aerobic capacity — how well your cardiovascular system delivers and processes oxygen. What it doesn't capture is marathon-specific fitness: the muscular endurance, fat adaptation, and glycogen management required to sustain race pace across 26.2 miles. The 5K tests the first. The marathon requires both.
Distance Difficulty Scales Faster Than Distance
The physiological demands of endurance events don't scale linearly with distance. Doubling the distance more than doubles the difficulty — a phenomenon captured mathematically in the exponent used to model race times across distances. The marathon is roughly 8.4× the distance of a 5K, but it requires disproportionately more preparation in terms of weekly mileage, fat oxidation capacity, and glycogen availability.
This non-linearity is why a 5K-to-marathon mileage extrapolation goes wrong. A runner can be well-prepared for a 5K on 25 miles per week. That same mileage is insufficient for the marathon — not because the aerobic capacity is lacking, but because the muscular and metabolic infrastructure needed for 26 miles hasn't been built.
The Mileage Variable
Research from Runalyze, Training Peaks data, and several peer-reviewed studies consistently shows that weekly training mileage is the single strongest predictor of marathon performance that VDOT alone cannot capture. Two runners with the same VDOT will produce very different marathon results based on their weekly mileage:
Why the Wall Hits Some Runners and Not Others
"Hitting the wall" — the dramatic pace collapse that usually occurs between miles 18 and 22 — is a glycogen depletion event. When muscle glycogen stores are exhausted, the body must switch primarily to fat oxidation for fuel. Fat oxidation is slower and less efficient, and the transition creates an abrupt drop in available energy for the muscles.
Higher-mileage runners are better prepared for this in two ways. First, chronic high mileage training improves fat-burning capacity and glycogen sparing — the body becomes more efficient at using fat at marathon pace, preserving glycogen for later in the race. Second, long runs of 20–22 miles expose the body to glycogen-depleted conditions, training it to continue running when fuel is critically low. A runner whose longest training run was 16 miles has never practiced this transition.
The practical implication: if your weekly mileage is under 40 miles or your long runs haven't exceeded 20 miles, subtract 10–20 minutes from your VDOT marathon prediction before trusting it. Our race predictor applies a mileage-adjusted penalty based on your weekly training volume — it's a more honest estimate than the raw VDOT table.
How to Close the Gap
The path from "5K shape" to "marathon shape" is mileage. Specifically:
- Build weekly volume to 45–55 miles before the marathon training cycle begins
- Ensure at least 2–3 long runs of 20+ miles before race day
- Practice race-day fueling during long runs — both gel/carb timing and race-pace effort while fueling
- Do some training runs at or near marathon pace, not just "easy" and "hard" — the middle ground matters for glycogen efficiency
VDOT is a ceiling, not a floor. The gap between your current ability and that ceiling is almost always filled by mileage and specificity — not by running faster in training.
