Running calorie calculator
Running 10 km at 70 kg on flat ground burns about 700 kcal net, roughly 1 kcal per kilo per kilometre. Add an average uphill or downhill grade and the estimate adjusts. No pace or finish time needed. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Distance
- 10 km
- Weight
- 70
- Weight unit
- kg
- Grade
- 0
- Weight (kg)
- 70 km
- Grade fraction
- 0
- Distance m
- 10,000
- Distance km
- 10
A running calorie calculator turns how far you ran, how much you weigh, and the average hilliness of the course into a clear net energy cost in kilocalories. Enter distance in kilometres, miles, or metres, body weight in kilograms or pounds, and an optional percent grade for uphill or downhill terrain; the tool applies the ACSM distance-based running oxygen-cost model, converts everything to SI units, and returns total net calories, calories per kilometre and per mile, oxygen cost per kilogram, dual-unit distances, and step-by-step arithmetic you can audit.
What running calories mean and how they are estimated
Net calories burned while running are the extra energy your body spends moving over the ground beyond quiet rest. Exercise physiologists often express that cost through oxygen uptake: roughly five kilocalories of mixed fuel per litre of oxygen consumed.
The American College of Sports Medicine running equation gives a practical distance form of that cost that does not require you to know pace: horizontal work costs about zero point two millilitres of oxygen per kilogram of body mass per metre travelled, and vertical work against a grade adds about zero point nine millilitres per kilogram per metre of distance times the grade as a decimal fraction. Multiplying the summed oxygen volume by body mass in kilograms and by five kilocalories per litre yields net kilocalories for the bout.
On flat ground that model collapses to about one kilocalorie per kilogram per kilometre, which matches the familiar coach rule of thumb many runners already use. A positive grade percent increases cost; a negative grade reduces it, and this implementation floors the oxygen term at zero so an extreme downhill model cannot invent negative fuel burn. The estimate is net of resting metabolism over time, so it is not a full daily energy expenditure figure and should not replace clinical metabolic testing.
Teachers, coaches, and app authors still value a transparent closed-form number they can recompute by hand and assert in tests without GPS files or heart-rate straps.
Practical tips, limits, and related searches
Prefer average grade for the whole segment when you only have one number: if a hilly ten-kilometre route climbs and descends the same net elevation, a near-zero average grade is often more honest than the steepest climb alone. Keep distance and weight strictly positive—zero distance would claim a free run, and zero weight is not a valid body mass.
Steep grades near the published plus or minus one hundred percent bounds are mathematical edge cases for trail or treadmill experiments, not everyday road races; stay near zero to ten percent for typical coaching scenarios. This landing targets people searching for a running calorie calculator, calories burned running by distance and weight, or grade-adjusted running energy cost; it is not a heart-rate calorie estimator, not a GPS file parser, and not a full TDEE planner.
Prefer this capability when you already know distance, body mass, and an average slope and only need a deterministic net kilocalorie figure; if your source is a FIT or GPX file, extract those scalars first. Round-trip checks are easy: for seventy kilograms over ten flat kilometres you should see about seven hundred net kilocalories from the one kilocalorie per kilogram per kilometre horizontal term, and a five percent average grade should raise that total in the documented proportion.
What you can do with it
Race fueling and gel planning
Coaches enter goal distance, athlete body weight, and course grade to estimate net calorie demand and size on-course carbohydrate.
Training log energy columns
Apps store distance and body mass from any unit system, then call this tool once to fill net kcal and kcal-per-km fields for charts.
FAQ
How are running calories calculated?
This tool uses the ACSM distance-based running oxygen-cost model: VO2 in mL/kg equals 0.2 times distance in metres plus 0.9 times distance times grade fraction, then kilocalories equal (VO2/1000) times body weight in kg times 5.
Do I need pace or finish time?
No. The net oxygen cost of running over a known distance is largely independent of speed in the ACSM horizontal and grade terms, so distance, weight, and grade are enough.
What happens if distance or weight is zero or negative?
Both distance and body weight must be finite and strictly positive.
Is grade required?
No. Grade defaults to 0 (flat). Enter a percent slope when you want uphill or downhill adjustment; negative values mean downhill.
Is the running calorie calculator free?
The browser tool is free and runs locally.
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/running-calories \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"distance":10,"weight":70}'const res = await fetch("https://api.kit.forhosting.com/health/running-calories", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"distance": 10,
"weight": 70
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/running-calories",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"distance": 10,
"weight": 70
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/running-calories", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"distance":10,"weight":70}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"distance":10,"weight":70}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/running-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
{
"distance": 10,
"weight": 70
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.running_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_distance | 1000000 |
max_weight_kg | 500 |
max_grade_percent | 100 |
min_grade_percent | -100 |
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
Non-positive distance or body weight is rejected with a clear invalid_input error so bad form data never looks like a zero-effort run.
How to call the API and what comes back
Send a JSON body with two required finite positive numbers: distance (aliases dist, d, length) and weight (aliases body_weight, bodyWeight, mass, kg, w). Optionally set unit (aliases distance_unit, distanceUnit, from) to km, mi, or m; when omitted the distance is interpreted in kilometres. Optionally set weight_unit (aliases weightUnit, mass_unit, massUnit) to kg or lb; when omitted weight is kilograms. Optionally set grade (aliases grade_percent, gradePercent, incline, slope) as a percent slope between minus one hundred and one hundred; default zero means flat. Distance must stay within one million units of the chosen system and converted body mass within five hundred kilograms so intermediate products remain finite on the Worker and in the browser. On success the response echoes rounded distance, unit, weight, weight_unit, and grade; publishes weight_kg, grade_fraction, distance_m, distance_km, and distance_mi; returns vo2_ml_per_kg, calories, calories_per_km, and calories_per_mi; and includes formula, message, and an ordered steps array showing unit conversion and the ACSM substitution. Failed validation—missing fields, non-finite numbers, non-positive distance or weight, unknown units, or values outside published limits—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.
Practical tips, limits, and related searches
Convert body weight carefully when athletes report pounds; this tool accepts lb and converts with the exact avoirdupois factor so API clients do not need a separate unit library. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send a zero weight to test client validation.
Integration use cases
Unit tests for fitness calculators
Generate known-good flat and graded fixtures plus deliberate non-positive distance or weight rejections for golden expected values.