⏵ Training guide · Free

How Long Should Your Longest Run Be Before an Ultramarathon?

For most runners your longest single run should top out around 30 miles or 5 to 6 hours, and it should fall well short of the race distance. The single longest run matters way less than people think, because it is a tiny slice of your total training. Build your weekly volume consistently, cap the long run, and use back-to-back long runs (two long days in a row) to rehearse running on tired legs without the injury risk of one giant effort.

The single longest run matters less than you think

This is the part most new ultrarunners get backwards. They obsess over one heroic long run and skip the thing that actually builds an ultra engine, which is months of consistent weekly mileage.

The math behind why it does not matter much

Think of your longest run as one data point inside a whole season of training. One coach works the numbers: a 7 hour long run before a 100K, sitting inside a 16 week build of about 10 hours per week, is only around 4 percent of your total training load. No single run that small is going to make or break your fitness. The stuff that carries you through an ultra gets built across the whole block, not handed to you on one epic day.

The proof is in who finishes. Coaches have guided runners whose longest training run was as little as 20 percent of race distance, and others who went as high as 80 percent. There is no magic distance that flips a switch and makes you ready. Like they say, first bake the cake with consistent running, and the long run is just the icing.

So what is the long run actually for?

So if it is not the main fitness driver, why do it at all? Because the long run trains the things weekly mileage cannot. You rehearse your full race-day nutrition and hydration, you build the head confidence to keep going when it gets hard, and you practice logistics like running into the night or through heat. The shortest run that actually lets you test your nutrition plan is about 4 hours.

That flips the whole question around. Instead of asking "how far is far enough," ask "how long do I need to rehearse fueling, build confidence, and practice logistics." For most runners you hit all three inside a 30 mile or 6 hour run.

Longest run and back-to-backs by race distance

Ranges, not rules. This is what experienced coaches usually prescribe. Where the research gives a window, we show the window.

Race	Longest single run	Peak back-to-back	Timing
50K (31 mi)	20 to 25 mi, or about 4 to 5 hr	30 to 40 mi over two days	2 to 4 weeks out
50 mile	Up to a 50K (about 31 mi), or 5 to 6 hr	35 to 50 mi over two days	4 to 6 weeks out
100K (62 mi)	A 50K race effort, or 5 to 7 hr	40 to 55 mi over two days	4 to 6 weeks out
100 mile	A 50 mile or 100K race, plus a 50K a month out	40 to 55 mi over two days	6 to 8 weeks out for the big effort

Note: a "back-to-back" total is split across two days in a row (for example, 30 to 40 miles for a 50K might be a 20 mile day and then a 12 to 15 mile day), not run in one go. Adjust for your terrain, since time on feet on steep trail is the truer measure.

You do not run the full distance in training

One of the most-searched questions, and the answer is simple: no. Here is roughly what share of the race a typical longest run actually covers.

Race	Typical longest run	Share of race distance
50K (31 mi)	20 to 25 mi	about 65 to 80%
50 mile	up to ~31 mi	about 60%
100K (62 mi)	a 50K (~31 mi)	about 50%
100 mile	a 50 mile (~50 mi)	about 50%

The pattern is clear. The longer the race, the smaller the slice you cover in your longest run. A 100 mile build tops out around a 50 mile effort, roughly half the race. You close that gap on race day with your built-up fitness, smart pacing, and a fueling plan you have rehearsed, not with one heroic training run. New to the distance? See making the jump from marathon to ultra and how to train for your first 50K.

Time on feet vs distance

On trails, the clock beats the odometer.

Why time is the better target on trails

Distance lies to you on technical or mountainous terrain. Twenty miles on a steep, rocky course can take five-plus hours and pack in thousands of feet of climbing and a lot of hiking, while 20 flat road miles might take half that. What your muscles, your connective tissue, and your gut actually adapt to is how long the stress lasts, so writing long runs in hours nails the real training dose better than miles do.

