Ultramarathon Pacing: The Cost You Pay Too Early

Three, two, one. Go. Months of work come down to this. You feel good. Really good. The legs are fresh, the breathing is easy, and the pack is moving at a pace that feels simple to follow.

That is where a lot of pacing mistakes begin. Not in a blow-up. In a pace that feels so comfortable early that you stop questioning it.

The signs are familiar once the race starts to turn. Breathing gets loud too soon. You stop eating as regularly as you should. Descents leave more in the legs than they should. A climb you should still be managing already turns into work. In training, the same mistake is smaller but not different: a run that felt easy leaves more fatigue than it should.

Everyone knows the rule: do not start too fast. The hard part is that in ultra, too fast usually does not feel stupid. It feels fine. That is why pacing matters. It decides how quickly strain builds, how long fueling stays manageable, how much damage the terrain leaves behind, and how much of your fitness is still available later in the day.

Who this is for

This article is for you if:

• you are preparing for an ultra or mountain race and want a clearer way to think about pacing than intuition alone
• you have had a race or long run fall apart even though the opening pace felt completely under control
• you want to understand why climbs, descents, heat, and fueling change what a sustainable pace really is
• you suspect some of your easy runs, recovery runs, or taper runs are drifting out of their intended purpose
• you keep making pacing decisions that feel harmless early and become hard to absorb later

This article is not for you if:

• you want one pacing formula that ignores terrain, heat, descents, fueling, and fatigue
• you want one number from the watch to make every pacing decision for you

Why this matters

Pacing mistakes rarely stay where they were made. A climb run a little too hard can return as breathing that refuses to settle. An early descent taken too freely can show up as quads that no longer handle the terrain cleanly. A pace that is only slightly too high can appear not as a split problem, but as food that stops sounding good, aid stations that get messy, or a race that turns into damage control before it needed to.

In training it works the same way. An easy run paced a little too honestly can return the next day as dull legs. A long run that never felt hard can still make the rest of the week heavier than it should be. A taper run that was supposed to keep you loose can take away freshness instead. Pacing is not just about speed. It is about what kind of strain you create, how much room you leave for recovery, and whether the rest of the week is still usable. Pacing is not only about race day. It is also part of how runners protect consistency over months and years.

The first pacing mistake happens before it feels like one

The first pacing mistake usually happens while nothing looks wrong. Breathing is easy. The legs feel light. Other runners are moving at a pace you could hold right now. That is exactly when people start spending more than the day can afford.

Most runners judge pace by one question: can I do this right now? Early in the race, the answer is often yes. The better question is whether this pace still makes sense after a few hours of climbing, descending, heating up, and trying to keep food going down.

That is the part freshness hides. The pace can feel fine in the moment while carbohydrate demand, heat load, downhill damage, fueling tolerance, movement quality, and decision-making are already starting to shift.

That is why early pacing mistakes are so easy to make. They do not feel reckless. They feel measured. You only find out hours later what they have taken away.

The most important rule: do not start too fast

Everyone has heard it. The reason it still matters is that it remains true in a deeper way than most pacing advice usually explains.

Starting too fast does more than damage your second-half splits. It changes the operating conditions of the whole day. Carbohydrate use rises sooner. Heat load rises sooner. Breathing becomes harder to keep settled. Fueling often becomes more fragile. If the early course includes steep descents, muscular damage also starts accumulating sooner, especially in the quads. None of this needs to announce itself immediately. A runner can still feel excellent while the race is already becoming harder to manage.

The carbohydrate part matters because a small rise in intensity does not just make the race a little harder. It also shifts fuel use toward the faster, more limited source. Fat supports long aerobic work in the background. Carbohydrate covers the sharper demands. The more often you ask for those sharper demands early, the more pressure you put on the fuel that the later sections still need. That is why pacing and an ultramarathon fueling strategy are not separate problems.

That is why "do not start too fast" should not be treated as cautious folk wisdom. It is one of the simplest physiological rules in ultra. Early overpacing narrows the options available in the second half. It makes a runner more dependent on things going perfectly at exactly the stage of the race when things usually become less tidy, not more.

In mountain races, this also means that a pace which looks modest on paper can still be too demanding if it comes from running climbs you should have hiked, descending harder than your legs can absorb, or trying to match someone else's effort instead of your own sustainable one.

What the body pays for

It helps to think less in terms of speed and more in terms of load. You are not only choosing how fast to move. You are choosing how much stress the body has to absorb to keep that pace going.

