Why Zone 2 Is the Foundation of My Ironman Run Training
Why most distance runners should be spending more time here than they think
I'm about nine weeks out from my first full Ironman in Cozumel, and if you look at my run training data right now, one thing stands out: most of my running happens at a heart rate between 138 and 152 beats per minute.
That's my zone 2 range. After years of training, running at this effort feels natural and sustainable. But the energy cost of pushing above it on a long run doesn't change - go too hard too early, and you can pay for it before you hit the distance you needed.
The data doesn’t lie. So I listen to it.
Zone 2 has become one of the most discussed training concepts in endurance sports over the last few years. Most of the conversation treats it like a magic system - run easy, build mitochondria, unlock unlimited aerobic capacity. The reality is more nuanced, and if you're a recreational runner building your base, that nuance matters for understanding what zone 2 is doing for you versus what some coaches overclaim.
This is what I know from research, my certifications, and years of putting it into practice.
Most Runners Are Training in the Wrong Zone Without Knowing It
Before zone 2 means anything, you need to understand why zones exist at all.
Your body produces energy through different metabolic pathways depending on how hard you're working. At lower intensities with sufficient oxygen, you're primarily using oxidative metabolism - burning fat and carbohydrates with oxygen, a process that's efficient and sustainable over long distances. As intensity increases and oxygen demands can’t be met, your body shifts toward faster pathways that don't require oxygen but produce lactate as a byproduct. At low levels, lactate gets cleared as fast as it's produced. Push hard enough, and it accumulates faster than you can clear it, forcing you to slow down or stop. At maximum effort, you simply run out of energy to produce - the system can't keep up with the demand at all.
Heart rate tracks with oxygen demand. As you work harder, your heart beats faster to deliver more oxygen to working muscles. At lower heart rates, oxidative metabolism dominates because oxygen supply keeps pace with demand. As heart rate climbs, the body shifts toward faster pathways to compensate for the shortfall, which is where lactate starts to accumulate. Heart rate zones are a way of assessing where that shift is happening for you specifically - they don't determine your metabolic state, but they give you a reliable window into it during a run.
Without that understanding, most runners misjudge their own intensity. What feels like a comfortable easy run, especially over a short distance, can often be at an intensity that has crossed into zone 3 or even zone 4. Perceived effort and actual metabolic state are telling different stories - and because the run feels manageable, there's no signal that anything is off. The aerobic base doesn't develop the way they expect, and they hit a ceiling at certain distances, struggle to hold pace as runs get longer, and can't figure out why consistent training isn't translating into greater improvements.
Pace alone doesn't tell you which zone you're in, because pace varies with terrain, fatigue, heat, and fitness. A pace that keeps you in zone 2 on a flat road might push you into zone 3 on a hill or in the heat. Heart rate gives you a direct read on how hard your body is actually working, regardless of the conditions around it.
The Grey Zone Blocks Progress From Both Directions
Most recreational runners spend the majority of their training time at a moderate intensity - not easy enough to build the aerobic base, not hard enough to drive threshold adaptation - the grey zone.
It feels like real training because it's hard enough to be uncomfortable. But the heart rate data shows something different - they're spending almost no time in zone 2 and almost no time in the zones where threshold adaptation happens either. Just medium work, all the time.
The cost for distance runners is specific. The oxidative pathway - the one zone 2 develops - is what allows your body to sustain effort over distance by drawing on fat as fuel and keeping lactate manageable. Without that foundation, you're relying more heavily on faster pathways that burn through glycogen and produce lactate faster than you can clear it. Everything past a certain distance starts to feel hard at the same point every time. You can partially compensate with a fueling strategy - taking in carbohydrates mid-run to replenish glycogen - but that's managing the symptom, not building the foundation.
The runner who can't get past ten miles without falling apart, or who blows up in the back half of every race, usually has an aerobic base that hasn't been developed to support the distance they're asking of it.
Runners who come to me after months of training without progress almost always show the same pattern in their data - every run clustered at the same moderate intensity. The hard sessions weren't producing threshold adaptation because the aerobic base wasn't developed enough to support them. The easy sessions weren't building the base because the intensity was too high to allow that development. Their training was consistent, but they didn’t distribute intensity enough to create more change.
Zone 2 Works - Just Not the Way Most Coaches Describe It
Before getting into what zone 2 does, it's worth naming something the research community acknowledges directly: the definition of zone 2 is inconsistent. The reason is that zones are estimates built around physiological thresholds - markers like lactate threshold and VO2 max - but those thresholds don't have hard edges.
Different zone frameworks draw the boundaries in different places, which is why zone 2 gets described as conversational pace, low intensity, a specific percentage of max heart rate, or the intensity at which fat oxidation is highest, depending on who's using the term. These descriptions don't always land in the same heart rate range, which is part of why so many runners write off zone 2 work or think they're doing it when they're not.
The most reliable way to find your zone 2 is to anchor it to your functional threshold heart rate (FTHR), the heart rate you can sustain at maximum effort for about one hour. Zone 2 sits at roughly 85-89% of that number. For a runner with an FTHR of 165, that puts zone 2 at approximately 140-147bpm.
My Garmin watch estimates my lactate threshold heart rate - essentially the same marker as FTHR, the point where lactate starts accumulating faster than it can be cleared - at 162bpm. Using the 85-89% calculation, my zone 2 sits between 138 and 144bpm. In practice, I train across that range and slightly above it, which puts my working zone 2 between 138 and 152 - taken from my watch, as calculated from my heart rate reserve, showing different methods don’t always have the same numbers. That wider range reflects where I'm actually aerobically stable during long efforts based on my own training data, rather than a strict percentage calculation.
If you don't have a formal test, most modern GPS watches estimate this threshold from training data and give you a reasonable starting point.
At zone 2 intensity, you're working primarily through the oxidative pathway - the metabolic state where fat oxidation is at or near its peak as a percentage of total fuel use. This matters for distance running specifically because fat is a far larger fuel reserve than glycogen. A well-developed oxidative pathway means you can sustain effort over long distances without burning through glycogen stores prematurely. Long runs and base-building work belong in this zone because that's the metabolic system distance running depends on most.
But the research picture is more nuanced than most zone 2 content admits, and this is where it's worth being specific about who the research applies to. For recreational runners and athletes still building their aerobic base, zone 2 training is doing exactly what it claims - developing foundational aerobic adaptations that make distance running possible. For trained athletes with already well-established aerobic bases, the adaptation claims get more complicated. A 2025 narrative review found that zone 2 likely increases fat oxidative capacity in untrained and sedentary populations, but the effect is likely limited in trained athletes. Further, a meta-analysis of 56 studies found that exercise below 60% of maximum work rate is not expected to produce meaningful increases in mitochondrial density compared to higher-intensity training - with this finding most pronounced in already-conditioned athletes.
This doesn't mean zone 2 is the wrong tool for aerobic base development - it means the mitochondrial and fat oxidation claims need to be matched to who's actually doing the training.
For a recreational runner whose heart rate still pushes above zone 2 on what should be easy runs, zone 2 is almost certainly still providing meaningful aerobic stimulus. For a highly trained athlete whose zone 2 feels genuinely effortless and whose aerobic base is already well-established, the research suggests that adding more intensity - specifically threshold and tempo work - may drive more adaptation than adding more zone 2 volume. Most recreational runners fall into the first group, not the second.
You Can't Skip the Base and Expect the Intensity Work to Deliver
If you've read this far, the obvious pushback is: if zone 2's adaptation claims are weaker for trained athletes, why not just run harder? More tempo, more threshold work, more intensity - that's where the bigger gains are, right?
The answer depends on what you've already built. Tempo work - zone 4, at or slightly above lactate threshold - trains your body's ability to clear lactate and buffer acidity. It’s often described as the biggest bang for the buck for trained distance runners, and the research supports it. For a well-conditioned athlete, the evidence suggests that increased intensity could drive adaptation as much as, or more than, increased volume.
But zone 2 builds the aerobic foundation that makes tempo work productive. A developing runner who hasn't built that base yet will get less from tempo sessions because the foundation isn't there to support them. The programming isn't zone 2 OR tempo - it's zone 2 as the base volume with tempo and threshold work layered in deliberately. In a well-structured marathon or Ironman run program, most weekly volume is in zone 2, with zone 3 steady-state and zone 4 tempo sessions added as specific, calculated sessions. When volume is increasing, you don't simultaneously pile in speedwork - your body is already managing increased training stress, and layering in intensity on top of that increases injury risk and compromises recovery before the volume adaptation is complete.
My tempo work is underdeveloped right now - I'll be honest about that. In multisport training, tradeoffs are real. With swim, bike, and run volume all competing for time, something gets compressed. Zone 2 run volume is my priority at this point in the build, and tempo sessions are getting less attention than ideal. That's the honest reality of my Ironman prep.
The data tells me why zone 2 is the right priority, though. An Ironman run is 26.2 miles at the end of a 2.4-mile swim and a 112-mile bike - by the time you hit the run, glycogen stores are significantly depleted. When I push above 152 bpm on long runs, I burn out before I reach the distance I need. When I stay in the 138-152 range, I can cover the distance, supplement with fueling to manage what glycogen I do need, and finish feeling like I could continue. The zone 2 development I'm doing right now - getting faster within that heart rate range - is building the specific capacity the Ironman run requires. Multiple weeks of data are confirming it.
How to Find Your Zone 2
We've already covered the calculation using my own numbers, but here's how to apply it to yours.
Your anchor is FTHR - the heart rate you can sustain at maximum effort for approximately one hour. The most reliable way to find it is a 20-minute test: run at maximum sustainable effort for 20 minutes, record your average heart rate, and take 95% of that number. That's your FTHR. Zone 2 sits at 85-89% of that number.
If your FTHR is 170, zone 2 runs from approximately 145 to 151bpm. If it's 165, you're looking at roughly 140-147bpm. Most modern GPS watches estimate a lactate threshold heart rate from training data - different watches use different algorithms, and the accuracy varies. Still, it gives you a reasonable starting point if you haven't done a formal test.
One thing worth naming clearly: the zones themselves are just estimates, and different people use them slightly differently. They're built around physiological thresholds that don't have hard edges, and the percentage ranges approximate where those thresholds tend to fall. Use the zone as a guidepost, not a hard limit. If you're consistently running above the ceiling at what should be an easy effort, that's a signal to either slow down or reassess your zones - as fitness improves, your FTHR and zone ranges shift upward, which is why recalculating periodically matters.
For most recreational runners just starting zone 2 work, it feels slower than you want to go. Your heart rate may push above the zone even at paces that feel easy - that's because the pace is demanding more oxygen than your aerobic system can efficiently supply, so your heart rate climbs trying to meet that demand, and your body shifts toward faster metabolic pathways to compensate. The fix is to slow down until your heart rate drops back into range. That changes as the base builds. Stay in the zone. The pace will come as your body adapts.
The runners who dismiss zone 2 because it feels too easy are usually the ones who blow up past mile ten. The ones who stay in it finish the way they planned.
What does your heart rate data tell you about where you're training?