That is why a lot of coaches write the long run as "4 to 6 hours" instead of a mileage number, especially for mountain races. On flat, fast courses time and distance track each other, so either one works. To turn flat fitness into honest effort on steep ground, use our free grade-adjusted pace calculator and the pacing guide below.

Back-to-back long runs: the smarter way to build

This is the trick that lets you train ultra-specific fatigue without one dangerous monster run.

What they are and why they work

A back-to-back is just two long runs on back-to-back days, say a 20 mile Saturday and then a 15 mile Sunday. The whole point lives in day two. You start it already tired, so you rehearse the exact skill an ultra asks of you, moving and fueling well on dead legs, and a fresh-legged single run cannot teach you that.

The safety side matters just as much. You cannot run a 40 or 50 mile single day in training without a high risk of injury or weeks of lost training. Split that load across two days and you get most of the cumulative-fatigue benefit at a fraction of the risk. A simple rule of thumb: make day two roughly 50 to 75 percent of day one. Plenty of elite ultrarunners build this way.

How often, and how to recover

Back-to-backs are hard on you, so do not stack them every weekend. Space your biggest blocks out roughly every two to three weeks, keep the long runs in between easier, and put your largest single effort 3 to 8 weeks out from race day depending on distance. A typical 50 or 100 mile build has only two or three genuinely peak long efforts.

Recovery is part of the workout. Refuel fast (carbohydrate plus protein within about 30 minutes, then keep eating dense food), rehydrate with electrolytes since you finish depleted, and protect your sleep that weekend. Follow a big block with several easy days or an easy week. And if your easy pace stays elevated or soreness sticks around, take more rest before the next block.

Want the full block structure? How long it takes to train for an ultra and strength training and injury prevention cover the supporting work that keeps big long runs from breaking you.

Use long runs to train your gut, not just your legs

The biggest payoff of a long run is the dress rehearsal for fueling. Stomach problems end more ultras than fitness ever does.

Practice race-day fueling on every long run

Most ultrarunners aim for roughly 60 to 90 grams of carbohydrate per hour and a sodium intake on the order of 300 to 700 mg per hour, and you scale that up in heat. But the gut is trainable, and those numbers only feel normal if you rehearse them. So treat your long runs (especially anything over 4 hours) as fueling practice. Eat and drink on the same schedule and with the same products you will use on race day.

This is where capping the run at 6 hours but doing it often beats one giant effort. More frequent long-but-not-crazy runs give you more fueling reps and more chances to teach your stomach, and they cost you way less recovery.

Dial in the numbers: how many carbs per hour, how much sodium per hour, how to build an hour-by-hour fueling plan, and how to avoid stomach problems and train your gut.

⏵ Free calculators to plan your long runs

Run your numbers with our free, no-signup tools, then let Summit Line tie them to your real fitness and your goal race.

See all free running tools →

⏵ Stop guessing from a static chart

A generic long-run number cannot know your fitness, your terrain, or your race. Summit Line reads your actual training and builds a plan that caps your long runs and auto-schedules back-to-back weekends by race distance, with a fueling schedule and a course-aware finish projection dialed to YOU. So your long runs are the right length, at the right time, and your race day is rehearsed instead of guessed.

Get started free →See it on a real plan

Longest run FAQ

Do I need to run the full race distance in training before an ultra?

No. Almost nobody runs the full race distance in training, and you should not try to for anything 50 miles or longer. Your single longest run is a small slice of your total training load (one coach runs the math and a 7 hour run before a 100K is only about 4% of a typical build), so it is not going to make or break your fitness. The thing that actually gets you ready is the weekly volume you stack up over months. Runners have raced well on a longest run anywhere from roughly 20 percent to 80 percent of race distance. So bake the cake with consistent weekly mileage first, and the long run is just the icing.

What is the longest run for a 50K vs 50 mile vs 100K vs 100 mile?

