Running for Weight Loss: What Actually Works

Running helps you lose weight, but rarely on its own: weight loss comes down to energy in versus energy out, and a typical run burns 600-900 kilocalories (kcal, usually just called calories) an hour depending on your weight and pace. Most people who succeed manage both sides of that equation, running and diet. Below: the energy principle, why distance matters more than speed, how often to run, what the fat-burning zone gets wrong, two diet pitfalls (sugar and low-fat products), three sample weekly schedules, and what this page does not cover. The trap is judging a run by how hard it felt. Slow running feels like it cannot be doing enough, so people push harder than they need to, and that is usually where a good plan starts to fall apart. I will show you why an easy pace is not failing.

The One Principle Behind Every Weight-Loss Strategy: Energy In vs. Energy Out

I've been coaching runners on weight loss for over twenty years, and I still got caught out by my own advice.

Here's the principle everything else on this page builds from: energy in versus energy out. Eat more energy than you burn, and you gain weight. Burn more than you take in, and you lose it. That's the entire equation — no pill, no powder, no piece of equipment changes it.

What surprised me wasn't the theory. It was logging my own food intake alongside my running. My wife started using MyFitnessPal to track her meals and felt bad about how much she was eating, so I logged my own intake too, to make her feel better about it. I was shocked. I ate pretty healthily, and I was still eating way too much of everything — in some weeks I'd gain weight despite running regularly, and I didn't understand why until I saw the numbers in front of me.

That's the trap diet-only approaches fall into, and it's also the trap runners fall into when they assume running alone is doing the job. Cut calories hard without exercise, and two things work against you: deprivation is genuinely hard to sustain day after day, and your body responds to prolonged restriction by slowing your metabolism — which is why diets plateau. Run without paying attention to what you eat, and the same plateau shows up from the other direction: you eat back what you burned without ever realising it.

The fix isn't complicated, even if it isn't effortless: combine the two. For the full calorie math behind sizing your weekly mileage to a specific weight-loss target, see the calorie math and weekly mileage framework.

Distance Matters More Than Speed: Why Running Slow Is Not Failing

Here's a beginner mistake I see constantly: someone starts running, goes off too fast, ends up exhausted or injured, and quits within a fortnight. Let's fix that before it happens to you.

Calorie burn while running is driven mainly by distance, not speed. The rule of thumb I use across this site: roughly 1 kcal burned per kg of body weight per kilometre covered.

If you're not sure where your own weight sits before you start working through these numbers, you can check your body mass index (BMI) as a rough starting reference.


Take a 70 kg runner covering 5 km: around 350 kcal, and that number barely changes whether you run that 5 km in 22 minutes or 35.

There's a real caveat here, and I'll state it accurately rather than pretend it doesn't exist: running faster does produce a bit more afterburn — extra calories burned after you finish, known as excess post-exercise oxygen consumption (EPOC). But for anyone early in their running, that small edge isn't worth the injury risk that comes with pushing pace before you've built a base. For the full numbers on how much EPOC actually contributes, see how much extra EPOC actually contributes.

So run further, not faster — and if further currently means run/walk intervals rather than running non-stop, that's not failing. That's the correct starting point. You can get a rough idea of your own numbers with the calories burned while running calculator.

How Often Should You Run? Frequency and the Metabolism Effect

How often should you run to lose weight? Three sessions a week is your minimum. Four to five days of some exercise is optimal — and it doesn't all have to be running. Cross-training on the days you're not running still counts towards the frequency your metabolism responds to.

Here's the effect that makes frequency matter beyond just the calories burned in the session itself: a hard run leaves your metabolism slightly elevated for hours afterwards. One lab study of 45 minutes of vigorous cycling found it was still raised 14 hours later. The extra energy is small, though, and an easy run adds far less, so I treat it as a bonus of running often rather than a reason to run harder.

Jumping straight to running every day, with no base to support it, is a fast route to injury rather than faster weight loss. If you want to run daily, keep those extra days easy and slow — that's genuinely preferable to resting on them, once you've built up to the mileage.

This is the same lesson the MyFitnessPal experience taught me from the food side: what you assume you're doing and what you're actually doing are often two different things. Track your training frequency just as honestly. For structured weekly schedules that put this into practice, see sample weekly running schedules for weight loss.

What the Fat-Burning Zone Gets Wrong — and What Pace Actually Burns More Fat

You'll still see heart-rate monitors advertising a "fat-burning zone" — a low-intensity range where you supposedly burn the most fat. Here's what the research actually shows, and what I'd have you do about it.

At low intensity, fat does make up a higher proportion of the fuel you're burning. But your total calorie burn is lower at that intensity too. Lab studies of trained men put the peak rate of fat burning at a moderate effort, roughly 64% of maximum aerobic capacity, and it falls away sharply at harder intensities. Even so, fat loss over weeks follows your overall energy balance, not which fuel you happened to burn during the run — the "zone" is real as a proportion, but it's the wrong number to chase.

