All Articles

Ask ten runners what the most important session of the week is and most will say the same thing: the long run. They're right. The long run is where you build the aerobic engine, teach your body to burn fat, toughen your legs against the pounding of race day, and, honestly, where you learn whether you can actually do this. Nearly every good running training plan is built around it.

But the long run is also where a lot of runners quietly go wrong. They run it too fast, they add distance too quickly, they skip fueling, or they treat it as a heroic weekend suffer-fest instead of the steady, patient work it's meant to be. This guide walks through what the long run actually does, how far and how fast yours should be, how to fuel it, and how to grow it without getting hurt.

What the Long Run Actually Does

The long run isn't magic. It's a specific set of adaptations, and understanding them tells you how to run it.

It builds your aerobic engine

Long, steady running is the single best way to grow your aerobic base. It pushes your body to build more capillaries, more mitochondria (the little engines inside your muscle cells), and a stronger heart that moves more blood per beat. This is the foundation everything else sits on. Speed work sharpens the engine, but the long run makes the engine bigger. If you want the deeper version of this, the piece on aerobic base training covers how easy mileage does the heavy lifting.

It teaches your body to burn fat

You store a lot of energy as fat and only a little as carbohydrate. On long, easy runs, your body gets better at tapping into that big fat reserve to fuel the effort, sparing your limited carb stores. That's a huge deal for the marathon, where running out of carbs is what people call "hitting the wall." The longer and more relaxed the run, the more you train this fat-burning machinery.

It builds mental durability

Some of the long run's value is simply between your ears. Spending two hours on your feet teaches you to settle into a rhythm and trust that you can cover the distance. On race day, that quiet confidence is worth a lot.

It toughens your legs

Tendons, ligaments, bones, and connective tissue adapt more slowly than your heart and lungs. The long run gradually builds that musculoskeletal resilience so the repeated impact of a race doesn't break you down. It's also why you have to build the long run up slowly. Push it too fast and the tissue that adapts slowest is the tissue that gets hurt.

The long run trains four things at once: your aerobic engine, your fat metabolism, your head, and your legs. Run it easy and build it slowly, and you get all four. Run it too hard or grow it too fast, and you trade the gains for fatigue and injury risk.

How Long Should the Long Run Be?

There are two ways to size a long run: by time and by percentage of your weekly volume. Both matter.

As a percentage of your week, the classic guideline is that the long run should be about 25 to 30 percent of your weekly mileage, and no single run should top roughly a third of your total week. If you run 30 miles a week, a 20-mile long run is 66 percent of your week. That's a run you'll need days to recover from, which eats into the rest of your training. Keep it proportional and the long run supports your week instead of wrecking it. The same logic explains why total mileage matters so much, which the guide on the training volume sweet spot digs into.

As time, most coaches cap the long run around 2.5 to 3 hours regardless of distance. Beyond about three hours, the extra fatigue and injury risk outweigh the benefit for most runners. A slower runner hitting 3 hours at 16 miles gets plenty of stimulus, and doesn't need to grind out 22 just to match a faster runner's mileage.

Here's a rough map by goal distance:

Goal raceLong run builds toAs timeShare of weekly volume
5K6 to 8 miles60 to 75 min25 to 30%
10K8 to 10 miles75 to 90 min25 to 30%
Half marathon10 to 14 miles90 to 120 min~30%
Marathon18 to 22 miles2.5 to 3 hr25 to 33%

Notice the marathon long run doesn't go all the way to 26 miles. You don't need to. The combination of a 20-mile long run plus a full training week's worth of accumulated fatigue prepares you for the full distance. Running the whole 26 in training just digs a recovery hole you can't climb out of before race day.

How Fast Should the Long Run Be?

Easy. Slower than you think. For most of the long run, you should be able to hold a full conversation, which usually lands 60 to 90 seconds per mile slower than goal marathon pace. Running long runs too fast is probably the most common mistake in all of distance training. It turns a run meant to build your aerobic base into a hard session that leaves you too tired to train well the rest of the week.

