Calories burned standing calculator
70 kg standing quietly for 60 minutes burns 91 kcal: body weight times hours times 1.3, the published value for quiet standing, already built in. Use it for a standing desk, a queue or a sideline. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Weight
- 70
- Duration
- 60
- Calories burned
- 91 kcal
- Calories kcal
- 91
- Weight (kg)
- 70
- Duration minutes
- 60
Quiet standing still costs energy: postural muscles hold you upright, so the clock on a standing desk, a queue, or a sideline is not a free rest period. This standing calorie calculator estimates kilocalories from two numbers you already have — body weight in kilograms and how long you stood — using the Compendium of Physical Activities MET for standing quietly (1.3) and the standard identity kilocalories equals MET times kilograms times hours. You do not supply a MET; it is baked in so the search “calories burned standing” has a one-step answer.
What calories burned standing measures and how the formula works
Standing is not sitting and it is not walking. Quiet standing raises energy cost above seated rest because postural muscles hold the trunk and legs against gravity, but it remains a light activity. The 2011 Compendium of Physical Activities codes standing quietly as 1.3 metabolic equivalents (METs), versus about 1.0 to 1.3 for sitting and 3 to 4 for a typical walk.
One MET is the approximate oxygen cost of quiet sitting; multiplying 1.3 by body mass in kilograms and by time in hours yields kilocalories for the standing bout. Algebraically that is the same as 1.3 times weight times minutes divided by sixty. Example: seventy kilograms standing for sixty minutes is 1.3 times seventy times one, which is ninety-one kilocalories.
An eight-hour workday of quiet standing at ninety kilograms is 1.3 times ninety times eight, which is nine hundred thirty-six kilocalories. The result is an estimate from a published MET table, not chamber calorimetry, and it is not a fat-loss guarantee. Diet, non-exercise activity, and the rest of the day still dominate total expenditure.
Where a standing calorie calculator earns its keep
Occupational-health and ergonomics teams compare sitting days with standing-desk days when they need a transparent energy number rather than a wearable black box. Teachers and sports-science labs assign homework that multiplies the quiet-standing MET by mass and time so students see why eight hours on your feet is not the same as eight hours of walking, and not the same as eight hours in a chair.
Coaches who keep athletes standing on the sideline for long matches want a bout cost they can add to the session log without inventing a MET. Nutrition coaches combining food logs with non-exercise activity want a documented 1.3 MET rather than an opaque AI guess that drifts between model versions. Failed validation does not consume balance.
Keep weight in kilograms and duration in minutes for the same standing bout — do not mix a weekly total of hours with a daily weigh-in from another week — and you get a reproducible kilocalorie figure for dashboards, LMS quizzes, and edge workers without standing up a metabolic cart of your own. Treat walking, running, cycling, swimming, fidgeting, and basal metabolic rate as separate product intents rather than overloading this standing calculator with every related sports formula.
What you can do with it
Standing-desk workday logs
Turn body weight and hours at a standing desk into a kilocalorie estimate for an occupational or wellness log without asking the user for a MET table.
Classroom MET homework
Let students check quiet-standing energy cost from mass and minutes against the Compendium 1.3 MET identity, with a hard error on non-positive inputs.
FAQ
How do you estimate calories burned while standing?
Send positive body weight in kilograms and standing duration in minutes.
What MET value does the standing calorie calculator use?
It uses 1.3, the Compendium of Physical Activities value for standing quietly (code 07040). You do not pass a MET; fidgeting and standing-desk light work are different activities.
What happens if weight or duration is zero or negative?
A calorie estimate requires a positive mass and a positive interval; those failures are not billed.
Is duration in minutes or hours?
Duration is in minutes. Sixty minutes is one hour. An eight-hour workday is 480 minutes.
How many calories does a standing workday burn?
At 90 kg, eight hours of quiet standing is 1.3 × 90 × 8, or 936 kcal. Fidgeting, reaching and sorting at a standing desk or pacing between stations are different activities and are not included.
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/calories-burned-standing \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"weight":70,"duration":60}'const res = await fetch("https://api.kit.forhosting.com/sports/calories-burned-standing", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"weight": 70,
"duration": 60
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/sports/calories-burned-standing",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"weight": 70,
"duration": 60
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/sports/calories-burned-standing", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"weight":70,"duration":60}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"weight":70,"duration":60}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/sports/calories-burned-standing", 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,
"duration": 60
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "sports.calories_burned_standing",
"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_kg | 500 |
max_duration_minutes | 10080 |
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 weight or duration is rejected as invalid_input rather than a silent zero that would look like rest.
What calories burned standing measures and how the formula works
The hourly rate is simply 1.3 times weight: seventy kilograms burns ninety-one kilocalories per hour while standing quietly. This calculator does not model fidgeting (often near 1.8 MET), standing-desk work with reaching and sorting, or pacing between stations. Those are different activities with different search intent. It answers the query people type as calories burned standing: given weight and how long you stood still, how many kilocalories did that bout cost. Identical weight and duration always produce identical JSON because the arithmetic is pure and has no clock, no random seed, and no model drift.
Input contract, response shape, and error behaviour
Weight and duration must be strictly positive: zero or negative values are rejected because a calorie estimate cannot be built from a non-physical mass or a non-physical interval, and those failures are not billed. Weight above five hundred kilograms and duration above ten thousand eighty minutes (seven days) are rejected as out of range so a typo cannot produce an absurd total. Wire the free browser form for a personal log or a classroom demo, then call the identical contract from scripts when you need bulk standing-desk estimates. If you need a generic MET times weight times time tool, that is a different landing; if you need walking or running calories, those formulas use speed or distance and do not belong on this standing page. POST a JSON body with two required finite numbers: weight, body mass in kilograms, and duration, standing time in minutes. Each field may arrive as a JSON number or as a numeric string. Aliases weight_kg, kg, mass, and body_weight are accepted for mass; aliases duration_min, duration_minutes, minutes, time, and mins are accepted for the clock. 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 weight_kg, duration_minutes and duration_hours, the fixed met of 1.3, kcal_per_hour as 1.3 times weight, plus a formula string documenting kcal = 1.3 × weight_kg × (duration_minutes / 60) and method compendium_standing_quietly. 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
Sideline and queue bout estimates
Add standing time on a sideline, in a queue, or at a station to a session energy ledger using the same formula the browser widget shows.
Technical questions
What does the calories burned standing calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.