Running a 50K isn't the same as running a marathon, and your training should reflect that.
A 50K is roughly 31 miles. It's longer than a standard marathon by about 6.2 miles, but significantly shorter than an ultra. That in-between distance is where most runners run themselves into the ground because they either over-train or under-equip themselves. I built and ran through a 12 Week 50K Training Plan to get from a sub-3:30 half-marathoner to finishing a 50K in 4:48, and the plan that got me there was nowhere near as complicated as most people make it sound. The core principle is that your longest weekly run needs to reach about 30 to 32 kilometers, and you need to do it at least twice before race day. Everything else is supporting infrastructure. Your weekly mileage typically lands between 35 and 55 kilometers depending on your fitness level. The plan structures around five runs per week, one speed or tempo session, and one long run that builds gradually. Rest days are mandatory, not optional. Most of the failures I see come from runners treating the long run as a second marathon effort instead of a manageable stimulus. Weeks one through three are about building the base. You run four to five times per week, with your longest run capping out at around 18 kilometers by the end of week three. Easy pace. Conversational pace. If you're gasping for air, you're going too fast. Weeks four through six introduce the tempo work. A weekly 10K-equivalent effort at threshold pace, which for most people means running at a discomfort level you could sustain for about an hour. Your long run hits 22 kilometers here. Weeks seven through nine are where the bulk of the adaptation happens. Long runs progress to 26, 28, and 30 kilometers. Two quality sessions per week alongside these longs. This is also where most people feel like they're falling apart, which is normal.
Weeks ten through twelve are the taper. Volume drops by roughly 30 percent in week ten, then another 30 percent in week eleven, then you race in week twelve. The taper isn't about losing fitness. You don't lose significant aerobic capacity during two weeks of reduced volume, but you do recover from accumulated fatigue. Running sharp into a 50K matters more than running peaked.
The Specifics You Actually Need to Know
Your long run needs to incorporate race-pace segments starting around week seven. Not the full distance at goal pace, just 5K to 8K chunks near goal 50K effort. This trains your legs and your gut to process fuel at the intensity you'll actually race at. Running 30 kilometers at an easy conversational pace and then trying to go faster on race day is a recipe for hitting the wall at kilometer 35 because your body hasn't adapted to metabolizing carbs at that workload. Back-to-back long runs on weekends, Saturday at 20K and Sunday at 12K with tired legs, simulate the later stages of the race far better than any single run will. Your legs accumulate fatigue over 50K. Training without accumulating that fatigue means you'll be surprised on race day, and surprise is what causes DNFs at this distance. Here's the part nobody tells you: the last eight kilometers of a 50K feel different from the first forty-two. Your glycogen stores are compromised, your quads are damaged from eccentric loading, and your decision-making capacity for nutrition drops because your gut gets sluggish. My workaround when I first trained for a 50K was running 32K long runs without any solid food, relying on gels and electrolyte drinks. I finished three kilometers into actual race-day conditions and threw up because my stomach had never practiced processing solids at that intensity. After that, I shifted to practicing one solid food item per long run above 25K — a banana, a granola bar, whatever. It sounds trivial but it eliminated my GI issues entirely.
Get the Full Details

