50K, 50 Mile, or 100K: Choosing Your First Ultra Distance

Almost every runner who comes to me asking about their first ultra has already picked a race. What they're actually asking is whether the distance is right, and most of the time the honest answer is that they've chosen based on how the number sounds rather than what it demands.

50K, 50 mile, and 100K are not three points on a smooth continuum. Each one adds a specific new problem that the shorter distance never asked you to solve.

What actually changes between them

The table understates it. Distance is the least interesting variable here. Time on feet, exposure to night, and the number of decisions you have to keep making correctly while exhausted are what actually separate these races - and none of those show up in the race name.

The 50K: the honest starting point

A 50K asks a genuinely different question than a marathon - can you keep moving well when the terrain, the fueling, and the clock stop cooperating at once - but it asks it inside a single daylight window, without crew, without drop bags, and usually without ever needing a headtorch. If you finish under about eight hours, you will likely never run in the dark.

That makes it the right first ultra for almost everyone. It teaches vertical gain, descending, and race-day fueling - the three skills every longer distance also needs - without adding the two hardest variables at once. The first 50K training plan is the framework I use for this.

The 50 mile: where the real jump happens

Most runners expect the jump from marathon to 50K to be the hard one. It usually isn't. The jump from 50K to 50 mile is bigger, and it's bigger for a specific reason: you cross from "eat enough to finish a long morning" into "eat enough for an entire day, possibly including part of a night."

At 50K, a fueling mistake costs you the last 5K. At 50 mile, the same mistake compounds for six or eight more hours, and by the time it's obvious you're in trouble, there often isn't enough race left to fix it. Pacing discipline in the first third matters more here than at any shorter distance, because the consequences of going out too hard don't show up until hour six, by which point the damage is done.

Night running enters the picture for a meaningful share of the field, even at 50 miles. If your finish projects past 10-11 hours, plan to run at least an hour or two after dark, and read the night running guide before you assume a headtorch is the whole preparation.

The 100K: fueling and sleep, not just distance

A 100K is roughly double a 50 mile in distance but considerably more than double in difficulty, because it reliably crosses into genuine sleep deprivation. Most mid-pack finishers are awake for 16-24 hours by the finish, on top of whatever sleep debt the race morning already cost them.

The limiter here is rarely aerobic fitness. It's decision-making quality at 3am on tired legs - whether to sit down at an aid station "for a minute," whether that stomach discomfort is worth stopping to address, whether to change into dry layers when it would cost ten minutes you don't feel you have. Athletes who've never made a hard decision while sleep-deprived and moving find this the single hardest new skill in the sport, and it genuinely cannot be simulated in training the way vertical gain or fueling can - the closest you get is deliberate back-to-back long runs and at least one long training run that runs into the night.

Match the distance to what you've already proven

The single best predictor of a good first ultra experience isn't how many marathons you've run or how many kilometres you log in a week. It's whether you've already demonstrated, in a race, that you can execute fueling, pacing, and terrain decisions under fatigue - and the only reliable way to demonstrate that is to have done it at a shorter ultra distance first.

The progression I recommend to almost everyone:

1. Finish a 50K comfortably, meaning you crossed the line able to hold a conversation, not staggering.
2. Only then consider a 50 mile, ideally the following season rather than six weeks later.
3. A 100K after at least one solid 50 mile finish, or after several years of 50-milers if you're not chasing anything specific.

When it's reasonable to skip a step: a strong marathon background (sub-3:30 marathon, several years of consistent training) combined with real trail experience and a specific, considered reason - a lottery entry you may not get again, a bucket-list race with a hard age or fitness cutoff. Skipping straight to a 100 mile as a genuine first ultra is a different conversation entirely, and one I'd actively try to talk most runners out of.

When it isn't: "my friends are running the 50 mile so I signed up too," or "the 50K sold out but the 100K still had spots." Neither of those is a reason grounded in what your body has actually proven it can do.

I had an athlete two years ago whose first-ever ultra was a 100K in the Dolomites - no 50K, no 50 mile, a strong road marathon PB and nothing else. She made it to 70K in good shape and then unravelled over the final six hours: a fueling plan she'd only ever tested on runs under four hours, night navigation she'd never practised, and no reference point for what her own bad patches actually feel like versus something more serious. She finished, barely, well outside her goal time. The athlete I'm proudest of from that same season ran a modest 50K first, a 50 mile eight months later, and then the 100K the year after that - and finished it four hours faster than the runner who'd skipped straight there, on a harder course. The extra year wasn't lost time. It was where the race was actually won.

A short decision framework

Answer honestly:

• Have I finished a shorter ultra well, not just survived it? If no, that's usually your answer regardless of what else follows.
• Can my schedule support 16-24 weeks of building volume, not just the peak weeks? A 100K build asks for real consistency across five to six months.
• Am I prepared to run at night, alone, tired, and still make good decisions? If the honest answer is "I don't know," a 50K or 50 mile is where you find out safely first.
• Would I still want to run this race if it took two hours longer than my optimistic projection? Ultra finish times spread widely; the distance you choose should be one you'd still be glad to have attempted at the slow end of your range.
• Is there a specific, considered reason to skip a step, or is it social pressure and a race that "sounds achievable"?

If most of your answers point toward caution, run the shorter race this year. The longer one will still be there next season, and you'll arrive at it having actually earned it.

If a 50K is where you're landing, the 16-week first 50K framework is the plan I'd give you. If you're further along and weighing a 50 mile or 100K build against your actual weekly schedule, that's exactly the judgement call 1:1 coaching exists for.