Long run meaning: how long, how slow, and how to prepare

The long run meaning, in one line: it's the longest run of your week, run at an easy effort, to build endurance. Not a race, not a time trial, not the day you find out how fit you are. Just the run that's longer than the others.

That's simple enough that people overcomplicate it. They run it too fast, grow it too quickly, put it the day after heavy squats, and skip breakfast because "it's only training". This post covers what counts as a long run, how long and how slow it should be, what a "block" long run means, and how to prepare for one, whether you plan your own week or follow a running plan that adapts every week.

Long run meaning: what counts as a long run?

A long run is defined by your week, not by a number. If your usual runs are 30 minutes, a 60-minute run is a long run. If you run 10 miles most days, it isn't.

Common coaching conventions:

• ›It's the longest run of the week, usually clearly longer than any other run.
• ›It's easy. Same effort as an easy run, just for longer.
• ›It happens once a week, often at the weekend when there's time.
• ›It grows through a training block, then comes down before a race.

Almost every distance plan is built around it, from a 10K build to a half marathon schedule with strength. The long run is the endurance session. Everything else in the week, including the hard runs covered in this breakdown of fartlek, tempo and intervals, sits around it.

Why the long run matters

The long run builds what races beyond 10K mostly test: the ability to keep going. Time on your feet teaches your legs, your fueling and your head what the back half of a race feels like.

There's evidence for its place in marathon training specifically. A meta-analysis with meta-regression of 85 studies of marathon runners found that several training behaviors, including the distance of the longest run and the number of runs of 32 km or more in the build, were associated with faster marathon times (Doherty et al., 2020). Associations, not proof, but they line up with how almost every marathon plan is built.

How long should a long run be?

It depends on your goal and on where you're starting. These are the ranges common plans peak at, not where you start.

How to build it:

• ›Start from your current longest run, not from where you'd like to be.
• ›Add about a mile, or around 10 minutes, most weeks.
• ›Cut it back every third or fourth week so you absorb the work.
• ›A common rule of thumb: keep the long run to somewhere between a quarter and a third of your weekly running, so the rest of the week still carries volume.

The famous "10% rule" for weekly increases has less evidence behind it than its fame suggests. In a randomized trial of 532 novice runners, a graded 13-week program based on the 10% rule didn't reduce running-related injuries compared with a standard 8-week program (Buist et al., 2008). In a separate cohort of 874 novice runners, those who increased their weekly distance by more than 30% over two weeks seemed more vulnerable to certain distance-related injuries than those who increased by less than 10%, a trend that fell just short of statistical significance in a study its authors called exploratory (Nielsen et al., 2014). The practical takeaway: grow gradually, and don't mistake any single percentage for a promise. Anything that hurts more as you run is a reason to stop and see a professional.

How slow should a long run be?

Easy. Conversational the whole way, for most long runs. If you're not sure what is considered an easy run, the short version: you can talk in full sentences, it feels about 3–4 out of 10, and your heart rate sits in zone 2.

That's the same intensity as your other easy runs, so zone-based training keeps you honest. Two things make long runs different:

• ›Heart rate drifts. During prolonged exercise, stroke volume (the blood your heart pumps per beat) declines progressively after the first 10–20 minutes while heart rate climbs (Coyle and González-Alonso, 2001). If you're running by heart rate, expect to slow down later in the run to stay easy.
• ›Fatigue builds late. The last third always feels harder than the first. That's the point of the session, not a sign you're failing it.

Running the long run too fast is the most common mistake. You finish the run, but you're wrecked for days, and the next week's hard session suffers. That's a bad trade. Like your other easy runs, the long run is supposed to be repeatable.

It's also the biggest single piece of the mostly-easy approach behind 80/20 running, as Matt Fitzgerald explained it: most of your running easy, a small slice hard. Across descriptive studies of competitive endurance athletes, about 80% of sessions were done at low intensity (Seiler, 2010). The long run is a big part of that 80.

