Summit Line

⏵ Pacing guide · Free

How to Pace an Ultramarathon

Effort, power-hiking, and grade-adjusted pace. The short version: pace by effort, not by the clock. Run the first few hours so easy it feels almost wrong, power-hike the steep climbs before your heart rate spikes, protect your quads on the descents, and keep some margin against the cutoffs. Do that and the back half of the race belongs to you, not the medical tent.

⏵ The short answer

How to pace an ultramarathon

Pace by how it feels, not by minutes-per-mile. Hold an easy, conversational effort (around RPE 3 out of 10) for the first hour or two, so it feels almost too slow. Power-hike the climbs once running would drop you below roughly 18 to 19 min/mile (about 4 to 15 percent grade and steeper), run the gentle and flat sections, and run the early descents controlled to spare your quads. Aim for even effort the whole way, which usually reads as an even-to-slightly-positive split, and build your plan backward from the aid-station cutoffs with a buffer. Most ultra DNFs come from going out too fast, so the first few hours really do decide the day.

Pace by effort, not by pace or heart rate

On a road marathon you can chase a pace number. In an ultra the grade and terrain make minutes-per-mile meaningless, so the one metric that survives all day is effort.

Why effort wins over pace and heart rate

Minutes-per-mile is the worst of the three on trail. The same effort can read as 9:00 on a flat road and 28:00 on a steep, rocky climb, so a pace target either pushes you to cook yourself on the hills or makes the flats feel like failure. Heart rate is better, but it drifts upward over the hours (cardiac drift), it lags on short climbs, and it spikes in heat, so a fixed heart-rate cap slowly lies to you as the day wears on.

Rate of perceived exertion (RPE), how hard it honestly feels on a 1 to 10 scale, is what most experienced ultrarunners actually pace by. And the plan is simple. Hold an easy, conversational effort (about RPE 3 to 4) for the first several hours, then let the terrain and your body set the pace. Keep the watch and the heart rate in view as cross-checks, but let effort be the boss.

Start so easy it feels wrong

The biggest pacing decision you make all day is how you run the first hour or two. Treat it as a long warm-up at around RPE 3, an effort you are dead sure you could hold all day. It should feel almost embarrassingly slow. People will pass you. Let them.

And this is not just trail folklore. Studies of long mountain ultras find that more even pacing lines up with faster finishes, and that the fastest runners start at lower relative intensities than the slower ones. A hot start does damage you cannot take back. It raises your core temperature, it shuts down your gut so you absorb fewer carbs, and it pre-fatigues the legs, and all of that piles up for the rest of the day.

When to power-hike instead of run

Power-hiking is not quitting. It is the efficient gear for steep ground. The rule of thumb from ultra coaches: once a climb would force you below roughly 18 to 19 min/mile, a strong hike costs you less energy for nearly the same speed.

Run-versus-hike decision by grade
GradeMoveWhy
0 to 4%RunEasy enough that running is still cheap. Settle in at a conversational effort and let it roll.
4 to 8%Run early, hike lateYou can run this while you are fresh. But as the day wears on your running pace sinks toward hiking speed anyway, so the run stops being worth it.
8 to 15%Power-hike (mostly)For most people, once you are grinding at roughly 18 to 19 min/mile or slower, a strong power-hike costs you less and gives you almost the same speed.
15%+Power-hikeSteep enough that just about everyone hikes here. Hands on the thighs, keep the cadence quick, and drive.

The thresholds are guidelines, not laws. A fitter or fresher runner holds the run a little steeper, and everyone hikes earlier as the fatigue builds. The real test is effort. If running the climb spikes your breathing and heart rate without buying you much speed, hike it. Make the switch before the spike, drive with your hands on your thighs, keep your cadence quick, and keep your eyes up the trail. Want the honest effort behind a given climb? Our grade-adjusted pace calculator translates a hill pace into its flat-effort equivalent so you can see when running stops being worth it.

