The Long Run: How Long, How Slow and How Often?

The long run is the single most important training session for any endurance athlete. No interval workout, tempo run or hill session builds your aerobic base as reliably as this one easy, extended effort each week. At the same time, the long run is the most commonly botched session of all: run too fast, kept too short or extended in sudden jumps. This article explains what happens inside your body, how to dose duration and pace correctly, and which mistakes to avoid.

Why the long run matters so much

The adaptations that make up endurance come predominantly from easy, sustained work — not from hard sessions. The long run delivers the longest continuous stimulus of your week:

• More capillaries: The fine network of blood vessels around your muscle fibres becomes denser. Oxygen and nutrients arrive faster, waste products leave faster.
• More and larger mitochondria: The cells' "power plants" multiply. Your muscles gain capacity to process fat and carbohydrates aerobically.
• Better fat metabolism: During long, easy runs the body learns to draw more energy from fat and spare the limited glycogen stores — exactly what decides whether you hit the wall at mile 19 in a marathon.
• A stronger heart: Stroke volume rises — each beat moves more blood. Resting heart rate drops, and so does your heart rate at any given pace.
• Musculoskeletal toughening: Tendons, ligaments and bones adapt to sustained loading. This adaptation is slower than the aerobic one — and the main reason volume may only rise gradually.
• Mental strength: Spending two to three hours on your feet regularly teaches you to handle monotony and fatigue. In a race, that is worth its weight in gold.

These effects compound over months and years. That is exactly why the long run sits at the heart of the 80/20 principle: around 80% of training stays easy — and the long run is the largest single building block of that easy share.

How long should the long run be?

The key rule: the long run makes up 20 to 30% of your weekly volume. If you run 40 kilometres a week, that means 8 to 12 kilometres; at 80 per week, 16 to 24. Concrete guidelines by goal:

• 5K/10K: 75 to 90 minutes. More is unnecessary for these distances — the aerobic base still grows without the load eating into the week's quality sessions.
• Half marathon: 90 minutes to 2 hours. At the peak of preparation, occasionally 18 to 20 kilometres.
• Marathon: 2 to 3 hours, at most around 32 to 35 kilometres. Running beyond three hours adds little extra adaptation but extends recovery significantly — the risk outweighs the benefit.

Think in time, not kilometres. The physiological adaptations hang on duration under load, not on the distance on your watch. A slower runner out for 2.5 hours gets the same stimulus as a faster one covering more ground in the same time. As for the marathon distance itself: you run the 42 kilometres on race day, not beforehand in training.

Progression works in waves: 5 to 10% longer each week, with every third to fourth week a deload week featuring a much shorter long run (about 60% of the previous duration). Jumping duration abruptly — from 90 minutes straight to 2.5 hours — invites exactly the kind of fatigue that tendons and joints cannot yet handle.

The right pace: slower than you think

The most common long-run mistake is pace. The target zone is base intensity: 65 to 75% of maximum heart rate — "comfortably easy" by feel. Three simple checks:

• Talk test: You can hold a conversation in full sentences without gasping. The most honest zone check there is.
• Heart rate: Within the zone 1 to 2 corridor — the exact derivation of your personal values is in our article on heart rate zones in training.
• Pace rule of thumb: About 60 to 90 seconds per kilometre slower than your marathon pace — for most recreational runners, closer to the upper end.

Why not faster? Because a brisk long run slips into the "grey zone": too hard for the desired aerobic adaptations, too slow for a genuine tempo stimulus. The result is double the fatigue for half the training effect — plus a quality session two days later that goes badly because the legs are still heavy from the weekend.

There is one deliberate exception: the progressive long run. In specific marathon preparation, the final third gradually accelerates toward race pace — roughly the last 30 to 45 minutes. This teaches the body to produce pace on tired legs. But such variants belong in targeted blocks, not in every weekend run.

How often, and where in the week?

For almost all athletes: one long run per week, classically on the weekend when time and recovery line up best. Two placement points:

• Distance from hard sessions: The day before the long run is easy or off. Running intervals on Saturday and 2.5 hours on Sunday means starting the long run already depleted — adaptation suffers, injury risk rises.
• Respect the deload week: Every third to fourth week, the long run is cut sharply. This wave structure is not a luxury but the very mechanism through which adaptation happens — details in our article on the deload week.

Advanced marathon runners occasionally schedule the long run "on tired legs" during peak blocks — for instance the day after an extended tempo run. This simulates the fatigue of a race's second half, but it is a technique for experienced athletes with a solid base, not for beginners.

Fueling during the long run

Up to about 75 minutes, the body needs nothing on the go — glycogen stores are ample. Beyond that, the real gut training begins: 30 to 60 grams of carbohydrates per hour, in small portions every 20 to 30 minutes, plus regular drinking. This serves two purposes: it prevents the late-run fade, and it accustoms the digestive tract to fueling under load — a skill that makes or breaks race day. Exactly what to eat and drink in the race itself is covered in our article on marathon fueling.

Straight after the long run, the recovery window counts: within 30 to 60 minutes, carbohydrates plus 20 to 30 grams of protein — then eat normally. Letting the session end "fasted" forfeits a measurable share of the adaptation and starts the week with a recovery deficit.

The most common long-run mistakes

• Running too fast. The classic: "easy" drifts into a medium-effort steady run because slow feels "unproductive". That very slowness is the training stimulus — run the long run too fast and you pay double fatigue for half the effect.
• Jumps that are too big. Increasing duration by more than 10% week over week overloads tendons and joints — they adapt more slowly than the cardiovascular system. Patience in progression is the best injury protection.
• Testing new gear. New shoes, a new gel, a new bottle — the long run is the dress rehearsal for race day, but every element gets tested individually and early enough. Close to the race: nothing new.
• Skipping the deload week. "I feel good" is no reason to skip the wave. Adaptation happens during the unload, not during the load.
• Grinding through stubbornly. Signs of illness, a stabbing pain or a resting heart rate well above normal are reasons to shorten or postpone — one skipped long run costs no fitness; one completed in the wrong state can cost weeks.

How Peakora plans your long runs

In the Peakora engine, the long run is firmly anchored in your weekly structure: duration and placement follow your race distance, your current volume and the wave logic of build and deload weeks. The engine progresses duration gradually rather than in jumps, keeps the day before it easy and shortens the long run automatically during deload weeks. And because the recovery monitor reads your form curve, the session shifts or shrinks when your recovery argues against it — instead of having you stubbornly work through a static plan.

Frequently asked questions about the long run