5K Training Pace Guide: Four Zones, Conversion Table, and When to Recalibrate

Your training plan tells you to run "easy," "tempo," or "interval" pace, and you want the actual numbers that go with each for your goal time. Four training paces for 5K runners: easy (race pace + 75–90 sec/km), tempo/threshold (race pace + 30–40 sec/km), interval (5–10 sec/km faster than race pace), and race pace. For a 20:00 5K runner (4:00/km race pace): easy at 5:15–5:30/km, tempo at 4:30–4:40/km, intervals at 3:50–3:55/km.

Why You Need Four Training Paces — What Each One Builds

Easy pace (zone 2): trains mitochondrial biogenesis, capillary density, fat oxidation, and aerobic base — the engine. At easy pace you can maintain full conversation for hours without accumulating fatigue that limits tomorrow's training. This is the majority of weekly volume: 75–80%. Runners who run their easy runs too fast (the most common error in recreational running) train the wrong system and exhaust the recovery capacity they need for quality sessions.

Tempo or threshold pace (zone 3): trains lactate threshold — the maximum pace you can sustain aerobically. The most performance-critical training zone for 5K racing because it directly raises the ceiling of your sustainable aerobic power. At threshold, you can manage 2–3 words. A 20–40 minute threshold effort in a single session.

Interval pace (zone 4–5): trains VO₂max and neuromuscular recruitment at race speed. Above threshold — you cannot speak in sentences at this effort. Held for 1–6 minutes per rep with recovery between. This is where the fast-twitch motor units are recruited and the neuromuscular patterns of racing are established.

Race pace: the target intensity for race day. Used in race-pace workouts and strides to familiarise the body with the specific physiological state of racing at goal pace.

The 80/20 principle: approximately 80% of weekly mileage at easy pace, 20% at tempo and above. This ratio is consistent with analysis of elite training (Seiler and Kjerland, 2006) and is the structure behind most evidence-based training plans. The most common training error in recreational runners is inverting this ratio — running 20–30% at tempo+, 70% easy — which produces over-training symptoms within 4–6 weeks.

The most consistent coaching correction I make is telling runners to slow down their easy runs. "Easy" is doing a lot of work in that description. Easy means: full conversation, breathing comfortably through the nose, feeling like you could go much longer, no accumulation of fatigue that limits tomorrow. For most runners, that's 75–90 sec/km slower than race pace. When they first try it, it feels embarrassingly slow. Within 4–6 weeks, their race paces improve.

The Conversion Formula — All Four Paces from Your 5K Time

The most important offset is easy pace. Runners systematically run easy runs 10–30 sec/km above the formula. The incorrect easy pace is the single most common training error in recreational running — it trains a pace that's neither easy enough to recover from nor hard enough to produce threshold adaptation. It produces consistent stagnation.

Quick check for interval pace: for 400m–800m intervals, use 5–10 sec/km faster than race pace. For 1km intervals or race-pace repeats: race pace ± 3 sec/km. The shorter the rep, the faster relative to race pace. Don't apply interval pace to long repeats (2km+) — that's threshold territory.

Calculation Systems Compared — VDOT vs. McMillan vs. Pfitzinger

VDOT (Jack Daniels): based on a physiological oxygen cost model; uses current race performance to predict training zones. Most widely validated in distance running coaching and the closest to a physiologically grounded system. Easy and interval zones tend to be slightly conservative compared to McMillan — this conservatism is intentional and is a feature, not a bug, for long-term training. My default recommendation.

McMillan Running Calculator: based on prediction of equivalent performance across distances; training paces derived from that equivalence. Easy pace often runs 5–10 sec/km faster than VDOT; threshold paces are similar between the two systems. Useful cross-check when VDOT produces paces that feel excessively conservative.

Pfitzinger (Pete Pfitzinger): more directly empirical; threshold zones align closely with heart rate data. Useful for runners who prefer heart rate to pace as primary guide — Pfitzinger's zones are more directly cross-referenceable with heart rate monitor output than VDOT's pace-based system.

Which system to use: any one of these, consistently, is better than switching between them. The differences are small (5–10 sec/km between systems) but become confusing if you use VDOT for easy runs and McMillan for intervals. Pick one. Use it throughout the training block.