Grade-adjusted pace, and why trail pace is so much slower

Grade-adjusted pace (GAP) is the flat-ground pace that would cost you the same effort as your actual pace on a hill. It is the bridge between your road fitness and what the trail is actually going to give you.

What the same effort looks like across grade
TerrainEffect on pace vs effort
Flat (0%)Your actual pace and your grade-adjusted pace are the same thing.
Uphill (+5 to +10%)You move way slower, but the effort matches a much faster flat pace. A power-hike up here can cost you the same as a hard run on the flat.
Steep uphill (+15%+)Running barely beats hiking on the clock and costs you a ton more. GAP is what shows you hiking is the smart move.
Downhill (-5 to -10%)You move faster than flat, but the effort is actually gentler. The cost here is hidden: it is eccentric quad damage, not aerobic strain.

Why your trail pace looks slow (and why that is correct)

Climbing burns way more energy per mile than flat running, so an honest, sustainable effort gives you a much slower clock. That is not weakness, it is physics. Uphill, your GAP is faster than your real pace because the hill is doing extra work. Downhill, your GAP is slower than your real pace because gravity is helping you out.

The bigger trap is that GAP only adjusts for the gradient, not the terrain. Rocks, roots, mud, off-camber footing, and stream crossings all add energy cost that GAP ignores, so real-world pace on technical singletrack often runs 10 to 20 percent slower than GAP at the same grade. Treat GAP as a best case, add a buffer for how technical the trail is, and never let a flat-road pace turn into your trail expectation.

Run your own numbers with the grade-adjusted pace calculator, then translate a recent result into a goal time with the race equivalent calculator.

Run-walk strategy and ratios

Planned walking is one of the most powerful tools you have in an ultra. The goal is to walk on purpose, from the start, before your body forces it on you. The best ratio is just the one you can hold for the whole race.

Run-walk starting points (pick the one you can sustain)
Course / runnerStarting ratioHow to use it
Runnable / flat courseRun 25 min, walk 5 minThe classic 25/5. Take the same breaks from the gun, before you feel like you need them.
Time-on-feet beginnerRun 2 min, walk 1 minShort walk breaks, taken often. For a lot of runners this still averages near 13:00/mi, and it saves the legs.
Rolling / mountain courseWalk the climbs, run the restLet the trail decide. Power-hike every real climb, run the flats and the gentle downhills.
Aid-station rhythmRun between aid, walk while eatingUse the walk to chew, drink, and get your head right. Then run again.

Walk early, walk fast

The trick is to take the walk breaks before you need them, while you are still fresh, so the breaks stay short and the legs stay fresh longer. Slow walking is where ultrarunners bleed time, so when you walk, power-hike. Walk as fast as you efficiently can, then run again. And tying the walk to eating and drinking is a bonus, because the walk window doubles as your aid window.

On mountain courses, forget fixed time ratios and let the terrain decide. Power-hike every real climb and run the flats and gentle downhills. On flatter, runnable courses, a structured ratio like 25 minutes running to 5 walking, or a frequent run 2 / walk 1 for newer runners, gives the legs a recurring micro-recovery that pays off late in the race.

Splits, climbs, and descents

Even effort is the target. On the clock that usually reads as an even-to-slightly-positive split, not a true negative split, because the heat, the fatigue, and all the climbing make a real speed-up rare.

Forget the negative split, chase even effort

Marathon advice about negative splits does not carry over cleanly to ultras. Chasing a faster back half tempts you to bank time early, which is the classic blow-up. Studies of long mountain ultras keep finding that the steadiest pacers finish fastest, so the goal is to feel like you are holding the same controlled effort at mile 70 that you held at mile 10.

And the win is easy to picture. You want to be the one passing people in the last few hours because you did not overspend at the start. Even effort across changing terrain naturally gives you a variable pace, fast on the runnable parts, slow on the climbs, and that variability is correct. What stays the same is how hard it feels.

Pace the climbs by effort, protect the quads on the descents