That said, there are two useful variations once you have a base:

  • Progression long runs. Start easy and gradually pick up the pace so the last few miles are at or near goal race pace. This teaches you to run strong when you're already tired, which is exactly what race day demands.
  • Marathon-pace long runs. In a marathon build, some long runs include a chunk in the middle or end at goal marathon pace (say, 8 to 12 miles of a 18-mile run). These are physically and mentally demanding, so you use them sparingly and always sandwich them with easy running.

If most of your runs feel hard, that's a sign your easy days aren't easy enough. The tempo run is where controlled hard effort belongs. The long run is mostly about time and patience.

Not sure how to pace or grow your long run?

Pheidi sizes your long run to your goal and your weekly volume, paces it to your fitness, and builds it up week by week so you don't overreach. It rebuilds your week when life moves your runs.

Build my plan

Fueling the Long Run

Once your long run passes about 75 minutes, plain water stops being enough. This is where you practice race fueling, because the long run is a dress rehearsal, not just a fitness session.

The target most runners land on is 30 to 60 grams of carbohydrate per hour, starting around the 45-minute mark rather than waiting until you're already low. Gels, chews, sports drinks, and real food all work. What matters is that you train your gut to handle fuel while running, because a stomach that isn't used to eating on the move will rebel on race day. Use the exact products and timing you plan to race with. The full breakdown lives in the race-day fueling guide, and everything in it should be tested on your long runs first.

Hydration follows the same logic: sip regularly rather than gulping, and on hot days or runs past two hours, add electrolytes. The long run is where you learn what your stomach tolerates, so there are no surprises at mile 20 of your race.

The Hansons "Cap at 16" Debate

You'll hear runners argue about whether the marathon long run should go past 16 miles. That argument mostly comes from the Hansons Marathon Method, which famously caps its longest run at 16 miles instead of the traditional 20.

The reasoning is "cumulative fatigue." Hansons keeps weekly mileage high and schedules the long run on already-tired legs, so those 16 miles late in a hard week feel like the last 16 miles of a marathon, not the first. They also hold the long run to roughly 25 to 30 percent of weekly mileage to avoid a single run you need days to recover from. For a runner logging 50 to 60 miles a week, that math works, and plenty of people have run great marathons off it.

The catch: it only works if the surrounding mileage is genuinely high. Cap your long run at 16 while running just 30 miles a week and you've removed the big aerobic stimulus without replacing it with anything. For most recreational runners on moderate mileage, a traditional long run building to 18 to 20 miles is still the safer bet. If the high-mileage philosophy appeals to you, the full breakdown is in the Hansons Marathon Method explainer.

How to Build the Long Run Safely

The long run is powerful, which is exactly why it hurts people when they rush it. Follow a few rules and you'll grow it without breaking down.

  • Add slowly. Grow the long run by 1 to 2 miles every week or two, not in big leaps. Your heart adapts fast; your tendons and bones don't.
  • Take cutback weeks. Every third or fourth week, drop the long run by 20 to 30 percent to let your body absorb the work. You get fitter during recovery, not during the run itself.
  • Keep it easy. If you can't finish the long run and still function the rest of the week, it was too hard or too long. Ease off.
  • Use walk breaks if you need them. There's nothing soft about walk breaks. The run-walk method lets beginners and returning runners cover long distances with far less injury risk, and many finish marathons faster because they don't blow up late.
  • Respect fatigue. A tired, niggle-filled body is telling you to cut the long run short. A shortened long run costs you almost nothing. An injury costs you weeks.

Done right, the long run compounds. Each week's run is a little longer or a little stronger, your body quietly adapts, and by race day the distance that once felt impossible feels like something you've already, in effect, done.

Key Takeaways

  • The long run builds four things at once: aerobic engine, fat metabolism, mental toughness, and leg durability.
  • Size it to your race and your week. Roughly 25 to 30 percent of weekly mileage, and cap around 2.5 to 3 hours for the marathon.
  • Run most of it easy, 60 to 90 seconds per mile slower than goal pace. Save progression and marathon-pace work for specific sessions.
  • Fuel anything over 75 minutes: 30 to 60 grams of carbs per hour, using your exact race-day plan.
  • The Hansons 16-mile cap works on high mileage. On moderate mileage, build the long run to 18 to 20 miles.
  • Grow it 1 to 2 miles at a time, take cutback weeks, and never trade a healthy body for one heroic run.