How Many Miles a Week Should You Run?

Most runners should run about 30 to 80 km a week, or 20 to 50 miles, scaled to their goal. A 5K needs the least. A marathon needs the most. Add new miles slowly, by about ten percent a week at most. And know that extra miles stop paying off at some point. Past your own ceiling, more volume buys little speed and a lot more risk.

Goal distance	Typical weekly range	Where it stops paying off
5K	30 to 50 km (about 19 to 31 miles)	Past about 50 km, sharper speed work adds more than extra easy miles do.
10K	40 to 65 km (about 25 to 40 miles)	Above about 65 km, gains shrink and one weekly hard session matters more.
Half marathon	50 to 80 km (about 31 to 50 miles)	Above 32 km helps, but the highest-volume runners gain little extra and get hurt more.
Marathon	60 to 110 km (about 37 to 68 miles)	More miles help the longest, yet risk climbs fast once you pass your steady ceiling.

How many miles a week should you run?

Run about 30 to 80 km a week for most goals. That is roughly 20 to 50 miles. The right number is not one size. It rises with your race distance and your training age.

A new runner aiming to finish a 5K does well on 15 to 25 miles a week. A runner chasing a faster 10K or half marathon often lands at 25 to 45 miles. A marathon runner usually needs 40 to 70 miles, sometimes more. The longer the race, the more your finish time leans on a deep aerobic engine.

Why does the number move so much? Miles are the raw fuel for your Aerobic Base. That is the part of your fitness built from easy running. A bigger base lets you hold goal pace longer before you slow. But miles also bring fatigue. The right weekly total grows your base. It also leaves you fresh enough to recover.

How should weekly mileage scale with your goal distance?

Weekly mileage should rise with the length of your race. A short race needs less volume. A long race needs more. The reason is simple. The longer you race, the more of the work your aerobic engine does.

A 5K lasts 15 to 35 minutes for most people. It leans on speed and a hard, steady pace. So its weekly base can stay small. A marathon lasts two to five hours. It runs almost fully on aerobic fuel. So its base must be deep and wide. The half marathon and 10K sit in between.

The data backs this up. A study of nearly 1,000 runners looked at this. Higher weekly volume was linked to faster half marathon and marathon times (Fokkema et al., 2020). The link was strongest for the longer races. A study of 917 Boston Marathon runners found the same. More weekly volume was one of the biggest signs of a faster finish (DeJong Lempke & Ackerman, 2025).

So pick your race first. Then let the distance set the volume. If your goal is a marathon, plan to build toward the higher end. If your goal is a 5K, you can race well on far fewer miles. For a deeper look at which sessions fit each distance, see how to match your workouts to your race goal.

What is the safe way to add mileage?

The safe way to add mileage is to grow it slowly and hold each step. A common guide is the ten percent rule. It says to raise your weekly miles by no more than about ten percent each week. Then sit at that new level for two or three weeks. Only then do you climb again.

This steady build ties straight to Load Consistency. It is one of five performance drivers. It tracks how smooth your training is week to week. A slow climb scores high. Big jumps score low. A sudden spike in miles loads your muscles and bones faster than they can adapt (Gabbett, 2016). That is how runners get hurt while feeling fit.

10%

a common ceiling for weekly mileage increases, used as a guide not a hard rule

A sharp jump in volume is its own trap. A study tracked new runners. Those who raised their weekly distance by more than 30 percent over two weeks got hurt more often (Nielsen et al., 2014). Smaller, slower steps were far safer. So spread new miles across the week. Let each step settle before you climb.

Add an easy step-back week every fourth week as well. Drop your volume for seven days, then build again. This rhythm lets your body lock in the work before you ask for more.

Does the ten percent rule actually work?

The ten percent rule is a useful guide, not a hard law. It points you in the right direction. But the exact number is not magic, and research has tested it.

A controlled trial followed new runners for 13 weeks. One group used a slow program built around the ten percent idea. The other used a more standard build. Both groups had about the same injury rate. It was near one in five runners (Buist et al., 2008). The slow program did not lower injuries. Many people assume it would. It did not.

So what does that mean for you? It means the spirit of the rule matters more than the number. The point is to climb slowly and skip sharp spikes. Add eight percent one week or twelve the next. That matters less than the shape of your whole build. Steady beats jumpy.

It also means injury risk has many parts. Your history, your sleep, your shoes, your terrain, and your stress all play a role. The ten percent rule controls just one of them. Use it as a brake on your eagerness. Do not treat it as a shield that makes you injury proof.

Where do extra miles stop paying off?

Extra miles stop paying off once you pass your own ceiling. The first miles you add give back a lot of fitness. The miles far above your normal load give back very little. This is the diminishing return of high volume.