Part of that load is carbohydrate demand. Ultra is mostly aerobic, yes, but climbs, surges, and slightly overexcited opening miles still push you toward a higher-intensity fuel mix. Fat is the deep reserve in the background. Carbohydrate is the more limited fuel that helps you deal with the sharper parts of the day cleanly. Use too much of it too early and a pace that felt ordinary in hour two can feel very different in hour eight.

Another part is mechanical. Downhill running often feels kind because breathing settles and the watch suddenly looks friendly again. The quads do not experience it that way. They are slowing you down, absorbing impact, and trying to keep you stable on every step. That eccentric load hangs around. You may not notice much on the first descent. Later you notice it everywhere. Climbs feel steeper. Footwork gets messier. You just stop moving as well as you were before.

This is what makes descents so deceptive. The muscles are not mainly pushing you forward. They are resisting impact and controlling collapse. That kind of loaded work, where the legs have to slow and control the body on every landing, can damage muscle more than it seems like it should in the moment. Breathing may feel easy while the legs are getting worse underneath you.

Then there is heat and circulation. The harder the race becomes internally, the more the body has to juggle movement, cooling, and fueling at the same time. Heart rate drifts. The gut gets less cooperative. Food or fluid that would have gone down easily earlier starts feeling like one more problem to solve. This is why pacing and fueling are tied so closely together. A pace that is slightly too ambitious does not just affect the legs. It can also take away the conditions that make eating and drinking manageable.

And then there is perception. This is the part runners usually know best from experience. The pace drops a little. The heart rate does not always look alarming. The effort still keeps rising. Research on mountain ultras sees the same thing: speed can fall, heart rate can flatten or drift, and perceived effort can keep climbing anyway. Sustainable pacing has to be learned in the body, not only read from the watch.

The first signs of overpacing

Most runners miss overpacing because they are waiting for a clear blow-up. That is usually not how it starts. It starts with small signs that strain is accumulating faster than it should.

One of the first places it shows up is breathing. On a climb that was supposed to stay controlled, you stop being able to speak in full sentences. The pace still looks reasonable. The climb is still runnable. But the effort is already too high for that point in the day.

Another early sign is fueling. You put off one feed because the terrain is steep, technical, or just hard to eat on. Then another because eating suddenly sounds less appealing than it did an hour ago. That matters. When the effort is too high, fueling often gets harder before the legs fully crack.

Then there is movement quality. Descents still look fine on paper, but your feet stop landing as cleanly. You clip a rock you would usually miss. You start working harder just to stay tidy. That is often an early sign that the race is demanding more than the watch suggests.

Sometimes the signal is decision-making. Aid stations start taking longer. You stand there longer than you need to. Small choices start to pile up. That is not only a logistics problem. It is often part of the pacing problem too.

In training, the signs are usually simpler. An easy run leaves a mark it should not have left. A long run that felt fine makes the rest of the week heavier than it should be. A recovery run gets in the way of recovery. That is overpacing too, just without the noise of race day around it.

If a few of these signs show up early, do not wait for confirmation. Back off a little. It is much easier to correct there than later in the race.

Pacing is strain management, not speed control

On flat road races, pace can sometimes serve as a clean anchor. In ultras, especially mountainous ones, it usually cannot. Terrain changes too much. Surface changes too much. Temperature changes too much. What your legs can still absorb changes too much.

A better way to think about pacing is this: you are managing how quickly strain accumulates. Speed is one output of that management, but not the whole thing.

That happens on more than one level at once. There is the next few steps, where you decide how hard to push this climb or how loose to let the descent get. There is the next section, where you manage the stretch to the next checkpoint. Then there is the whole day, where you decide when to eat, when to cool, when to keep ambition in check, and when the race has earned a little more pace.

In mountain ultras, pacing the whole race as one number is usually less useful than pacing the section you are in. The next climb, the next descent, the next checkpoint.

That is one reason even pacing in the marathon sense is not the right model for mountain ultras. The more useful equivalent is closer to even effort. Even the best runners on these courses usually run positive splits, meaning the second half is slower than the first. A modest slowdown is normal. In many mountain races, something like a 10 to 20 percent fade in the second half is not unusual. The real question is whether the second half becomes merely slower or whether it turns into a collapse. Research on mountain ultramarathons consistently shows that faster finishers tend to have lower variability of speed, smaller late-race slowdown, and less aid-station dead time. They are not winning because they attack the opening half harder. They are winning because they preserve more of themselves into the later half.

