Running for Weight Loss: A Complete Framework Combining Calorie Math and Weekly Mileage
Running for weight loss works best as a framework with two levers, your weekly mileage and your daily calorie intake, and a realistic starting point is 15–25 miles a week combined with a moderate cut of 200–300 kilocalories (kcal, usually just called calories) a day, which gets most runners to a loss of roughly 0.4–0.6 kg a week. Below you'll find the short answer, the two levers, the arithmetic of deficit, mileage and rate of loss, mileage targets adjusted for bodyweight, a worked week, how the framework shifts as you get fitter, the injury ceiling on mileage, ways to track progress beyond the scale, and a four-week starter plan.Pull only one lever and you pay for it: rely on running alone and you chase mileage your joints won't thank you for, rely on food cuts alone and you lose the fitness running gives you. Used together, the numbers become much kinder, so let me show you how they fit.
The Short Answer: It Depends on Your Bodyweight and How Much You Cut
Let's face it — most runners who want to lose weight have no idea which lever to pull first. I've coached enough people through this to tell you directly: weight loss comes down to one equation — calories in minus calories out — and running is only one side of it. As a realistic starting point, 15-25 miles a week combined with a moderate 200-300 kilocalories (kcal)/day dietary cut gets most runners to a loss of roughly 0.4-0.6kg a week. Both levers matter here, and this page builds directly on the principles covered in Running for Weight Loss — this is the calculator behind that framework.The Two Levers: Running Volume and Calorie Intake
Every weight-loss plan for runners rests on exactly two levers. Confusing which one to pull — and when — is where most efforts go wrong.Lever one is calories burned — your running plus your everyday activity. Lever two is calories consumed — everything you eat and drink. I'd recommend you think of them as a pair, not alternatives. Rely on running alone and you'll be logging enormous mileage to get there; rely on diet alone and you lose the training benefit running gives you.
Worth flagging early: the running side has a ceiling — an injury ceiling, covered in full further down this page — which is exactly why the diet lever matters as much as it does.
The Math: Deficit, Mileage, and Weight Loss Rate

Here's the arithmetic behind all of this, worked through step by step so you can apply it to your own numbers.
Burning off 1kg of body fat costs roughly 7,700 kcal (the familiar 3,500 kcal per pound) — treat that as a rule of thumb, not a law, because individual metabolism genuinely varies enough that pretending otherwise would be dishonest. Running burns roughly 1.4 kcal per kg of body weight per mile (about 0.63 kcal per lb per mile) — that's an approximation too, and pace shifts it slightly at the extremes, but it's close enough for planning.
Take a real example from my coaching inbox: a woman weighing about 80kg, wanting to lose a stone (6.5kg), targeting 0.5kg a week (about 13 weeks). A woman's maintenance intake sits around 2,000 kcal a day. Cut that to 1,800 kcal a day — a 200 kcal/day deficit — and you've banked 7 x 200 = 1,400 kcal from diet alone by the end of the week. The rest of that week's roughly 3,850 kcal target has to come from running: about 2,450 kcal, which at roughly 1.4 kcal/kg/mile (112 kcal a mile for an 80kg runner) works out to about 35km (22 miles) a week.
Reader Coaching Q&A — Fiona, Ireland
Fiona runs on a treadmill before six every morning — small kids at home, and her husband works away, so the early slot before they wake is the only one she has. She wrote back after a previous question to tell me her progress: she'd gone from struggling past two or three miles to running five miles in about 53 minutes, four to five days a week, roughly 20-25 miles a week in total. She'd heard she needed six days a week — 30 miles — to keep losing weight, and didn't want to find out the hard way that 20-25 wasn't enough.
Here's the arithmetic applied to her situation. At an assumed bodyweight around 80kg (the working figure from her own earlier question), a 5-mile session costs roughly 1.4 x 80 x 5 = 560 kcal. At four to five sessions a week, that's 2,240-2,800 kcal from running alone. Add her existing 200 kcal/day dietary cut — 1,400 kcal a week — and her total weekly deficit lands around 3,640-4,200 kcal. Against roughly 7,700 kcal per kg of fat, that's about 0.5kg a week: a solid, sustainable rate for where she was. My answer to her wasn't a mileage threshold — there's no magic number where 25 works and 20 doesn't. She was already losing weight on her current volume, which is the evidence that mattered, and the diet side of the equation counts for just as much as the miles. A plateau may well come. That's the point to re-examine both levers, not to assume more running is automatically the fix.
Body-Weight-Adjusted Mileage Targets
Here's the practical consequence of the arithmetic above: a heavier runner burns more calories per mile, so the mileage needed to hit a given deficit is lower. A lighter runner needs more miles to close the same gap. The table below assumes a fixed 200 kcal/day dietary cut and applies the 1.4 kcal/kg/mile figure consistently across three bodyweight bands.| Body weight | 0.25kg/week target | 0.5kg/week target |
|---|---|---|
| 60kg | ~6.3 miles/week | ~29.2 miles/week |
| 75kg | ~5.0 miles/week | ~23.3 miles/week |
| 90kg | ~4.2 miles/week | ~19.4 miles/week |
These are estimates — your own metabolism, pace, terrain, and fitness level will all shift the real number. Use this as a starting range, not a prescription.
Notice how low the 0.25kg/week column runs. That's not a typo. At a fixed 200 kcal/day dietary cut, diet alone is already covering most of a 0.25kg-a-week deficit, so running only needs to make up a modest shortfall. The 0.5kg/week column tells a different story: diet is capped, so the entire extra burden falls on mileage — which is exactly why that target demands so much more running, and why I'd call it the more aggressive of the two.
Here's a pattern I see constantly in coaching: two runners doing the same weekly mileage, one getting far better results than the other. Nine times out of ten it's not a metabolic mystery. It's bodyweight arithmetic. The heavier runner burns more per mile. Full stop.
A Worked Week: Mileage Sessions and Daily Calories Together

