How Long Should Your Longest Run Be Before Your First Marathon? (About 18 to 20 Miles, or 3 to 3.5 Hours If You're Slow)

Most first-marathon plans peak with one run of 18 to 20 miles, about three weeks before race day. If you are slow, cap that run at about 3 to 3.5 hours instead, and stop there even if you haven't reached 20 miles.

A solitary figure walks along a foggy road winding through a forest at dawn.
Photo: Quang Nguyen Vinh / Pexels

You are partway through a plan. The long runs keep getting longer. At some point you start asking where it ends, and whether you have to run the whole 26.2 once to prove you can. You don't.

Here is the number, when to run it, and why the rule changes if you are going to be on the course for five or six hours.

How long should your longest run be before your first marathon?

For most first-time marathoners, the longest training run is 18 to 20 miles. That is the peak of nearly every mainstream beginner plan, and you usually run it only once or twice.

Hal Higdon's Novice 1 plan, one of the most widely used first-marathon schedules, builds the weekend long run from 6 miles in week one to a single 20-miler in week 15 of 18. Along the way you run 15, 16 and 18 miles once each. Higdon's reasoning is that the taper and race day carry you over the last 6.2 miles.

Other plans set the ceiling lower. The Hansons Marathon Method caps the long run at 16 miles and spreads the work across six running days, so you start the long run already tired. Coach Luke Humphrey, writing about the Hansons 16-miler, argues that the long run should be a sensible share of your weekly mileage, and that for most people a 20-miler is out of proportion to the rest of the week.

So the honest answer is a range. If your plan says 20, run 20. If it says 16 and your weekly mileage is high, 16 is not a shortcut. What matters is that the plan agrees with itself.

When should you do your longest run?

Do your longest run about three weeks before the marathon. That gives your legs time to recover and your training time to settle in before the start line.

In the Higdon novice plan the 20-miler comes in week 15, and a three-week taper follows it. Weekly mileage drops from about 40 to 29 and then 21 before race week. Most plans follow the same pattern.

Moving the peak run closer to the race does not make you fitter for it. A run that long takes days to recover from, and you want to show up rested, not still sore from the previous Saturday. If you are wondering what those last three weeks should look like, how long a marathon taper lasts covers it, including the part where you keep running.

Do you need to run 26.2 miles before your first marathon?

No. Most plans for first-time marathoners never have you run the full distance in training, and that is on purpose.

Running 26.2 in training means recovering from a marathon and then running another one a few weeks later. The fitness that gets you through the last 10K is built over months of weekly mileage, not in one rehearsal. The taper, race-day adrenaline and the crowd cover the gap. Everyone who has done this already knows the last six miles are hard. A training run that long doesn't make them less hard. It just leaves you more tired at the start.

Does the 20-mile rule apply if you are a slow runner?

Not really. The 20-mile convention fits runners who cover that distance in about three hours. If you are slower, a time limit works better than a distance.

Take a runner aiming for 3:30. At an easy training pace of around 9 minutes per mile, 20 miles takes about three hours. Now take someone heading for a 6-hour finish, with an easy pace closer to 14 or 15 minutes per mile. The same 20 miles takes nearly five hours. It's called the same session, but for the slower runner it is a much bigger one.

That is why many coaches cap the long run by time. RunFitCoach sets the ceiling at 22 miles or three hours, whichever comes first, and says a slower runner should not stay out for four and a half hours just to prove they can. The coach Jack Daniels is often cited for a 2.5 to 3 hour cap. In practice, about 3 to 3.5 hours is a reasonable peak for a slower first-timer. Stop there, even if your watch says 16 or 17 miles.

Not every coach agrees. Coach Laura Norris argues the three-hour rule is not absolute, and that some 5-hour-plus marathoners do need to go past it. Her point is that a slow long run is less intense, so there is less to recover from. She also notes the original cap came from coaches who mostly worked with much faster runners. If you are durable and your plan builds to it gradually, a 3.5-hour peak is defensible. Five hours of running on a Saturday, a few weeks out, is usually not.

What if your marathon will take five or six hours?

You will be out there longer on race day than in any training run, and that is normal. You can add time on your feet without one huge run.

Sifuentes Coaching suggests two ways for runners who expect to need four hours or more. One is to add walking before and after a capped long run. The other is a long run weekend: two fairly long runs on back-to-back days, so you practise running on tired legs without the cost of one enormous session.

Walk breaks during the long run count as training, not cheating. Plenty of people run the marathon itself with planned walk intervals. If that is your race plan, use it in your long runs too, so race day feels familiar.

How fast should your longest run be?

Slowly. Run your longest run at an easy, conversational pace, slower than you plan to race.

The point is to spend the time, not to set a pace. Running it too fast is the most common way a peak long run goes wrong. People finish wrecked, take a week to feel normal again, and lose the training they needed most. If you are not sure what easy looks like for you, what pace a beginner should actually run at is a good place to start. If the long runs feel harder every week, how to run longer without getting tired explains why slowing down usually comes before adding distance.

Use the long run to practise race day. Wear the shoes and clothes you will race in. Eat what you plan to eat. Start at the time of day the race starts. Nothing new on race day is old advice because it is right.

What if you missed your longest run?

If you missed your peak long run, don't cram it into the taper. A run of 16 or 18 miles a few weeks out is enough to start a first marathon, as long as the weeks before it were consistent.

A peak long run done ten days before the race costs more than it gives. You will start more tired, not more ready. If you are close to race day and the long run didn't happen, let it go and follow the taper as written. If you are injured or something hurts, ask a clinician, not your training plan.

What gets most people to the start line is the dull part: months of showing up week after week. The single big run matters less than the habit underneath it. Joggy's AI training plans are built on that idea, with streaks to track the weeks you showed up, which is a fair measure of whether the plan is working.

// The short version

For a first marathon, your longest training run is usually 18 to 20 miles, done once, about three weeks before race day. You do not need to run 26.2 miles beforehand. If you are slow enough that 20 miles would take you more than about 3 to 3.5 hours, cap the run by time instead and stop when the time is up.

Sources

joggy gives general fitness coaching, not medical advice. Talk to a physician before starting a new exercise program, and get persistent pain checked by a professional.
// joggy says

Reading about running counts as a rest day. Running counts more. I'm joggy, the AI running coach in your pocket: a plan that bends around your week, a voice on every run, and zero judgment when you walk. Free on iPhone and Android, and every new runner gets 14 days of joggy Club.

Run with joggy