Steps to calories calculator
10,000 steps at 70 kg with a 0.76 m stride come to about 382.375 kcal over 7.6 km: the calculator turns your step total into distance, walking time and energy. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Weight
- 70
- Stride
- 0.76
- Calories burned
- 382.375 kcal
- Calories kcal
- 382.375
- Weight unit
- Kg
- Weight (kg)
- 70
Phone and pedometer totals count footfalls, not energy. This steps to calories calculator converts a step count into estimated kilocalories from the three numbers a walker already has: how many steps, body weight, and stride length. Distance is steps times stride in metres. Duration follows from a documented moderate walking speed of 4.8 kilometres per hour, which is 80 metres per minute. Kilocalories then come from the ACSM flat-ground walking identity: oxygen cost VO2 equals 0.1 times that speed plus 3.5 millilitres per kilogram per minute, and kcal equals VO2 times kilograms times minutes divided by 200.
What the steps to calories calculator measures and how the formula works
A step counter answers how many times the foot struck the ground. Calories answer how much energy that bout cost, which depends on how far those steps carried you and how heavy the body that carried them is. This calculator multiplies the step count by stride length to recover distance in metres, then treats the bout as a moderate walk at 80 metres per minute (4.8 kilometres per hour, about three miles per hour).
That speed is not a hidden guess: it is the ACSM walking band used when duration is not an input, so two people with the same steps, weight, and stride always get the same kilocalorie figure. Oxygen cost on level ground is VO2 equals 0.1 times speed in metres per minute plus 3.5, which at 80 metres per minute is 11.5 millilitres per kilogram per minute.
Kilocalories equal that VO2 times body mass in kilograms times duration in minutes divided by 200, because each litre of oxygen is taken as five kilocalories. Example: ten thousand steps at seventy kilograms with a 0.76 metre stride cover 7.6 kilometres in ninety-five minutes and burn 382.375 kilocalories under this model. The metabolic equivalent is VO2 divided by 3.5, about 3.29 MET, which is a typical moderate walk rather than a run.
Stride may arrive in metres, centimetres, inches, or feet; weight may arrive in kilograms or pounds. The engine converts to metres and kilograms before the identity runs, then echoes both the caller units and the SI values so a log can be audited.
When turning steps into calories is useful
Wearable dashboards and phone health apps already store a daily step total, a profile weight, and often a calibrated stride. Turning those three numbers into a documented kilocalorie figure is the search people type as steps to calories, not walking calories from a mapped GPS distance and not steps to distance with no energy at all. Coaching products that set a ten-thousand-step goal can show the energy that goal represents at each athlete's mass and stride without reverse-engineering a vendor console.
Nutrition coaches combining food logs with pedometer weeks want a published ACSM walking identity rather than an opaque firmware guess that drifts between watch revisions. Classroom labs assign homework that multiplies steps by stride, derives minutes at 80 metres per minute, and checks 382.375 kilocalories for ten thousand steps at seventy kilograms and 0.76 metres, and they see a hard error when the step count is zero instead of a silent rest. Failed validation does not consume balance.
Keep the step total, the weigh-in, and the stride from the same bout — do not mix a weekly tally with last year's inseam — and you get a reproducible kilocalorie figure for dashboards, LMS quizzes, and edge workers without standing up a metabolic cart of your own. Treat distance-only conversion, pace-based walking calories, running, cycling, swimming, elliptical, and standing as separate product intents rather than overloading this landing with every related sports formula.
What you can do with it
Pedometer and phone step logs
Turn a daily step total, profile weight, and calibrated stride into a kilocalorie estimate for a journal or wellness dashboard without asking the user for pace or GPS distance.
FAQ
How do I convert steps to calories?
Distance is steps times stride. Kilocalories follow the ACSM walking identity at 80 metres per minute.
Which walking speed is assumed?
A moderate walk of 80 metres per minute, which is 4.8 kilometres per hour, about three miles per hour. Duration is distance divided by that speed so the same steps, weight, and stride always match.
What happens if the step count or weight is zero or negative?
Step count and body weight must be positive numbers; non-positive values are rejected and not charged.
Can I send weight in pounds and stride in inches?
The engine converts to kilograms and metres, then echoes both the caller units and the SI values.
How far do 10,000 steps take me?
Multiply your steps by your stride length. With a 0.76 m stride, 10,000 steps cover 7.6 km, which at the assumed walking pace of 4.8 km/h takes 95 minutes.
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/sports/steps-to-calories \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"steps":10000,"weight":70,"stride":0.76}'const res = await fetch("https://api.kit.forhosting.com/sports/steps-to-calories", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"steps": 10000,
"weight": 70,
"stride": 0.76
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/sports/steps-to-calories",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"steps": 10000,
"weight": 70,
"stride": 0.76
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/sports/steps-to-calories", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"steps":10000,"weight":70,"stride":0.76}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"steps":10000,"weight":70,"stride":0.76}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/sports/steps-to-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
{
"steps": 10000,
"weight": 70,
"stride": 0.76
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "sports.steps_to_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_steps | 1000000 |
max_weight_kg | 500 |
max_stride_m | 3 |
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
Zero or negative step counts or body weights fail as invalid_input rather than a silent zero. Successful API calls use prepaid KIT balance at $0.002 per item; validation failures are not billed.
What the steps to calories calculator measures and how the formula works
Identical inputs always yield identical JSON because the algorithm never touches the network, a model, a clock, or a random generator.
Input contract, response shape, and error behaviour
Step count and body weight must be strictly positive: zero or negative values are rejected because a calorie estimate cannot be built from a non-physical tally or a non-physical mass, and those failures are not billed. Stride must also be positive. Steps above one million, mass above five hundred kilograms, and stride above three metres are rejected as out of range so a typo cannot produce an absurd total. Wire the free browser form for a personal step log or a classroom demo, then call the identical contract from scripts when you need bulk estimates. Do not treat the figure as a medical diagnosis or lab-grade calorimetry: grade, load carriage, and individual economy all move real expenditure. POST a JSON body with three required finite positive numbers: steps, the pedometer or phone total; weight, body mass in weight_unit (kilograms by default); and stride, step length in stride_unit (metres by default). Each numeric field may arrive as a JSON number or as a numeric string. Aliases step_count, n_steps, and count are accepted for the tally; aliases weight_kg, body_weight, mass, bodyweight, and kg are accepted for mass; aliases stride_length, stride_m, step_length, and pace_length are accepted for stride. Optional weight_unit is kg or lb; optional stride_unit is m, cm, in, or ft. Missing fields, empty strings, NaN, Infinity, and non-numeric text fail with invalid_input naming the field. On success the body includes calories_burned and calories_kcal as the same cleaned total in kilocalories, unit set to kcal, the cleaned steps, weight, weight_unit, weight_kg, stride, stride_unit, stride_m, distance in metres, kilometres, and miles, duration_min at the assumed 80 metres per minute, speed_kmh of 4.8, vo2_ml_kg_min, met, plus a formula string documenting the ACSM identity and method acsm_walking_from_steps. Successful API calls use prepaid KIT balance at the published $0.002 base price per item; validation failures do not consume balance.
Integration use cases
Coaching apps and step goals
Apps that already store mass and stride call a stable prepaid endpoint to show how a ten-thousand-step target translates into energy for each athlete.
Classroom ACSM homework
Courses recover distance from steps times stride, derive minutes at 80 metres per minute, and pin expected JSON for the VO2 times mass times time identity.
Technical questions
What does the steps to calories calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.