Everything above has been numbers in isolation. Here's what it looks like stitched into one actual week — a moderately active 75kg runner, targeting 0.5kg/week loss, running four days a week.
| Day | Session | Distance/Duration | Calorie burn | Daily calorie target |
|---|---|---|---|---|
| Mon | Rest | — | — | 1,700 kcal |
| Tue | Easy run | 4 miles / ~35 min | ~420 kcal | 1,900 kcal |
| Wed | Rest | — | — | 1,700 kcal |
| Thu | Tempo run | 3 miles / ~24 min | ~315 kcal | 1,900 kcal |
| Fri | Rest | — | — | 1,700 kcal |
| Sat | Long run | 6 miles / ~55 min | ~630 kcal | 1,900 kcal |
| Sun | Easy run | 4 miles / ~35 min | ~420 kcal | 1,900 kcal |
| Weekly mileage | 17 miles |
| Total calorie burn from running | ~1,785 kcal |
| Dietary deficit vs. baseline maintenance | ~2,000 kcal (about 285 kcal a day below maintenance) |
| Projected weekly loss | ~0.5kg |
Those calorie-burn figures use the 1.4 kcal/kg/mile formula from earlier — close enough for planning, but if you want a tighter number for your own pace and weight, calculate your actual calories burned per session and swap it straight into the table.
That dietary-deficit line is the real lesson of this table. At this mileage, running and the dietary cut each carry roughly half of the weekly deficit: about 1,785 kcal from running and about 2,000 kcal from eating less. The daily target rises on running days and drops slightly on rest days — same weekly total either way, whichever approach you find easier to stick to. If you'd rather eat the same amount every day, a flat ~1,815 kcal target lands in the same place — see sample meal plans that hit the dietary side of this framework for what that actually looks like on a plate.
Rising mileage brings rising hunger. I'd rather you knew that now than discovered it on a long-run Saturday — see managing hunger as your mileage climbs if the extra appetite on long-run days is catching you off guard.
The sessions aren't randomly placed either. Two easy days, one tempo day, one long day — not five hard days or five easy days — keeps injury risk down while still delivering enough quality to make you fitter, not just tired.
How the Framework Shifts as You Get Fitter

This framework isn't static. Two things change as you improve.
First, running economy gets better — a fitter runner often burns somewhat fewer calories per mile than a beginner running at the same pace, because training improves running economy by a few percent. Second, your body weight drops, which independently lowers the calories you burn per mile again. Put those together and the exact same weekly mileage produces a smaller deficit than it did eight weeks ago.
Practically: after 8-12 weeks on a fixed plan, I'd recommend you recalculate your mileage target or tighten the dietary cut slightly. Don't assume the same mileage keeps producing the same result. I see coached runners stall at an unchanged mileage after this window regularly — and it's rarely the plan that's broken. It's their own efficiency catching up with them. For what to expect week by week as the framework takes effect, including where this efficiency shift typically shows up, see the dedicated timeline page.
When something has to give, pull the dietary lever first. Adding mileage to compensate for improving efficiency is tempting — but it risks injury from ramping too fast, and that's a far bigger setback than a slightly tighter plate.
The Injury-Risk Ceiling on the Mileage Side

You cannot add miles indefinitely. This is the constraint that separates a real framework from a calculator spitting out a number.
The standard guideline — no more than a 10% increase in weekly mileage — applies with extra force here. Runners chasing weight loss often start from a low base and want results fast, and that combination of a calorie deficit plus rapid mileage increases compounds injury risk rather than simply adding it up.
Practically: a new runner starting at 10 miles a week and targeting 25 needs 8-10 weeks of progressive build, not 3-4. Tighten the diet lever in the short term if you want faster results — it's far safer to adjust than mileage is. Running is your long-term engine. Don't damage it trying to rush the short term.
Tracking Progress Beyond the Scale

