ToolJutsu
All tools
Calculator Tools

Running Calorie Calculator

Estimate calories burned per run from weight, pace, and distance using METs methodology.

Weight unit
Distance unit
How will you specify intensity?
Terrain

Calories burned

610 kcal

10.3 METs

Per km

76 kcal/km

Total energy per km

Per mile

122 kcal/mi

Total energy per mile

Run details

  • Speed10.2 km/h (6.3 mph)
  • Pace9:30 min/mi
  • Duration47 min 30 sec
  • Terrain factor×1.00

Individual variation in running economy, VO₂ max, gear and weather can shift the actual burn by ±20 % from this estimate. Use as a planning figure, not a precise meter.

5 mi at 9:30 min/mi: 610 kcal burned (10.3 METs × 74.8 kg × 0.79 h, flat terrain).

Processed on your device. We never see your files.

How to use Running Calorie Calculator

What this calculator does

This calculator estimates the calories burned during a run using the standard METs methodology from the Compendium of Physical Activities. Enter your weight, the distance you ran, your pace or total time, and whether the terrain was flat or hilly. The tool returns total kcal burned, plus per-km and per-mile breakdowns and a detailed view of the speed, pace and METs value used.

All math is plain arithmetic running locally on your device.

How METs methodology works

The Metabolic Equivalent of Task (METs) is the standard unit for expressing the energy cost of physical activities. 1 MET = the energy cost of sitting at rest, roughly 1 kcal per kg of body weight per hour. Higher-intensity activities are quoted as multiples:

  • Walking at 5 km/h: ~3 METs
  • Light jogging at 8 km/h: ~8.3 METs
  • Moderate run at 10 km/h: ~9.8 METs
  • Brisk run at 12 km/h: ~11.5 METs
  • Fast run at 14.5 km/h: ~14.5 METs
  • Elite pace at 17-19 km/h: ~18-20 METs

Calories burned = METs × weight (kg) × hours. So a 70 kg runner at 9.8 METs for 1 hour burns 686 kcal. A 90 kg runner at the same pace for the same time burns 882 kcal. Weight scales the burn linearly.

This calculator’s METs values come from the 2011 Compendium of Physical Activities (Ainsworth et al.), the standard reference used by fitness trackers, the ACSM (American College of Sports Medicine), and most exercise-physiology textbooks. METs values for paces between table rows are linearly interpolated.

Why the ±20 % uncertainty?

The METs methodology produces a population-average energy cost. Real individuals vary widely from this average for several reasons:

Running economy — VO₂ at submaximal speeds — varies by 20-30 % across runners of similar fitness. An efficient runner at 5 min/km uses noticeably less oxygen than a less-economic runner at the same pace. METs values assume average efficiency.

Body composition — at the same total weight, two runners with different muscle-to-fat ratios will burn different amounts of energy per kilometre. Muscle costs more to move than fat per unit of weight.

Environmental conditions — running in heat raises HR and energy cost (sweat production alone uses calories). Running in cold lowers it slightly. Running into wind is meaningfully more demanding than the same pace in still air. The calculator doesn’t know any of these.

Equipment — heavy shoes, hydration vest, layers — adds dead weight that scales the calorie burn. A 70 kg runner with a 4 kg vest burns ~6 % more than the same runner without it.

Hydration and fueling state — dehydration raises cardiac strain; glycogen-depleted runs (fasted morning) shift metabolism toward fat oxidation but don’t change total kcal much.

Net of all these: a 500 kcal estimate could be anywhere from 400 to 600 kcal in reality. The estimate is most useful for comparing across your own runs (relative differences hold up) and for rough food-intake planning, not as an exact meter.

Per kilometre vs per mile vs per minute

