Walking calorie calculator
A 70 kg walker at 12 minutes per kilometre covers 5 km in 60 minutes at 5 km/h and burns about 248 kcal on flat ground. Enter weight, pace and distance or time to plan a walk. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Weight
- 70
- Pace
- 12
- Distance
- 5
- Weight unit
- Kg
- Weight (kg)
- 70
- Distance unit
- Km
- Distance km
- 5
This walking calorie calculator estimates how many kilocalories you burn on a flat walk from three practical inputs: body weight, walking pace, and either distance or duration (or both). Pace is minutes per kilometre or per mile, which the engine converts into speed, ACSM walking oxygen cost, metabolic equivalent (MET), and total calories. For a familiar check, a seventy-kilogram walker at twelve minutes per kilometre over five kilometres spends sixty minutes at five kilometres per hour and burns roughly two hundred forty-eight kilocalories under the flat-ground model used here. The arithmetic is fully deterministic finite math with no network calls, no sampling, and no date-dependent shortcuts.
Where walking calorie estimates fit in coaching, products, and study
Coaches and clients use a transparent bout estimate before they adjust for hills, pack weight, heat, or recovery. App builders map a walk form into log entries without shipping opaque calculator code that drifts between platforms. Students and exercise-science trainees check textbook examples that assume flat ACSM walking VO2 and need a fast, offline source of kilocalories and MET.
Product and education tools use the same contract when a learner types seventy kilograms, twelve minutes per kilometre, and five kilometres and the UI must show duration, speed, MET, and calories beside the inputs. Extreme paces outside everyday walking bands are rejected rather than silently extrapolated into running territory, so the UI can prompt for a realistic walk pace.
Pair it with pace converters, deficit planners, or heart-rate tools when you are building a small lab of free, deterministic health helpers, and always treat the output as a planning estimate rather than a clinical prescription.
What you can do with it
Route and bout planning
Estimate kilocalories for a known walk distance or time at your usual pace and body weight before you head out.
Fitness apps and coaching logs
Generate reproducible walking-calorie figures for workout logs, onboarding defaults, and client plan worksheets.
FAQ
What does the walking calorie calculator cost?
It is free in your browser on this page.
How are calories calculated?
Pace becomes speed; ACSM flat walking VO2 is 0.1×speed in m/min plus 3.5; kilocalories equal VO2×weight in kg×minutes divided by 200.
What happens if weight is zero or negative?
Non-positive weight cannot define a meaningful energy estimate.
Do I need both distance and duration?
No. Provide at least one; the missing value is derived from pace. If you send both, both are kept and speed still comes from pace.
Does this account for hills or carrying a pack?
No. The model is flat-ground ACSM walking only. Grade, load, and running are out of scope for this tool.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/health/walking-calories \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"weight":70,"pace":12,"distance":5}'const res = await fetch("https://api.kit.forhosting.com/health/walking-calories", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"weight": 70,
"pace": 12,
"distance": 5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/walking-calories",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"weight": 70,
"pace": 12,
"distance": 5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/walking-calories", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"weight":70,"pace":12,"distance":5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"weight":70,"pace":12,"distance":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/walking-calories", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"weight": 70,
"pace": 12,
"distance": 5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.walking_calories",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_weight | 500 |
max_distance | 1000 |
max_duration_min | 1440 |
max_pace_min | 120 |
min_pace_min | 5 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
What the walking calorie estimate returns and how to read it
Walking energy cost rises with body mass, time on feet, and speed. This calculator does not invent a lifestyle profile from age or sex; you supply the weight you want to model, the pace that matches how you walk, and either how far or how long the bout is. Internally, pace becomes speed, speed becomes walking VO2 with the American College of Sports Medicine flat-ground equation, VO2 becomes MET by dividing by three point five, and calories follow from oxygen cost times weight times minutes using the usual five kilocalories per liter of oxygen conversion. The response echoes normalized weight and units, weight in kilograms, pace, distance in the chosen unit and in kilometres, duration in minutes, speed in kilometres per hour and miles per hour, VO2 in millilitres per kilogram per minute, MET, calories in kilocalories, a method tag acsm_walking_flat, a short formula string, and the decimal precision used. There is no machine-learning path and no random sampling: either the finite arithmetic succeeds inside the documented limits or the request fails with invalid_input. Rejected cases include missing weight or pace, missing both distance and duration, non-finite values, values above the documented ceilings, non-positive distance or duration, impossible pace bands, and any non-positive weight, because a non-positive mass cannot define a meaningful energy estimate. If you need calorie deficit planning, cycling power, or heart-rate zones, pair this page with those dedicated tools; this landing answers only walking bout energy with stable numeric output for worksheets, product UIs, and API consumers that must not invent adaptive models.
How weight, pace, distance, and duration are read and kept reproducible
Optional leading plus signs and scientific notation on numeric strings are allowed when they parse as finite decimals; embedded spaces, hex prefixes, and non-numeric tokens are rejected with a clear message so a bad cell does not become a wrong calorie total. The preferred fields are weight for body mass, pace for minutes per unit distance, distance for bout length in space, and duration_min for bout length in time. At least one of distance or duration_min is required; when only one is present, the other is derived from pace so the response always includes both. Aliases such as body_weight, mass, pace_min, minutes_per_unit, dist, duration, minutes, and time_min are accepted so spreadsheets, query strings, and typed forms can reuse one contract. Optional weight_unit defaults to kilograms and also accepts kg, kilogram, lb, lbs, pound, and pounds. Optional distance_unit defaults to kilometres and also accepts km, kilometer, mi, mile, and miles; pace is always interpreted as minutes per that same distance unit, so twelve with km means twelve minutes per kilometre while twelve with mi means twelve minutes per mile. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose, defaulting to two and capped at fifteen so JSON goldens stay stable. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing the walking formulas yourself.
Where walking calorie estimates fit in coaching, products, and study
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result.
Integration use cases
Deterministic test fixtures
Seed CI and unit tests with fixed calories_kcal, MET, and VO2 from the ACSM flat walking model.