Runsy
Guides

The long run

How far your long run should be, how slow to run it, when to add quality — and the part every plan skips: what to do with it after you miss a week.

25–30%

Of your recent weekly volume — the weeks you actually ran

2:30–3:00

Practical time cap, even in marathon training

Conversational

Default effort, the whole way

+10–15 min

Every second week — then cut back every 3rd or 4th

Almost every training plan agrees the long run matters, and most runners get it wrong in the same two ways: too long relative to the rest of their week, and too fast.

It is also the session most exposed to real life. A weekday run can be moved; a two-hour Sunday cannot, so it is the first thing a bad week deletes — and it is the piece printed plans handle worst when you come back. Both tables below exist for that.

How far: set it from the weeks you actually ran

The useful rule is proportional, not absolute. Your long run should be roughly 25–30% of your recent weekly volume — where "recent" means the average of the last three or four weeks you genuinely completed, not the week you had planned.

Recent weekly volumeLong run
20 km6–8 km
40 km10–13 km
60 km16–19 km
80 km20–24 km

Two adjustments. If you run only three days a week the share creeps up — 30–35% is normal and hard to avoid, because there are fewer days to spread the volume across. And if you are marathon training, the long run legitimately exceeds 30% during peak weeks; that is a deliberate, temporary distortion for race specificity, not a general principle.

The failure this rule prevents is the most common one in amateur running: a 32 km Sunday hanging off 45 km weeks. That long run is 70% of the week, it takes four days to recover from, it degrades every other session, and it predicts injury better than it predicts a good marathon.

Cap it in minutes, not kilometres

A 30 km long run is a two-hour job for a fast runner and a three-and-a-half-hour job for someone finishing a marathon in 5:30 — the same number on paper, a completely different stress. Most non-marathon training is well served by 60–105 minutes; marathon training caps somewhere between 2:30 and 3:00 whatever distance that produces. If a plan's distance would take you more than three hours, run the time cap and let the distance be what it is. Past about three hours the injury and recovery cost rises faster than the fitness returned.

What to run when you have missed weeks

This is the situation almost every runner is actually in, and the one every distance ladder ignores. Week 9 of a printed plan asks for 26 km because it assumes you completed weeks 1 through 8. If you did not, that number is a fiction, and running it anyway is how people get hurt in the last month before a race.

What you missedWhat to run nextThen
One long runResume the schedule exactly where you left itNever double up. Do not run last week's and this week's back to back, and do not add the missed distance to the next one
Two to three weeks70–80% of your last completed long runRebuild from there at the normal rate. Aerobically you have lost less than you fear; structurally — tendon, bone, feet — more than you think, and that is the system that gets injured
Four weeks or moreAround half of your previous longest — and treat the plan as voidThree or four consistent weeks of easy running before the long run grows at all, then re-derive the target from the 25–30% rule using the weeks you are now actually running
Illness below the neck, or a feverDo not run at allRebuild as though you missed one tier more than you actually did

Whatever the case, the number to re-derive from is your recent completed weekly volume. Almost every bad decision here comes from anchoring to a plan you did not execute, or to the fittest you have ever been, instead of to the last three weeks you genuinely ran.

How to progress it

  1. 01

    Add 10–15 minutes every second week

    Not every week. The connective-tissue adaptations that make a longer run safe lag the cardiovascular ones that make it feel possible. If a distance felt hard, repeat it next time rather than extending — nothing says the long run has to grow every fortnight.

  2. 02

    Cut back every third or fourth week

    Drop the long run by 25–30% and hold the rest of the week. This is where the adaptation actually consolidates, and it is the week most people skip because they feel good.

  3. 03

    Never grow the long run and the weekly volume together

    Pick one. Growing both in the same week is the fastest route to the sort of injury that costs a month.

How slow: slower than you think, and that is the point

Easy, conversational effort throughout — full sentences, not gasped fragments. For many runners that is 60–90 seconds per kilometre slower than the pace they think of as normal, and it will feel almost embarrassing for the first few weeks.

Running it too fast is costly in a specific way. A long run at moderate effort is hard enough to require real recovery but not hard enough to be a quality session — so it takes the sharpness out of the week's threshold work and gives nothing back. You end up with a week containing two mediocre hard days and no easy ones.

Hold effort constant, not pace: heat, hills and fatigue all mean the same effort produces a slower pace, and chasing the number on those days is how a long run turns into a hard one. A little drift late in the run is normal — you are tired. Fighting to keep the pace flat at the end is not the same as finishing strong.

What the long run is actually for