On the climbs, hold the effort and let the pace fall. Power-hike the steep pitches, keep your breathing easy enough to talk in short sentences, and fight the urge to chase a number uphill. Burning matches on the climbs is how runners get to the descents already cooked.

The descents hide the opposite trap. The aerobic effort feels easy, so people bomb the downhills and quietly wreck their quads. The eccentric braking of a fast descent steeper than about -10 percent costs more energy than flat running and causes muscle damage that can hurt your force production for days. Run the early descents controlled and light, with quick feet and a short stride, and the back half becomes a different race. The finishers still standing at mile 80 are almost always the ones who took care of their legs on the early downhills.

Building a pacing plan that clears the cutoffs

Build the plan backward from the official aid-station cutoffs, not forward from a dream finish. The early checkpoints are the ones that catch people, because the climbing, the heat, and the night all slow you down late.

Rough required pace by distance (illustrative, confirm your race's actual cutoffs)
Distance & cutoffRequired averageWhat it really means
50K (8 hr cutoff)About 15:00/mi movingLooks generous on paper. But on a hard course the climbs and aid time eat that buffer fast.
50 mile (14 hr cutoff)About 16:30/mi movingHold even effort. Trying to bank time early by running the climbs usually comes back to bite you.
100K (18 hr cutoff)About 17:00/mi movingPlan your walk-eat windows so that fueling does not cost you the cushion.
100 mile (30 hr cutoff)About 17:30/mi all-inThat is roughly 4 mph of moving plus aid stops and maybe a nap. Margin against the early checkpoints is everything.

Plan backward, leave margin, account for the stops

Take the cutoff at each major aid station and work out the moving pace and run-walk plan you need to reach each one with a buffer. Then subtract the time you will actually spend stopped: aid, eating, blister care, a clothing change, maybe a short nap on a 100. Over a full 100 miler that non-moving time often adds up to one to three hours, and it has to fit inside the cutoffs too.

A flat per-mile average will quietly lie to you, because it ignores where the vert and the heat land. A course-aware projection that loads the climbing into each segment is a lot more honest, and it tells you exactly how much margin you are carrying into the night.

Sanity-check a goal time with the vert-aware race time calculator. Planning a specific 100? See how the cutoffs and climbing stack up in our Angeles Crest 100 course guide and our 100-mile finish-times and cutoffs guide.

⏵ Pace it from your real fitness

A static pace chart does not know your climbs, your heat, or your legs. Summit Line reads your actual training and your exact course profile, then builds a pacing plan, an hour-by-hour fueling schedule, and a finish projection dialed to YOUR fitness, so race day is rehearsed by effort and grade instead of guessed off a flat average.

Keep going

Pacing is just one piece of it. These guides cover the training, the fueling, and the finish-time side of the same race.

Ultramarathon pacing FAQ

Should I pace an ultra by pace, heart rate, or effort?

Pace by effort, and use the other two as cross-checks. Minutes-per-mile is close to useless on trail, because grade and terrain swing it all over the place. Heart rate is fine early on, but it drifts upward (cardiac drift) and lags on short climbs, so it starts lying to you late in the day. Most experienced ultrarunners go by rate of perceived exertion (RPE). You hold an easy, conversational effort, somewhere around RPE 3 to 4 out of 10, for the first several hours, then you let the terrain and how you feel set the pace from there. Keep the watch and the heart rate in front of you as a sanity check, but do not let them run the show.

What pace should I start an ultramarathon at, and why do most DNFs go out too fast?

Start slower than feels right. A good rule is that the first hour or two should feel almost too easy, an effort you know you could hold all day, around RPE 3 out of 10. And the reason matters. Research on long ultras finds that more even pacing lines up with faster finishes, and the fastest runners start at lower relative intensities than the slower ones. Going out too hot does damage you cannot take back. It raises your core temperature, it shuts down your gut so you absorb fewer carbs, and it trashes your legs early, and all of that piles up over the back half. In an ultra a fast start does not cost you a slightly slower finish. It often costs you the whole race.

What is grade-adjusted pace (GAP) and why is my trail pace so much slower?

Grade-adjusted pace is the flat-ground pace that would cost you the same effort as your actual pace on a hill. Uphill, your GAP is faster than your real pace, because the climb is doing extra work for you. Downhill, your GAP is slower than your real pace. And your trail pace looks slow for two reasons. Climbing burns way more energy per mile, so an honest effort gives you a much slower clock, and GAP only accounts for the gradient, not the terrain. Rocks, roots, mud, and stream crossings all add cost that GAP ignores, so real trail pace often runs 10 to 20 percent slower than GAP on technical ground. Treat GAP as a lower bound and add a buffer.

When should I power-hike instead of run (what grade)?

Hike once running stops paying off, which for most people is when a climb forces you below roughly 18 to 19 minutes per mile. On grades of about 4 to 15 percent, if you are grinding at that pace or slower, dropping to a strong power-hike costs you less energy for almost the same speed. Above 15 percent, just about everyone should hike. The trick is to make the switch before your heart rate spikes, not after, and to hike like you mean it: hands driving on the thighs, quick cadence, eyes up the trail. Power-hiking is not quitting. It is the efficient gear for steep ground, and it banks energy you will want for the runnable miles.

What is the best run-walk strategy and ratio for an ultra?

The best ratio is the one you can hold for the whole race, and you should walk from the start, before the race forces it on you. Common starting points are 25 minutes running to 5 walking on runnable courses, or a frequent run 2 minutes / walk 1 minute for time-on-feet beginners (which averages near 13:00 per mile for a lot of runners). On rolling or mountain courses, let the terrain set the ratio: power-hike every real climb and run the flats and gentle descents. Walking is not failure. It saves your legs, it lets you eat and drink, and very often it gets you a faster overall time than trying to run the whole thing.

Should I run negative splits in an ultra?

Aim for even effort. On the clock that usually shows up as an even-to-slightly-positive split, not a true negative split. The fatigue, the heat, and all the climbing in an ultra make a real negative split rare, and chasing one tempts you to bank time early, which is the classic blow-up. Studies of long mountain ultras find the steadiest pacers finish fastest. So the goal is simple: feel like you are holding the same controlled effort at mile 70 that you held at mile 10, and still be passing people in the last few hours because you did not overspend at the start.

How do I pace by effort on big climbs and descents?

On the climbs, hold the effort and let the pace fall. Power-hike the steep pitches instead of forcing a run, and keep your breathing easy enough to talk in short sentences. The mistake is chasing a pace number uphill, which spikes your effort and burns matches you are going to want later. On the descents the opposite trap gets you. The aerobic effort feels easy, so people bomb the downhills and shred their quads. Eccentric braking on steep descents (steeper than about -10 percent) actually costs more than flat running and causes muscle damage that can stick around for days, so run the early descents controlled and light. The runners still standing at mile 80 are the ones who protected their quads early.

How do I build a pacing plan that clears the aid-station cutoffs?

Build it backward from the cutoffs, not forward from your dream finish. Take the official cutoff at each major aid station, then work out the moving pace and run-walk plan you need to reach each one with a buffer, accounting for the elevation, the terrain, the heat, and the time you will actually spend stopped (often 1 to 3 hours total over a 100). The early checkpoint cutoffs are the ones that catch people, because climbing, heat, and the night all slow you down late, so you want margin in the bank early without sprinting. A course-aware projection that loads the vert into each segment beats a flat per-mile average, which the mountains will quietly tear apart.

This guide is for training and planning, and it reflects expert consensus and published sports-science research on ultramarathon pacing. Everyone responds a little differently, the grade and run-walk thresholds are starting points and not rules, and the example cutoff math is illustrative. Always confirm your race's actual cutoffs and aid-station distances on the official race website, and build your pacing and fueling plan around your own training.