TL;DR
- For a 75 kg adult walking 45 minutes at brisk pace (MET 3.5) with the "slight" incline multiplier (1.2×), the Walking Calorie engine returns 236.3 kcal (5.25 kcal/min).[4]
- The Treadmill Pace Converter at 10 kph with 3% incline returns 778 kcal/hour (583.7 kcal over 45 min) — far above walking, because 10 kph is jog territory and the incline raises the effective speed to 11.35 kph.
- The generic Calories Burned engine at 9.8 MET / 30 min / 78 kg returns 401.3 kcal for a running session — about 2.5× the per-minute rate of brisk walking.[1]
- The engines agree on the formula; they disagree on the MET (and speed/incline) assumption baked into each activity label, which is the practical source of the hidden disagreement.
Walking calorie math looks easy but routinely produces wildly different numbers across engines. The disagreement is rarely in the formula — it is in the MET assumption baked into "walking." This article runs the same 75 kg adult through three engines and shows where the calorie estimates diverge and which one is right for each use case.
Scenario inputs
weight_kg: 75
duration_min: 45
activity: walking, brisk
treadmill_speed: 10 kph (jog, for comparison)
incline_percent: 3Engine outputs
Walking Calorie Calculator
calories: 236.3
caloriesPerMinute: 5.25
met: 3.5 (brisk walk)
inclineMultiplier: 1.2 ("slight")
durationHours: 0.75
foodEquivalents:
Medium banana: 2.3
Slice of pizza: 0.8
Chocolate chip cookie: 1.5MET-based: 3.5 METs × 75 kg × 0.75 h = 196.9 kcal at flat. Apply the 1.2 "slight" incline multiplier: 196.9 × 1.2 = 236.3 kcal. The 3.5 MET assumption corresponds to brisk walking (4–5 kph) per the Ainsworth Compendium.[1]
Treadmill Pace Converter
speedKph: 10
paceMinPerKm: 6:00
adjustedPaceMinPerKm: 5:17 (with 3% incline)
adjustedSpeedKph: 11.35
caloriesPerHour: 778.2
caloriesTotal: 583.7 (45 min)
durationMinutes: 4510 kph is well above walking pace — the engine treats this as a jog/run session. The 6:00/km flat pace adjusts to a 5:17/km flat-equivalent (effective 11.35 kph) under the 3% incline, reflecting the metabolic cost of climbing.[2]
Calories Burned Calculator (running, MET 9.8)
primaryValue: 401.31 (kcal, for 30 min)
caloriesPerHour: 802.62
met: 9.8
durationMin: 30
incline: 0%Same 9.8 MET running session for a 78 kg subject — 401.31 / 30 = 13.38 kcal/min, about 2.5× the per-minute rate of brisk walking (5.25 kcal/min). The MET difference (3.5 walk vs 9.8 run) is the load-bearing parameter. (The engine uses the standard metabolic equation, MET × 3.5 × kg / 200 × minutes; there is no extra "efficiency" multiplier.)
Reading the calories
Walking 45 min at MET 3.5: 236.3 kcal. Treadmill jogging 45 min at 10 kph / 3% incline: 583.7 kcal. Running 30 min at MET 9.8: 401.3 kcal. The numbers tell a coherent story when you read the speed and MET load rather than the activity labels — the treadmill session burns most because it is the longest (45 min) at a brisk jog with an incline.
Where the "300 kcal hides" framing in the title points: it's the MET assumption gap. A "walking" session with steep incline and brisk pace can easily reach MET 5–6, producing 320–380 kcal/45 min — well above the engine's default. A "treadmill" session at a slow pace can sit at MET 4 (essentially walking on a moving belt), producing similar numbers to outdoor brisk walking.
Where the engines disagree
MET assumption for "walking"
The Walking Calorie engine defaults to MET 3.5 for brisk walking. The generic Calories Burned engine exposes the MET as an input, so you choose. The treadmill engine maps pace and incline onto MET via published curves. Three engines, three implicit MET assumptions — and 300 kcal of difference depending on which assumption you accept.
Incline math
The Walking Calorie engine uses a 1.2× multiplier at 3% incline. The treadmill engine uses a published per-percent-incline correction (~6% caloric increase per 1% grade for walking pace). For 3% incline, the corrections are equivalent (1.2 vs 1.18). Above 5% incline, the two engines diverge: the walking engine's multiplier scales linearly while the treadmill engine's curve flattens slightly at high grades.[2]
Overground vs treadmill
The literature notes a small difference between treadmill and overground walking at the same speed (the moving belt changes the work slightly). Neither engine models this overground/treadmill offset explicitly: the Treadmill Pace Converter computes calories from the ACSM walking/running VO2 equation given speed and grade, while the Walking Calorie Calculator uses fixed MET tiers by pace. The practical gap between them comes from speed and incline, not a belt-vs-ground correction.[3]
When to use which
- Casual walking session, outdoor, simple input: Walking Calorie Calculator. Accept the MET 3.5 default for brisk pace.
- Treadmill at known speed/incline: Treadmill Pace Converter. Pace and grade map cleanly onto calorie estimate.
- Custom activity outside the walking defaults: Calories Burned Calculator with explicit MET input. Best when the activity isn't standard walking.
- Converting calorie targets to time: Use the engine's reverse direction (kcal target ÷ kcal/min = required minutes).
The MET cheat sheet
Published MET values for the most common activities at typical recreational pace:
Activity MET kcal/min for 75 kg subject
─────────────────────────────────────────────────────────────────
Slow walk (3 kph) 2.5 3.13
Brisk walk (4-5 kph) 3.5 4.38
Power walk (6 kph) 4.3 5.38
Walk with backpack (>10 kg) 5.5 6.88
Jog (8 kph) 7.0 8.75
Easy run (10 kph) 9.8 12.25
Tempo run (12 kph) 11.5 14.38
Race pace 5K (15+ kph) 14.0 17.50Same body, very different calorie rates. The "300 kcal target" requires roughly 96 minutes of slow walking, 68 minutes of brisk walking, 34 minutes of jogging, or 21 minutes of tempo running. The activity label matters less than the MET load it implies.[1]
Practical takeaway from the MET table: doubling the calorie burn per minute costs more than doubling the activity intensity, so very small upgrades in pace (from 4 kph to 6 kph) produce surprisingly large per-minute calorie improvements without large changes in perceived effort.[1]
Cross-checking against related tools
The Walking Calorie Calculator handles the default walking case with incline support. The Treadmill Pace Converter adds pace and grade as inputs. The Calories Burned Calculator accepts arbitrary MET inputs for non-walking activities. The Food to Exercise Converter works the other direction — convert a food's calorie load into minutes of various activities.
Related reading: How To Break A Weight Loss Plateau for the calorie-deficit-versus-activity-volume trade-off, TDEE For Athletes for the larger calorie-budgeting framing, and How To Count Macros for converting calorie burn into intake adjustments.
FAQ
Does walking really only burn 5 kcal/min?
At brisk pace (4–5 kph, MET 3.5) for a 75 kg adult, yes — within ±15% individual variation. Heavier subjects burn more (linearly with body weight). The published walking-MET tables are anchored on average-pace recreational walking; faster or hillier walking pushes the MET higher.[1]
Why does the treadmill engine return more calories than the walking engine?
Mostly because of the inputs, not a hidden multiplier. The Treadmill Pace Converter at 10 kph / 3% incline computes calories from the ACSM running/walking VO2 equation, which puts a 10 kph jog far above brisk walking. The Walking Calorie Calculator uses fixed MET tiers (3.5 for brisk) and a coarse incline multiplier. Feed both the same speed and grade and they converge; the difference here is that 10 kph is a jog, not a walk.[3]
How accurate is the incline multiplier?
For grades under 6%, the linear 1.2× per 3% rule is within ±5% of the more granular curves. Above 6%, the curves flatten and the linear multiplier over-states the calorie cost by 5–10%. For very steep walks (10%+), use the Treadmill Pace Converter rather than the Walking Calorie Calculator.[2]
Should I trust my fitness tracker over the engine?
Generally no for absolute calorie counts. Consumer wrist-tracker calorie estimates run 15–35% high against doubly-labelled-water validation. The engine's MET-based approach is more conservative and closer to validated values. Use the tracker for relative (this week vs last week) trend; use the engine for absolute calorie budgeting.
References
- 1 Compendium of Physical Activities and MET intensity ratings — Medicine and Science in Sports and Exercise (Ainsworth et al.) (2000)
- 2 Energy cost of walking at different speeds and gradients — European Journal of Applied Physiology (2004)
- 3 Compendium update with treadmill vs overground walking adjustments — Medicine and Science in Sports and Exercise (Ainsworth et al.) (2011)
- 4 Methodology notes for the Walking Calorie Calculator — AI Fit Hub (2026)