What Pace Should My Long Runs Be? The Slower-Than-You-Think Marathon Long-Run Rule

Your long run should feel almost uncomfortably easy. If it doesn’t, you’re running it too fast — and you’re paying for it on Wednesday.

Most runners know the rule: “go slow on long runs.” Almost none of them actually do it. They drift 30–45 seconds per mile above the target and tell themselves the extra effort is building fitness. It isn’t. It’s borrowing recovery from the rest of the week.

Here’s the number that matters: easy pace — the physiologically correct intensity for long runs — sits at 59–74% of VO2max. That translates to 65–79% of your max heart rate. For a runner targeting a 3:30 marathon, that’s roughly 8:49 to 9:37 per mile. Their marathon goal pace is 8:01. The gap is real, and it’s intentional.

The Origin of the “60–90 Seconds Slower” Rule — and Why It Only Half-Works

The classic heuristic says to run long runs 60–90 seconds per mile slower than your 5K race pace. That advice has a solid physiological foundation. It was calibrated for runners whose 5K pace and marathon pace sit in a certain range.

It breaks down badly at the extremes.

For a runner who can run a 5:30/mile 5K, adding 90 seconds lands at 7:00/mile. That’s still well inside the aerobic zone. Fine. But for a runner with a 12:00/mile 5K who adds 90 seconds, they end up at 13:30/mile — which may be slower than walking pace provides useful stimulus for. The formula assumes a particular body-weight, lactate curve shape that doesn’t generalize.

The better anchor is your marathon goal pace. Every major coaching system uses it. They just disagree slightly on how far below it to go.

What Three Coaching Systems Actually Prescribe for Long Run Pace

Here’s where the systems diverge. Each applies to the same set of goal marathon times so you can see the spread.

Notice how wide the Daniels range is at 4:30 and 5:00. That’s the race-pace relativity effect: slower runners’ goal marathon pace already falls inside the aerobic development zone. Running much slower than that doesn’t add more mitochondrial stimulus — it just reduces time on feet.

For runners targeting sub-3:30, Daniels and Pfitzinger are nearly identical. Both say the long run should be 45–90 seconds slower than marathon pace. Hansons sits a bit tighter — their philosophy places the hard work on midweek “strength” runs, not the long run itself.

The Physiology of the Long Run — What Your Body Is Actually Building

Think of your aerobic system as a power grid. Easy running lays down new cable — more mitochondria, more capillaries, more fat-burning enzymes. Harder running flips the switches and draws power through existing cable.

You can’t flip switches and lay cable at the same time. The long run is cable-laying day.

Holloszy’s 1967 foundational research showed that 12 weeks of running at 50–75% VO2max — the easy long-run zone — produced roughly a 100% increase in mitochondrial oxidative enzyme activity. Cytochrome oxidase activity rose 81%. Mitochondrial protein increased 57%. In short: the body nearly doubled its aerobic machinery in three months of slow running.

That 50–75% VO2max intensity range maps almost exactly to the easy long-run pace prescriptions from Daniels, Pfitzinger, and the 80/20 research.

A 2021 study in the Journal of Strength and Conditioning Research tracked 85 elite male long-distance runners over seven years. Easy run volume was the single strongest predictor of performance — ahead of tempo volume, short intervals, and long intervals combined. The cable-laying mattered more than the switch-flipping.

The Hidden Cost of Running Your Long Run 30 Seconds Too Fast

Here’s what 30 extra seconds per mile on a long run actually costs you.

A properly paced long run takes 1–2 days to recover from. An overpaced run that runs 3+ hours at moderate intensity needs 4–5 days. That’s a 3-day swing. For a runner who does Tuesday tempos and Thursday intervals, a Sunday long run that runs too hot eliminates both workouts.

Recovery doesn’t disappear. It shifts — from the weeks’s quality sessions into absorbing the long run’s damage.

A 2025 study by Zanini, Folland, and Blagrove in Scandinavian Journal of Medicine & Science in Sports measured what happens when well-trained marathoners run at heavy intensity for 90 and 120 minutes. After 90 minutes, lactate threshold speed dropped from 14.0 to 13.5 km/h. After 120 minutes, it fell further to 13.0 km/h — a 6.6% total drop. VO2 peak fell 7.1%. Running economy worsened 5.8%. Translation: running your long run too hard doesn’t just make you tired. It actively degrades the performance markers that predict your marathon time.

The data is clear. Go too hard and you pay for it twice.

