Training zones calculator

Without structured intensity control, most runners default to a moderate effort that is too fast to recover from but too slow to stimulate speed or VO2max adaptation. This "gray zone" problem is the most common training mistake in distance running.

Research from Seiler and Kjerland (2006) showed that successful endurance athletes follow a polarized distribution: roughly 80% of training at low intensity and 20% at high intensity. Zones make this distribution measurable and repeatable.

When you train at the right intensity for the right duration, you target specific physiological adaptations. When you don't, you accumulate fatigue without proportional benefit. Zones solve this problem by giving each session a clear purpose.

A training zone is an effort band with a specific objective. Low zones build aerobic durability and recovery capacity. Mid and high zones target threshold, VO2 kinetics, and speed support.

The most useful zone system is the one you can apply consistently. The goal is repeatable execution, not perfect precision on every run.

Internal load is your body's response, usually tracked by heart rate. External load is the mechanical output, usually tracked by pace. You need both.

Example: on a hot day, pace can fall while HR rises. In that case, forcing pace can turn an easy run into threshold stress. Endurance distribution research such as Seiler and Kjerland supports controlling intensity so easy days stay easy.

Use Karvonen (heart rate reserve) when you have a reliable resting HR measurement. This method adjusts zones based on your individual cardiac reserve, producing more personalized boundaries. It is the recommended default.

Use Max-HR percentage when resting HR is unavailable, unreliable, or when you want a quick comparison. Max-HR percentage is simpler but less individualized -- two runners with the same max HR but different resting HRs will get identical zones despite different fitness levels.

Karvonen uses heart-rate reserve (max HR minus resting HR), which improves personalization compared with max-HR percentages alone.

Original method source: Karvonen et al. (PMID 13470504).

If max HR is not entered manually, the calculator estimates it from age and sex:

Supporting evidence: Tanaka et al. (PMID 11153730) and Gulati et al. (PMID 20585008).

VDOT pace bands are derived from race performance, not guesswork. They provide practical ranges for easy, marathon, threshold, interval, and repetition sessions.

This tool keeps pace guidance aligned with the same VDOT anchor so table outputs remain internally consistent. Method context: Daniels' Running Formula.

In practice, easy pace usually aligns with HR Zones 1-2, threshold pace often aligns with HR Zones 3-4, and interval pace trends into HR Zone 4-5 once HR catches up.

Short intervals can show HR lag and cardiovascular drift. This is why pacing and repeat quality should be reviewed alongside HR trend, not by HR alone. Reference: Cardiovascular drift evidence (PMID 11337829).

A well-structured week for a runner training 5-6 days typically distributes intensity as follows: 3-4 sessions at easy effort (Zones 1-2), one threshold session (Zone 3-4), and one interval or repetition session (Zone 4-5). The remaining day is rest or an optional recovery run.

This produces approximately 80% easy volume and 20% hard volume, consistent with the polarized model. The specific days are flexible, but the ratio matters more than the schedule.

Running easy days too fast. This is the most common mistake. If your Zone 2 ceiling is 150 bpm and you routinely hit 160 bpm on easy runs, you are accumulating unnecessary fatigue that compromises hard-session quality.

Ignoring HR drift. Heart rate rises during long runs even at constant pace due to cardiac output changes and dehydration. This is normal and does not mean you should slow down if the drift is gradual (5-10 bpm over 60+ minutes). Reference: Coyle and Gonzalez-Alonso.

Recalculating zones from bad data. A race run in extreme heat, at altitude, or while undertrained is not a good VDOT anchor. Wait for a representative performance before updating zones.

Treating zones as rigid boundaries. Zones are ranges, not walls. Being 2-3 bpm above or below a boundary does not invalidate the session. Focus on staying within the intent of the session, not on hitting exact numbers.

Site standards and update policy are documented in Editorial Policy and Contact.