What works best in practice is mostly easy running with one harder session a week. My prescription for weight-loss runners: one interval session a week, and not until you can run 30 minutes non-stop comfortably first — earlier than that, and the injury risk outweighs the benefit. For the full research-backed breakdown, see the fat-burning zone myth explained, and for help choosing your own pace, see finding your fat-loss training pace.

Two Diet Pitfalls That Catch Runners: Sugar and Low-Fat Products

Two mistakes I see constantly in runners who think they're already eating well: sugar, and the low-fat aisle.

Start with sugar. It's increasingly linked to rising obesity rates, and it behaves a lot like unhealthy fat once it's in your system — it can raise the fats (triglycerides) in your blood, and it doesn't switch off your appetite signals as well as other foods do. The result: you keep eating, and you get fatter without realising why. A book called Sweet Poison put this in front of me in stark terms years ago — worth a read if you want the fuller picture, and part of why my own list below is as strict as it is.

I don't say this theoretically. Here's what I actually cut from my own diet: no fruit juice, no jam or other fruit spreads, no sweet liqueurs, no soft drinks, no sugar in my coffee or tea. My rule of thumb when I'm reading a label: more than 10 g of sugar per 100 g of product, and it stays on the supermarket shelf.

The second trap catches people who think they're being careful: low-fat products. "Low fat" very often just means "more sugar" — manufacturers need something to replace the flavour that fat was providing. Try this next time you're shopping: pick up the full-fat and low-fat versions of the same product — peanut butter is a good one to test — and compare the sugar content on the label. More often than not, the low-fat version loses.

None of this needs to become a full nutrition overhaul. Get the sugar and low-fat traps right, and you've closed off two of the most common ways runners undo good training with their food choices. For the complete diet picture, see the runner's diet.

Sample Weekly Schedules — Three Starting Points

Once the principles above are in place, you need a schedule. Three starting points cover most situations:


Across all three, the same pattern holds: regular exercise, mostly longer runs at an easy pace, one more intense session a week, and diet awareness running alongside all of it. For the full day-by-day tables behind each of these three schedules, see sample weekly running schedules for weight loss.

What Happens Next: The Gaps This Page Won't Cover

This page gives you the framework. Four questions come up often enough that they deserve their own dedicated treatment, and I'd rather send you to the right page than give you a shallow answer here.

• Scale going up instead of down when you start running? That's common early on, especially once you add harder interval sessions — see gaining weight when you start running.
• Getting hungrier than expected? Compensatory eating is real, and it's the single most common way a correctly-sized deficit gets cancelled out without you noticing. See compensatory eating and hunger management.
• Worried about losing muscle along with fat? It happens when your deficit runs too deep or your protein too low — and it's avoidable. See how to preserve muscle while running for weight loss.
• Wondering how long this should take? Set your expectations properly before you start, not after week three. See a realistic weight-loss timeline.
• Clothes fitting better but the scale barely moving? Fat and muscle don't take up the same volume for the same weight, so that's a real sign of progress. See why your clothes fit better before the scales move.
• Stopped losing weight after early progress? Stalls are normal, and usually explainable — sometimes it's temporary water retention rather than a genuine plateau. See why your weight loss stalls.

Frequently Asked Questions

Will running alone make me lose weight?
Only if it creates a big enough calorie deficit, and that's harder than most people expect — especially once compensatory hunger kicks in. Combining running with diet awareness is almost always more effective.

Do I need to combine running with a diet to lose weight?
Not mandatory, but very likely necessary in practice. Running burns 300-700 kcal a session — one poorly judged meal erases that. Most runners who succeed long-term adjust both sides of the equation. It's your total calorie balance for the day that matters, not meal timing — so if you're wondering about evening running and dinner timing, eating dinner after a run isn't the problem.

How many miles and how many days do I actually need to run to lose weight?
Minimum three sessions a week, at least 30 minutes each. The specific calorie math — how many kilometres a week it takes to lose 1 kg of fat — is worked through in full on the calorie math and weekly mileage framework.

Will running make me lose muscle as well as fat?
Yes, if you run in a steep deficit without adequate protein. The full muscle-preservation protocol is on how to preserve muscle while running for weight loss.

Does it matter whether I track distance in miles or kilometres for weight loss?
No. The calorie-burn rule of thumb (1 kcal per kg per km) works in any unit as long as you're consistent — just convert once at the start and stick with it.

More Pages on This Topic

Some Other Pages You May Like

Home > Running for Weight Loss & Nutrition > Running for Weight Loss

  ☕ Buy Dom a Coffee