The Fokkema study makes the point clear. Runners who trained more than 32 km a week finished a half marathon faster than those under 20 km a week. But the gap between the highest volume group and the middle group was small. And the highest volume group picked up more injuries than the middle group (Fokkema et al., 2020). They paid more and gained little.

32 km

weekly volume above which half marathon runners ran faster (Fokkema et al., 2020)

Picture the curve in your head. The climb from 20 to 40 miles a week is steep with reward. The climb from 50 to 65 miles is nearly flat. Each new mile costs more recovery, more time, and more risk. At some point the cost is larger than the gift.

This is why piling on volume is not the answer once you are trained. If your weeks are already full and your time has stalled, more miles rarely fix it. The fix is usually better miles, not more of them. We unpack that idea in detail in why peak mileage alone will not save your half marathon.

How do more miles raise injury risk?

More miles raise injury risk. Each mile adds load. Load needs recovery to turn into fitness. Add miles faster than your body can take, and the gap shows up. First soreness. Then small aches. Then an injury that stops your training.

Bone, tendon, and muscle all adapt at different speeds. Your heart and lungs get fit fast. Your tendons and bones lag behind. So a runner can feel fit and fast while the legs are not yet ready for the new load. That gap is where many running injuries begin (Gabbett, 2016).

An injury is costly in two ways at once. It stops the training you planned. And it erases the fitness you already built. Miss two weeks and your Aerobic Base starts to slip. Miss four weeks and much of your block is gone. A runner who stays healthy on steady miles wins. A runner who chased a big number and lost weeks to a strain does not.

This is the quiet case for holding back. The best weekly mileage is not the most you can survive. It is the most you can repeat, week after week, without breaking down. A strong base is built before you train hard. That is why a patient base building phase sets up all that follows.

How does PIRX know how many miles you need?

A one-size-fits-all calculator cannot tell you your right weekly mileage. It sees a finish time and gives one number back. It does not know if your legs are fresh or fried. It does not know if your last build was smooth or jumpy. A wrist watch is no better. It reads today's heart rate and a rough VO2 max guess, not the shape of your training.

PIRX is a proprietary machine-learning prediction engine. It reads your real runs, not just a race result. It scores five performance drivers from that data. Two matter most here. Aerobic Base grows from your volume. Load Consistency tracks how steady your weeks have been. Each driver ties to real seconds, gained or lost, since your baseline race.

So when you add miles, you can see whether they helped. Say you raise your weekly distance and hold it for a month. If that lifts your Aerobic Base, PIRX shows the gain in seconds off your Projected Time. If your build was too sharp and your Load Consistency dropped, you see that too. You stop guessing whether the extra miles were worth it.

The projection recalculates after every synced activity. A visible change in your Projected Time appears only when the structural change is at least 2 seconds. So you see real progress from your mileage, not daily noise. Each Projected Time also comes with a Supported Range, the spread of finish times that fits your current fitness. If you want to see how all five drivers work together, read the five performance drivers that set your race day ceiling.

98%

validated prediction accuracy (PIRX users)

See what your weekly mileage is worth

Stop guessing how many miles a week you should run. Your goal and your training history set the answer, and a static calculator cannot see either one. PIRX can. Connect your Garmin, COROS, or Strava in under a minute. See how your weekly volume feeds your Aerobic Base and how steady your Load Consistency has been. Then add miles the safe way, hold them, and watch the seconds drop. Free, no signup needed.

Sources

• Fokkema, T. et al. (2020). Training for a (half-)marathon: Training volume and longest endurance run related to performance and running injuries. Scandinavian Journal of Medicine & Science in Sports. (Higher weekly volume was linked to faster half marathon and marathon times, but the highest-volume group gained little over the middle group and had more injuries.)
• DeJong Lempke, A.F. & Ackerman, K.E. (2025). Training Volume and Training Frequency Changes Associated with Boston Marathon Race Performance. Sports Medicine. (Higher weekly volume was one of the strongest signs of a faster marathon finish in 917 Boston runners.)
• Buist, I. et al. (2008). No effect of a graded training program on the number of running-related injuries in novice runners: a randomized controlled trial. American Journal of Sports Medicine. (A 13-week program built around the ten percent rule did not lower injury rates compared with a standard program.)
• Nielsen, R.O. et al. (2014). Excessive progression in weekly running distance and risk of running-related injuries: an association which varies according to type of injury. Journal of Orthopaedic & Sports Physical Therapy. (Novice runners who increased weekly running distance by more than 30 percent over two weeks were more prone to distance-related injuries.)
• Gabbett, T.J. (2016). The training-injury prevention paradox: should athletes be training smarter and harder? British Journal of Sports Medicine. (Sudden spikes in training load raise injury risk; steady, gradual load protects fitness gains.)