On flatter, faster ultras, that can move a little closer to even pace or a mild negative split. In the mountains, the cleaner anchor is usually even effort with speed changing underneath it. Good pacing is therefore not about looking restrained for its own sake. It is about avoiding volatility you did not need. The course will create enough of its own.

The shape of good pacing

It usually looks more ordinary than runners expect. Good pacing early in the race often just looks controlled. It can even feel a little too patient. On the results sheet, it shows up as smaller collapse rather than spectacular opening speed.

In mountain ultra data, winners and faster finishers are commonly characterized by three things: smaller variation in speed, smaller deterioration across the race, and less wasted stop time. That matters because it shifts attention away from the usual amateur fantasy of "banking time" and toward a more useful standard. The race is not asking how bold you can look in the opening hour. It is asking how much of your pace, judgment, and movement quality you can still carry several hours later.

Aid stations belong in this conversation too. Pacing is not only how fast you move between checkpoints. It is also how much unnecessary stillness you allow to gather around you. For many mid-pack runners, stop time is one of the easiest performance leaks in the whole race. Five extra minutes at one aid station feels harmless. Repeated across the day, it becomes part of your pacing profile whether you think of it that way or not.

This matters because stop time is rarely neutral. Long, indecisive stops usually arrive together with rising fatigue, fuzzier thinking, and a race that is already becoming harder to manage. That is one reason better pacing often looks smoother around checkpoints too. The runner arrives with a clearer plan, spends less time negotiating with the buffet, and gets moving again before standing still starts turning into a habit.

Good pacing usually shows up in simpler ways. Fewer unnecessary changes of pace. Less reacting to every climb or descent. Fewer pointless stops. A steadier relationship between effort and output. Not perfect steadiness. Just less waste.

When walking is the better pacing choice

This deserves to be said plainly, because many runners still carry a road-running idea of what counts as "real running" into the mountains. Call it power hiking if you want. It is still walking, and on steep climbs it is often the smarter choice.

The reason is simple. As gradient rises, the energy requirement of trying to keep running rises very quickly too. The exact switch point is not the same for everyone. On gentler uphill grades, many runners can still run economically. In the middle zone, stronger or fresher runners may still run while newer runners are often better off hiking. Once the climb gets properly steep, and especially once fatigue starts building, walking often becomes the more sustainable option. If you want to estimate that switch more systematically, the run-walk calculator gives a useful starting point.

You may still be able to run. That is not the same as it being the right decision. If the gain in speed is tiny but breathing jumps, fueling gets harder, and the legs start working above what the whole day can absorb, then running the climb is usually poor pacing dressed up as determination.

This is why experienced mountain runners often hike earlier than newer runners expect. They are not giving away the race. They are preserving the conditions that let them keep racing. A steadier hike can keep breathing lower, preserve carbohydrate a little better, make eating more manageable, and reduce the damage that has to be managed in the final hours. As fatigue builds, that hiking threshold usually comes down. A climb you could still run early may become a clear hiking section later. Late in a long race, some runners are already better off hiking grades they would have run comfortably in the first third.

A useful rule of thumb is this: if running changes more in your breathing than in your actual progress, walking is probably the smarter move. If you cannot speak in full sentences anymore, or if the climb pushes you out of that steady, sustainable effort zone, that is another strong cue to hike. The same is true if running starts to turn into short, choppy steps and that strained feeling where you are working hard without really going anywhere. In practice, that often means switching before the climb forces the decision for you.

It also helps to stop calling it "just walking." In ultra, uphill hiking is part of movement strategy. It belongs in the plan in the same way that disciplined descending or efficient aid stations do. The runner who starts hiking at the right moment is often still racing well much later. The runner who keeps proving they can run every climb is often the one who absorbs the penalty all at once.

Where mountains distort pacing

Descents

Descents are one of the biggest pacing traps in ultra because they often feel generous while they are still leaving damage behind. Metabolically, downhill running can feel easier than climbing. Mechanically, it can be brutal. The quads are doing a lot of impact-absorbing and control work here, and that load accumulates early. It keeps showing up, not only on the next descent but also on the next climb, the next runnable stretch, and eventually in the simple quality of each step. That is the same basic stress-and-absorption problem described in Stress, Strain, and Recovery.

This is why "free speed" on descents is often an illusion. The downhill that feels smooth in hour two can still be sitting in your legs in hour nine. Strong pacing on descents is less about courage than about restraint. A runner who handles the first real descents with discipline is often protecting the whole second half of the race.

