The Science of the Long Run: How Far Is Far Enough?

I used to measure my long runs in kilometres. Sixteen. Twenty. Twenty-five. The number on the plan was gospel, and hitting it felt like an accomplishment regardless of how the run actually went. It took me longer than I'd like to admit to realise I was asking the wrong question. The question isn't "how far should I run?" It's "how long should I be on my feet, and at what cost?"

The long run is the cornerstone of endurance training. Every coach prescribes one. Every training plan features one. But the why behind it is more nuanced than most runners appreciate, and getting it wrong — too long, too fast, too frequent — can do more harm than good.

What the long run actually does

The long run isn't about toughness, though it builds that too. It's about forcing your body into physiological territory that shorter runs simply can't reach.

Glycogen depletion and fat adaptation. After about 90 minutes of running, your glycogen stores start running low. This forces your body to increasingly rely on fat oxidation for fuel. The more you practice this, the better your body gets at it — and the longer you can sustain pace before hitting the wall. This is the primary physiological argument for runs exceeding 90 minutes.

Slow-twitch fibre recruitment. As your primary muscle fibres fatigue during a long run, your body recruits additional slow-twitch fibres that don't normally get called upon. This is how you expand your aerobic workforce — by running long enough that the B-team has to show up and learn the job.

Mental endurance. There's no simulation for the psychological experience of running when your body wants to stop. Long runs teach you what discomfort feels like at 25 kilometres, so that when you encounter it at 30 kilometres in a marathon, it's familiar rather than alarming.

Structural conditioning. Bones, tendons, and connective tissue need sustained, repetitive loading to adapt. Short runs don't apply enough total stress. Long runs — done at appropriate intensity — teach your musculoskeletal system to handle the cumulative impact of thousands of strides.

The long run doesn't make you fast. It makes you durable. And durability is what allows you to do the work that makes you fast.

Time on feet vs. distance: the metric that matters more

Here's where the conventional wisdom gets it wrong. Most training plans prescribe long runs by distance — "run 30 kilometres this weekend." But a 30K run means very different things to different runners.

For an elite marathoner running 4:00/km, 30 kilometres takes two hours. For a recreational runner at 6:30/km, the same distance takes over three hours. The physiological stress of a three-hour run is dramatically different from a two-hour run — not just more of the same, but qualitatively different in terms of muscle damage, glycogen depletion, inflammation, and recovery time.

This is why many experienced coaches prescribe long runs by time rather than distance. A 2.5-hour long run for both runners achieves similar physiological goals without the slower runner accumulating significantly more damage. Your running analytics should track both distance and duration — but for the long run, duration tells you more.

The diminishing returns curve

Here's the part that might save you from yourself: there's a point where longer stops being better. The physiological benefits of the long run — glycogen depletion training, fat adaptation, slow-twitch recruitment — are largely achieved within 2.5 to 3 hours of running. Beyond that, the returns diminish rapidly while the costs — muscle damage, suppressed immune function, extended recovery time — accelerate.

Running for four hours on a Saturday doesn't give you twice the benefit of running for two hours. It might give you 15-20% more stimulus at the cost of significantly more damage and a longer recovery period that compromises your training in the following days. The maths doesn't work.

This is the trap that many marathon runners fall into. They believe that if their race is 42 kilometres, they need to run close to that in training. But the research doesn't support this. The longest runs in most elite marathon programmes top out at 35-38 kilometres, and many successful coaches cap the long run at 2.5-3 hours regardless of the distance covered.

Pace: the most common long run mistake

The second-most common long run mistake (after running too far) is running too fast. The long run should be performed at genuinely easy pace — the same conversational effort you use for your regular easy runs. Many runners unconsciously speed up during long runs, particularly in the second half when they start feeling the distance and want to "get it done."

Running your long run too fast converts it from an aerobic-building session into a moderately hard effort that's too easy to build speed and too hard to recover from quickly. You end up tired for Tuesday's intervals but without the aerobic benefits that a properly paced long run would have delivered.

The exception is the marathon-specific long run, where the final 30-60 minutes are run at or near goal marathon pace. These runs have a specific purpose — teaching your body to find marathon pace on tired legs — and they should be used sparingly, perhaps three or four times in a training cycle. Every other long run should be at easy effort from start to finish.

Frequency: how often is enough?

One long run per week is sufficient for nearly every runner at every level. The idea that you need two long runs per week, or that you should do back-to-back long runs every weekend, is not supported by the evidence for most runners. The stress-to-benefit ratio simply isn't favourable.

What matters more than frequency is consistency over months. One long run every week for sixteen weeks produces far better results than sporadic heroic efforts. An AI training plan can help you build your long run progressively without the temptation to jump ahead.

If you're training for an ultra and feel the need for back-to-back long days, keep the total time manageable and ensure the second day is truly easy. The goal is cumulative time on feet with acceptable recovery cost, not a single session that wrecks your training week.

Building your long run: a progressive approach

If you're currently running a long run of 60 minutes, don't jump to two hours next weekend. The conventional wisdom of increasing distance by no more than 10% per week is a reasonable starting heuristic, though it's not a rigid law.

A more practical approach: build your long run by 10-15 minutes per week for three weeks, then drop back for a recovery week where you cut the duration by 20-30%. Repeat. This build-and-recover rhythm allows your body to absorb the training rather than just survive it.