Block long run meaning

A block long run is a long run with one or more sections at a faster, specified pace, usually goal race pace, inside an otherwise easy run. You'll see it in half marathon and marathon plans as something like:

• ›14 miles: 4 easy, 3 × 2 miles at marathon pace with 1 mile easy between, 2 easy
• ›12 miles: 8 easy, last 4 at goal half marathon pace
• ›90 minutes: 60 easy, 30 steady, finishing at goal pace

The "blocks" are the race-pace sections. They teach you what goal pace feels like on tired legs and give you a rehearsal for race-day fueling at pace.

Rules for block long runs:

• ›Later in the build only. Easy long runs come first. Blocks come once the distance is established.
• ›Not every week. Every other week, or every third, is common. The rest stay easy.
• ›They count as a hard day. A long run with 6 miles at marathon pace is a quality session, so don't put an interval workout the day before or after. Our guide to interval training for runners covers how those sessions fit around it.
• ›Goal pace has to be honest. Base it on a recent race, not a wish. How to improve your running pace covers picking a number you can actually hold.

How to prepare for a long run

Fuel before and during

Eat a familiar, carb-forward meal or snack beforehand, and for runs well over an hour, take carbohydrate during. Burke et al. (2011) describe 30 to 60 g of carbohydrate per hour as an appropriate target for longer events, and note that events over 2.5 hours may benefit from up to 90 g per hour. Start at the low end on long runs and build up. The long run is where you train your gut, not race day.

Schedule it away from heavy legs

If you lift, the long run and leg day are the scheduling fight that never ends. Keep heavy lower-body work at least two days before the long run, and nothing heavy the day after. Count the long run as one of the hard days of your week, even though it's slow.

Plan the route and recover

Pick a loop where you can get water, wear shoes you've already run in, and run hot days by effort.

Eat something with carbs and protein afterward, keep the next day easy or off, and expect to feel it a bit. If you're still flat two days later, the run was too long, too fast, or both.

Long runs for hybrid athletes

If you lift too, you might not need a marathon-style long run. For Hyrox or general fitness, 60–90 minutes easy once a week builds plenty of aerobic base, and the bigger the long run, the more it costs your lifting. Keep faster work separate, too: short sprints and strides belong on fresher days. A guide to sprint training for beginners would put them on an easy day midweek, not at the end of 18 miles.

Common long run mistakes

• ›Running it at tempo pace. Speed lives elsewhere in the week.
• ›Growing it too fast. Patience here is the whole plan.
• ›Skipping fuel. A two-hour run on coffee alone is a fuel problem with a schedule.
• ›Making every long run a block long run. Most should be plain easy running.

How exrsz handles the long run

exrsz builds a periodized plan from your goal, schedule, level and equipment, growing the long run gradually and adding goal-pace blocks later in the build when your goal calls for them. It balances running and lifting in one plan so leg day doesn't land before the long run, adapts each week to how you actually trained, and reshuffles missed sessions instead of stacking them.

FAQ

What is the meaning of a long run?

A long run is the longest run of your training week, usually run at an easy, conversational effort. Its job is to build endurance, and it's the backbone of most half marathon and marathon plans.

What does block long run mean?

A block long run is a long run that includes one or more sections at a faster set pace, usually goal race pace, inside an otherwise easy run. Example: 12 miles with the last 4 at half marathon pace.

How long should my long run be?

Start from your current longest run and build gradually. Common peaks are 10–12 miles for a half marathon and 18–20 miles for a marathon, with a cutback week every third or fourth week.

How fast should a long run be?

Easy, at a pace where you can talk in full sentences, in heart rate zone 2 for most of it. Only block long runs, later in a build, include faster sections.

How much should I eat during a long run?

For runs well over an hour, a common target is 30 to 60 g of carbohydrate per hour, with up to 90 g per hour for efforts over about 2.5 hours (Burke et al., 2011). Build up gradually in training.