That is also why the metabolic picture can be misleading here. A descent may look easy in theory and still be damaging in practice, because footing, impact, and muscle damage limit how much of that apparent saving you can turn into useful pace.

Heat

Heat makes a familiar pace harder to sustain before that shows up clearly on the watch. That is why runners so often misread it at first. The pace can still look fine while the body is already working harder to support it.

Cooling now competes harder for blood flow. Heart rate drifts. Fueling tolerance can narrow. The same pace that belonged to a cool morning can stop being sustainable once the day becomes hot enough. Faster runners can get caught here especially hard because they spend more of the race exposed to the hottest window while already working close to their ceiling. On a hot day, the smart move is to adjust early, not to keep forcing the pace you planned.

The reason pace can look normal for a while is that the body can hide part of the problem before it has to slow you down. More blood has to go toward cooling. The cardiovascular system works harder to support the same output. The gut often gets less help. So the external pace may hold for a bit, but the internal strain is already climbing.

One of the harder pacing skills in hot races is accepting that the day has already changed before the watch makes that obvious.

Altitude

Altitude asks for the same kind of humility. The pace that works near sea level can stop making sense once lower oxygen pressure makes it harder to take up and use oxygen well, especially when steep climbs start asking more from the same apparent effort.

The practical mistake is waiting for the crisis before adjusting. On hot days or high courses, the smarter move is usually to start a little more conservatively and leave yourself more room than you think you need.

Technical terrain

Technical terrain often gets mistaken for "just slower terrain," but the real issue is not only speed. It is precision. Foot placement asks more. Slowing and controlling each landing asks more. Attention asks more. The load rises even when the pace number falls.

That matters for pacing because a runner can believe they are being conservative simply because they are moving slowly, when in reality the terrain is extracting a high mechanical and cognitive price. Not all slow running is low-load running.

Where the watch helps, and where it doesn't

Heart rate can be useful. It is just not useful in the same way all day.

Early in a race, heart rate can still be a useful check, but not a perfect one. Adrenaline, caffeine, nerves, and early terrain can all push it around, especially in the first minutes. That is why it works better as a ceiling than as something to chase. If the number is already high and your breathing says the same thing, pay attention. If the number looks odd but your effort still feels controlled, do not hand the whole decision over to the watch. Later, heart rate gets harder to read. Heat, dehydration, cardiovascular drift, fatigue, and decoupling reduce how cleanly it reflects workload. In some races, speed and heart rate both fall while perceived effort keeps rising.

That is why heart rate becomes less reliable as a pacing anchor late in long mountain events. It still has value. It can hint at heat stress or a hydration problem. It can warn you that something is off. It just stops being a complete guide.

Grade-adjusted pace can help too, especially on cleaner climbs and rolling terrain, because it gives a more honest picture of the work behind an uphill pace. It still has limits. Once terrain gets very technical, footing gets messy, or the legs are already carrying a lot of damage, no adjusted pace number captures the whole problem. For structured route checks, the GAP calculator can help separate terrain effect from plain overpacing.

Average pace can still look fine while one section is already demanding too much. That is one reason checkpoint-to-checkpoint pacing is often more useful than whole-race pace in the mountains.

Late in the race, perceived effort often tells you more than heart rate or pace. That is usually the stage where checkpoint-to-checkpoint times, terrain context, and the simpler question of whether the effort still feels sustainable in the body you currently have start mattering more than the watch.

Training pacing: where runners often get this wrong

A lot of pacing mistakes happen on days that were never supposed to be hard.

Long runs

A long run can become the wrong session long before it becomes an obvious struggle. It starts feeling smooth, so you stop watching it closely. You run the climbs a little stronger than planned. You push the flatter sections because the legs still feel good. By the end, what was supposed to be durable aerobic work has turned into a session with more training stress than it needed.

That matters because long runs are not only about time on feet. They are also where you practice the relationship between pace, terrain, fueling, and fatigue that you will depend on in racing. If every long run gets a little too honest just because you felt good, you may be rehearsing exactly the mistake that undermines the race.

Long runs are also where race logistics get rehearsed properly. Eating on schedule, drinking before thirst turns messy, refilling flasks, changing layers, getting poles in and out, and leaving stops before they become social breaks all belong here too. A lot of race-day pacing gets lost not on the trail itself, but in the small negotiations that were never practiced in training.

Easy runs

