Every runner switching to cycling asks the same question in the first week, usually while comparing a ride's calorie count on their watch to what a run of the same duration would have shown. Cycling says 480. Running would have said 650. The instinct is to panic and assume the bike is a worse tool for the job.
It isn't. The comparison is just measuring the wrong thing.
Calories per minute: running wins, and it's not close
Start with the honest number, because pretending otherwise doesn't help anyone. At matched perceived effort — the "this feels moderately hard" zone most people ride and run in — running burns more calories per minute than cycling. It's weight-bearing. Every stride means decelerating and re-accelerating your entire body mass against gravity, and that costs energy cycling simply doesn't ask for because the bike carries your weight for you. Running also recruits more total muscle mass per stride — calves, glutes, hip stabilisers, core — all doing real work to keep you upright and moving forward.
So if you ran and cycled for exactly thirty minutes at what felt like the same effort, the run would show a bigger number. That part of the running-is-better argument is true. It's also almost irrelevant to whether you lose weight.
Why the per-minute number is the wrong number
Weight loss isn't decided by your best single session. It's decided by what you can repeat, week after week, for months. And this is where the comparison flips entirely.
A 90-minute easy ride is a normal Tuesday for most trained cyclists. It leaves you tired in the pleasant, "that was a good session" way — legs a bit heavy, appetite up, ready to go again in a day or two. A 90-minute easy run, for most people over 35, is a different proposition. The impact of roughly 1,500 to 1,800 footstrikes per leg starts to accumulate real structural load — tendons, joints, connective tissue that doesn't announce itself as fatigue the way muscles do, right up until it does, usually as a nagging Achilles or a knee that resents stairs.
This is the entire ballgame. Cycling's lower calorie burn per minute is more than compensated for by the volume of minutes you can bank without breaking down. A rider who can comfortably do five sessions a week, totalling six or seven hours, will out-burn a runner doing three sessions a week at higher per-minute cost but capped total volume — especially once you factor in the runner's inevitable down weeks when something starts hurting.
Total weekly energy expenditure is what matters for fat loss. Not the number on the watch after one session.
The EPOC argument is real but overstated
If you've spent any time in fitness forums, someone will bring up EPOC — excess post-exercise oxygen consumption, the "afterburn" where your body keeps burning slightly elevated calories for hours after a hard session while it repairs tissue and restores oxygen debt.
Running does generate somewhat more EPOC than cycling, mostly because of the eccentric muscle damage from repeated impact — your body has more repair work to do afterward, and repair costs energy. This is a real physiological difference. It is also a small one. EPOC typically accounts for a modest percentage of total daily energy expenditure, even after a properly hard session. It is nowhere near large enough to offset a training approach you can't sustain, and treating it as a deciding factor is giving a rounding error the weight of a strategy.
If someone tells you running is better for fat loss because of the afterburn effect, they're technically correct about the direction and wrong about the size of it mattering.
Appetite: cycling's quiet problem
Here's a factor that gets left out of most versions of this comparison entirely, and it matters more than EPOC ever will.
Running tends to suppress appetite more reliably than cycling in the hours immediately after a session, for a lot of people — likely related to the higher core temperature and gut-blood-flow disruption from the impact and intensity. Cycling, particularly longer steady rides, often does the opposite: it can leave you ravenous, and the "I just burned 700 calories" mental accounting makes second helpings feel earned.
This is not a knock on cycling. It's a genuine risk worth naming, because a rider who quietly eats back the deficit a long ride created will wonder why the scale isn't moving despite all the training. The fix isn't complicated — track your food for two weeks alongside your riding before assuming the exercise itself isn't working, because in almost every case it's the plate afterward, not the pedals.
There's an argument that cycling's weaker appetite suppression is actually an advantage over the long run. You're not white-knuckling through hunger the way some runners describe during a cut. That makes the deficit easier to sustain psychologically, provided you're honest with yourself about portions.
Muscle preservation: an underrated point in cycling's favour
At comparable training volumes, cycling tends to preserve more muscle mass through a fat loss phase than running does. The reason is simple: cycling is largely a concentric movement — you push down and pull through, but there's no braking or impact-absorption demand the way there is with every single footstrike in running. Running's eccentric loading, the deceleration force your leg absorbs on contact, contributes to muscle protein breakdown that has to be repaired, and that repair competes for the same resources you need for recovery when you're already eating in a deficit.
This matters more than it sounds like it should. Preserving muscle during a cut is what determines whether you come out the other side leaner and stronger, or just smaller and softer. Cycling's movement pattern gives you a structural advantage here that has nothing to do with calories burned and everything to do with what kind of tissue you're left with at the end.
What actually happened when I tried this
I lost seven kilos in twelve weeks — 86 down to 79 — and I was eating more food than I had in years. Power didn't drop. If anything it climbed. Energy went up across the board, not down, which is the opposite of what most people expect from a cut.
The variable that changed wasn't quantity. It was quality — protein at every meal, less ultra-processed food filling gaps, more consistency in when and what I ate. And it happened on top of training consistently on the bike, week after week, without a single missed block because something in my legs gave out. That last part is the one people skip past. The deficit did the work. The bike is what let me show up for the deficit five or six days a week without interruption.
So which one should you do?
If you're choosing purely on calories-per-minute, running wins the argument and loses the war. The number on your watch after one session tells you almost nothing about what you'll look like in three months, because what you'll look like in three months is a function of total consistent volume, not peak efficiency per session.
Every version of "cycling vs running for weight loss" collapses to the same answer: whichever one you will actually do, five or six days a week, without getting hurt. For most people past their mid-thirties, carrying some old niggle or simply short on recovery capacity, that's the bike. Not because it burns more per minute — it doesn't — but because it lets you show up again tomorrow.
If you're making that switch and want a structured way to train consistently instead of guessing at volume and intensity, the Roadman community is built for exactly this stage — riders coming from other sports, building a sustainable engine instead of chasing a single big session.