Running burns more calories than cycling at comparable effort levels, but the gap narrows or disappears as cycling intensity increases. A 155-pound person running at 6 mph burns about 704 calories per hour, the same as cycling at 14 to 16 mph. At moderate effort, running at 5 mph and cycling at 12 to 14 mph both burn roughly 563 calories per hour. The real difference comes down to how hard you push and how long you can sustain it.
Calorie Burn at Every Speed
The most reliable way to compare these two activities is through metabolic equivalents (METs), a standardized measure of energy cost. Running produces higher MET values at nearly every comparable speed. A 5 mph jog scores 8.3 METs, while leisurely cycling at 9.4 mph scores just 5.8. Bump running up to 6 mph and you hit 9.8 METs. To match that on a bike, you need to ride at 14 to 16 mph, which scores 10.0 METs.
At the high end, the picture shifts. Racing-pace cycling above 20 mph reaches 15.8 METs, comparable to running at 10 mph (14.5 METs). But most recreational cyclists cruise at 12 to 14 mph, which produces 8.0 METs. Most recreational runners settle around 5 to 6 mph, producing 8.3 to 9.8 METs. For the average person doing a moderate workout, running wins by roughly 20 to 30 percent per minute.
Why Running Burns More Per Minute
The core reason is simple: running is a weight-bearing activity. Every stride forces your body to support and propel your full weight against gravity. On a bike, the seat and frame carry most of your weight, and the wheels handle forward momentum efficiently. Cycling is, by design, the most mechanically efficient form of human-powered movement. That efficiency is great for transportation but works against you when the goal is burning calories.
Running also demands more from your muscles in a way that costs extra energy. When you run, your muscles perform both concentric contractions (pushing off the ground) and eccentric contractions (absorbing impact on landing). The activation level of muscles during those eccentric contractions is higher than during the pushing phase. Cycling involves only concentric contractions, the pushing-down motion on the pedals. That difference in muscle recruitment means running creates more microscopic muscle damage per session, which requires more energy to perform and to recover from.
The Afterburn Is Similar
You might wonder whether one activity creates a bigger “afterburn,” the extra calories your body uses after exercise to recover. Research comparing matched bouts of cycling and running found no meaningful difference. In one study, post-exercise calorie burn was 53.7 kilojoules after cycling and 61.5 kilojoules after running, a gap that was not statistically significant. The afterburn accounted for about 44 to 49 percent of total recovery energy in both activities. So if you’re choosing between the two based on what happens after the workout, it’s essentially a wash.
Why Total Burn Often Favors Cycling
Here’s where the comparison gets interesting. Running burns more per minute, but most people can’t run as long as they can ride. Cycling’s lower impact means your joints, tendons, and muscles can handle far more volume. A typical runner might do 30 to 45 minutes comfortably. A cyclist can easily ride for 90 minutes to two hours at a similar perceived effort.
Experienced exercisers consistently report needing about twice the time on the bike to match the training effect of a run. A 35-minute run at moderate pace produces roughly the same physiological stress as a two-hour easy bike ride. If you have the time, that longer cycling session can match or exceed the total calorie burn of a shorter run. A 155-pound person cycling at moderate effort for two hours burns over 1,100 calories, more than the 704 they’d burn running at 6 mph for one hour.
The injury math matters too. Running’s repetitive impact limits how many sessions per week your body can handle, especially if you’re new to it. Cycling lets you train more frequently without the same breakdown risk, which can add up to more total weekly calorie expenditure even if each minute on the bike burns less.
Intensity Changes the Equation
At high intensities, the calorie gap between cycling and running shrinks dramatically. A vigorous cycling session at 16 to 19 mph hits 12.0 METs, matching or exceeding a 7.5 mph run (11.5 METs). If you’re willing to push hard on a bike, particularly through interval training, you can match running’s calorie burn minute for minute.
High-intensity interval training on a bike is particularly effective. Research comparing sprint intervals to sustained high-intensity efforts on a cycle ergometer found that the high-intensity interval approach burned about 209 calories per session while feeling easier than the sprint protocol, which burned 194 calories. The takeaway: structured hard efforts on the bike can close the calorie gap with running while feeling more manageable.
Which One Should You Choose
If your only goal is burning the most calories in the least time and your body can handle the impact, running is more efficient. A 30-minute run at moderate pace burns roughly the same as a 45 to 60-minute bike ride. For people who are short on time, running delivers more bang per minute.
If you have joint concerns, prefer longer sessions, or simply enjoy cycling more, you can absolutely match running’s calorie burn by riding longer or harder. A cyclist doing three 90-minute rides per week at moderate effort burns more total calories than a runner doing three 30-minute jogs.
The activity you’ll actually do consistently matters more than the one that scores higher on a MET chart. A person who loves cycling and rides five days a week will burn far more calories over a year than someone who dreads running and skips half their sessions. Both activities comfortably meet the recommended threshold of 150 minutes of moderate aerobic activity per week, and both can be scaled up to whatever calorie target you’re chasing.