An easy run only does its job if it stays light enough to support the rest of training. Many runners pace easy days by mood. The legs feel good, so the pace creeps up a little. A small hill comes, and they keep pressing instead of backing off. None of it feels like a mistake. Over time that turns easy running into a grey zone where the session is no longer hard enough to build something specific and no longer easy enough to preserve freshness.

That kind of pacing error rarely feels like a mistake. It usually feels normal. That is why it lasts.

Recovery runs

Recovery runs fail when they add load that recovery was supposed to avoid. A recovery run can feel fine and still be paced badly if it leaves the legs heavier, the nervous system flatter, or the next key session slightly dulled.

Many runners pace recovery runs by restlessness or reassurance. They want to loosen up. They want the watch to show something decent. They do not want to be slow. None of those is a useful standard. Ask a simpler question instead: did this run leave recovery intact?

Taper weeks

Taper pacing often gets spoiled by the urge to feel sharp. Runners start adding a little more effort than the run needs. They let short runs creep. They chase a sensation of readiness with pace that the body did not need.

Taper runs are there to keep you moving without getting in the way of freshness. A taper run that becomes moderately demanding because you wanted reassurance still takes something from race week. It just hides behind lower volume.

A practical pacing framework

You do not need a clever pacing philosophy. You need a system that limits early decisions made under freshness, adrenaline, and group pressure.

1. Make the first hour feel almost too easy

If it already feels like racing, you are probably going too hard. Let other runners go. Keep breathing under control. Preserve the race for the sections where restraint starts to matter.

2. Think checkpoint to checkpoint

Do not pace a mountain ultra by average pace. Pace the section in front of you. Know what the next climb, descent, and checkpoint require, not what the whole-race average says.

3. Cap the climbs early

The first big climbs are not a fitness test. If running makes breathing spike but barely changes progress, hike. If you lose the ability to speak in full sentences, hike.

4. Protect the descents before you need them

Run the first real descents with discipline. If you chase speed there, you are often moving the damage bill into the second half of the race.

5. Use fueling and heat as pacing signals

If eating starts getting hard unusually early, or heat starts pushing breathing and heart rate up, do not just fight through it. First ask whether the pace is too high for the day you are actually in.

6. Use heart rate early if it helps, but downgrade it later

Early, heart rate can help as a ceiling. All day, terrain and breathing matter. Later, perceived effort and checkpoint times usually tell the truth better than the watch does.

7. Keep easy days light and taper days boring

If an easy day leaves a mark, it was too fast. If a taper run starts feeling like a little test, you are probably missing the point.

8. Remove decisions before fatigue makes them worse

Know in advance what you will eat, drink, cool with, and how long you want to spend at major stops. Less improvisation usually means better pacing.

The most common mistakes

FAQ

References

• Abbiss CR, Laursen PB. Describing and understanding pacing strategies during athletic competition. Sports Medicine. 2008.
• Hoffman MD. Pacing by winners of a 161-km mountain ultramarathon. International Journal of Sports Physiology and Performance. 2014.
• Kerherve HA et al. Pacing strategy and change in body composition during a mountain ultramarathon. Journal of Sports Sciences. 2015.
• Balducci P et al. Performance factors in a mountain ultramarathon. International Journal of Sports Medicine. 2017.
• Martinez-Navarro I et al. Pacing and performance in a mountain ultramarathon. Journal of Human Kinetics. 2021.
• Fornasiero A et al. Physiological intensity profile of a mountain ultramarathon. Journal of Sports Sciences. 2017.
• Minetti AE et al. Energy cost of walking and running at extreme uphill and downhill slopes. Journal of Applied Physiology. 2002.
• Giovanelli N et al. Uphill walking versus running economy on steep gradients. Journal of Applied Physiology. 2016.
• Millet GY et al. Alterations of neuromuscular function after an extreme mountain ultra-marathon. PLoS One. 2011.
• Vernillo G et al. Biomechanics and physiology of uphill and downhill running. Sports Medicine. 2017.
• Coyle EF, Gonzalez-Alonso J. Cardiovascular drift during prolonged exercise. Medicine & Science in Sports & Exercise. 2001.
• Parise CA, Hoffman MD. Influence of temperature and performance level on pacing in a 161-km ultramarathon. International Journal of Sports Physiology and Performance. 2011.
• Jeukendrup AE. A step towards personalised sports nutrition: carbohydrate intake during exercise. Sports Medicine. 2014.
• Volek JS et al. Metabolic characteristics of keto-adapted ultra-endurance runners. Metabolism. 2016.