Heart Rate, Pace, or RPE — Which Should You Use?

This is where most articles lead you wrong. They say “use heart rate zone 2.” The data says be more careful than that.

A 2022 study measured recreational marathoners during a full marathon race. Heart rate held steady at about 89% of HRmax from kilometer 5 onward. But the effort those runners were actually producing — measured as percent of VO2max — dropped from 81% to 74% over the race. The heart-rate-to-effort ratio rose from 1.01 to 1.19. Same HR, harder work.

Using heart rate as your only pacing tool on a long run means you can be working meaningfully harder than you think while the watch stays quiet.

The best combination for most runners:

1. Pace as a ceiling. Pick the slow end of your target range and don’t go faster than that. Treat the number on your watch as a limit, not a target.
2. The talk test as a real-time check. Can you speak 6–8 words in a row without gasping? If not, you’re above your first ventilatory threshold (VT1) — the scientifically validated upper boundary of easy running. Slow down.
3. HR drift as a retrospective signal. After the run, look at your drift ratio in session analysis. A drift of less than 5% means your pace and heart rate stayed coupled — the hallmark of an aerobic long run.

Heart rate doesn’t lie. But it also can’t tell you the full story in real time on a long run.

A Real Runner in Practice: What Fixing Long-Run Pace Actually Does

Marcus is 41, training for a 4:00 marathon. He runs about 45 miles per week. His long runs were clocking in at 9:20–9:40/mi — a pace that felt controlled and purposeful.

By Pfitzinger’s prescription, his long-run range should be 10:04 to 10:58/mi. He was running roughly 45 seconds per mile too fast.

After eight weeks of deliberately slowing his long runs to 10:10–10:30/mi, two things changed. First, his Tuesday tempo workouts improved — he was hitting target paces without the same grind. Second, his training plan fitness score in AthleteOS climbed steadily instead of plateauing. His next marathon: 3:58.

The long runs felt embarrassingly slow. The race didn’t.

When Can You Run Faster? Fast-Finish Long Runs Explained

Easy long runs are not the only kind. There’s a second format that belongs in your build phase: the fast-finish long run.

The structure: run the first 75–80% of the run at easy long-run pace, then finish the last 4–6 miles at or near goal marathon pace. You arrive at those final miles already glycogen-depleted — which is exactly the condition you’ll face at mile 20 on race day.

This only makes sense in the race-specific block, typically 8–4 weeks before the marathon. Use it every 2–3 weeks at most. Running fast-finish work every week is one of the most common mistakes self-coached runners make. Race-phase pacing principles matter here — train the pattern you’ll race, not just the speed.

The three long-run formats and when to use them:

How AthleteOS Calculates Your Long-Run Pace

The “60–90 sec/mile slower” rule works reasonably well for runners with a 5K time between 20 and 30 minutes. Outside that range, it breaks down — sometimes badly.

AthleteOS prescribes your long-run pace from two inputs: your current goal marathon pace and your measured threshold pace. If your threshold improves mid-training block — which it should — AthleteOS recalculates your long-run zone automatically. You don’t stay locked into a range you set in January.

If your long run last weekend ran 10% faster than your prescribed range and you were already carrying fatigue, AthleteOS adjusts Tuesday’s session target down to prevent the bleed-over. The training week stays coherent. The quality sessions stay quality.

Start building your training plan on AthleteOS and see your exact long-run pace range after answering six questions about your training history and goal race.

The 80/20 Rule — Why Slow Running Built Every Elite

Seiler’s foundational 2010 research found that elite endurance athletes across rowing, running, cycling, and cross-country skiing converge on the same distribution: about 80% of sessions at low intensity, 20% at high intensity. A 2024 systematic review of 14 studies confirmed that polarized training — the model that puts the long run squarely in that 80% — produces VO2max improvements up to 29.9% and running economy gains of 5.3%.

Elite Kenyan marathoners run their long training runs 2–3 minutes per mile slower than race pace. Eliud Kipchoge’s recovery runs start at 8:30–8:45/mile. His race pace is 4:34/mile. That’s nearly four minutes of offset. The gap isn’t accidental.

Slow is the strategy. Fast is the result.

The correct long-run pace isn’t a feeling. It’s a number. Pick the slow end of your coaching system’s prescribed range, run to it, and resist the urge to drift faster when you feel good. The science of easy-day pacing is unambiguous: the adaptation happens in the easy zone, not just above it.

Run your long runs embarrassingly slow. Race them hard.