For a 50K, your longest run is usually 20 to 25 miles or about 4 to 5 hours. For a 50 miler, build up to one long run of around a 50K, or 5 to 6 hours, and it is often paired with back-to-back days. For a 100K, a 50K race run as a training day is the classic peak effort. For a 100 miler, your biggest single effort is usually a 50 mile or 100K race a couple of months out, plus a 50K about a month before, with back-to-back long runs filling in the gaps. Notice the longest run comes up well short of the race distance every time. And the gap gets bigger as the race gets longer.

Is time on feet or distance the better target for the long run?

For trail and mountain ultras, time on feet is usually the better target. Distance lies to you on technical or steep terrain, where 20 miles might take five hours and pack in thousands of feet of climbing and hiking. What your body and your gut actually adapt to is how long the stress lasts, so coaches often write long runs in hours (say 4 to 6 hours) instead of miles. The shortest long run that is any good for rehearsing your full race nutrition is about 4 hours. On flat, fast courses distance and time track each other close, so either one works.

Should I cap my longest run at 30 miles or 6 hours?

For most runners a cap in that range is a solid rule of thumb. Past roughly 30 miles or 5 to 6 hours, one run gives you less and less fitness back while the recovery cost and the injury risk climb fast, so you tend to lose more training days than you gain. Honestly the cap should be set by what you are trying to get out of the run, not by some magic number: how long do you need to rehearse your nutrition, build confidence, and practice race logistics like running into the night. For most people you hit all of that inside a 30 mile or 6 hour run, and the extra mileage is better spent as back-to-back days or higher weekly volume.

What are back-to-back long runs and why use them instead of one huge run?

Back-to-back long runs are two long runs on back-to-back days, say a 20 mile Saturday and then a 15 mile Sunday. The whole point is the second run. You start it already tired, so you practice the exact skill an ultra asks of you, moving and eating well on tired legs, and you get it without the injury risk of one monster effort. You cannot safely run a 40 or 50 mile single day in training, but you can split that load across two days and get most of the benefit at way lower risk. A common rule of thumb is to make day two about 50 to 75 percent of day one. Plenty of top ultrarunners build this way.

How many big long runs should I do before race day?

Fewer than most people think. You only need a handful of genuinely big long runs or back-to-back weekends across a whole training block, not one every week. They are hard to recover from, so space your biggest efforts out roughly every two to three weeks and keep the long runs in between easier. A typical 50 mile or 100 mile build might have two or three peak long efforts (a tune-up race plus one or two big back-to-back weekends), each one followed by a recovery week. Quality and recovery beat piling on long run after long run.

How far out from the race should my longest run be?

Put your single biggest effort about 3 to 8 weeks before race day, and the longer the race the more taper room you want. For a 50K, your longest run can land 2 to 4 weeks out. For a 50 mile or 100K, do the peak effort or tune-up race about 4 to 6 weeks out. For a 100 miler, put the biggest single effort 6 to 8 weeks out, then a smaller long run (around a 50K) a month before, so you show up fresh. The point is to soak up the fitness and fully recover. Never cram a giant run into the last two weeks.

How do I recover from back-to-back long runs?

Treat the recovery as part of the workout. Refuel fast after each run, getting carbohydrate and protein in within about 30 minutes and continuing to eat nutritionally dense food, and rehydrate with fluid and electrolytes because you will finish day one depleted. Sleep is the biggest lever, so prioritize it that weekend. Follow a big back-to-back block with several genuinely easy days or an easy week (easy runs, cross-training, or rest), and only schedule the next big block once you feel recovered, usually two to three weeks later. If soreness lingers or your easy pace stays elevated, take more rest.

Keep reading

This guide is for general training education and reflects expert-consensus ranges, not personal coaching or medical advice. The right long-run length depends on your experience, your weekly volume, your terrain, and your goal race, and the figures here are ranges where coaches and the research disagree. Build gradually, respect recovery, and talk to a coach or clinician if you are coming back from injury.