When systems disagree with your felt experience: if your calculated "easy" pace consistently feels hard, your pace is wrong — not the effort. Use the effort description to self-calibrate and accept that the formula may be slightly off for your individual physiology. The descriptions (full conversation, 2–3 words, can't speak) are more reliable than any formula for most recreational runners.

Training Without a Recent Race Time

All three calculation systems require a recent race time. Three options if you don't have one:

Option 1 — 1.5km time trial: run 1.5km flat and all-out (after a proper warm-up). Multiply the time by 3.5 to get an approximate 5K prediction. Example: 1.5km in 6:30 → predicted 5K of approximately 22:45. Then apply the conversion formula to that prediction.

Option 2 — 20-minute tempo test: run as far as possible in 20 minutes at a hard but sustainable effort. Add 5% to the pace for an approximate threshold pace estimate, and use threshold + 30–40 sec/km for easy pace.

Option 3 — Effort-based zones: use the conversation test for each zone (full conversation = easy; 2–3 words = tempo; can't speak = interval) until you have a race result to calibrate from. For runners new to structured training, this is the starting point.

For detailed instructions on training pacing without a race result, see interval pacing without a recent race time.

When to Recalibrate Your Training Paces

Primary trigger: a new race or time trial. Recalculate training paces after every race — not just goal races, but every parkrun. Stale training paces are one of the most common reasons runners plateau at a finish time they've been running for 2–3 years. I've seen athletes recalibrate from a 22:00 5K result set three years earlier and discover they've been training at paces 30–40 sec/km below their current fitness.

Secondary trigger: zones feel misaligned with effort descriptions. If easy runs feel notably easier than 6–8 weeks ago at the same pace — the conversation is effortless, you're not accumulating any fatigue — your aerobic base has improved faster than the formula reflects. Recalibrate via a time trial rather than adjusting by feel alone.

Warning sign: if your easy pace and tempo pace are within 20–25 sec/km of each other, easy runs are almost certainly too fast. At a 25:00 5K level, easy pace should be approximately 6:15–6:30/km and tempo should be 5:30–5:40/km — a gap of approximately 40–50 sec/km. If that gap is smaller, the easy runs are eroding recovery capacity.

Recalibration frequency for structured runners: every 8–12 weeks via a parkrun or local 5K race. More frequently if training load has increased significantly. Paces should not be fixed throughout a 16-week block; they should shift as fitness improves.

Weekly Load Balance — How Much of Each Zone

Target ratio for 5K runners: 75–80% easy, 10–12% tempo, 8–12% interval. For a 35km/week runner: approximately 27km easy, 4km tempo, 4km interval.

The most common error is inverting the ratio — running 20–30% at tempo and above, 70% easy. This produces over-training symptoms within 4–6 weeks: elevated resting heart rate, persistent fatigue, declining interval performance, increasing susceptibility to minor illness. The fix is adding more easy volume, not more speed work.

The counterintuitive truth that I find myself repeating most often: more easy running — not more speed work — is the most available training upgrade for recreational runners who have plateaued. Almost every runner at a plateau is running their easy days too fast and doing too much quality relative to their aerobic base. Adding 15–20 minutes to each easy run and slowing it correctly produces faster race times within one training block in most cases.

FAQ — 5K Training Paces

What pace should I run easy runs?

Race pace + 75–90 sec/km. For a 20:00 runner: 5:15–5:30/km. This feels embarrassingly slow the first time. That's correct.

Tempo vs. threshold — what's the difference?

Often interchangeable. Threshold is the maximum aerobic pace (approximate 1-hour race pace). Tempo is run slightly below it. The 2–3-word conversation test applies to both.

How do I calculate training paces from my 5K time?

From race pace: easy = +75–90 sec/km; tempo = +30–40 sec/km; intervals = −5–10 sec/km. Use the table above for common 5K times.

Should interval pace be faster than 5K race pace?

Yes, for 400m–800m reps: 5–10 sec/km faster. For 1km reps: race pace ± 3 sec/km.

Easy runs feel too easy — am I doing it right?

Yes. Full conversation = correct. Easy runs aren't meant to feel like training stimulus; they're aerobic base and recovery.

How do I know if paces need updating?

Easy runs feel notably easier than 6 weeks ago at the same pace, or easy and tempo paces are within 20–25 sec/km of each other. Recalibrate via a parkrun or time trial.

See also: converting race pace to in-race strategy · training paces without a race time · race splits and training pace reference chart

Some Other Pages You May Like