The scale alone will mislead you. Weekly weight fluctuates by 1-2kg even on a plan that's working exactly as intended — so I'd like you to judge the weekly average, not the daily number.
Two markers tell you more than the scale does. Your pace at a given heart rate improving is your fitness improving, even if the scale hasn't moved yet. Your clothes fitting differently is real signal — scale be damned.
Hold course through normal weekly noise. Only troubleshoot the framework itself — mileage, deficit, or both — once the weekly average has genuinely stalled for two to three weeks running. Not after one disappointing Tuesday.
A 4-Week Starter Framework
Here's a concrete four-week ramp you can start this Monday — pulling everything above into one sensible sequence.| Week | Focus | Mileage target | Dietary cut | Checkpoint action |
|---|---|---|---|---|
| 1 | Baseline and deficit | Current comfortable mileage — no change | 200-300 kcal/day below total daily energy expenditure (TDEE) | Confirm TDEE estimate before Week 2 |
| 2 | Hold and confirm | Same as Week 1 | Same as Week 1 | Track weekly-average weight, not daily |
| 3 | Mileage increase | +10% (or +1-2 miles if base is low) | Held fixed — no further cut yet | Watch for soreness or fatigue accumulating |
| 4 | Recalibration checkpoint | Held at Week 3's level | Held fixed | Working? Repeat the pattern. Stalled? Review TDEE before cutting calories further |
Step 1 depends on an accurate starting number — see calculating your personal TDEE before setting a target before you set Week 1's target.
Frequently Asked Questions
Is it better to create my deficit mostly through running or mostly through diet?I'd aim for roughly 70% from a dietary cut and 30% from added running in the early weeks — diet changes are safer to make quickly than mileage increases. As fitness improves and running efficiency rises, that balance may need to shift slightly toward diet.
Can I hit my deficit with 3 runs a week, or do I need to run daily?
Three runs a week is enough if the total weekly mileage and dietary cut together create the required deficit. Four to five days a week is more practical for hitting 20-30km/week without putting all the mileage burden on a single run.
How do I combine this framework with strength training without overcomplicating it?
Treat strength sessions as replacing — not adding to — one easy run a week in the early phases. Calorie burn from strength is lower per session; the benefit is muscle preservation under a deficit. See adding strength training without overcomplicating the framework for the full integration guidance.
Is there an injury risk to ramping mileage quickly for weight loss?
Yes — and it's higher in a calorie deficit than in normal training because recovery is already compromised. The 10% weekly increase rule applies; a new runner targeting 25 miles a week from a 10-mile base needs at least 8-10 weeks of build, not 3-4.
How do I know when to increase mileage vs. tighten my diet instead?
Increase mileage only once you've held the current week's volume for 2-3 weeks without soreness or fatigue building up. If progress has stalled and mileage is already at your safe ceiling, cut 100-150 kcal from daily intake before adding another running day.
Some Other Pages You May Like
About the author
Dominique de Rooij (Dom)
Advanced Running Coach certified by Athletics Australia with 20 years of writing about running and over a decade coaching runners — from first-timers to marathoners. Dom's beginner programs have guided thousands of runners and been praised above plans from Jeff Galloway, Hal Higdon, and Runner's World. Now over 50, Dom still loves trail running, parkrun, and the coffee after.

Free beginner guide • From Coach Dom
Start Running This Week, Even If Your Week Is Already Full
Most beginners don't quit for lack of motivation. They quit because their plan doesn't fit their life. The 3-Run Busy Week Starter plans your first week around the week you actually have.
- Find 3 run slots you can actually keep
- The talk test: the simple way to stop running too fast
- Your complete week 1 plan: 3 run/walk sessions, about 20 minutes each
I'll email you a link to confirm your address, then send the guide plus a short email every few days to help you through week 1. Unsubscribe any time. Privacy policy.
What's New?
-
Cut 90 Seconds Off Your 1.5 Mile Run for the Army Test
Cutting 90 seconds off a 1.5 mile run in 3-4 weeks for the Army test: Dom breaks down realistic pacing to reduce 10:32 toward sub-9:00 for Paras selection. -
Training for a 1.5 Mile Run - How to Qualify For Your Test
Coach Dom's 3-step plan for 1.5 mile run training: build aerobic base, add strides, then tempo and pace work to hit your test time. -
Improve Your 1.5 Mile Running Time to 10:30: Shin Splints
From 12:59 to 10:30 for 1.5 miles: Coach Dom's shin-splint fix and training plan to improve your running time in 2-3 months.