Standing desk height calculator
At 175 cm tall and typing, set the desk surface to 107.8 cm and the monitor centre to 155.75 cm, with the top of the screen at eye level, 163.8 cm. No more guessing at a chest-high mark. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Height
- 175
- Posture
- Typing
- Elbow height
- 110.25
- Eye height
- 163.8
- Desk height
- 107.8
- Monitor height
- 155.75
This standing desk height calculator turns a person's standing stature and a typing or viewing posture into the recommended desk surface height and monitor height for a sit-stand workstation. Office fitters, remote workers, and occupational-health students use it so a new standing desk is set to elbow height instead of a guessed chest-high mark that leaves the wrists cocked or the neck craned. The engine applies published standing anthropometric ratios: elbow height is 0.630 of stature, eye height is 0.936 of stature, the typing desk sits at 0.616 of stature so a keyboard deck keeps the wrists near neutral, the viewing desk sits at 0.659 of stature so reading material is closer to the visual line, and the monitor centre sits at 0.890 of stature so the top of a typical display is near eye level.
What your desk and monitor marks mean
A standing-desk-height result is the pair of vertical marks you need when a sit-stand workstation is set for a specific person: how high the work surface should sit, and how high the monitor centre and the top of the screen should sit, given that person's standing stature and whether they will type or only view.
It is not a furniture shopping list, and it is not a full anthropometric survey: it is the closed-form application of published standing body proportions so a facilities technician or a remote worker can set the desk without guessing. Zero centimetres is not treated as a valid empty person here, because a zero tape reading is almost always a missing measurement rather than a planned stature.
If you need a sitting-desk elbow chart, a viewing-distance converter, or a chair-to-desk clearance planner, use a dedicated helper; this page is the standing-desk-height ergonomics landing.
Where standing-desk-height planning fits in workplaces, teaching, and software
People meet standing-desk-height math when a new sit-stand frame arrives and nobody can say whether the keypad should sit at belt height or at the solar plexus, when a shared hot-desk floor must be preset for a known roster of statures, or when a teacher wants an anthropometry word problem that is not another body-mass index drill.
Facilities teams can pre-check a one-hundred-and-seventy-five centimetre colleague at typing posture before they treat a new frame as a sunk cost, and occupational-health tutors can compare a typing mark against a viewing mark without opaque spreadsheet macros. Contest and homework practice often needs a fast, offline source of workstation marks so solutions can be checked without a tape and a live volunteer under time pressure.
Product and education tools use the split when a learner types a stature and the interface must show a clean desk and monitor pair beside the echoed elbow and eye landmarks. Pair it with a viewing-distance or chair-clearance helper when you are assembling a small lab of free, deterministic workstation-planning tools, and keep this page for the standing-desk-height search itself.
What you can do with it
Set a new sit-stand desk for one person
Turn a measured standing stature and a typing or viewing task into desk height and monitor height before the first workday at the new frame.
Homework and occupational-health worksheets
Generate a reproducible workstation from stature and posture, including the elbow landmark, the eye landmark, and the monitor-top mark.
FAQ
What does the standing desk height calculator cost?
It is free in your browser on this page.
How are desk height and monitor height defined?
Each numeric field is rounded to ten decimal places.
What happens if height is zero or negative?
A missing, non-finite, or out-of-range stature is rejected the same way.
What is the difference between typing and viewing posture?
Typing places the desk slightly below standing elbow height so a keyboard deck keeps the wrists near neutral. Viewing raises the desk slightly above the elbow so a book, tablet, or presentation sits closer to the visual line. Monitor centre uses the same 0.890 ratio in both postures.
Does this convert centimetres to inches or plan a sitting desk?
Sitting-desk elbow charts, viewing distance, and manufacturer stroke limits are out of scope.
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/life/standing-desk-height \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"height":175,"posture":"typing"}'const res = await fetch("https://api.kit.forhosting.com/life/standing-desk-height", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"height": 175,
"posture": "typing"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/life/standing-desk-height",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"height": 175,
"posture": "typing"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/life/standing-desk-height", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"height":175,"posture":"typing"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"height":175,"posture":"typing"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/life/standing-desk-height", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"height": 175,
"posture": "typing"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "life.standing_desk_height",
"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_abs_value | 1000000000000000 |
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
Height must be a positive finite number — zero or a negative tape reading is rejected as invalid_input so a missing measurement is not treated as a valid workstation. Run it free in the browser for a one-off setup, or call the API at $0.002 per successful request when a facilities sheet, classroom demo, or furniture script needs the same figure.
What a standing-desk-height result means and what the response contains
This calculator answers that with four ratios. elbow_height is stature times 0.630, the standing elbow landmark from Pheasant-style proportion tables. eye_height is stature times 0.936, the standing eye landmark from the same family of sources. desk_height is stature times 0.616 when posture is typing, which places the keyboard surface slightly below the elbow so a typical keyboard deck keeps the wrists near neutral, or stature times 0.659 when posture is viewing, which raises the surface so a book, tablet, or presentation deck sits closer to the visual line. monitor_height is stature times 0.890, the recommended centre of the display; monitor_top_height equals eye_height so the top of a typical screen sits at or just below the eyes. The response echoes the two normalized inputs, returns those derived fields, and includes a method tag pheasant_standing_proportions plus a formula string so a spreadsheet or a test can repeat the same steps without guessing. There is no hidden chair offset, no dual sit-and-stand pair, and no manufacturer-specific stroke limit: the engine either multiplies a positive finite stature by the posture ratios or it rejects the input with invalid_input. Rejected cases include a missing height or posture field, a non-finite value, a magnitude above the documented ceiling, a posture that is not typing or viewing, and — this is the product contract — a height that is not a positive number.
How height and posture are read so results stay reproducible
Optional leading plus signs and scientific notation on the numeric height string are allowed when they parse as finite decimals; embedded spaces, hex prefixes, and non-numeric tokens are rejected with a message that names the field so a bad cell does not become a wrong desk mark. Both the desk and the monitor heights share one length unit with the stature you typed: centimetres, inches, or metres, as long as you do not mix them. A one-hundred-and-seventy-five centimetre person at typing posture yields a desk of one hundred and seven point eight and a monitor centre of one hundred and fifty-five point seven five in the same centimetres; a seventy-inch person at viewing posture yields the same ratios in inches. Computation uses ordinary floating-point multiplication, then rounds each numeric field to ten decimal places so goldens stay stable across runtimes. The preferred field for stature is height, but aliases stature, user_height, h, and height_cm are accepted so a form, a query string, or a spreadsheet column can reuse the same contract without renaming cells. Posture prefers posture, with aliases mode, use, task, and work; the closed domain is typing or viewing, and those two words are what the response echoes even if a synonym arrived. Height must be strictly greater than zero: that is the product contract, and a missing, zero, or negative tape reading is invalid_input. Posture must resolve to typing or viewing; an empty string or an unknown token such as sitting is invalid_input because this page is the standing workstation, not a seated elbow chart. Pair the free browser run on this page with the priced API when you need that identical mathematical result inside an automated facilities or inventory pipeline without re-implementing the proportion table yourself.
Where standing-desk-height planning fits in workplaces, teaching, and software
Developers call the same contract from scripts to seed deterministic test vectors for ergonomics calculators, to normalize user-entered stature before a furniture demo, or to satisfy a product statement that demands desk_height and monitor_height fields rather than a hand-waved “raise it until it feels right.” 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 tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result.
Integration use cases
Facilities tools and test fixtures
Normalize stature and posture into stable desk_height and monitor_height fields for product interfaces and continuous-integration assertions.