Running a marathon burns roughly 2,200 to 3,200 calories for most people, with the biggest variables being your body weight and pace. A 155-pound runner finishing in about 4 hours will burn around 2,500 calories, while a 200-pound runner covering the same distance burns closer to 3,200. That’s the equivalent of an entire day’s worth of food for many adults, consumed in a single effort.
How the Calorie Estimate Works
The most reliable way to estimate calorie burn during running uses a system called METs (Metabolic Equivalents of Task), which measures how much energy an activity requires compared to sitting still. Running at different speeds carries different MET values: a 12-minute mile pace scores 8.5 METs, a 10-minute mile pace hits 9.3, an 8.5-minute mile jumps to 11.0, and a 7.5-minute mile reaches 12.0.
The formula multiplies your MET value by your body weight in kilograms and the number of hours you’re running. This means two things matter enormously: how much you weigh and how long you’re out there. A heavier runner burns more calories per mile because it takes more energy to move more mass over the same distance. And a slower runner, while burning fewer calories per minute, spends more total time on the course.
Here’s what that looks like in practice for a few common body weights at a 10-minute mile pace (about a 4:22 marathon):
- 130 lbs (59 kg): approximately 2,400 calories
- 155 lbs (70 kg): approximately 2,850 calories
- 180 lbs (82 kg): approximately 3,300 calories
- 200 lbs (91 kg): approximately 3,700 calories
Why Pace Changes the Number Less Than You’d Think
A common assumption is that faster runners burn dramatically more calories. They do burn more per minute, but they also finish sooner. A runner completing a marathon at an 8.5-minute mile pace (about 3:42 finish) is working at 11.0 METs but running for roughly 3 hours and 42 minutes. A runner at a 12-minute mile pace works at 8.5 METs but runs for over 5 hours. The slower runner actually burns a comparable total because the extra time on the course compensates for the lower intensity.
For a 155-pound person, the difference between a 3:42 marathon and a 5:14 marathon is only about 300 to 400 calories in total burn. Body weight is by far the more powerful variable.
Why Men and Women See Different Numbers
If you’ve ever compared calorie counts with a running partner of a different sex, you’ve probably noticed a gap. Men burn more calories during the same run, and the reason is largely about body composition. Men carry more muscle mass on average, and muscle tissue is more metabolically expensive to fuel than fat tissue. National health survey data shows men average 23 to 31 percent body fat depending on age, while women average 32 to 42 percent.
Higher muscle mass also drives a higher resting metabolic rate, which means men are burning more calories even before they start running. During exercise, testosterone-driven differences in muscle fiber density amplify the gap further. The standard calorie prediction formulas used by exercise scientists include sex as a variable for exactly this reason. For two people of identical weight running the same pace, the male runner will typically burn 10 to 15 percent more calories over a full marathon.
Hills Can Increase the Burn Significantly
A flat marathon and a hilly one are not the same workout. Research published in Frontiers in Physiology measured oxygen consumption (a direct proxy for calorie burn) at different grades and found that running uphill dramatically increases energy cost. On flat ground, runners consumed about 40 milliliters of oxygen per kilogram per minute. At a 5 percent uphill grade, that jumped to 47, an 18 percent increase. At a 10 percent grade, it reached 54, a 34 percent increase over flat running.
Downhill sections don’t fully offset the extra cost of climbing. Running at a negative 5 percent grade used only about 33 ml/kg/min, which is less than flat running, but the savings on the downhills are smaller than the extra cost on the uphills. A net-downhill course like Boston still has enough climbing to push total calorie burn above what you’d see on a pancake-flat course like Chicago or Berlin. If your marathon has significant elevation gain, expect your total burn to land toward the higher end of the range.
Fueling During the Race
Burning 2,500 to 3,200 calories over several hours creates a fueling challenge your body can only partially solve in real time. Your muscles store roughly 1,500 to 2,000 calories worth of glycogen (stored carbohydrate), which means you’ll run out before the finish line unless you take in fuel along the way. This is the physiological basis of “hitting the wall,” usually somewhere around mile 18 to 22.
The general guideline is to consume 60 to 90 grams of carbohydrates per hour during the race, which translates to roughly 240 to 360 calories per hour. That won’t replace everything you’re burning, but your body can also tap into fat stores for a portion of the energy. The limiting factor isn’t your muscles’ demand for fuel but your gut’s ability to absorb it. Your intestines can transport about 60 grams of glucose per hour, so getting above that threshold requires mixing in other carbohydrate types like fructose.
In practical terms, one energy gel every 20 to 30 minutes plus some calories from a sports drink keeps most runners in the right range. Elite marathoners often push intake to 120 grams per hour, but this requires trained gut tolerance that most recreational runners haven’t built up. Starting with a gel every 30 minutes and experimenting in training is the standard approach.
What Calorie Trackers Get Wrong
GPS watches and fitness trackers estimate marathon calorie burn using your heart rate, pace, weight, and age. These estimates are useful as ballpark figures, but they consistently overestimate by 15 to 30 percent in most studies. Heart rate, which many devices rely on heavily, is influenced by heat, dehydration, caffeine, and fatigue in ways that inflate the reading without reflecting extra calorie burn.
The MET-based calculation described above is generally more accurate for steady-state running like a marathon, because it’s grounded in direct measurements of oxygen consumption at specific speeds. If your watch says you burned 3,500 calories, the true number is likely closer to 2,800 to 3,000. This matters if you’re using the data to plan post-race recovery meals or to calculate how much fuel you need for your next race.