CM height conversion
180 cm is 5 feet and about 10.87 inches. Enter a height in centimetres and get it the way US and UK forms ask for it, whole feet plus leftover inches, using the exact 2.54 cm inch. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Cm
- 180
- Result
- 5 ft 10.866141732283 in
- Feet
- 5
- Inches
- 10.8661417323
- Total inches
- 70.8661417323
Converting a height given in centimeters into feet and remaining inches is the everyday request behind school forms, visa applications, sports profiles, clothing size charts, and clinic records when a metric measurement must be spoken in imperial height notation. This CM height conversion calculator takes a single finite nonnegative height in centimeters and splits it into whole feet plus the leftover inches using the exact international definitions: one inch equals 2.54 centimeters and one foot equals twelve inches.
How centimeters become whole feet and leftover inches
A height stated in centimeters is a single metric length. Imperial height, as used on United States and United Kingdom forms, is not a single number: it is a mixed pair of whole feet plus leftover inches that do not fill another foot. The conversion is therefore two exact constants followed by an integer split, not an approximate lookup table.
One inch is defined as 2.54 centimeters exactly by the 1959 international yard and pound agreement; one foot is twelve inches, so one foot is 30.48 centimeters exactly. Divide the given height by 2.54 to obtain total inches, take the integer number of complete twelve-inch groups as feet, and keep the remainder as inches. For a typical adult height of 180 centimeters, 180 divided by 2.54 is about 70.866 inches, which is five complete feet and about 10.866 leftover inches.
A height of 182.88 centimeters is exactly six feet with zero leftover inches, because six times 30.48 equals 182.88. Zero centimeters converts to zero feet and zero inches. This capability never uses survey-foot variants, never rounds to the nearest half-inch as a hidden default, and never invents a second unit.
The same identities appear in the formula field so a student or a user interface can reprint the working next to the answer without reconstructing the arithmetic.
Where CM height conversion earns its keep, and what it costs
Clinics, school nurses, and occupational-health forms collect stature in centimeters from a stadiometer and must print the imperial pair that parents, insurers, and visa officers still expect. Sports rosters, dating profiles, clothing size charts, and furniture listings convert a metric height so an international audience can read five-foot-ten instead of 178 centimeters. Product catalogs for door frames, bunk beds, and safety rails use the same split when a specification sheet is metric but the shopper thinks in feet and inches.
Keep this landing focused on the search intent cm height conversion—centimeters in, mixed imperial height out—and use a dedicated reverse or a generic length converter when the pipeline needs the opposite direction or a unit that is not a human-height split. Source inputs follow the same retention rules as other KIT parse items; nothing is stored after the task completes.
What you can do with it
School, visa, and clinic height forms
Convert a stadiometer reading in centimeters into the feet-and-inches pair that paper forms, visa applications, and growth charts still print for families and officers.
Sports rosters and clothing size charts
Turn metric athlete or customer heights into a readable five-foot-ten style label for international rosters, dating profiles, and apparel size guides.
Product specs for doors, beds, and rails
Split a metric clearance or stature figure into whole feet plus leftover inches so shoppers who think in imperial units can compare a specification at a glance.
FAQ
What happens if the height is negative or not a number?
Height must be a finite nonnegative number; missing, empty, NaN, Infinity, and non-numeric strings are rejected and are not billed.
Why return leftover inches instead of only total inches?
Search intent for cm height conversion is the mixed imperial pair people write on forms (for example 5 ft 10.87 in), not a single inch count.
Is the 2.54 factor exact?
Yes. One inch equals 2.54 centimeters exactly under the 1959 international yard and pound agreement, so one foot equals 30.48 centimeters exactly. No survey-foot or approximate 2.5 shortcut is used.
What height in centimetres is exactly six feet?
182.88 cm, because one foot is exactly 30.48 cm and six times that is 182.88. Entering it returns 6 feet and 0 inches, a handy check that the conversion is exact.
Does it round the inches to the nearest half inch?
No. The leftover inches are shown with their decimals and are never quietly rounded to a half or a whole inch. If a form asks for whole inches, round the figure yourself as that form requires.
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/conv/cm-height-conversion \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"cm":180}'const res = await fetch("https://api.kit.forhosting.com/conv/cm-height-conversion", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"cm": 180
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/cm-height-conversion",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"cm": 180
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/cm-height-conversion", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"cm":180}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"cm":180}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/cm-height-conversion", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"cm": 180
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.cm_height_conversion",
"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_cm | 1000000000000 |
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
Invalid, missing, negative, or non-finite input fails with invalid_input and is not billed. Successful API calls cost $0.002 per item.
How centimeters become whole feet and leftover inches
Leftover inches are rounded to twelve decimal places only so JSON goldens stay stable across runtimes; if that rounding would land on twelve, the extra foot is carried so the remainder stays in the half-open interval from zero inclusive to twelve exclusive.
Input contract, response fields, and error behaviour
Zero is a valid height and returns zero feet and zero inches. The formatted field writes the mixed unit as N ft M in, display writes the common prime notation, and result repeats formatted for callers that look for a single primary string. Formula restates feet equals floor of (cm divided by 2.54) divided by 12, with leftover inches as the modulo. A short message and a steps array walk through input, definitions, the total-inch division, and the split, which tutoring software can show verbatim. POST a JSON body with the required field cm, a finite nonnegative number or a plain numeric string. Aliases height, centimeters, centimetres, value, and height_cm are accepted so forms, spreadsheets, and SDKs can use the name that already exists in the source record. Negative values, NaN, Infinity, empty strings, and non-numeric text fail with invalid_input naming the field, and those failures are not billed. Magnitudes above one trillion centimeters are rejected so Worker isolates stay safe. On success the body echoes the parsed cm value, returns feet as a whole number, inches as the leftover remainder, and total_inches as the undivided inch length. Constants cm_per_inch 2.54 and cm_per_foot 30.48 travel with the payload so a client can cache the identities. Pair the numbers with your own rounding for a tape-measure card if you need half-inch display; this endpoint keeps twelve-decimal leftovers so automation can round last, not first.
Where CM height conversion earns its keep, and what it costs
Successful API calls bill as one item at $0.002; invalid_input is free, so you can validate a form field without burning balance.
Technical questions
How do I convert a height in centimeters to feet and inches?
Send a finite nonnegative number in the cm field (aliases height, centimeters, centimetres, value, height_cm). The API divides by 2.54 to get total inches, takes whole feet as floor of that total divided by 12, and returns the leftover inches.
What does the CM height conversion calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.