Three things, and they justify different treatments of it.

  • Aerobic development. Sustained low-intensity running drives capillary growth in working muscle, mitochondrial density, plasma volume, and a heart that moves more blood per beat.
  • Durability. Time on your feet conditions tendon, bone and connective tissue to tolerate repeated loading. This adapts far more slowly than your cardiovascular system does — which is exactly why distance has to be built patiently even when your lungs are fine with it.
  • Rehearsal. Beyond about 90 minutes, it is where you practise fuelling, pacing, kit and the business of continuing when it stops being fun. Not fitness — and the reason marathon runners keep long runs even in weeks the physiology does not demand one.

Note what is missing: it is not primarily a speed session, and it is not a weekly test of how far you can go. Treating it as either is the root of most long-run mistakes.

When to add quality — and when not to

An all-easy long run is correct for most runners most of the time. Quality inside it is a race-specific tool, and only makes sense once the easy version is comfortable and habitual.

  • Strides at the end. 4–6 × 20 seconds relaxed and quick. Cheap, low risk, a good counter to the shuffling gait long slow running encourages.
  • Fast finish. The last 10–15 minutes at a steady, controlled effort — harder than easy, well short of threshold. The best first step into quality.
  • Race-pace segments. For marathon runners in the last eight weeks: blocks such as 3 × 15 minutes at goal marathon pace inside an otherwise easy run. The most specific session in marathon training, and the most commonly over-cooked.

Three rules keep this from backfiring. A long run with quality in it is a hard day — count it as your hard session, or keep the week's other one far away from it. Do not add quality in the same week you extend the distance. And never turn the whole thing into a tempo run: the length is the stimulus, and running it fast means making it short.

Fuelling and rehearsal

Below about 75 minutes, water is generally enough for most people. Beyond roughly 90 minutes the long run becomes the place you practise fuelling — and the practice matters as much as the fuel, because the gut adapts to taking on carbohydrate while running and race day is a bad time to discover it has not.

The commonly cited guidance is 30–60 g of carbohydrate per hour for efforts over 90 minutes, taken at regular intervals rather than all at once, with higher intakes used by experienced endurance athletes who have trained their gut for it. Start at the bottom of that range and build. Use the product you plan to use on race day, at the intervals you plan to use it, in the same pockets or belt — and the same for shoes, socks, chafing, hat, and what happens in rain.

A worked example, including the week it goes wrong

A runner averaging 40 km across four days, targeting a half marathon in twelve weeks. Long run starts at 12 km, easy throughout.

  • Weeks 1–2: 12 km. Weeks 3–4: 14 km.
  • Week 5: cut back to 10 km, hold the weekly volume.
  • Weeks 6–7: 16 km. Week 8: 18 km, last 12 minutes at a steady effort.
  • Week 9: cut back to 12 km.
  • Week 10: 19 km, the longest of the block. Week 11: 14 km.
  • Week 12: 10 km easy, race weekend.

Now suppose weeks 6 and 7 disappear to a chest infection. The plan says 18 km with a steady finish. What you should actually run is around 11 km, all easy — roughly 75% of the 14 km you last completed — then rebuild, accepting that the peak long run this cycle will be nearer 16 km than 19 km. That race will be fine. The one you run on a body that skipped the rebuild will not be.

A plan that re-derives your long run from the weeks you ran

Runsy sets your long run from the volume you actually completed, and rebuilds the block when you miss a week instead of asking you to run a number you did not earn. iPhone, $12.99/mo after a 7-day free trial.

7-day free trial · then $12.99/mo · cancel anytime

Fair questions

How long should my long run be?

Roughly 25–30% of your recent weekly volume — the average of the last three or four weeks you actually completed. On 40km weeks that is about 10–13km. Runners training only three days a week will sit nearer 35%, and marathon runners exceed the range deliberately during peak weeks.

How slow should a long run be?

Easy and conversational throughout — often 60–90 seconds per kilometre slower than your normal training pace. Hold effort rather than pace, since heat, hills and fatigue all slow the same effort down. Running it at moderate effort is the most common long-run mistake, because it costs recovery without qualifying as a quality session.

Should the long run always be a set distance, or a set time?

Time is the better unit. A 30km target is a two-hour run for a fast runner and three and a half hours for a slower one, at very different cost. Most coaches cap the long run at 2:30–3:00 regardless of the distance that produces, and past three hours the injury cost tends to outrun the benefit.

What should I do if I miss a long run?

Miss one and simply resume where you left off — never run two back to back to make up the distance. After two to three weeks off, come back at 70–80% of your last completed long run. After four weeks or more, rebuild the base for three or four weeks first, restart at about half your previous longest, and re-derive the target from your current weekly volume rather than the abandoned plan.

Should I eat during a long run?

Below about 75 minutes, water is generally enough. Beyond roughly 90 minutes it is worth practising fuelling — commonly 30–60g of carbohydrate per hour, taken at regular intervals. The practice is the point as much as the fuel: the gut adapts to taking carbohydrate on the move, and race day is a poor place to find out yours has not.

Search

Search across every page on the site.