Common Mistakes That Derail People
Going too fast on easy days is the single most common error. Your easy runs should be slow enough that you can hold a conversation without pausing for breath. If you're doing threshold work three times per week instead of one, you're not training harder. You're just accumulating noise that prevents recovery. I watched a runner on my local group hit a wall in week eight of a 12 Week 50K Training Plan because she'd been doing tempo runs every single day, mistaking discomfort for progress. She pulled out of the race at kilometer 38 with stress-related symptoms that took two weeks to resolve. The second mistake is ignoring strength work. Running 50 kilometers puts enormous load on your stabilizer muscles, particularly your hips and ankles. Two sessions per week of calf raises, single-leg deadlifts, and hip abduction work, even just twenty minutes each, will reduce your injury risk more than any additional running volume will. I added a minimal strength routine midway through my plan and my recurring IT band issues disappeared completely. Not because the volume changed, but because my legs stopped compensating for weak glutes. A third mistake is treating the 50K like a marathon with extra kilometers. Your pacing strategy should be slightly conservative relative to marathon pace, not the same. A reasonable goal is 50K pace sitting about 15 to 25 seconds per kilometer slower than your marathon pace. If you run the first 30K at marathon effort, you'll be running backwards for the final 20K. This isn't theory. I saw it happen to someone at the finish line of a race I was volunteering at. He looked like he was about fifteen minutes ahead of his projected time at the halfway checkpoint. He finished forty-five minutes slower than his target.
What the Plan Looks Like Week by Week
Here's how a straightforward 12 Week 50K Training Plan organizes itself for an intermediate runner targeting a sub-5-hour finish. Monday is rest or cross-training like swimming or cycling for thirty minutes at low intensity. Tuesday is a seven-kilometer easy run with ten minutes of strides at the end to keep neuromuscular sharpness from degrading during the build phase. Wednesday is a six-kilometer tempo run at roughly 15K race pace — you should feel like you're working but you could hold this for sixty minutes if forced. Thursday is an eight-kilometer easy recovery run. Friday is rest. Saturday is your long run, progressing each week. Sunday is a seven to ten-kilometer easy run. Weeks one through three follow this template with Saturday long runs at 14, 16, and 18 kilometers. Weeks four through six move to 20, 22, and 24 kilometers on Saturday, with the Sunday run sometimes extending to ten kilometers if recovery allows. Weeks seven through nine push to 26, 28, and 30 kilometers on Saturday, and some weekends shift to a Saturday long run with a shorter Sunday run to create the back-to-back effect. Week ten drops Saturday to 22 kilometers and Sunday to 8 kilometers. Week eleven has Saturday at 14 kilometers with a few short tempo bursts, and Sunday is a 6K shakeout. Week twelve is race week. Tuesday a 5K easy run. Thursday a 4K with a few kilometers at goal pace. Friday complete rest. Saturday or Sunday race day.
Where This Approach Falls Apart
A 12-week block assumes you already have a solid aerobic base. If your current longest run is under 15 kilometers or you've been inactive for more than six months, this timeline is aggressive and potentially harmful. Fourteen weeks would be a safer window for that population. The plan also doesn't account well for people who run uphill-heavy courses. If your race is mountainous, you need to add specificity: hill repeats once per week starting in week four, and your long runs should include any significant elevation your race will feature. Nutrition is another area where the plan is thin by default. You should be practicing your in-race fueling strategy during every long run above 20 kilometers. Two to three hundred calories per hour is the typical recommendation, spaced across gels, chews, or real food depending on what your stomach accepts. If you've never taken a gel during a run before, don't start doing so now. I learned this the hard way during a training 28K when I tried an energy drink I'd never used before. Bloating and cramping set in at kilometer 22 and ended my training run. It took three weeks to recover the volume I'd lost. If you're targeting a top-ten finish or a course record, this plan undershoots you. That crowd needs higher weekly volumes, double-days, and more aggressive intensity blocks. This structure is designed for the typical amateur runner who wants to finish strong, not for someone chasing qualification times. For that, a 16-to-18-week plan with greater volume makes more sense, though the underlying principles remain identical.

Materials and Gear Considerations
Shoes matter more at 50K than at any shorter distance. By kilometer 35, your feet have swollen enough that the shoe you wore on day one won't fit the same. Buy your race shoes two to three weeks before the event and break them in on at least two long runs above 20K. Don't wear anything on race day that you haven't logged at least thirty kilometers in. Blisters at kilometer 20 are annoying. Blisters at kilometer 40 are a race-ending problem. Chafing cream isn't a luxury. Apply it before every long run above 18K, especially in humid conditions. I switched from powder-based products to a silicone-based barrier cream and cut my chafing incidents from three per season to zero. Cost difference is about eight dollars per tube. Worth it. For a race like this, a hydration vest is usually necessary unless the course has aid stations every three kilometers or less with fluids. Pack two liters minimum for self-supported sections. Weight matters less than comfort and fit. A vest that bounces or shifts will irritate you enough to change your running form, and altered form at kilometer 40 leads to lower-body overuse injuries. Get fitted properly.
Monitoring Your Progress
Use a simple metric: your Saturday long run should feel progressively harder, but not impossibly so. If a 24K run in week six leaves you unable to walk normally the next morning, you pushed too hard and need to drop volume the following week. Training is about accumulating the right stimulus, not maximum suffering. Heart rate data helps here. Your easy runs should sit in zones two and below, which for most people is below 70 percent of maximum heart rate. If your easy pace is creeping up while your heart rate stays the same, that's a positive sign of fitness development. If your heart rate is climbing at the same pace, you're accumulating too much fatigue or not recovering adequately. Morning resting heart rate is another straightforward tracker. A jump of five to eight beats above your personal average for two consecutive mornings usually signals that your autonomic nervous system is stressed and you should take an extra rest day. I started tracking this during my fifth training cycle and it prevented at least two potential overtraining situations that would have cost me a month each. The 12 Week 50K Training Plan is not mysterious. It's a structured progression that takes an already-capable runner from base fitness to race readiness by manipulating volume, intensity, and recovery in a predictable sequence. The people who succeed with it are the ones who follow the easy days as carefully as the hard days, practice everything before race day, and adjust when their body signals that something is wrong rather than powering through. Finish strong.