The relationship between pace and calorie burn looks different depending on which unit you read:

  • Per minute of running: faster paces burn more (higher METs per minute). A 6:00/km pace burns more per minute than a 7:00/km pace.
  • Per km or per mile: slower paces burn slightly more per unit of distance (because they take more time at lower METs, and the METs difference is less than the time difference). A 6:00/km pace burns less per km than a 4:00/km pace, but covers ground in less time so total kcal per km is similar.

For weight management, total distance × calories-per-km is the main lever. Doubling your weekly mileage roughly doubles your weekly running calorie burn, regardless of how you split it between fast and slow runs.

Comparing running to other activities

Rough METs values for common cardio at moderate intensity:

  • Walking 5 km/h: 3.0 METs
  • Cycling 16-19 km/h (moderate): 6.8 METs
  • Swimming (moderate): 6.0 METs
  • Elliptical (moderate): 5.0 METs
  • Rowing (moderate): 7.0 METs
  • Running 10 km/h: 9.8 METs

Running is one of the highest-METs continuous activities a typical person can sustain, which is why it punches above its weight for calorie burn relative to time spent.

Privacy

The calculator runs JavaScript arithmetic on your device — METs lookup, weight conversion, pace conversion, simple multiplication. Weight, distance, pace, terrain — every value stays in your browser tab. No fetch calls, no analytics on your fitness data, no server-side logging.

Frequently asked questions

How accurate is the calorie estimate?
±20 % for an individual, even with perfect inputs. The METs methodology produces a population-average estimate at each pace and weight. Individual variation in running economy (VO₂ at submaximal speeds), VO₂ max (aerobic capacity), gait efficiency, gear weight, weather (heat raises burn; cold lowers it), and hydration state all push the actual burn away from the population average. The estimate is best used for comparing across runs (your half-marathon vs your 5K) or rough food-intake planning, not as a literal kcal meter. For higher precision, a heart-rate-strap-based estimator that accounts for your individual HR-vs-VO₂ relationship is better; a metabolic chest mask is best.
Does the calculator account for the 'afterburn' effect?
No. The calculator estimates calories burned during the run only. The 'afterburn' (post-exercise excess oxygen consumption, EPOC) — your elevated metabolic rate for hours after a hard run — adds 5-15 % to total energy expenditure for a typical aerobic run, more for interval/HIIT sessions. The numbers shown above are conservative for steady-state running; for high-intensity intervals you can add 10-20 % to account for EPOC. The companion TDEE Calculator in our suite handles the all-day energy expenditure picture if you want the bigger frame.
Why does pace matter so much?
Because running economy is roughly linear in speed. At 6 min/km (~10 min/mi), you're at ~10 METs. At 4 min/km (~6:30 min/mi), you're at ~14 METs — 40 % more energy per kg per hour. Faster paces burn more calories per minute, but per kilometre or per mile the relationship is flatter because faster paces cover the same distance in less time. A 10K at 5 min/km burns ~600 kcal; at 4 min/km it burns ~700 kcal — a 17 % difference in total kcal for a 25 % difference in pace. If your training goal is total energy burn (e.g. weight management), longer runs at moderate pace are more efficient than short intense runs.
How does terrain affect the burn?
Hilly terrain raises energy cost by roughly 10-20 % for moderate grade (rolling hills), 30-50 % for sustained climbing (mountain trails with significant elevation gain). This calculator applies a flat 10 % uplift for the 'hilly' selection — a midpoint reasonable for typical hilly park trails or suburban undulations. For a trail-running calorie estimate with significant climbing, multiply by a higher factor (1.2-1.4) yourself. Note that the energy benefit doesn't fully reverse on downhills — you spend more energy on eccentric muscle contraction descending steep grades than going flat — so hilly runs net more calories than the simple grade math suggests.
Is my fitness data sent anywhere?
No. The calculator runs as JavaScript arithmetic on your device — METs lookup, weight conversion, pace conversion, multiplication. Weight, distance, pace, terrain — every value stays in your browser tab. No fetch calls, no analytics on your fitness data, no server-side logging.

Related tools